Hello,
we use Summit's HL7 Adapter instead of the Microsoft HL7 Adapter.
Summit hasn't been able to solve this problem, and I was hoping
someone knew a solution. Any help is appreciated.
Incoming messages from our HIS where the Patient's last name (PID.5) =
"PIDGEON" get scrambled:
MSH|^~\&|||||200804301402||ADT^A05||P|2.1|
PID|1||M#########|||PIDGEON^FIRSTNAME^^^^||...
generatesMSH|^~\&|||||200804301402||ADT^A05|||2.1|||||||||||
EVN|A05|200804301402||||||
PIDGEON^FIRSTNAME^^^^|1||...
Notice how the PID segment is assumed to start with the value in PID.
5? Below is the PID Schema:
- <xs:element minOccurs="0" name="PID">
- <xs:annotation>
- <xs:appinfo>
<b:recordInfo structure="delimited"
preserve_delimiter_for_empty_data="true"
suppress_trailing_delimiters="false"
tag_name="PID"
child_order="postfix"
child_delimiter_type="char"
child_delimiter="|"
sequence_number="1" />
</xs:appinfo>
</xs:annotation>
