We are trying to validate the structure of an HL7 message at runtime by
comparing the Segment names and their respective order with the structure
implicit the messages corresponding structure. We do this by comparing an
ordered List of segments derived from a deep call to getNames() method of the
Message with HAPI's ReadOnlyMessageIterator that collects the actual segments
from the message. What we have found is that with Merge events the structure
names are different than the actual segments used in the message.
2 Examples:
1. a HAPI ADT_A17 names it's 2nd PID as "PID2" while the HL7 spec simply
has 2 PIDs in the message
2. For merge events certain segments are derived from a group, such as an
A39 which gets the PID from the PATIENT group. The actual HL7 for an A39
however does not reflect this group structure.
Are there any recommendations for getting around this? Thanks.
----------------------
Melissa Rabin | Senior Software Engineer | Healthcare & Science | Thomson
Reuters | W 215 463 4461 | M 267 271 2227
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Hl7api-devel mailing list
Hl7api-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hl7api-devel
