[HAPI-devel] How should you deal with an ADT^M02

[Mike M. <mi...@th...>]

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