|
PID shows up beneath PATIENT_RESULT.PATIENT because HAPI follows the
rules for XML Encoding described in the normative "HL7 Version 2: XML
Encoding Syntax" specification. Section 2.4.1 describes how groups of
segments are represented and observes that "There was no explicit way
to express these groups in the tradition v2 "vertical bar" encoding..." As for why group names differ in 2.3 vs 2.3.1,2.4,2.5... I would assume this is because the group names are defined differently in the database for v.2.3. As to the behaviour when you feed multiple messages to the parser... Are you batching them using the batch method described in the spec, or are you just appending a bunch of messages together and feeding that to the parser? PK deg2cents wrote: I think that your response refers to how HAPI expresses the HL7. My question is more "Why does the HAPI schema not reflect the layout of the HL7 EDI segments?" For example in HL7 multiple ORU^R01 requires multiple MSH, but HAPI collects these into a single MSH. The positioning of the PID is also different.Of course I realize that it is way too late to change this in HAPI. - Don --
Patrick
Kobly,
CISSP
T: 403-274-9033 C: 403-463-6141 F: 866-786-9459 56 388 Sandarac Dr NW
|
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
_______________________________________________ Hl7api-devel mailing list Hl7api-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hl7api-devel
