FHIR Workflow Minutes CC 20160106

FHIR Workflow Conference Call 3:00PM Eastern Time (Date above)

Return to FHIR Workflow Minutes

Agenda

• Approve Minutes Prior Meeting on 01/04

Attendees

• Lloyd McKenzie (chair/scribe)
• Michelle Miller
• Irena Roy
• Keith Boone
• Gary Dickenson
• Jose Costa Teixeira
• Eric Haas (joined after minutes approval)
• Marla Abitz (joined after minutes approval)

Minutes approval

Motion to approve minutes of Jan 4: Michelle/Iryna 4-0-1

Task Resource

• Worked through a simple and complex scenario using Task to manage the fulfillment process

Assumptions: One “reconciled” copy of the task (which could be federated in multiple systems but that aspect is outside of the scope for this discussion) in the “system of record” (which could change over time, but that aspect is outside of scope for this discussion).

1. Placer asks for fulfillment of Order A by Filler 1.

• Placer creates Task Resource on Filler 1 System (or other system) referencing Order A, and (optionally) subscribes to updates on Task Resource.

2. Filler 1 refuses.

• Filler 1 marks task on its (or other) system as failed and provides (optionally) a reason for refusal on the task.
• Placer is notified of update to task (or polls for status).
• Placer reads the status of the task.

3. Placer asks for fulfillment of Order A by Filler 2.

• Same as 1 above, replacing Filler 1 with Filler 2, with a new task instance.

4. Filler 2 accepts.

• Filler 2 marks task as assigned to Filler 2, changes state to assigned or higher.

5. Filler 2 provides preliminary results (linked to the fulfillment request).

• Filler 2 adds reference to preliminary results to the Tasks list of outputs, ensures state is “In Progress”

6. Filler 2 provides final results (linked to the fulfillment request) and indicates that they're done.

• Filler 2 adds reference to final results to the Tasks list of outputs, ensures state is “Complete”

7. Filler 2 provides amended results (linked to the fulfillment request).

• Filler 2 (optionally) changes state back to “In Progress”
• Filler 2 adds reference to amended results to the Tasks list of outputs
• Ensures state is “Complete”

What does that look like in a Task-based implementation? How many tasks? Who owns which ones? How is the overall state derived?

Prescription of multiple items:

1. Prescriber creates a prescription for three items, A, B and C.

2. Prescriber sends the items out for fulfillment via a pharmacy.

• Prescriber creates fulfillment task for patient P.

3. Prescription is validated by a pharmacist.

• Pharmacist assigns fulfillment task to him/herself, and marks it as in progress.
• Pharmacist creates validation task.
• Pharmacist validates prescription and creates initial dispense tasks for items A, B and C (each as a separate task) as subtasks of fulfillment.

4. Pharmacy 1 starts dispenses items A and B

• Pharmacy 1 assigns dispenses to itself to items A and B, and marks these tasks in progress.

5. Pharmacy 1 issues external request for dispense of item C

• Pharmacy 1 delegates dispense task to pharmacy 2 (or creates a new task for pharamacy 2)

6. Pharmacy 1 dispenses Item B

• Pharmacy 1 marks task B as complete

7. Pharmacy 1 is only able to dispense half of item A.

• Pharmacy 1 creates subtasks for dispenses of item A, half A1, and half A2.
• Pharmacy 1 updates subtask A1 as complete.

8. Pharmacy 1 issues external request for dispense of remaining half of item A

• Pharmacy 1 assigns/delegates Pharmacy 3 to subtask A2

9. Pharmacy 2 dispenses Item C

• Pharmacy 2 marks task C as Completed

10. Pharmacy 3 dispenses remaining half of Item A

• Pharmacy 3 marks task A2 as completed

11. Pharmacy 1 sees that A2 is completed

• Pharmacy 1 marks task A as completed

12. Pharmacy 1 sees that C is completed

• Pharmacy marks fulfillment task as Completed