Stream: implementers
Topic: Translations
Grahame Grieve (Jul 20 2016 at 06:10):
We've always said that we have a translation extension for language translation
Grahame Grieve (Jul 20 2016 at 06:10):
but I've just gone to use, and discovered that it's... useless
Grahame Grieve (Jul 20 2016 at 06:11):
<extension xmlns="http://hl7.org/fhir" url="http://hl7.org/fhir/StructureDefinition/iso21090-ST-translation" > <valueString value="rwefwf"/> </extension>
Grahame Grieve (Jul 20 2016 at 06:11):
where's the language....
Grahame Grieve (Jul 20 2016 at 06:11):
grrr
Grahame Grieve (Jul 20 2016 at 06:11):
has anyone used this or another approach for real? how did you do it?
Lloyd McKenzie (Jul 20 2016 at 13:41):
Language is a second extension - which can appear on the translation or on the base string.
Lloyd McKenzie (Jul 20 2016 at 13:42):
Probably would be good to declare that extension is mandatory on the translation extension though . . .
Grahame Grieve (Jul 20 2016 at 22:01):
actually, it turned out I was already making extensive use of another extension, so I defined it properly
Grahame Grieve (Jul 20 2016 at 22:03):
<extension url="http://hl7.org/fhir/StructureDefinition/translation" > <extension url="lang"> <valueCode value="de"/> </extension> <extension url="content"> <valueString value="rwefwf"/> </extension> </extension>
Lloyd McKenzie (Jul 21 2016 at 02:15):
Um, why use that one instead of the 21090 ones that do the same thing?
Grahame Grieve (Jul 21 2016 at 02:31):
it's poxy. I'll retire the iso 21090 extensions and map this one instead
Last updated: Apr 12 2022 at 19:14 UTC