System Roles Role 1: Ordering System – creates and send FHIR based orders for DME and/or Home Health Services (should prepare in advance but may build at connectathon) Role 2: Rendering System – receives and interprets the FHIR based orders for DME and/or Home Health Services and performs the requested actions (should prepare in advance but may build at connectathon) Role 3: Intermediary System – receives order and routes it to the correct Rendering System(s) – may split/modify order and/or convert order and to other format based on capability of the Rendering System(s) (should prepare in advance but may build at connectathon) Scenarios Scenario 1 Step 1: Home Oxygen Order Action: Ordering System creates a POA order and Task for Home Oxygen Therapy including PAO DeviceRequest as the basis for the order and POST the Task to the endpoint of the Rendering System or Intermediary System. Precondition: None Success Criteria: Rendering System or Intermediary System receives a valid Task for Home Oxygen Therapy using the PAO Task profile Bonus point: Ordering System updates status of Task locally based on HTTP return code (200x: received, 40x: failed) Success Criteria: Ordering System recognizes HTTP code and sets Task.status accordingly Scenario 1 Step 2: Rendering System or Intermediary System retrieves Order and associated documentation Action: GET the Device Request that is the .focus of the Task Success Criteria: Demonstrate ability to retrieve (GET) the DeviceRequest that is the focus of the Task Bonus point: GET associated clinical documentation referenced by DeviceRequest.supportingInfo (Observation resource (O2 Saturation) Success Criteria: Demonstrates ability to get Observation Scenario 1 Step 3: Ordering System subscribes to the Task Action: Create a Subscription to the Task and POST it to the Rendering System or Intermediary System. Success Criteria: Receive a valid Subscription to the Task Scenario 1 Step 4: Rendering System or Intermediary System sends a notification to the Ordering System Action: Rendering System or Intermediary System updates the Task status and statusReason and sends a Subscription notification to the Ordering System indicating that the Task resource has been updated. Success Criteria: Ordering Systems receiving a valid notification Bonus point: Ordering System GETs the Task pointed to by the notification. Success Criteria: Demonstrate retrieving the updated Task resource pointed to by the notification Scenario 2 Step 1-4: Hospital Discharge Order for Home Health Physical Therapy Same steps as for the Home Oxygen Order but focused on Home Health using the PAO ServiceRequest profile Bonus Point: includes exchange of documentation supporting the order (suggestion to include specific resources that support the order for Physical Therapy (e.g. condition, observation, procedure, encounter) Scenario 3 Step 1-4: Medication Order for Immunosuppressives Same steps as for the Home Oxygen Order but focused on Immunosuppressives using the PAO MedicationRequest profile Bonus Point: includes exchange of documentation supporting the order (suggestion to include specific resources that support the order for Immunosuppressives (e.g., .basedOn: condition) TestScript(s) Use basic Aegis test scripts for the R4 release: https://wildfhir4.aegis.net/fhir4-0-0-gui/index.jsf Security and Privacy Considerations Identify any expectations around security (e.g. will TLS, mutual-TLS, OAuth, etc. be required to participate) | 
