Re: [HAPI-devel] Parser and Message Structure

Hi Frederic, ADT^A28 messages actually share the same structure as the ADT^A05 according to the HL7 spec, so the parser would be parsing into an ADT_A05 message type regardless of whether MSH-9-3 was set or not. This behaviour is one of the more confusing aspects of HAPI for sure, and for that ma

Re: [HAPI-devel] HL7 parsing question

Hi Depeche, A24 is kind of a weird message structure, in that it has two distinct PID segments in the same group. To access the second one, use "/PID2-x-x" instead of "/PID-x-x" in your terser paths. Note that you can find the appropriate value to use in situations like this using the HAPI Xref <

Re: [HAPI-devel] HL7 parsing question

Hi, I am using HAPI to parse a Link Patient Information (Event A24) message. In order to set PID 3.1 and PID 3.4 of Patient (1) Identification as well as to set PID 3.1 and PID 3.4 of Patient (2) Identification, what shall I use? MSH|^~\&|AAA|BBB|CCC|DDD|20100617093730||ADT^A24|MSG1

Re: [HAPI-devel] PID generation in RSP_K22.QUERY_RESPONSE: solved

Hi, How can we generate PIDs for ADT^A24 message? Any idea Thanks, depeche Éamonn Ó Nualláin wrote: > > Hi, > > Just in case anyone runs into the same issue > > Regards, > > Éamonn > > String PID = "PID"; > RSP_K22 rsp = new RSP_K22(); > RSP_K22_QUERY_RESPONSE queryRespon