Stream: terminology
Topic: designation in ValueSet.compose?
Josh Mandel (Mar 24 2022 at 23:50):
Can someone help me understand why ValueSet.compose.include.concept.designation is part of the data model for listing concepts to include? Designations are generally defined by the underlying CodeSystem rather than by a ValueSet, no? (And, for example, there is no ValueSet.compose.include.concept.property element, so the goal can't be to convey a full concept inline here...)
Michael Lawley (Mar 25 2022 at 00:03):
The idea is that, in limited circumstances, you may want ValueSet-specific (ie context-specific) display text that varies from that of the underlying code system. One example might be a limited language translation. Another might be where the display device has limited space, so you need a set of carefully crafted short names that fit in the space.
Of course doing it this way is not really re-usable, and the preferred approach from a reusability perspective would be a code system supplement (esp. for translations).
Josh Mandel (Mar 25 2022 at 00:23):
Thanks! So when performing an expansion on a value set of that defines some designations inline, should these designations be added to the set of underlying designations from the code system itself, or should they be "pasted over" them, effectively replacing/shadowing any designations from the underlying code system?
Michael Lawley (Mar 25 2022 at 00:42):
They augment, just as a supplement would. The corner-case is display. We resolve this by repeating display as an explicit designation, and then the specific value used in the display element is just the one selected based on the displayLanguage parameter or the Accept-Language header, but all options are available as designations.
Last updated: Apr 12 2022 at 19:14 UTC
