Stream: questionnaire
Topic: Defining a question as part of an order
Don Langlois (Mar 08 2019 at 23:03):
I see mention of Questionnaire questions that can be associated with Task/ServiceRequest. I also see several fields that could be used to convey this, for example "useContext" , "definition" and some others, but would like to get some thoughts/suggestions from this group
Thanks
Lloyd McKenzie (Mar 08 2019 at 23:05):
So you want an order to complete a questionnaire?
Don Langlois (Mar 08 2019 at 23:07):
yes, for example consults that can be both questionnaire and order
Don Langlois (Mar 08 2019 at 23:09):
Sorry just to clarify, our project requirement is to create a questionnaire for form rendering in a consumer application
Lloyd McKenzie (Mar 08 2019 at 23:31):
Task can be used to essentially create items on a to-do list, and one such possible item would be "fill out form X". The Questionnaire would be passed as an 'input' for the Task. Once done, the completed QuestionnaireResponse would be associated as an 'output'.
Dave Carlson (Mar 08 2019 at 23:35):
Or, a ServiceRequest can be created with patient as the performer, with servicerequest-questionnaireRequest reference to Questionnaire. When I looked at these alternatives, the ServiceRequest seemed to fit better into a care planning scenario.
Lloyd McKenzie (Mar 08 2019 at 23:50):
ServiceRequest is an "authorization". If you need a full-blown signed order, then ServiceRequest is what's needed. If you just want to tell a patient (or provider) "hey, it's time to fill out form X", then Task is more appropriate. I've added GF#20515 asking OO to provide more clarity on this
Dave Carlson (Mar 09 2019 at 00:01):
Another situation where I find ServiceRequest a better fit is to use Timing, e.g. patient should complete PHQ-9 assessment Questionnaire every 2 weeks for the next 3 months.
Lloyd McKenzie (Mar 09 2019 at 00:04):
Right. Though you might then spawn a Task for the patient each time they're supposed to fill out the form.
Don Langlois (Mar 15 2019 at 16:25):
Thanks again everyone, wondering if i can pick your brains again? The following use case i see several ways to accomplish but wondering your thoughts on the following:
Use case:
User creates a form template for consumption by providers. The form could be a simple questionnaire or more complex questionnaire with an Order(ServiceRequest). The Consumers of the form have a few options based on their EMR integration:
1) Print the form and fill out manually
2) Load and render the form in EMR, populate then print out form
3) All managed in EMRs electronically
As a form can contain simple questions or orders would it make sense to define Questionnaire.items.definition to reference a ServiceRequest and/or Task "template" that the consuming EMR would need to manage (or ignore if just printing)
Thanks
Don
Lloyd McKenzie (Mar 15 2019 at 16:51):
The Questionnaire is a definition - it spans all patients and all time, so it couldn't point to a patient and time-specific resource like Task or ServiceRequest. A QuestionnaireResponse could point to a Task or ServiceRequest and indicate that the response was created based on a particular order or task.
Don Langlois (Mar 15 2019 at 16:58):
Thanks,
Agree, however a form creator could create their forms and store in repository for consumption by form users (at any point in time). If the form template that the creator developed needs to inform the receiver that an order needs to be generated when it gets filled in, where could this be defined.
A hypothetical example could be a MI Questionnaire with a section for CT Scan if question "xyz" is true. The form itself is just a template at this stage, the form user/consumer when they retrieve and fill in the form would need to be informed that part of the Questionnaire needs to generate a ServiceRequest.
Sorry hope my descriptions make sense :)
Lloyd McKenzie (Mar 15 2019 at 17:12):
So you're wanting to trigger the creation of orders based on questionnaire answers? To do that properly, you'd probably be looking at a separate PlanDefinition that had triggers based on information in the QuestionnaireResponse. I suppose you could shortcut that with an extension in the Questionnaire.
Don Langlois (Mar 15 2019 at 17:19):
Not necessarily, that scenario was just used that as example. The form could be a generic lab requisition that gets stored in repository as "template". Users would retrieve the form and fill in required information but since the form is a requisition they need to generate an Lab Order. Currently providers would just print it out once filled, however to send electronically would need way to inform system to create additional resources.
Lloyd McKenzie (Mar 15 2019 at 17:21):
Take a look at the Structured Data Capture implementation guide - it provides guidance for how to transform a QuestionnaireResponse into other FHIR resources.
Don Langlois (Mar 15 2019 at 18:43):
Thanks
Last updated: Apr 12 2022 at 19:14 UTC
