The supported product locales are English (en-US) and Japanese (ja-JP). This locale is set during installation.
The following locales are defined by an administrator after the installation is complete:
Note: Studies can still be versioned based on protocol changes, even though each study version may have multiple languages.
How locales are applied in the InForm user interface
User interface page(s) | Locale(s) |
---|---|
Administration | The administration pages in the InForm user interface are all based on the default product locale that is defined during the installation (or by using pfadmin commands). The only exception is the Reset Password page, which uses the user's product locale. For the following items, you can use the administration pages to create item names in any locale:
|
Login | Uses the locale that matches the user's browser setting, if available. Otherwise, the page uses the default Product Locale. |
Screening Log | Uses the user's Product Locale. |
CRFs | Day, month, and year ordering is controlled through configuration settings at the study, site, and user levels. The user's Product Locale controls whether months appear as abbreviations or numbers. |
Subject (users) listings | Operational status values such as subject status (Enrolled, Randomized, and so on), form status (Verified, Locked, and so on) and query status (Open, Answered, and so on) display based on the user's Product Locale.
|
Time and Events Schedule page | Presents visit and CRF names in the user's Study Locale. Other text is in the user's Product Locale. |
Source Verification | Displays study elements such as visit and CRF names in the user's Study Locale. This applies to the saved filter dialog box as well. The user's Product Locale is used for all other displayed elements. |
Reg Docs and Visit Reports | For other monitor functions, the Reg Doc and Visit Report forms must be translated to each of the study locales, and they appear in the user's Study Locale. |
Query Listing | Uses the user's Study Locale for displaying study elements. All other page elements are rendered using the user's Product Locale.
|
Queries |
|
Data Value(s) |
|
Audit Trail | Data in the Audit Trail page is in the language that was captured at the time of an event. Following a subject transfer, codelist labels (such as Male/Female) are translated to the language of a receiving site.
|
Online Help | There are two types of online Help:
|
Comment history
|
|
Subject record transfers | When subjects move between sites that have different study locales, the already started CRFs display in the locale of the destination site. The InForm application does not allow subject transfers to sites that are on earlier study versions or which do not have translations for any started CRFs in the study locale of the destination site.
|
Affidavit | The InForm application allows for signature affidavit text to be translated to any Study Locale and displayed to the signer in the language specific to a CRF's Study Locale. The signature print preview functionality is configurable by study. Note: Translating the signature affidavit must be done by editing the MedML, not through the Central Designer application. For more information, see the Utilities Guide. The InForm application supports a paper-based signature process. You have the option to print a copy of the CRF in order to manually sign the CRF or CRB. |
Data Viewer | Uses the same multilingual support as the main InForm application.
|
Documents | The Documents button displays:
|
Copyright © 2014 Oracle and/or its affiliates. All rights reserved. |
---|