As part of fuzz testing it has been identified that strange combinations of
MSH-9 can cause some quite unexpected behaviour.
In this example a message defined as ADT^M02 was routed as an MFN^M02 due
to routing only checking MSH-9-2 and ended up being processed as a
V24.GenericMessage.
So my questions are:
1, should you always route a message based on the MSH-9-1 & MSH-9-2?
2, Is it possible to get the pipe parser / hapi context to throw an
exception if a message is received that does not have a valid message
class. (note we use our own custom ModelClassFactory so we could trap the
failed lookup at that point)
Thanks
-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
