Skip to main content

Integrated Language Translation

Medical Information Cloud's integrated language translation feature enables the translation of certain Interaction data and content using a 3rd party translation service. The translation service (also referred to as a vendor) provides a framework for applications such as Medical Information Cloud to translate field values within an Interaction. The vendor performs the translations asynchronously and stores the results within Medical Information Cloud and can be configured to integrate with custom vendors that offer this service.

Note

Mavens recommends clients work with their Mavens representative for licensing options and preferred 3rd party translation service.

Translation types

The integrated translation feature can translate both data and content. Data includes the static text on records while content refers to documents and files. The Setup and configuration section below describes the setup and configuration steps that apply to both translation types while the following pages provide more detailed information and configuration instructions for each one:

Setup and configuration

To use either translation type, you must complete the following setup and configuration steps to enable them:

Add a custom vendor

To enable the integrated translation feature, you must have a custom vendor that provides and performs the content and/or data translation. To implement and add a custom vendor:

  1. Create an Apex class that implements the methods in the Translator Interface (CT_ITranslator).

  2. Create a Translation Vendor (mvn__CT_Vendor__mdt) metadata record.

    1. Set the Translator (mvn__CT_Translator__c) field to the name of the Apex class from step 1 above.

    2. Set the Translator Namespace (mvn__CT_TranslatorNamespace__c) field to the namespace of the Apex class from step 1 above, if applicable.

    3. Check the Enabled (mvn__CT_IsEnabled__c) checkbox (i.e., set to true) to enable the vendor's translations to be used.

    4. Leave the API Endpoint (mvn__CT_Endpoint__c) field blank.

Configure the vendor regions

Vendor regions determine the translation service the translation request is sent to based on the region associated with the content and/or data. To create a Vendor Region (mvn__CT_VendorRegion__c) record:

  1. In the App Launcher, search for and select Vendor Regions.

  2. On the Vendor Regions page, click New.

  3. Complete the following fields:

    Table 158. Vendor Region fields

    Field

    Description

    Values

    Vendor Developer Name

    The name of the vendor that should be used for the region.

    This must match the name of an existing Translation Vendor (mvn__CT_Vendor__mdt) metadata record.

    Region

    The region that encompasses the area that will be serviced by the vendor.

    Select the region to assign the vendor to.

    Priority

    The order in which this region applies.

    Using numerical values, add the priority for the specified vendor region. The lower the number, the higher the priority.

    Is Content Translation Enabled?

    A checkbox that indicates if content translation is enabled for this vendor in this region.

    This box must be checked to enable content associated with the selected region to be translated by the vendor.

    Is Data Translation Enabled?

    A checkbox that indicates if data translation is enabled for this vendor in this region.

    This box must be checked to enable data associated with the selected region to be translated by the vendor.



  4. Click Save.

Warning

A vendor region can be saved without selecting either translation checkbox. However, when neither content translation nor data translation is selected, no translation requests for that region will be sent to the selected translation vendor.

A vendor region can be defined for the same or overlapping regions to customize the translation routing process. Data and content can be routed to separate translation services for the same region by creating different vendor regions for each translation type. Vendor regions can also prioritize different translation services for overlapping areas.

Example vendor regions are shown below:

Table 159. Example vendor regions

Field

Vendor Region A

Vendor Region B

Vendor Developer Name

Custom Vendor

AWS

Region

Mexico

North America

Priority

1

2

Is Data Translation Enabled?

Selected

Selected