Stream: implementers
Topic: Localisation and language dialect
Jeffrey Chen (Jul 25 2016 at 03:58):
I'm working on building a lightweight terminology server. When trying to implement the FHIR ValueSet, I noticed that there is need to localise the concept descriptions. For example, the current FHIR ValueSet UnitsOfTime ( http://hl7-fhir.github.io/valueset-units-of-time.html) uses "s" to display second. What happens to the users who need to display "second" inside of "s" on their user interface? Does that means local terminology server need to have a different ValueSet or use different descriptions to replace the HL7 standard? Also, does FHIR Restful API support localisation in the ValueSet $expend operation?
Grahame Grieve (Jul 25 2016 at 04:24):
generally, have a look at ExpansionProfile. And see how the value set is extended for Chinese. That should point you in the general direction to go....
Grahame Grieve (Jul 25 2016 at 04:24):
as in, that particular value set is extended for Chinese
Jeffrey Chen (Jul 25 2016 at 04:35):
Thanks Grahame. Having a look at the ValueSet expansion profile, "profile" looks good but there is no agreed format or functionality for the target has been defined.
This happens a lot when local implementation uses SNOMED CT language refset. Displaying "haemochromatosis" instead of "hemochrombtosis" may be considered as disaster to some clinicians.
Michael Osborne (Jul 28 2016 at 20:43):
@Jeffrey Chen That's why there is a language reference set in SNOMED CT. The local version of SCT should accommodate the local language description.
Jeffrey Chen (Jul 28 2016 at 22:22):
Thanks @Michael Osborne , SNOMED CT does support dialect through language refset. The qeustion is how FHIR terminology service knows which dialect is asking for? Or, should one terminology service only support one dialect during implementation?
Grahame Grieve (Jul 29 2016 at 05:07):
the terminology server can support multiple dialects. The client can ask for a particular language in the expansion profile or as a parameter to the $expand operation. I don't know what you mean when you say 'there is no agreed format or functionality for the target'
Jeffrey Chen (Jul 29 2016 at 07:41):
I thought the syntax for query the terminology server to get a value set using Austrlian language refest is [base]/ValueSet/administrative-gender/$expand?profile=http://snomed.info/sct/32570271000036106
. The parameter profile
has no agreed format or functionality for the target which is stated at https://hl7-fhir.github.io/valueset-operations.html#expand. Maybe it should be [base]/ValueSet/administrative-gender/$expand?displayLanguage=en-AU
but what happen to a state level dialect?
Last updated: Apr 12 2022 at 19:14 UTC