The video above describes how to use the CORE HL7 Listener to dynamically manipulate HL7 messages as they come IN or HL7 Acknowledgements before they go OUT. The scenarios depicted in the video are REAL. Real customers of ours encountering these scenarios in live production environments.

 

Scenario 1:

You have a client who sends you HL7 messages but in the Message Control ID (MSH 10.1) they use a GUID (which is technically NOT HL7 compliant). Your system which consumes these HL7 messages will reject them if the Message Control ID is not HL7 compliant. The client is unable (or unwilling) to change the messages they send. What can be done?

Scenario 2:

You receive HL7 messages using the CORE HL7 Listener which were sent by a medical device. The device manufacturer REQUIRES that the HL7 Acknowledgement message returned by the listener place the word ACK in component 3 of the Message Type field (MSH 9) which is NOT required by any HL7 standard and thus is not handled natively by the CORE HL7 Listener. What can be done?

We can handle both of these scenarios using the CORE HL7 TCP/IP Listener.