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

[Archie C. <ar...@de...>]

Tripp, Bryan wrote:
> That's how HAPI was first implemented actually, and I agree it's the 
> safest.  It was changed because there were several complaints from 
> people who use non-standard messages, and because the HL7 spec says that 
> unexpected segments are to be ignored (presumably so that compliant 
> processors don't choke on messages with local additions).  How about 
> making this a configurable option in HAPI 0.5, i.e. the options would be: 
>  
> 1) Fail if there are any unexpected segments
> 2) Fail if there are any unexpected non-Z segments 
> 3) Fail if any required segments are missing 
> 4) Try to parse everything  

That would be nice... my question though is whether the heuristic
for option #4 can be improved to handle an unknown non-Z segment
in the middle of a message. What it does now is not quite right.

Thanks,
-Archie

__________________________________________________________________________
Archie Cobbs      *        CTO, Awarix        *      http://www.awarix.com


*
Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
*