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

Submitting WG/Project/Implementer Group

Justification and Objectives

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.

This track will use R4 version of FHIR.

Clinical input requested (if any)

Not Required

Implementation Guide Draft being tested at the Connectathon 24

https://build.fhir.org/ig/HL7/dme-orders/index.html

Related tracks

None

Proposed Track Lead

David Bruinsma, Colonial Medical Supplies david@colonialmed.com

Zane Schott, DMEhub, Zane.Schott@DMEhub.com

Supporting Role: Robert Dieterle, rdieterle@enablecare.us

Supporting Role: Nandini Ganguly, nganguly@scopeinfotechinc.com 

Expected participants

EHR vendors, DME suppliers or DME order management systems and home health agency technology suppliers  – expect 5-6

Track Orientation

A webinar was hosted about this track on Date:  at 12 noon ET.

Recording of the session and the slides are posted here. If you would like to hear the Implementation Guide tutorial and information about sample artifacts, please click here. If you have any questions please email nganguly@scopeinfotechinc.com 

Zulip chat link for this session: https://chat.fhir.org/#narrow/stream/236612-DME-Orders.20on.20FHIR

Touch point: May 14th 1:00 pm ET and 4:30 pm ET (Zoom platform); May 15th 1:00 pm ET (Zoom platform) and 4:00 pm ET (report out using GoTo global meeting)

Track Report Out Video: https://www.pathlms.com/hl7/courses/18823/video_presentations/158287

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

  • No labels