RE: [HAPI-devel] ADT^A13 bad parse

[Tripp, B. <Bry...@uh...>]

Hi Archie,=20
=20
> This would fine with me, but it doesn't seem like this is what HAPI
> currently does. Instead, at least in the example I saw, it put *all*
> segements following the unknown segment at the end of the=20
> message. In my
> example, the unkown segment caused the XML tags to get moved=20
> like this:
>=20
>    ADT_A13/NK1 -> ADT_A13.IN1IN2IN3/NK1
>    ADT_A13/PV1 -> ADT_A13.IN1IN2IN3/PV1
>    ADT_A13/OBX -> ADT_A13.IN1IN2IN3/OBX
>=20
> In the actual HL7 message, NK1, PV1, OBX, etc. came after the unknown
> segment but otherwise in their rightful places.

If you have an unexpected segment, it goes at the end of the current =
group
(or end of the first subgroup reached), which is the only legal option.
Then segments after it have to go after it, again the only legal option.
HAPI won't re-order them. =20

On second thought, maybe we should add another option to that previous =
list,
i.e. quietly drop unexpected segments.  Would that help in your case, or =
did
you want access to that PD1? =20

Bryan=20