Stream: implementers
Topic: Translation
Patrice Duhoux (Feb 14 2018 at 11:05):
How do we manage translation on all the different concept of Fhir ? We would like to manage translation of text, description in Fr, NL, EN, ... depending on the culture ?
Grahame Grieve (Feb 14 2018 at 11:16):
I think you need to provide a little more information...?
Patrice Duhoux (Feb 14 2018 at 11:24):
so for all CodeAbleConcept , valueset, text, description entries we would like to have different translation for the same item. We support different language "English", "French", "Dutch" depending on the regions and each data are being filled in the different languages. So reference data we send to fhir must support language at each level.
Grahame Grieve (Feb 14 2018 at 11:29):
so you can have translations in code system and value set and profiles.
Grahame Grieve (Feb 14 2018 at 11:29):
or you can have translations on any string or markdown using the translation element
Grahame Grieve (Feb 14 2018 at 11:29):
is that what you are asking?
Simone Heckmann (Feb 14 2018 at 11:46):
There's a standard extension you can use on string, markdown and code to add different language translations to any field: http://hl7.org/fhir/STU3/extension-translation.html
Paco Novillo (Oct 23 2018 at 15:15):
I think it is already solved in the ValueSet resource itself https://www.hl7.org/fhir/valueset-definitions.html#ValueSet.compose.include.concept.designation
I have created an example here with a valueset with 3 concepts translated to Spanish: http://fhirtest.uhn.ca/baseDstu3/ValueSet/fnpEncounterTypeTranslations
yahyadeveloper (Jul 16 2019 at 08:40):
Hello
I am working on translation the FHIR on the Arabic language.
Is there any way can help us to set the translations as standard methods?
Lloyd McKenzie (Jul 16 2019 at 14:11):
To clarify, you're wanting to translate the spec, not the interface, correct? @Grahame Grieve
Grahame Grieve (Jul 26 2019 at 10:37):
well, more clarity needed on this one
Last updated: Apr 12 2022 at 19:14 UTC
