FHIR Chat · Extracting Observation(s) for a multi-select question · questionnaire

Stream: questionnaire

Topic: Extracting Observation(s) for a multi-select question


view this post on Zulip Paul Lynch (Jun 05 2019 at 15:01):

If I you have question at that allows multiple selections (repeats=true, i.e. , checkboxes or a multi-select list), and observationLinkPeriod is set, should that be extracted as multiple Observations, or as one Observation with multiple components? If the latter, then would Observation.code and the Observation.component.codes all have the same values (the question code)?

view this post on Zulip Lloyd McKenzie (Jun 05 2019 at 15:03):

It probably depends on the conventions for that Observation. Typically, I'd say they should be separate Observations

view this post on Zulip Paul Lynch (Jun 05 2019 at 15:15):

I can't imagine general-purpose code that handles data extraction from a QuestionnaireResponses knowing about conventions for particular Observations. It will be always one way or the other. I am not pushing for using component, but the section on Observation.component says a use case is "Representing multiple answers to a question".

view this post on Zulip Lloyd McKenzie (Jun 05 2019 at 15:26):

It'd have to be determined by the questionnaire author and is driven by what's useful/typical for that particular Observation.

view this post on Zulip Paul Lynch (Jun 05 2019 at 15:31):

How would a Questionnaire author specify a preference as to whether the observationLinkPeriod extraction resulted in multiple Observations or multiple Observation.components?

view this post on Zulip Lloyd McKenzie (Jun 05 2019 at 17:44):

Using the "Observation period" approach, I don't think we provide any support for Observation.components at all - every repetition would have to be a separate Observation. Using one of the other mechanisms would allow you to map to components and/or other elements.


Last updated: Apr 12 2022 at 19:14 UTC