[HAPI-devel] ADT^A13 bad parse

[Archie C. <ar...@de...>]

We received an ADT^A13 message that has "2.2" in the MSH.12 field,
but contained these segments: MSH EVN PID PD1 NK1 PV1 PV2 OBX AL1
DG1 DG1 GT1 IN1 IN2 ..

Note that the ability to include the "PD1" segment was added in 2.3.
So technically this is a bogus message because it says "2.2" but has
a PD1 segment (right?).

In any case, HAPI happily parses this message but the resulting XML
contains information in the wrong places, etc. For example, the PV1.3
information ends up in ADT_A13.IN1IN2IN3/NK1/NK1.40.

So although it's nice that HAPI handles this message at all, it seems
like it doesn't do so very gracefully. Is this the intended behavior?

Could HAPI be configured to try a later version of the spec if the
message doesn't parse correctly, instead of putting things in the
wrong field? It seems like in practice the MSH.12 field is sometimes
just more of a hint than reality.

Thanks,
-Archie

__________________________________________________________________________
Archie Cobbs      *        CTO, Awarix        *      http://www.awarix.com