Stream: implementers
Topic: ValueSet with SNOMED code in post-coordination
Katarina (Feb 04 2022 at 11:44):
Hi,
i want define a ValueSet with SNOMED-Codes. Some of the SNOMED-Codes should be in post-coordination. Is this possible? How would the codes look like?
My idea:
<ValueSet xmlns="http://hl7.org/fhir">
<compose>
<include>
<system value="http://snomed.info/sct" />
<concept>
<code value="281666001|family history of disorder|:246090004|associated finding|=22298006|myocardial infarction|" />
<display value="myocardial infarction in family history" />
</concept>
....
Is this correct?
Thank you,
Katarina
Vadim Peretokin (Feb 04 2022 at 13:24):
I believe so. Guidance on this is a bit hidden, but you can find it here: https://www.hl7.org/fhir/terminologies.html#grammar
Vadim Peretokin (Feb 04 2022 at 13:25):
Though I have to say Note that there is no display defined for SNOMED CT expressions. is a bit ambiguous - does it say you cannot have display, or just that the base standard offers no guidance on how to use the element? Regardless I'm including it in my work since 128045006:{363698007=56459004} to me as a human means nothing.
Katarina (Feb 04 2022 at 18:34):
Thank you. Even if the expression has no display defined by the base standard, I think it would be possible to add an user display in the expansion element. Am I right?
Grahame Grieve (Feb 04 2022 at 19:08):
this one:
The base standard offers no guidance on how to use the element
Katarina (Feb 04 2022 at 19:32):
So this means I can define an own display and set it in the concept.display element in the ValueSet?
Lloyd McKenzie (Feb 04 2022 at 19:36):
You can. The expansion is generally expected to be automatically generated, so putting it in the 'compose' side rather than the 'expand' side might be better.
Peter Jordan (Feb 04 2022 at 19:47):
I guess one solution is to place the terse form of the expression in the code (thus not breaking implementations that don't permit spaces in codes) and the full form in the display (as, effectively, the FSH for the concept).
Although, I realize that this is just an example, I would be interested in it being validated by anyone with a Classifier (e.g. @Rob Hausam ) as that might illustrate some important points. For example, it would surprise me if this example is valid without any adherence to role/relationship grouping requirements.
Grahame Grieve (Feb 04 2022 at 20:09):
I have code to generate the display - it uses the term, and it uses a more explicit and less dense syntax that makes it easier for non-technical users, though it's the same structure
Vadim Peretokin (Feb 05 2022 at 06:39):
Added a ticket to clarify text - FHIR-35963.
Last updated: Apr 12 2022 at 19:14 UTC
