uently a call to getINSURANCE(), which uses the short
> name, returns a null.
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> *From:* Michael Conner
> *Sent:* Wednesday, August 15, 2012 11:37 AM
> *To:* 'James Agnew'
> *Cc:* [email protected]
11:37 AM
To: 'James Agnew'
Cc: [email protected]
Subject: RE: [HAPI-devel] Custom Segments immediately following a group
Re: ambiguous. OK, that's pretty much what I thought.
Re: Custom Model: I went down this path initially till I realized that
it would be
m: [email protected] [mailto:[email protected]] On Behalf Of
James Agnew
Sent: Wednesday, August 15, 2012 11:11 AM
To: Michael Conner
Cc: [email protected]
Subject: Re: [HAPI-devel] Custom Segments immediately following a group
Hi Michael,
Unfortunately this is an area whe
Hi Michael,
Unfortunately this is an area where the HL7 specification is ambiguous
about how your message should be correctly parsed. HAPI generally errs on
the side of putting unexpected segments closest in the structure to the
segment immediately before it, which in your case sounds like it's no
We've got a message where we want to have a custom segment at the end of
an Patient Admit, ADT A01 message. We don't have anything between IN1
and the custom segment.
...
[{ --- INSURANCE begin
IN1Insurance
[ IN2 ]Insurance Additional Info.
5 matches
Mail list logo
