Hi,
I'm sorry I haven't answered earlier :(
The message you have is indeed incorrect !
It should indeed be better if HAPI threw an exception ... but it
doesn't in the current version.
I don't know the situation in which you encounter this issue, but to
my opinion the only solution is to ask t
Hello,
i know that OBR is Not Repeatable, and it is configured as Not
Repeatable on the model.. So i expect that, if i have 3 OBR Segments
after an ORC in my message, the HAPI PipeParser will throw an exception.
Instead of this i find 1 OBR inside the ORDER_DETAIL Group, which is
correct, and
Hello all,
Somebody can explain me what happens in this case?
I need this information to finish a parser
Greetings,
Fabio
Fabio Daprile wrote:
> Hello all,
>
> while parsing an ORM_O01 message i found what i think is an error.
> I parse it first with the PipeParser and after that with the
Hello,
this is the definition of the Message structure. the segment OBR cannot
be repeated, and there is no OBR after the OBSERVATION GROUP.
MESSAGE SEGMENT HL7GROUPREPETITIONALOPTIONAL
ORM_O01 MSH 0 0
ORM_O01 NTE 1
Hello all,
while parsing an ORM_O01 message i found what i think is an error.
I parse it first with the PipeParser and after that with the
DefaultXMLParser.
here is the message:
MSH|^~\\&|VERBENA|PRAEZISION|RIS|SYNCROMED|20070828135556+||ORM^O01|5366|P|2.5|
PID|||410379^^^PRAEZ||MORCHI^ANTO
5 matches
Mail list logo
