Stream: implementers
Topic: How to use "extensible"
Tim Berezny (Jul 10 2018 at 01:29):
I'm trying to grasp the meaning of "extensible" valuesets. For example, I am looking at patient.contact.relationships, which uses this valueset: https://hl7.org/fhir/2018Jan/v2/0131/index.html , and is an extensible codeable concept.
This valueset is pretty limited. In the world of referrals, there are plenty of other potential values like Parent, Substitute decision maker, etc...
Let's say I want to use "Parent". The closest code would be O - Other. My current theory on what to do is:
contact.relationship.coding.code = O
contact.relationship.coding.display = Other
contact.relationship.text = Parent
Is this correct?
Lloyd McKenzie (Jul 10 2018 at 01:59):
Yes. You could also include a local code for "parent" or a code from a different code system. (The existence of "Other" in an extensible value set is pretty odd, actually. If you've got "Other", you might as well make it Required, because one of the codes will always apply.
Lloyd McKenzie (Jul 10 2018 at 02:00):
If Other hadn't been in the value set, you would have been fine with just text and/or with a code from outside the value set
Grahame Grieve (Jul 10 2018 at 22:13):
can we make a task to fix that?
Lloyd McKenzie (Jul 10 2018 at 22:31):
GF#17472 - @Brian Postlethwaite for your attention
Tim Berezny (Jul 11 2018 at 03:02):
(deleted)
Tim Berezny (Jul 11 2018 at 03:03):
Does "local" code basically mean, I can populate it with whatever value i have in my system (i.e., treat it kind of like a text), without going through the trouble of publishing a valueset formally?
Tim Berezny (Jul 11 2018 at 03:03):
(deleted)
Tim Berezny (Jul 11 2018 at 03:05):
note @Joel Francis
Joel Francis (Jul 11 2018 at 13:31):
if the valueset weren't published or an inclusion not made via the gap analysis by the publishing organization of the ValueSet, what would the sending/receiving systems validate against. Also in the documentation, it says - If the value set does not cover the concept (based on human review), an alternate system.code may be used instead. Want to clarify if this is the code in the CodeableConcept . @Lloyd McKenzie
Lloyd McKenzie (Jul 11 2018 at 13:51):
"local code" = any code not in the value set (possibly even from one of the code systems that is in the value set). There's no need to define a value set that includes your extensions unless you plan to expose a profile that declares what your system actually supports. (Though doing that is generally good practice.) Having an explicit value set also gives you something to check if the base value set evolves.
Lloyd McKenzie (Jul 11 2018 at 13:52):
The alternative code would be sent in a CodeableConcept.coding
Joel Francis (Jul 11 2018 at 17:58):
The alternative code would be sent in a CodeableConcept.coding
Thanks @Lloyd McKenzie
note @Tim Berezny
Tim Berezny (Jul 11 2018 at 20:19):
Thank you very much @Lloyd McKenzie
Last updated: Apr 12 2022 at 19:14 UTC
