I have been attempting to convert our routing code to use the more
performant PreParser over a full PipeParser.

I have found this message to throw an exception in the pipe parser, but no
exception is thrown with the PreParser:

MSH|^~\\&|||||20161024182512||ORM^O01|1624|T|2.4||||||8859/1


Note the \\ in the MSH-2, this was an actual case in our production system
and is one of the edge tests we perform.

When I moved to the PreParser this test failed as it no longer throws the
HL7Exception:

ca.uhn.hl7v2.HL7Exception: Invalid or incomplete encoding characters -
MSH-2 is ^~\\&


Surely the same exception should be generated by the PreParser?

-Mike
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Hl7api-devel mailing list
Hl7api-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hl7api-devel

Reply via email to