Stream: implementers
Topic: Questionnaire template & resourceComposition
Maria Hu (Jan 02 2020 at 17:33):
When building a Questionnaire template, is it necessary to bundle it with resourceComposition? and why?
Likewise, is it necessary to bundle the QuestionnaireResponse with resourceComposition?
Please advise, thanks.
Paul Lynch (Jan 02 2020 at 21:53):
What do you mean by a "Questionnaire template"?
Abbie Watson (Jan 02 2020 at 22:11):
Hi. My understanding is no... the Questionnaire template can be sent as a singleton response. The format would simply be: GET /fhir/Questionnaire/<templateId> What's not supported, however, is that the Questionnaires resource doesn't support a search on the derivedFrom field.
Composition is always included as part of the Bundle. You can think of it as a the postal sticker with address and tracking number that the post office puts on manilla envelopes and parcels. The nice thing about a large manilla envelope, is that you can put a lot of papers in it. So, keeping in mind that Questionnaire templates and QuestionnaireResponse templates aren't necessarily the same thing, or you might have multiples and mix-and-match in more complex active questionnaires... you can just bundle that all together as a Bundle. Just got to include the Composition as a sort of cover letter.
Lloyd McKenzie (Jan 03 2020 at 17:20):
It would be unusual to use Composition with QuestionnaireResponses and extremely uncommon to use it with Questionnaire. But it would be helpful to understand what you mean by QuestionnaireTemplate. Are you talking about a profile that constraints the design of a set of Questionnaires or are you talking about a single Questionnaire instance (which can be thought of as a 'template' for the QuestionnaireResponses against that Questionnaire).
Shamil Nizamov (Jan 08 2020 at 15:57):
But it would be helpful to understand what you mean by QuestionnaireTemplate.
I believe this is about my question in the "Questionnaire" stream to divide a single Questionnaire into a smaller connected Questionnaires to build a form which is currently not supported. Extensions may work but they make it harder to retrieve a "form" comprised of a set of QuestionnaireResponses than using Composition or List.
Lloyd McKenzie (Jan 08 2020 at 16:18):
Right now, you can't have a QuestionnaireResponse created against more than one Questionnaire (whether you use extensions or not). If a QuestionnaireResponse points to a Questionnaire, then all of the linkIds for the questions in the response must correspond to linkIds in the referenced Questionnaire. Anything else is non-conformant. We're exploring how to handle the use-case. The most likely outcome is that we'll have a notion of 'compiled' vs. 'uncompiled' questionnaires where you can design a questionnaire that references other questionnaires, but on completion you first assemble a 'complete' questionnaire that has all of the questions in-line. We still haven't figured out how we're going to manage linkId uniqueness though.
Rob Dingwell (May 06 2020 at 15:30):
@Lloyd McKenzie would the idea of a Questionnaire that is composed of other smaller smaller questionnaires leverage the derivedFrom field with specific guidance on how to deal with linkIds and compilation of the multiple questionnaires into a single Questionnaire?
Lloyd McKenzie (May 06 2020 at 15:36):
No, it won't use derivedFrom. There'll be a specific extension that will appear on a 'display' item that will be replaced with the items of the referenced Questionnaire
Last updated: Apr 12 2022 at 19:14 UTC
