- Created by Nandini Ganguly, last modified on Nov 13, 2020
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 6 Next »
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. |
Agenda | 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. |
Type | Test an Implementation Guide (https://build.fhir.org/ig/HL7/dme-orders/index.html) |
Submitting Work Group/Project/Accelerator/Affiliate/Implementer Group | Post-acute Order Workgroup (for Orders and Observations) |
Proposed Track Lead | Track Lead: Zane Schott, zane.schott@hme360.com; Kenneth Hodel, kenneth.hodel@apria.com ;Nandini Ganguly, nganguly@scopeinfotechinc.com SME: Robert Dieterle, rdieterle@enablecare.us |
Related Tracks |
|
FHIR Version | FHIR R4 |
Specification(s) this track uses | Implementation Guide: https://build.fhir.org/ig/HL7/dme-orders/index.html |
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, home health agency technology suppliers. If interested please email at nganguly@scopeinfotechinc.com. |
Zulip stream | Zulip chat: https://chat.fhir.org/#narrow/stream/236612-DME-Orders.20on.20FHIR |
Zoom Link | TBD |
Track Orientation Date | TBD |
Track Orientation Details | TBD |
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) 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