Stream: implementers
Topic: delivery tracking for DeviceRequest
Addy Naik (Feb 14 2019 at 16:15):
For SupplyRequest there is a SupplyDelivery resource that can be used to track its delivery. What would be appropriate way to track workflow for when a device is being requested to be delivered to the patient at home (DeviceRequest) and we want to track the delivery?
Would it be appropriate to manage it under SupplyDelivery?
Lloyd McKenzie (Feb 14 2019 at 16:29):
Tracking fulfillment is generally handled with Task. You can capture a "business status" that conveys all the nuances of a particular workflow. E.g. "packaged for shipping", "loaded on cart", "departed warehouse", ...
Addy Naik (Feb 14 2019 at 16:36):
In that case wouldnt SupplyDelivery also be a task?
Addy Naik (Feb 14 2019 at 17:06):
And just so I understand this correctly - would we do a DeviceRequest and the track the delivery using Task? or would we do the request and the delivery in the task?
Lloyd McKenzie (Feb 14 2019 at 17:22):
DeviceRequest represents the "authorization". Task represents the request for fulfillment. So you might have someone who orders a prosthetic (DeviceRequest). Then you try to find a place that will actually manufacture it (Task for each location, which will get rejected until you find one that says 'yes'). The Task for the one that says 'yes' will then get updated to reflect their progress with the manufacturing/delivery.
Last updated: Apr 12 2022 at 19:14 UTC
