System and permissions
How to define patient languages
Defining the languages your patients speak with a title and a code, and the role that language plays in routing, vouchers and the API.
Where to find it
System SettingsPatient Languages
In medical tourism, language is the first fact that decides which consultant meets the patient. MetoCRM keeps languages as their own definition with two fields: Title and Abbr (code).
That small definition pays off in three places: team structure (user groups by language), voucher production, and the lead API, where an incoming language code is matched against these records.
Step by step
- Title — what the team calls the language (Turkish, English, Arabic).
- Abbr — the short code. Records coming through the API match on it, so use standard codes.
- Once defined, languages can be used on patient records and in API submissions.
Tips and common mistakes
- Careful Do not change a code later: if API submissions keep arriving with the old one, the language will not match and the record lands without one.
- Tip Define only the languages you actually serve. Keeping a language you have nobody to answer in means leads in that language reach no one.
- Careful A voucher cannot be produced for a patient with no language — the system warns instead.
Frequently asked questions
How does language relate to user groups?
Language is a property of the patient; a group is a structure of your team. The most common setup is a group per language: an English team, an Arabic team. See user groups.
What if the patient's language changes?
Update it on the patient record. If a handover is needed, move the patient to the relevant language team.
Is the panel language the same as the patient language?
No. The panel language is the user's interface; the patient language is what the patient speaks, and it drives the operation.