需要有关HL7的帮助

Question

I need all your help in guiding me with working on HL7 Interface Integration which I am to work on between two disperate clinical applications.

Its something like this, let me explain my query with an example.

We have Epic system that places orders(lab,medications..etc) presently. Now, next these lab orders are to result in another Cerner application.

For this, there has to be a INTERFACE ENGINE which has to read the HL7 messages coming from the EPIC system and translate them to proper messages for the Cerner SYSTEM and then write into their database.

So, could you please explain me with an example interface engine which reads the HL7 messages first and translates them to Cerner application format.

How will i implement a Interface Engine here which would read the EPIC data?

What steps are involved? An example would be best.

Mainly, orders are first placed in EPIC and is to resulted in Cerner applications.

Please help me with understanding the process,and how to do interface intregation with an Interface Engine?

Answer 1

HL7 is a hairy beast, and by far your best bet is to look at using a pre-built interface engine that takes care of the problem for you. Something like Mirth Connect , which is a Java based system for receiving, decoding, routing, and firing events based on HL7 messages. Mirth is free software and open source under the Mozilla Public License and being based on Java it runs on most major OS or your can purchase dedicated hardware appliances to interface with HL7 devices. It can be used to transform HL7 messages between different systems and also works well for converting from HL7 to other protocols (TCP, SQL/ODBC, File, JMS, FTP, SOAP/HTTP).

For more information on Mirth Connect check out their Webinars or check out the Wiki for examples .

Answer 2

Most critical in comparing engines (IMO) is total cost of ownership. Interfaces have a long life cycle -- they takes minutes to months to create and then live forever. The logging, monitoring, alerting (etc) features in the engine are critical to success over the life of an interface.

Pushing HL7 messages around via any engine is "pretty easy" these days. Commercial or open source engines allow the trivial interfaces to come up fast. Commercial tools typically differentiate by making the non-trivial interfaces much easier to build. The best engines make interface construction fast, easy, and dare I say fun. :-)

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

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

If you're open to commercial software, check the KLAS rankings.

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

Answer 3

No one has mentioned HAPI yet...it's based in Java, and open source. The front page has a bunch of 'HAPI by Example' code snippets that should help you get started.

This IS a very deep subject, however. I'm currently writing a parser for labs coming from Spire (Cerner) using HAPI, and there's lots of little things you have to do to get it working. Notably, 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, which aren't part of any HL7 standard (they seem to be just ORU R01 messages with ZDS segments in them..).

Has Cerner provided you with an interface specification? They should - if not, you should ask for one. Also get a spec document for EPIC.

I don't think there is an API that will automatically translate the HL7 message from EPIC to Cerner - I think you'll have to do that bit yourself. But you can use an existing API to help you (it should make it much easier, considering a lot of the heavy lifting of parsing the HL7 message and enconding it should be done for you).

Anyway, good luck!

Answer 4

需要考虑的另一份白皮书： 接口引擎在现代医疗保健中的作用 -引擎的主要功能

Answer 5

HL7 Integration engine: The integration engine is used to interface/talk (Communicate) between two applications. In your example Epic and Cerner. With the use of the EPIC, you are going to create new Orders and send these Orders to Cerner to Resultout the Orders. Here the EPIC may support one field and data type and Cerner may support different datatypes and other fields.
Here you need Integration Engine to Conver one data type format for another data type format. For Ex: We have different types of Integrations Engines Mirth / CloverLeaf / Rapsody etc Integration Engine as Mirth Connect is an Open source software. Here you are receiving the Orders from EPIC in EPIC format with the use of the Mirth you are going to convert these format to Cerner format. Once the LIS Cerner accepts those Order and Resultout the message and needs to send back to EPIC as Results. Mirth will accept the Results from Cerner and in Cerner format and Mirth will pick these Results and Convert into the EPIC format and sent to the EPIC system.