What are Hl7 Interface Engines

Do you need help with HL7 - HL7

I need all of your help to support me in my work HL7 interface integration that I have to work on between two different clinical applications.

It's something like that, I want to explain my question with an example.

We have the Epic system that is currently placing orders (lab, medication, etc). Next, these lab assignments are supposed to lead to another Cerner application.

For this there has to be an INTERFACE ENGINE that has to read this HL7 messages from the EPIC system and translate them into real messages for them Cerner SYSTEM and then write to their database.

Could you please explain me with an exemplary interface engine that first reads the HL7 messages and translates them into the Cerner application format.

How do I implement an interface engine here that would read the EPIC data?

What are the steps? An example would be best.

Orders are mainly placed in EPIC and should lead to Cerner applications.

Please help me understand the process and how you can interface integration with an interface engine.

Reply:

16 for the answer № 1

HL7 is a hairy beast and, by far, your best bet is to have a pre-built interface engine that will take care of the problem. Something like Connect Mirth, a Java-based system for receiving, decrypting, forwarding and triggering events based on HL7 messages. Mirth is free software and open source under the Mozilla Public License. As it is based on Java, it runs on most major operating systems or you can purchase dedicated hardware appliances to communicate with HL7 devices. It can be used to transform HL7 messages between different systems and is also well suited for converting HL7 to other protocols (TCP, SQL / ODBC, File, JMS, FTP, SOAP / HTTP).

For more information on Mirth Connect, see Webinars or check the wiki for examples.


7 for the answer № 2

When comparing engines (IMO), the total crucial factor is cost to ownership. Interfaces have a long lifecycle - it takes minutes to months to create and then live forever. The logging, monitoring, and warning functions (etc.) in the engine are critical to its success over the life of an interface.

Moving HL7 messages through any engine is "pretty easy" these days. Commercial or open source engines allow the trivial interfaces to emerge quickly. Commercial tools usually differ in that the non-trivial interfaces are much easier to create. The best engines make building interfaces quick, easy, and I dare say fun. :-)

Some white papers to provide background and thoughts for your search:

http://www.corepointhealth.com/whitepapers/evolution-hl7 - in-depth review of HL7 V2 and V3

If you're interested in commercial software, check out the KLAS leaderboard.

Disclosure: I am CTO at Corepoint Health (provides a commercial interface engine) and Co-Chair Infrastructure and Messaging (InM) Committee at HL7.


4 for the answer № 3

Nobody mentioned HAPI yet ... it is based on Java and Open Source. The title page contains a number of "HAPI by Example" code snippets to help you get started.

However, this is a very deep subject. I'm currently writing a parser for labs coming from Spire (Cerner) with HAPI, and there are a lot of little things you need to do to make it work. In particular, Cerner labs use ZDS (Z segments) in their labs, which requires some customization (Z segments are "custom" segments that are not part of the HL7 standard). They also send "MDM R01" messages that are not part of any HL7 standard (they just appear to be ORU-R01 messages with ZDS segments in them).

Did Cerner provide you with an interface specification? You should - if not, you should ask one. Also obtain a specification document for EPIC.

Not me think There's an API that translates automatically from EPIC's HL7 message to Cerner - I think you'll have to do the bit yourself. However, they can use an existing API to help you (this should make it a lot easier considering the HL7 message is very difficult to parse and it should be done for you).

Anyway - good luck!


0 for the answer № 4

Another white paper to ponder: The Role of an Interface Engine in Modern Healthcare - Main Functions of an Engine