Orders Recipe

Standards-Based Orders

Many EHR systems don't accept orders based on HL7 FHIR resources.  However, building your application to these standard HL7 FHIR models allows your application to remain isolated from the complexity of each EHR system individually and at scale.

When integrating with healthcare system for orders, interopiO™ provides your application or service with a standards-based interface utilizing HL7 FHIR.  Your application will utilize FHIR resources including these common order-based resources:

interopiO provides your application with an HL7 FHIR Gateway between your system and the healthcare system's EHR.  This gateway allows your system to utilize the same HL7 FHIR resources independent of the specifics of the EHR.  Your system will read and write HL7 FHIR resources to and from your interopiO Gateway while utilizing our interopiO Data Adapter to handle the complexity and variance of each EHR's interfaces and APIs.


Integration with HL7 Interfaces

interopiO provides an integration with a healthcare system's HL7 interfaces by providing an HL7 receiver, a translation & enrichment to HL7 FHIR, and a FHIR Message system to send the order information to your application. 


HL7 V2 "Outbound" Orders Flow

Outbound orders are those orders that originate within the EHR system and are send outbound for fulfillment, often being Radiology or Laboratory systems.  Apps or services wishing to track outbound orders would utilize the following flow:



In this flow, interopiO receives the HL7 V2 messages via our HL7 V2 Receiver, converts those messages to HL7 FHIR resources and sends those resources to your app or service following the HL7 FHIR Message protocol.  interopiO can enrich the message by querying additional data from the EHR's APIs (FHIR and non-FHIR).  

In this flow, your app only has to support HL7 FHIR as a standard integration between various EHR vendors.


HL7 V2 "Inbound" Orders Flow

Inbound orders are those orders placed by your system to the EHR for fulfillment.  Inbound orders offer more integration options as EHR systems often provide an API (FHIR or Non-FHIR).  An app or service wishing to place orders within an EHR system would utilize the following workflow:




In this flow, your app or service would send (HTTP POST/PUT) a FHIR resource based on the order type to your interopiO Gateway.  The interopiO Gateway and Data Adapter would process the resource based on the type of data adapter (corresponding to the EHR Vendor).  Data Adapters can submit orders to the EHR using the HL7 V2 Interface, FHIR API, web services, or other interfaces.


Let Us Help

We have implemented these flows many times with many EHR Vendors.  Contact us for support.

0 out of 0 found this helpful



Please sign in to leave a comment.