Re: [HAPI-devel] MLLP errors while sending an ORU^O01 message

It does not seem to complain about your message, but about the Lower Layer encapsulation. It says "Expected byte '11'"  so, given that dec 11= hex 0B (namely VT), I would rather check your MLLP encapsulation ( 0B msg 1C 0D) Is that what you are asking? Hope that helps Dan

Re: [HAPI-devel] NCK

Hi João, The structure NMD_N02 is available in HAPI(since 2.3.1)http://hl7api.sourceforge.net/v231/apidocs/ca/uhn/hl7v2/model/v231/message/NMD_N02.html It is not good practice to create new messages, let alone without event type or version. As a rule of thumb you should inspect the standard befor

Re: [HAPI-devel] ORM_O01

();   pp.setValidationContext(myContext); pp.parse(strReceivedMessage); Regards Daniel Nebot IZASA --- On Wed, 12/28/11, Garrett McTear wrote: From: Garrett McTear Subject: Re: [HAPI-devel] ORM_O01 To: "Daniel Nebot" Date: Wednesday, December 28, 2011, 8:48 PM Daniel, Thanks fo

Re: [HAPI-devel] Help- ORU and PID

ca.uhn.hl7v2.model.v23.message.ORU_R01 kk = new ca.uhn.hl7v2.model.v23.message.ORU_R01(); ca.uhn.hl7v2.model.v23.segment.PID pid = kk.getRESPONSE(0).getPATIENT().getPID(); and pid.getX(..) Hope that helps Daniel Nebot Lucas Gonz <[EMAIL PROTECTED]> wrote: Hello, I am work

Re: [HAPI-devel] OML O21 does not parse more than one ORDER group?

age, and it seems to have had the desired effect: the message now parses into an OML_O21_ORDER (rep 0) and an OML_O21_ORDER (rep 1) Charles Fisher Division of Epidemiology New York State Dept. of Health 518-474-2735

[HAPI-devel] OML O21 does not parse more than one ORDER group?

Hi there, I am trying to parse a rather simple message with more than one order into it, like the one below. Unfortunately, HAPI does not seem to go further than the first ORC-OBR block. I have looked to the source code but I cannot see why. This really urges for me... I would be very grateful