Stream: questionnaire
Topic: SDC Extract: valueReference
Brian Kaney (Jan 23 2021 at 19:12):
Following the "Observation -based extraction" mode, since Observation does not have valueReference should a questionnaire item that is a valueReference be non-extractable item in this mode?
Lloyd McKenzie (Jan 23 2021 at 20:01):
Do you have a concrete example of information you'd expect to be captured as an Observation that would be a Reference?
Brian Kaney (Jan 23 2021 at 21:21):
The question is to pick a device (form a filtered list of DeviceDefinition). So the extracted Observation could mean a type of device (the Obs code could be a dialyzer, for instance) and the valueReference would be a reference to one (from a catalog).
Brian Kaney (Jan 23 2021 at 21:24):
Does it make sense that an Observation value be a reference to something defined in FHIR? BodyStructure also comes to mind. I imagine this might also be the case to refer to ObservationDefinition or perhaps other archetypical resource types as well.
Lloyd McKenzie (Jan 23 2021 at 23:17):
That wouldn't make sense for any Observation-type system I've ever seen. At best, you might have an Observation that would capture an identifier
Brian Kaney (Jan 24 2021 at 22:08):
Okay, as Observation can't have a valueReference, then the SDC documentation should explain expected behavior in the case the QR answer is a valueReference -- (http://build.fhir.org/ig/HL7/sdc/extraction.html#observation-based-extraction, bullet number 10 "Observation.value[x] - set to QuestionnaireResponse.item.answer.value[x]")
Brian Kaney (Jan 24 2021 at 22:09):
Likely omit extraction for this item, I am guessing...
Lloyd McKenzie (Jan 24 2021 at 22:45):
No need to explain that as if you're creating an Observation-driven Questionnaire, you wouldn't have any 'Reference' questions
Brian Kaney (Jan 25 2021 at 00:47):
What's an Observation-driven Questionnaire?
Brian Kaney (Jan 25 2021 at 02:25):
Also, does a QuestionnaireResponse.answer.valueCoding => Observation.valueCodeableConcept.coding[0]
Lloyd McKenzie (Jan 25 2021 at 03:12):
A Questionnaire where some/most/all of the questions correspond to things that would typically be captured as Observations.
The Questionnaire answer wouldn't necessarily be the first. We haven't talked about how to select. In most cases, I'd expect the Questionnaire to have a list of allowed options. The extraction process would grab the coding repetition that fell within the value set. If the answer was an 'open' question (i.e. that allowed other codings) and no match was found, the ideal thing to do would be to grab the valueCodeableConcept.text. If that didn't exist, second best would be the display from whatever code was flagged as userSelected. If that wasn't possible, it'd be up to the client. It could choose to grab the display from the first repetition, but there's no 'special' meaning to the order of the codings, so picking one at random would be just as viable.
Last updated: Apr 12 2022 at 19:14 UTC
