NeoTool — Singular Focus, Healthcare Integrated

Posted in Healthcare Integration, HL7 Standard

All interface engines route, filter, map and send messages. But when evaluating different engines, what makes a good one?

A good interface engine should first be generic, meaning independent of any existing systems or software vendors. This allows it to remain a neutral party that is better able to integrate with new and existing systems.

Your healthcare integration engine should also include the following specific features:

HL7 Version Support

To ensure connectivity with all vendors and sites regardless of the version of HL7 standard being used. In addition, an engine should be configurable to handle any application’s interpretation of a specific HL7 version. Additional information on HL7 can be found in the HL7 Reference Guide.

Data Integrity

To ensure correct handling of the information, the engine should have multiple layers, checks and processes. Guaranteed message delivery with First In, First Out (FIFO) message processing should also be inherent.

Monitoring and Alerting

To understand message flow and identify abnormal activity from a centralized location. This results in more cost effective monitoring.

Message Logging

To provide an audit trail and method to recover lost messages, preventing catastrophic loss of patient data. Logging capabilities should include ways to view, filter, edit, search and resend the information.

Communications and Protocol Bridging

To provide support TCP/IP connections utilized by HL7 standards. This should include MLP support, partial message handling, acknowledgement (ACK) message handling, and other protocols or custom communication needs.

Message Acknowledgement

To support HL7 acknowledgement (ACK) messages. The engine should be configurable to allow for sending, receiving, or not receiving ACK messages, and should work with all possible send or receive situations.

Custom Communications and Formats

To support special communications needs that are not handled by the standard TCP/IP connection, such as custom acknowledgements or encryption, as well as non-HL7 formats that may have been implemented for a particular application.

Last 5 posts by Elizabeth Armenta

• Continuity of Care Document for Clinical Data Exchange - July 29th, 2008
• An Overview of CCD Templates - July 23rd, 2008
• What Are LOINC Codes? - December 18th, 2007
• The Essentials of a Good Interface Engine - January 10th, 2007
• The Ideal Healthcare Interface Monitoring and Alerting Approach - December 8th, 2006