Stream: implementers
Topic: DSTU2/Order vs STU3/Task : Are these similar ?
Janaka Peiris (Jan 19 2021 at 12:16):
We need to map a "task" in our EHR into both DSTU2 and R4. I see there is a Task resource from STU3/R4 but the closest I found in DSTU2 was Order (under Workflow). As per the description, an Order can be used to carry out an action request, and designed in a generic way. My questions/concerns are:
1) Is there any other "closer" resource in DSTU2 for a task?
2) Other order resources (DiagnosticOrder, NutritionOrder, MedicationOrder ) are all clinical. Therefore using the Workflow/Order seems more logical for a task.
Thanks In advance!
Lloyd McKenzie (Jan 19 2021 at 15:30):
- No. And 'Order' was somewhat broken, so be prepared to use extensions or otherwise be creative to make it work. (Alternatively, you could use Basic.)
- Not all of the request resources are clinical. ServiceRequest can cover quite a lot of things (ProcedureRequest in DSTU2). Keep in mind that 'Request' resources represent an authorization, while Task initiates action (sometimes based on an authorization, sometimes not).
Janaka Peiris (Jan 20 2021 at 08:53):
Thanks @Lloyd McKenzie . Will use Basic resource with some extensions.
Tim Berezny (Mar 11 2021 at 14:13):
@Lloyd McKenzie regarding "'Request' resources represent an authorization", if a request processor wants to make an update to the ServiceRequest, such as adding a not or a performer - Is that something the request processor is "allowed" to do, since it modifies the authorization? Is there a most typical workflow for this kind of process?
Vassil Peytchev (Mar 11 2021 at 15:02):
I think usually the processor will not have access to modify the ServiceRequest, in fact there might be two different ServiceRequests: one on the requester's server, and one on the request processor's server. This is where Task could have a role similar to an "interface" between the requester and processor: The processor can modify the Task resource, and the requester can act on that modification to update the ServiceRequest.
Lloyd McKenzie (Mar 11 2021 at 16:57):
FHIR places no limitations. FHIR is totally happy if you update a prescription and change the drug, dose, patient and prescriber. Most colleges of pharmacy would frown on that though...
Often both the 'placing' and 'filling' system will have a Request instance. The 'filler' one reflects the details of what they actually intend to do. The placer one reflects what's 'authorized'. How much variation between the two varies based on business rules, who's making the decisions, etc. Task provides the communication vehicle to negotiate fulfillment and keep both parties up-to-date on status.
Last updated: Apr 12 2022 at 19:14 UTC
