Stop message in case of parsing error

[Diana de Bruin]

From time to time I find info on parsing errors in my process log files.

The segments that don’t belong in the HL7 message definition of an .xlt are ignored (a warning is written in the prc log) and the message is then processed.

I recently received a single DFT message on Cloverleaf that should have been send by the sending system as 2 seperate messages.

The MSG and PID of the 2nd part of the message were ignored (warning in the prc log) and the FT1 segments were processed and ended up with the patient from the 1st PID segment.

Is there a way to prevent such a message from being processed, or can it be dumped in the errorDB?

What’s the effect of activating the “Elevate warnings to errors when parsing incoming HL7, UN/Edifact, NCPDP, or X12 messages” checkbox on the Xlate Route Detail

Diana

LUMC -Leiden University Medical Centre
The Netherlands

Topic