# Perform Local Language to English Intake

Safety supports dual language intake for entering cases that are received in a non-English language but require reporting in English. This article covers this intake scenario only. For localized (non-English) submissions, see <a href="/en/gr/01290/">Prepare a Localized Case</a>. When you promote an _Inbox Item_ with local data to a _Case_, Vault generates a <a href="/en/gr/01168/">_Case_ in the local language</a> and maps the relevant field values to the _Cases_. For example, the EMA requires ICSR submissions in English. If an adverse event that occurred in Germany is reported in German. Intake users can enter data in the source language (German) while entering the corresponding English translations in the text fields on the _Inbox Item_. Upon promotion, Vault maps the data to create a global _Case_ which can be used for English submissions.


<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: When processing Cases that may be reportable to the PMDA, see <a href="/en/gr/696910/">Complete Intake and Process Cases for the PMDA</a> for regionally specific features in Veeva Safety.</p>
    </div>
  </div>
</div>



## Prerequisites

Your Admin must <a href="/en/gr/01357/">enable local language to English intake</a> and, if applicable, <a href="/en/gr/01306/">enable the auto-translation framework</a>.

## Send Translation Requests Through the Auto-Translation Framework {#auto-translations}

If your Admin has configured the Auto-Translation Framework, after <a href="/en/gr/01133/">manually creating</a> or <a href="/en/gr/01135/#local-inbox-item-import">importing</a> a local _Inbox Item_, you can send all localized text fields to Amazon Translate for translation to English. Although _Inbox Items_ do not display all imported _Case_ fields, all localized text fields with values are sent for translation, unless excluded by your Admin's configuration. For manually created _Inbox Items_, Vault only sends [supported fields][1] for translation. You can review returned translations on the _Inbox Item_ or after _Case_ promotion.

You can manually send a translation request by navigating to the _Inbox Item_ and selecting the **Translate Inbox Item** action from the **All Actions** menu, which moves the record to the _Translation Requested_ state. Upon receiving a third-party translation, Vault automatically imports and applies the translation, then moves the _Inbox Item_ to the _Translation Verification_ state. Vault does not verify the quality of the translation.

### Considerations for Translation Requests

* If you modify _Inbox Items_ in the _Translation Requested_ state, Vault updates those values upon receiving translations.
* If the length of the translated text exceeds the character limit of any text field, Vault truncates the text to that field's maximum length and displays a notification message indicating which fields are truncated.
* The translation must be returned within 60 minutes or the task expires. Vault displays a notification message for failed translation requests.

### Translation Notifications

Depending on your Admin's configuration, Vault may send translation notification messages in the following scenarios:

* When a translation error occurs, Vault notifies the user who sent the _Inbox Item_ for translation and moves the _Inbox Item_ to the _Translation Error_ state. A translation error can occur if the translation is not returned to Vault within 60 minutes or if the translation service goes offline during the translation.
* When a translation is complete and pending verification, Vault notifies the user who sent the _Inbox Item_ for translation.


<!--HIDDEN CONTENT. Hiding because new functionality has sped up translations considerably, so there is no time to cancel a request before it is processed. Unhide if this is made available again in the future.
### Cancel a Translation Request

When an Inbox Item is in the **Translation Requested** state, you can cancel the request.

Select the **All Actions** menu, and then select **Cancel Translation Request**.

Your Inbox Item returns to the **Active** state and no translations are applied. If needed, you can send another translation request.-->

## Display Localized Field Labels

You can view fields in Vault in your preferred language by selecting a language from your User Profile. When you change this setting, all field labels and picklist values in Vault will display in the selected language. The **Default Localization** field determines the language in Object Reference fields, such as Report Type.

<a href="https://platform.veevavault.help/assets/images/saf-default-localization-field.png" data-lightbox="saf-default-localization-field.png" data-title="" data-alt="The Default Localization and Language Fields on the User Profile">
  <img class="docimage" src="https://platform.veevavault.help/assets/images/saf-default-localization-field.png" alt="The Default Localization and Language Fields on the User Profile" style=""  />
</a>

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: If the <strong>Default Localization</strong> field is blank, Vault automatically refers to the <strong>Language</strong> field to determine the language for the picklist field values.</p>
    </div>
  </div>
</div>



Configuring the above settings allows you to perform localized manual intake with _Inbox Items_.  

## Show Dual Entry Fields 

When an _Inbox Item_ has a a non-global _Localization_, you can perform local language to English translation. To include local intake fields, update the **Localization** field of the <a href="/en/gr/01285/">_Inbox Item_</a> to specify the language in which the adverse event was reported. For _Localizations_ with a <a href="/en/gr/01194/#local-scope">_Localization Scope_</a> limited to _Narratives_ or _Company Comments_, dual-entry fields appear only after you promote an _Inbox Item_ to a _Case_.

## Local Intake Fields with English Translations

The following sections provide more information about how Vault translates <a href="/en/gr/01285/">_Inbox Item_ fields</a> during intake:

* [Text Fields][2]
* [Picklist and Object Fields][3]
* [Adverse Events][4]

### <a id="translate-text-fields"></a>Translate Text Fields

You can manually translate text fields during intake. For each text field that supports dual language intake, there are two fields:

1. In the first field, enter the information in the language in which the adverse event was reported.
2. In the English (<img class="inline" src="https://platform.veevavault.help/assets/images/saf-dual-language-local-intake-english-field-label.png" alt="English label" style=" width: 60px;" />) field, enter the English translation.

<a href="https://platform.veevavault.help/assets/images/saf-dual-language-local-intake-reporters-comments-german-english.png" data-lightbox="saf-dual-language-local-intake-reporters-comments-german-english.png" data-title="Dual Language Entry Text Field" data-alt="Dual Language Entry Text Field">
  <img class="docimage" src="https://platform.veevavault.help/assets/images/saf-dual-language-local-intake-reporters-comments-german-english.png" alt="Dual Language Entry Text Field" style=""  />
</a>

#### <a id="text-field-mapping"></a>Text Field Mapping and Translation on Case Promotion

On _Case_ promotion, only the English (<img class="inline" src="https://platform.veevavault.help/assets/images/saf-dual-language-local-intake-english-field-label.png" alt="English label" style=" width: 60px;" />) field translations map to the global _Case_. Vault does not copy field values in the local language to the global _Case_.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: Auto-Translation Framework does not support narrative or document translation.</p>
    </div>
  </div>
</div>



##### Visible Inbox Item Fields

The following table shows _Inbox Item_ fields that are available for translation and describes how Vault maps text fields with local and English values on _Case_ promotion:

<table>
    <thead>
        <tr>
            <th colspan="2">Inbox Item</th>
            <th colspan="2">Case</th>
        </tr>
        <tr>
            <th>Section</th>
            <th>English (<img class="inline" src="https://platform.veevavault.help/assets/images/saf-dual-language-local-intake-english-field-label.png" alt="English" style=" width: 60px;" />) Field</th>
            <th>Object</th>
            <th>Field</th>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>Awareness Details</td>
            <td>Reporter's Comments</td>
            <td>Case (Narrative)</td>
            <td>Reporters Comments</td>
        </tr>
        <tr>
            <td>Contacts</td>
            <td>Additional Information</td>
            <td>Details</td>
            <td>Additional Information</td>
        </tr>
        <tr>
            <td>Contacts</td>
            <td>Organization</td>
            <td>Details</td>
            <td>Organization</td>
        </tr>
        <tr>
            <td>Contacts</td>
            <td>Department</td>
            <td>Details</td>
            <td>Department</td>
        </tr>
        <tr>
            <td>Contacts</td>
            <td>State/Province</td>
            <td>Address</td>
            <td>State/Province</td>
        </tr>
        <tr>
            <td>Product</td>
            <td>Product (Reported)</td>
            <td>Case Product</td>
            <td>Product (Reported)</td>
        </tr>
        <tr>
            <td>Product</td>
            <td>Indication (Reported)</td>
            <td>Case Product</td>
            <td>Indication</td>
        </tr>
        <tr>
            <td>Product > Dosage</td>
            <td>Dose Form (Custom)*</td>
            <td>Case Product Dosage</td>
            <td>Dose Form</td>
        </tr>
        <tr>
            <td>Product > Dosage</td>
            <td>Patient RoA (Custom)*</td>
            <td>Case Product Dosage</td>
            <td>Patient RoA</td>
        </tr>
        <tr>
            <td>Product > Dosage</td>
            <td>Dose Text</td>
            <td>Case Product Dosage</td>
            <td>Dose Text</td>
        </tr>
        <tr>
            <td>Product History</td>
            <td>Drug (Reported)</td>
            <td>Drug History</td>
            <td>Drug (Reported)</td>
        </tr>
        <tr>
            <td>Events</td>
            <td>Event (Reported)</td>
            <td>Adverse Event</td>
            <td>Event (Reported)</td>
        </tr>
    </tbody>
    <tfoot>
        <tr>
            <td colspan="4">*Text translations are only available when entering custom Dose Forms or Patient RoAs. Translations for standard system-provided Dose Forms and Patient RoA values are automatically mapped upon Case promotion.</td>
        </tr>
    </tfoot>
</table>

##### Imported Case Text Fields Eligible for Auto-Translation

The following text fields may be included in translation requests. While not all of these fields are displayed or editable on _Inbox Items_, all translated English values copy to the _Case_ after promotion.

* _Case_ fields:
  * _Medical History Text_
  * _Reporter's Comments_
  * _Company Comments_
  * _CIOMS Remarks_
  * _Reporting Summary_
  * _Study Name_
  * _Study Name (continued)_
* _Case Adverse Event_ fields:
  * _Event (Reported)_
* _Case Assessment Result_ fields:
  * _Method (Text)_
  * _Result (Text)_
  * _Source (Text)_
* _Case Cause of Death_ fields:
  * _Name (Reported)_
* _Case Contact_ fields:
  * _City_
  * _Department_
  * _Facility_
  * _First Name_
  * _Last Name_
  * _Middle Name_
  * _Organization_
  * _State / Province_
  * _Street_
  * _Street Line 2_
  * _Title_
* _Case Drug History_ fields: 
  * _Drug (Reported)_
  * _Drug (Coded)_
* _Case Identifier_ fields:
  * _Source_ (not available for translation when imported through E2B)
* _Case Medical History_ fields:
  * _Condition / Procedure (Reported)_
  * _Comments_
* _Case Product_ fields:
  * _Other Additional Information_
  * _Product (Reported)_
* _Case Product Dosage_ fields:
  * _Dose Text_
  * _Dose (Unit Text)_
  * _Parent RoA Text_
  * _Patient RoA Text_
* _Case Product Indication_ fields:
  * _Name (Reported)_
* _Case Product Substance_ fields:
  * _Name_
* _Case Case Test Result_ fields:
  * _Comments_
  * _Result (Text)_
  * _Test Name (Reported)_

### <a id="picklist-and-object-field-translations"></a>Picklist and Object Field Translations

Any standard and system-managed picklists and object lookup fields are shown in the value selected in the _Default Localization_ field on your <a href="/en/gr/7239/">user profile</a>. Vault does not automatically translate custom picklists and object records: 

* _Controlled Vocabularies_
* _Route of Administrations_
* _Dose Forms_
* _Units of Measurement_
* _Reasons Omitted_

### <a id="event-meddra-translations"></a>Event MedDRA Translations

The _Event_ field on _Adverse Events_ includes MedDRA details that may automatically translate <a href="/en/gr/01164/">coded MedDRA terms</a> in the applicable language.

[1]: #text-field-mapping
[2]: #translate-text-fields
[3]: #picklist-and-object-field-translations
[4]: #event-meddra-translations