[HAPI-devel] Datatpe RP in OBX spews an error

2012-11-19 Thread Carlos Oliva
Is there a way in which I can exclude some data types or segments from the validation? I am getting some ORU messages with a data type RP in one of the OBX segments. The parser spews an error when it tries to parse the segment. I have found very little information about the data type RP. This i

Re: [HAPI-devel] Handling HL7 ambiguity in OMG message

2012-11-19 Thread christian ohr
OMG_O19 is one of the messages which may be hard to parse unambiguously. The problem lies in the fact that the ORDER_PRIOR group begins with an *optional* ORC segment. So, the sequence ORC TQ1 OBR can be parsed in both ways Søren described it, and there is virtually no means for HAPI to pick the "

Re: [HAPI-devel] First Question

2012-11-19 Thread Rahul Somasunderam
Frank, HAPI is implemented in Java. So you might be able to leverage it if you're using a Java runtime for PHP or the PHP java bridge like http://php.net/manual/en/book.java.php. I haven't used either. Sorry! R, rahul On Nov 18, 2012, at 11:36 AM, Frank Indelicato wrote: > Thank you for you

Re: [HAPI-devel] Handling HL7 ambiguity in OMG message

2012-11-19 Thread Jens Villadsen
Okay, I get your point - the keywords in the note was "newly defined" ... I'm just thinking that it's a weird way of maintaining backwards compatibility - gotta blame that on the specification, this is of course not HAPI's fault ;) If, for instance the OMG^O19 was defined in, say the 2.4 spec (whi

Re: [HAPI-devel] Datatpe RP in OBX spews an error

2012-11-19 Thread christian ohr
RP is a resource pointer, but its first component is a plain ST. What is the HL7 and HAPI version you are using? Can you provide the complete message? Is there a more detailed stacktrace? RP did not exist until HL7 v2.3, but with later versions I had no problems when I pasted the segment into a O

Re: [HAPI-devel] Handling HL7 ambiguity in OMG message

2012-11-19 Thread christian ohr
The definition for OMG^O19 did not change in 2.5 - the first segment in that group is still optional. I don't think this statement in the spec does anything about this - it's just that any new messages structures (introduced in 2.5 and after) may not contain optional segments as first element in a

Re: [HAPI-devel] Handling HL7 ambiguity in OMG message

2012-11-19 Thread Jens Kristian Villadsen
I agree - As far as I know the OMG^O19 did not change in 2.5. I just find it troublesome that new 'global rules' such as the ones in section 2.5.2 does not apply for all messages, but only newly defined. I guess I'll just have to live with that. 2012/11/20 christian ohr > > The definition for O