With NHapi.Base.dll version 2.3.0 I was able to parse a message like the following, while I can't with the latest version (2.5.0.6).
Here is the message:
MSH|^~\&|sys1|sys1|sys2|sys2|20180503174921||ORM^O01|1234567890|P|2.4
EVN||20180503
PID|||1^^^XXX~2^^^YYY||LastName^FirstName||19660429|F
PV1||I|3906||||||||||||||||100001
ORC|CA|1410|3121||CA
OBR|1|1410|3121|RX50^ADDOME SUPINO
I know that the EVN segment is not expected in a ORM^O01 message, but this is what I receive from the external system. With the old version of the library the message was ok. If I filter out the EVN segment the message is correctly parsed, but I don't like to manually filter out the message content differently for each kind of message.
I don't receive an error or an exception, simply the PID and PV1 structures are empty.
Any suggestion?
With NHapi.Base.dll version 2.3.0 I was able to parse a message like the following, while I can't with the latest version (2.5.0.6).
Here is the message:
MSH|^~\&|sys1|sys1|sys2|sys2|20180503174921||ORM^O01|1234567890|P|2.4EVN||20180503PID|||1^^^XXX~2^^^YYY||LastName^FirstName||19660429|FPV1||I|3906||||||||||||||||100001ORC|CA|1410|3121||CAOBR|1|1410|3121|RX50^ADDOME SUPINOI know that the EVN segment is not expected in a ORM^O01 message, but this is what I receive from the external system. With the old version of the library the message was ok. If I filter out the EVN segment the message is correctly parsed, but I don't like to manually filter out the message content differently for each kind of message.
I don't receive an error or an exception, simply the PID and PV1 structures are empty.
Any suggestion?