Why Use an HL7 Engine?
May 14th, 2007 by Dave Shaver
Posted in Healthcare Integration, HL7 Integration
There are two primary methods of moving clinical data in a hospital or clinic:
- Point-to-point interfacing, which provides a direct connection between exactly two applications
- Interface engine interfacing, which provides a way to leverage a set of interfaces between many applications
The presence of an HL7 interface engine in a healthcare environment gives more control to an organization and saves money and time by:
- Reducing the required number of export and import endpoints
- Allowing for reuse of data between applications
- Providing an easier method to interface a new or replaced application
- Providing the ability to monitor the entire system at one time
- Providing the ability to proactively notify interested persons using visual display and e-mail, when problems arise
Facilities that are pursuing healthcare integration initiatives and use an interface engine model find that:
- It is much less expensive and takes less time to initially implement an interface because an engine allows for leveraging of data and an engine is flexible in its acceptance of data
- The cost and time required to add new or replace existing applications is frequently less than half that required in a point-to-point model
- It requires considerably less time and money to maintain and monitor the interfaces because of the availability of centralized monitoring
There is an excellent 22 page white paper on this website entitled, “Why Do I Need an Interface Engine? Evaluating Two Approaches: Point-to-Point and Interface Engine.” It discusses the pros and cons of these two approaches in detail. Specifically, the white paper provides details on how an HL7 integration engine provides more control and saves time and money in a clinical or healthcare environment. The paper includes a comparison of an interfaced environment using point-to-point communications and an interfaced environment using an interface engine.
Last 5 posts by Dave Shaver
- Massachusetts Hospitals Must Have CPOE by 2012 and CCHIT-Certified EHRs by 2015 - August 13th, 2008
- HL7 Dates and Times - July 25th, 2008
- HL7 Time Zone Qualification - July 25th, 2008
- RHIOs vs. Peer-to-Peer Communications - July 11th, 2008
- Hospitals Allowed to Pay for EMR Interfaces and Not Violate Stark - June 3rd, 2008

(2 votes, average: 4.5 out of 5)




[…] HL7 integration presents the opportunity to streamline processes and share information quickly between systems. For example, in a hospital setting, if the laboratory adds on an additional test (e.g., reflex test), then the lab can send a charge message directly to the billing department. The billing department will get notification of the add-on procedure, and it will not require any manual intervention by a clinician to fill out a manual charge capture form. […]
[…] approach is to take the data that is coming from an application, modify the data in an interface engine, and then send the resulting message structure to the receiving application in their custom version […]
[…] The key question is not what the HL7 standard says about document encoding or even what the interface engine can do with the document. Rather, the focus should be on how the PDF file will be delivered to and […]