Medical Translations
The terminology an MSL uses is not the same as the terminology a Commercial Sales Rep uses. Medical Translations allows users to view specific data fields, objects, and user interface elements in terms specific to their company or organization. This feature supports global pharmaceutical and life sciences teams by ensuring that the CRM content, especially critical terms and objects relevant to healthcare professionals, is accessible and accurate for their business.
Some terms in Vault Medical CRM are pre-translated with industry standard Medical terminology by default. For example, Account is labeled Stakeholder and Call is labeled Interaction. Additional terminology can be customized as needed.
The following items are supported for translation:
- Frequently used objects and fields - Custom fields, object types, and objects. For example, Call and Account, which are critical in tracking interactions with healthcare providers.
- User interface elements - Parts of the Vault CRM interface. For example, labels, section headers, picklist values, and buttons.
- Veeva Messages - Custom text and labels for all configured components, labels and error messages
Who can use this feature?
- iPad, iPhone Users
- Users do not require an additional license
- Business Admin Users
Configuring Medical CRM Translations for
Business Admin Users
To configure this feature:
- Ensure Configuring Medical CRM is complete.
- Ensure the is_medical__v check box is on the appropriate application_label__v object layout.
- Create an Application Label tab:
- Navigate to Admin > Configuration > Tabs
- Select Create
- Select Tab Type > Object
- Select Object > application_label__v
- Select Save
Using Medical CRM Translations as
Business Admin Users
To data load medical translations from the application_label__v object, see Vault Loader.
To add an application label translation:
- Select the Application Label tab.
- Select Create.
- Select the application_label__v type.
- Complete the appropriate fields.
- Select Save.
- Repeat steps 2-5 to create all required application labels.
The following example outlines the labels required for a Call Translation.
|
Application Label |
Label |
Object Type |
Object |
Component |
Field |
Is Medical? |
|---|---|---|---|---|---|---|
|
Call |
Interaction |
object__v |
call2__v |
Label |
n/a |
Yes |
|
Plural for Call |
Interactions |
object__v |
call2__v |
LabelPlural |
n/a |
Yes |
|
Name (and any other simple fields) |
Interaction Record |
custom_field__v |
call2__v |
FieldLabel |
name__v |
Yes |
|
Call Related List in Medical Event |
Event Interactions |
custom_field__v |
call2__v |
RelatedListLabel |
medical_event__v |
Yes |
|
Call Lookup in Medical Inquiry |
Source Interaction |
custom_field__v |
medical_inquiry__v |
FieldLabel |
call2__v |
Yes |
|
Call Notes Layout Section on Call |
Notes |
layoutsection__v |
call2__v |
Call Details |
n/a |
Yes |
Considerations
- If an object is relabeled, the metadata relabeling logic uses that object label for all lookups from other objects to the relabeled object
