Medical CRM Translations

Medical CRM Translations allows users to view specific data fields, objects, and user interface elements in terms specific to their company or organization. The terminology an MSL uses is not the same as the terminology a Commercial Sales Rep uses. Customers can create customized labels which are applied for mobile devices. 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 Medical CRM are pre-translated with industry standard Medical terminology. For example, when Medical CRM is enabled, Account is labeled Stakeholder and Call is labeled Interaction. Additional terminology can be customized as needed.

Who can use this feature?

Configuring Medical CRM Translations for

To configure this feature:

  1. Navigate to Admin > Users & Groups > Permission Sets.
  2. Select the appropriate permission set.
  3. Select the Objects tab.
  4. Grant the following permissions:

    Object

    Object Permission

    Object Types

    Fields

    Field Permission

    application_label__v

    CRED

    • buttonorlink__v
    • customfield__v
    • customlabel__v
    • layoutsection__v
    • object__v
    • picklistvalue__v
    • recordtype__v
    • veevamessage__v

    All fields

    Edit

    user__sys

    E

    user__sys

    custom_application__v

    Edit

  5. Ensure the is_medical__v check box is on the appropriate application_label__v object layout.

  6. Create an Application Label tab:
    • Navigate to Admin > Configuration > Tabs
    • Select Create
    • Select Tab Type > Object
    • Select Object > application_label__v
    • Select Save

To configure this feature:

  1. Navigate to Admin > Users & Groups > Permission Sets.
  2. Select the appropriate permission set.
  3. Select the Objects tab.
  4. Grant the following permissions:

    Object

    Object Permission

    Object Types

    Fields

    Field Permission

    application_label__v

    CRED

    • buttonorlink__v
    • customfield__v
    • customlabel__v
    • layoutsection__v
    • object__v
    • picklistvalue__v
    • recordtype__v
    • veevamessage__v

    All fields

    Edit

    user__sys

    E

    user__sys

    custom_application__v

    Edit

  5. Ensure the is_medical__v check box is on the appropriate application_label__v object layout.

  6. Create an Application Label tab:
    • Navigate to Admin > Configuration > Tabs
    • Select Create
    • Select Tab Type > Object
    • Select Object > application_label__v
    • Select Save
  7. Navigate to Business Admin > Objects: 
    • Select user__sys
    • Select the appropriate user
    • Select Edit
    • Expand the Medical Custom Application section
    • Select Medical as the Custom Application value
    • Select Save
  8. Navigate to Business Admin > Objects: 
    • Select vmobile_object_configuration__v
    • Enable VMOCs for the following objects for the appropriate mobile devices:
      • application_label__v
      • user__sys

Users should perform a full database refresh on mobile devices and users must log out and log back in for the Medical CRM icon to display on a mobile device after configuration is complete.

Using Medical CRM Translations as

To data load medical translations from the application_label__v object, see Vault Loader.

To add an application label translation:

  1. Ensure the language__sys field on each user's record is populated. If a user's language is null or empty, the default labels display instead of the medical translations.
  2. Select the Application Label tab.
  3. Select Create.
  4. Select the application_label__v type.
  5. Complete the appropriate fields.
  6. Select Save.
  7. Repeat steps 3-6 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
  • There can only be one application label translation for a Veeva Message

The following items can be translated in the UI:

  • 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

Related Topics

Medical CRM Overview