Stream: questionnaire
Topic: Grouping Questionnaire Responses
Diane (May 10 2021 at 17:02):
I don't know if this question belongs in the questionnaire track or somewhere else.
I have a similar issue to @Grey Faulkenberry and his question about grouping Questionnaires, but I want to group questionnaire responses together. I don't think the PlanDefinition resource fits our use case involving clinical study protocols and administrative forms.
For some of the clinical studies, there might be 1 study initiation questionnaire response, 3 consent questionnaire responses (one per study site), 3 determination questionnaire responses (one per study site), 1 protocol questionnaire response, 4 continuing review questionnaire responses (per regulatory requirements and length of study) and 7 adverse event questionnaire responses. Another study might have a different distribution of questionnaire responses. I am debating trying to use the List resource, vs. a dynamically updated QuestionnaireResponse resource so that my application can present the group of completed questionnaire responses to the researchers and study coordinators for the intent of reviewing/editing the questionnaire responses for a particular study.
Does anyone have any feedback on whether a QuestionnaireResponse Resource vs a List Resource would be a better approach?
If I used a List Resource, I was thinking something like this:
<List xmlns="http://hl7.org/fhir">
<id value="study # 12345678"/>
<mode value="working"/>
<title value="List of the questionnaire responses for study # 12345678"/>
<status value="current"/>
<entry>
<item>
<reference value="QuestionnaireResponse/851" />
<display value="Study Initiation QR# 851" />
</item>
</entry>
<entry>
<item>
<reference value="QuestionnaireResponse/852" />
<display value="Determination Letter QR# 852" />
</item>
</entry>
<entry>
<item>
<reference value="QuestionnaireResponse/853" />
<display value="Determination Letter QR# 853" />
</item>
</entry>
<entry>
<item>
<reference value="QuestionnaireResponse/854" />
<display value="Determination Letter QR# 854" />
</item>
</entry>
<entry>
<item>
<reference value="QuestionnaireResponse/855" />
<display value="Protocol QR# 855" />
</item>
</entry>
</List>
Lloyd McKenzie (May 10 2021 at 17:27):
My recommendation would be to use the http://build.fhir.org/extension-workflow-researchstudy.html extension and have a search criteria on your server that allows you to filter QuestionnaireResponses based on study. (You could also propose this be defined as a standard SearchParameter in the core spec.)
Paul Lynch (May 10 2021 at 17:39):
BTW, if you are using a HAPI FHIR server, adding the ability to search on an extension is easy-- you just add a SearchParameter resource to the server (and possibly reindex-- not sure). Here is an example of a SearchParameter for an "age-at-event" extension: https://github.com/ncpi-fhir/ncpi-model-forge/blob/master/site_root/input/resources/search/SearchParameter-age-at-event.json
Diane (May 10 2021 at 22:25):
@Lloyd McKenzie I think that extension-workflow-researchstudy appears to be what we need. Thank you.
Diane (May 10 2021 at 22:34):
@Paul Lynch If the questionnaire response captures the reference to the research study, then does LHC-Forms have the ability to include this data when it sends the QR to the server? We are using the HAPI Server. I have never tried setting up a SearchParameter before, but that would definitely make life easier.
Paul Lynch (May 10 2021 at 22:46):
LHC-Forms does not know about ResearchStudies. What you can do is ask it for the QuestionnaireResponse, and then before sending it to the FHIR server, add the workflow-researchstudy extension Lloyd mentioned.
Diane (May 10 2021 at 22:57):
Understood. That's what I was thinking.
Diane (May 22 2021 at 02:01):
Is this how I would use the http://build.fhir.org/extension-workflow-researchstudy.html extension to capture that this Questionnaire Response is related to the Research Study with ID 1234?
{
"resourceType": "QuestionnaireResponse",
"id": "1153",
"meta": {
"versionId": "1",
"lastUpdated": "2021-05-22T00:03:07.063+00:00",
"profile": [ "http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse|2.7" ],
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/workflow-researchStudy",
"value": {
"reference": "/ResearchStudy/1234"
"display": "1234"
}
}
]
},
"status": "completed",
"authored": "2021-05-22T00:03:04.001Z",
"item": [
{ "linkId": "Initiate_1",
"text": "Study Title",
"answer": [ { "valueString": "Testing a higher treatment dosage for condition X" } ] },
{ "linkId": "Initiate_4", "text": "Will there be compensation for participation?", "answer": [ { "valueCoding": { "code": "1", "display": "Yes" }
} ] }
[SNIPPED]
]
}
Lloyd McKenzie (May 22 2021 at 02:06):
There shouldn't be a '/' in front of the resource in a local reference. Also, a local reference presumes that the ResearchStudy is on the same resource as the QuestionnaireResponse. Otherwise, yes.
Last updated: Apr 12 2022 at 19:14 UTC