Table of Contents
You can build your study forms in any language. Castor CDMS supports UTF-8 and double-byte characters, so you can use any alphabet, for example Cyrillic, Greek, Chinese or Japanese.
The CDMS interface for study teams (menus, buttons and navigation) is always in English. Only the content of your forms (field labels, options, help texts) is in the language you build it in. Castor does not translate your questions automatically.
This article is about study forms. Surveys for participants work differently: the survey interface itself is available in multiple languages. See How to build surveys in multiple languages in CDMS.
First, prepare translated versions of your questions. Then choose one of the methods below to show the right language to each user.
Multilingual forms using dependencies
Use dependencies to show or hide individual fields based on a language field. This works best for short forms.
- At the start of the form, add a field where the user selects the language, for example a radio button field Preferred language with the options English and German.
- Add each question in every language you need, for example Date of birth and Geburtsdatum.
- Add a dependency to each translated field, based on the language field. For example, show Geburtsdatum only if Preferred language is equal to German.
During data entry, only the fields in the selected language are shown. Until a language is selected, only the language field is visible.
Each language adds a full set of fields to the form. With several languages, forms quickly become long and harder to maintain.
Multilingual forms using the Automation Engine
For studies with only a few visits, you can build a separate visit for each language and use the Automation Engine to hide the visits that aren't needed.
In this example, the study has a visit for the language selection and a visit in each language: Patient characteristics EN and Patient characteristics DE.
Create one automation for each language:
- Open the Automation Engine and create a new automation, for example Hide German visit for English
- Under Automation Trigger Event, select the language field. The automation runs when the field value is updated.
- Click Add Condition and select Study field value: the language field is English.
- Under Automation Action, select Show/hide visit and choose the visit to hide, here Patient characteristics DE.
- Click Save.
Then create the opposite automation: if the language is German, hide the visit Patient characteristics EN.
When the user selects English, the German visit is hidden right away.
One language per site? If each site uses only one language, you can base the automation on the participant's site instead of a language field. The right visits are then shown automatically, without anyone having to select a language.
Large studies: a separate study per language
If your forms contain many questions, dependencies or automations can become hard to manage. In that case, we recommend creating a separate study for each language.
Multilingual data in your exports
With the dependencies and Automation Engine methods, each language version of a question is a separate field, so it's exported as a separate variable (for example dob_en and dob_de). With separate studies, you export each study separately. In all cases, plan how you will combine the data for analysis.
To make combining easier:
- Use the same option values in every language, for example Female = 0 and Weiblich = 0.
- Use a clear naming pattern for variable names, for example the same name with a language suffix (
_en,_de).