Not to accept unnecessary HL7 into Mirth

[imageRAD]

Hi,

We have a channel listener for ORUs coming from vital monitors. Source is sending HL7 ZHB (kind of heart beat messages) frequently. So these messages are filling up the logs unnecessarily. We are giving NACKS and not to keep meta data however it increase message ID and stays there till next prune.

If there is a way to ignore these messages and not to have any trace in Mirth. We have found remove messages at client API however no remove message functionality inside Mirth.

Pre-processor also didn't work in this case or we couldn't find a way to make it happen.

Thx,

Haluk

[kirbykn2]

The pre-processor should work for this. What did you try.
Here is some untested code.

// This script executes before the message is processed by the source connector
if (message.contains("ZHB|")) {
// Discard the message by returning an empty string
return "";
}

// Return the original message if it is not a ZHB message
return message;

[imageRAD]

Hi,

thx for the answer. "contains" didn't work however with "includes" did. this is eliminating the content and messages are shown at the dashboard. we want not to have any messages on the dashboard and not to increase message ID.

Cheers,

Haluk

[imageRAD]

return null is also creating message ID and logged but clears the content of the messages. :(

[imageRAD]

Or just filter on another channel and send to the main channel

yeap we thought this however number transactions too much this is not optimized way. and now not to create message ID becomes a challenge. :)

[kirbykn2]

What is the issue with increasing the msg id?

[pacmano1]

actually, filtering on another channel and storing no message history on that channel is certainly an optimized way.

[yonajj]

Or just filter on another channel and send to the main channel

@imageRAD I think this the better option for what you want:

One channel with a high prunning, with a filter for those ZHB messages, and just a sender to another channel (Main)
Main channel will process only not ZHB message, and that message will have an Id that only will increment when a not ZHB message is received, and not high prunning is needed.

[kirbykn2]

The most optimized way is to have the sending system/device only send messages you need. ;)

[pacmano1]

I think the final answer here is that @imageRAD 's request is not possible for a TCP/MLLP listener; however, another channel can filter messages, or the OP can stop worrying about extra messages that are filtered.