Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Track overview

Short Description

This track focuses on FHIR based RESTFUL exchange of orders from an EHR to a supplier or supplier HIT (or Hub) and the ability to update the order after order fulfillment.

Long Description

Ability to define a Post-Acute FHIR based Order (PAO) for DME and Home Health Services to facilitate order exchange between the ordering provider and the DME supplier or the Home Health Agency.

Test: To send a message bundle with a Task, Subscription, Order (e.g. DeviceRequest) and supporting documentation). The receiver (supplier, service provider, HUB) is able to receive it, respond back to the message, instantiate the Task, and has the ability to respond back to the ordering provider’s subscription with an alert or Task order when the Task is updated. We also want to test the ability to exchange an updated and cancel for the order or cancel the order.


  • Test an Implementation Guide

Submitting Work Group/Project/Accelerator/Affiliate/Implementer Group

Post-acute Order Referral Workgroup (for Orders and Observations)

Proposed Track Lead

Nandini Ganguly, ScopeInfoTechInc

David Bruinsma, Colonial Medical Supplies

Zane Schott,

Supporting Role: Robert Dieterle,

Related tracks



FHIR Version

  • FHIR R4

Specification(s) this track uses

Implementation Guide Link: (Please Note: This link will be updated with the latest build on Aug 4th 2020)

Artifacts of focus

Clinical input requested (if any)

Not Required

Patient input requested (if any)

Not Applicable

Expected participants

EHR vendors, DME suppliers or DME order management systems and home health agency technology suppliers . If interested please email us at 

Zulip stream

Zulip chat link for this session:

Track Orientation

A webinar will be hosted about this track on Monday Aug 17, 12 noon - 1:00 pm ET. Dial in details below

Participation Information

Phone Number: +1 929-436-2866

Participant Passcode: 510 046 7805

Web Meeting Info

Join Zoom Meeting -  | Meeting ID: 510 046 7805 | +1 929-436-2866-US (New York) | Find your local number:

Track details

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)


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)


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)

  • No labels