System Roles Role 1: Order creation 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: Order receiving system – receives and interprets the FHIR based orders for DME and/or Home Health Services (should prepare in advance but may build at connectathon) Role 3: Intermediary routing system – receives order and routes it to the correct endpoint – may convert order to other format based on capability of the final endpoint (should prepare in advance but may build at connectathon) Scenarios Working on (2) Scenarios with multiple steps for basic order content, advanced order content, and ability to support clinical attachments Scenario 1 Step 1: Home Oxygen Order Action: Create an POA order message bundle for Home Oxygen Therapy including PAO DeviceRequest Profile as the basis for the order and sending it to the processmessage endpoint of the supplier or intermediary. Precondition: None Success Criteria: Receiving a valid order bundle for Home Oxygen using the PAO DeviceRequest profile Bonus point: None Scenario 1 Step 2: Responding to the message bundle with an appropriate status Success Criteria: Sender receiving a confirmation of the status of the order in response to the initial submission Scenario 1 Step 3: Responding to the subscription with an appropriate notification Success Criteria: Sender receiving a subscription notification when the status of the order (task) changes Scenario 2 Step 1-3: Home Oxygen Order Same steps as for the Home Oxygen Order but focused on Home Health using the PAO ServiceRequest profile Bonus Point: include documentation for the order in the order bundle (suggestion is to include specific resources that support the order of Home Oxygen (e.g. condition, observation, encounter) TestScript(s) Use basic Aegis test scripts for the R4 release Security and Privacy Considerations Identify any expectations around security (e.g. will TLS, mutual-TLS, OAuth, etc. be required to participate) | 
