Stream: terminology
Topic: ValueSet designations and languages
Grahame Grieve (May 31 2021 at 20:40):
@Michael Lawley Got a question for you. If a code system (or a supplement) has designations in a particular language, and a value set has designations but not for a the particular language, does the value set designation override the code system designation?
I think it should, but what does ontoserver do?
Michael Lawley (May 31 2021 at 20:58):
I think the expansion should always provide the display in the language requested, if available. So this would suggest that the ValueSet does not override, but if you ask for includeDesignations, then you get all.
However I don't know what Ontoserver does - our ValueSet designation support is limited.
Michael
Michael
Grahame Grieve (May 31 2021 at 21:29):
but if the value set specifies a designation, that's a high value thing - contextualised. So I'm not clear which is worse
Michael Lawley (May 31 2021 at 21:48):
Why not expect the ValueSet to have translations in that case?
Grahame Grieve (May 31 2021 at 22:34):
well, i think that would make perfect sense. But I'm not writing a value set, I'm working on my service...
Michael Lawley (Jun 01 2021 at 00:47):
I think it's reasonable to prioritise language over alternate designations. If I have a ValueSet that imposes, for example, an alternate spelling of a term in English, I wouldn't want that to affect an $expand that specifies Greek as it's displayLanguage
Michael Lawley (Jun 01 2021 at 00:48):
In theory, I would treat ValueSet designations the same way as a CodeSystem supplement
Last updated: Apr 12 2022 at 19:14 UTC
