Difference between revisions of "201605 Workflow"

From HL7Wiki
Jump to navigation Jump to search
 
Line 30: Line 30:
 
#Ron will monitor all tasks to track what is happening.
 
#Ron will monitor all tasks to track what is happening.
  
 +
=== Refinement before Lunch ===
 +
#Rik is going to create a care plan containing a diagnostic order for the patient.
 +
#Pascal is going to read the care plan.  His system will see the diagnostic order as an activity.
 +
##Creates a Task whose '''subject''' is Diagnostic Order, and is '''for''' the patient
 +
##Creates a subtask referencing that task where input.name = 'test to be scheduled' and input.valueReference = the diagnostic order
 +
##Creates a subtask referencing that task where input.name = 'test to be performed' and input.valueReference = the diagnostic order, in the
 +
#The patient schedules the test.
 +
##Pascals software makes the 'test to be scheduled' task as done, and sets output.name to 'scheduled appointment' and output.valueReference to an appointment containing the date which the test will be performed.
 +
##It also marks the 'test to be performed' task is marked ready
 +
#The lab (Angus) sees that the test is ready -- at this stage we have to deal with specimen collection, but to simplify
 +
#When the lab sees that the test is ready, it will
 +
##Create a Specimen Resource as an input
 +
##Create a Diagnostic Result Resource as an Output
 +
##Mark the test to be performed task as 'done'
  
 
== Track Stream ==
 
== Track Stream ==

Latest revision as of 17:08, 7 May 2016


Workflow

Submitting WG/Project/Implementer Group

FHIR Infrastructure, Patient Care, Patient Administration

Justification

Workflow is a primary focus of the upcoming release. A number of new approaches are being proposed and they need to be tested

Proposed Track Lead

See Connectathon_Track_Lead_Responsibilities Keith Boone (keith.boone@ge.com) Skype: kwboone

Expected participants

Ron Shapiro
QVera
Pascal Pfiffner
Boston Children's Hospital
Angus Millar
NETHA
Nikolai Schwertner
Boston Children's Hospital
Rik Smithies
NProgram
Keith Boone
GE Healthcare

Use Case

It's time for our patient to get his annual physical exam.

  1. Rik will create a Task for the Patient to schedule the prework as part of his care plan.
  2. Patrick will ask the Patient to select the Laboratory which will perform his results. The patient will select a lab (e.g., Acme Labs), and Patrick will create a new task, #containing the Laboratory Order as input, and assign that task to Acme labs to perform.
  3. Angus will monitor the task list for tasks assigned to Acme lab, perform the test, produce the results, and attach them as the output of the lab task, marking that task as complete.
  4. Ron will monitor all tasks to track what is happening.

Refinement before Lunch

  1. Rik is going to create a care plan containing a diagnostic order for the patient.
  2. Pascal is going to read the care plan. His system will see the diagnostic order as an activity.
    1. Creates a Task whose subject is Diagnostic Order, and is for the patient
    2. Creates a subtask referencing that task where input.name = 'test to be scheduled' and input.valueReference = the diagnostic order
    3. Creates a subtask referencing that task where input.name = 'test to be performed' and input.valueReference = the diagnostic order, in the
  3. The patient schedules the test.
    1. Pascals software makes the 'test to be scheduled' task as done, and sets output.name to 'scheduled appointment' and output.valueReference to an appointment containing the date which the test will be performed.
    2. It also marks the 'test to be performed' task is marked ready
  4. The lab (Angus) sees that the test is ready -- at this stage we have to deal with specimen collection, but to simplify
  5. When the lab sees that the test is ready, it will
    1. Create a Specimen Resource as an input
    2. Create a Diagnostic Result Resource as an Output
    3. Mark the test to be performed task as 'done'

Track Stream

Our Track Stream


TestScript(s)