Hi Bryan-Attached is a test file I've been using for in my unit tests for the
transformation. The file was generated using a conformance profile generated
by VA's Message Workbench and a sample message generated by NIST's Message
Maker. It conforms to the layout described in my original message. I've also
done a rough comparison of the test file against the live data we're receiving
from the laboratory in question and the two match. If you run the message
through the parser I think you'll see the behavior I'm describing. If you (or
your team) have time, maybe you can take a look at the output and comment on
it?Thanks,Jim> Date: Thu, 22 Mar 2007 17:13:10 -0400> From: [EMAIL PROTECTED]>
To: [EMAIL PROTECTED]> Subject: Re: [HAPI-devel] Placement of ZLR segment> CC:
hl7api-devel@lists.sourceforge.net> > Hi Jim,> > No, you have to customize the
message class to put a Z-segment in the> middle of a group. Actually looking at
your output structure, the ZLR> should appear after the OBX group ... is that
not happening?> > Bryan> > On 3/13/07, Jim Krygowski <[EMAIL PROTECTED]>
wrote:> >> > Hey All-> >> > I'm in the middle of coding a 2.3.z (as defined by
CDC's ELR guide) to 2.3.1> > message transformer and have run into something of
a problem. The ORU^R01> > message I'm transforming looks like this:> >> > MSH>
> PID> > {> > OBR> > ZLR> > {> > OBX> > { [ NTE ] }> > }> > }> >> >
but what I'm getting out of HAPI once I parse the message looks like this:> >>
> MSH> > PID> > {> > OBR> > {> > ZLR> > OBX> > { [ NTE ] }> > }>
> }> >> > So a message like:> > MSH...> > PID...> > OBR...> > ZLR...> >
OBX|1...> >> > ends up with two observations, one containing the ZLR and a
blank OBX and> > the other for the OBX:> >> >
response(0).order_observation(0).observation(0) contains> > ZLR and an empty
OBX> > response(0).order_obsercation(0).observation(1) contains> > OBX 1> >> >
I suppose there's no way for HAPI to know a priori that the ZLR in this> >
message should be associated with the order_observation group and not the> >
observation group so is it possible to direct the parser to associate it in> >
that fashion? The issue is clearly something I can code around but it would> >
be cleaner if I didn't have to.> >> > Thanks,> >> > Jim> >> >> >> >> >> >> >> >
________________________________> > Get news, entertainment and everything you
care about at Live.com. Check it> > out!> >
-------------------------------------------------------------------------> >
Take Surveys. Earn Cash. Influence the Future of IT> > Join SourceForge.net's
Techsay panel and you'll get the chance to share your> > opinions on IT &
business topics through brief surveys-and earn cash> >
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV> >
_______________________________________________> > Hl7api-devel mailing list> >
Hl7api-devel@lists.sourceforge.net> >
https://lists.sourceforge.net/lists/listinfo/hl7api-devel> >> >
_________________________________________________________________
Live Search Maps – find all the local information you need, right when you need
it.
http://maps.live.com/?icid=wlmtag2&FOR M=MGAC01
sample2.3.z.txt
Description: application/binary
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Hl7api-devel mailing list Hl7api-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hl7api-devel
