Stream: implementers
Topic: Observations: "other, please specify"
Josh Mandel (Nov 21 2016 at 22:52):
Does anybody have best practices for mapping LOINC answer lists that include "other, please specify" into a FHIR Observation? For example, http://r.details.loinc.org/AnswerList/LL2654-3.html — the question is where you'd put the specified "other" answer. Some possibilities include:
- a
.text
on the same CodeableConcept - a second
Coding
in the sameCodeableConcept
- a
.component
- a
.related
- an
extension
... but none of these sounds ideal, and I feel like I may be reinventing the wheel
Eric Haas (Nov 21 2016 at 22:59):
I'd narrow to my first choice would be .text
"... or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source."
second choice an"Other" .extension
Grahame Grieve (Nov 22 2016 at 04:55):
.text yes
Josh Mandel (Nov 22 2016 at 05:34):
So you'd provide the LOINC Answer code for "Other" in s Coding, and supplied value in CodeableConcept.text?
Grahame Grieve (Nov 22 2016 at 06:12):
yes
Josh Mandel (Nov 22 2016 at 13:45):
OK. For anyone following along, that's something like:
{ "resourceType": "Observation", "code": { "coding": [{ "system": "http://loinc.org", "code": "74076-1", "display": "Medication or substance involved" }] }, "valueCodeableConcept": { "coding": [{ "system": "http://loinc.org", "code": " LA20343-2", "display": "Other substance: PLEASE SPECIFY" }], "text": "Other substance: Blue pills I found under my couch" } }
Marc de Graauw (Nov 22 2016 at 16:37):
Thanks, I was just wondering how to model a similar case. Since this is such a common use case, might it be an idea to Put @Josh Mandel 's example straight in http://build.fhir.org/observation.html? (Though I think "text": "Other: Blue pills I found under my couch" might be better.)
Robert McClure (Nov 22 2016 at 16:45):
FWIW, I agree!
Eric Haas (Nov 22 2016 at 18:04):
make a GForge Comment so it gets in the Queue
Grahame Grieve (Nov 23 2016 at 05:30):
yes
Last updated: Apr 12 2022 at 19:14 UTC