Custom hl7 / segment out of order

[Stewart]

I have built a custom hl7 (see screenshot) with ADT_A03 to match what is being sent from the system but still get the following error even though I have the custom hl7.  Any idea on why this error would be generating?
<p style=”padding-left: 30px;”>The # 8 segment encountered ‘DG1’ is out of order when parsing hl7 (2.5.1 meditech) for message type ‘ADT_A03_ADT_A03’.  Segment ignored.</p>
<p style=”padding-left: 30px;”>MSH|9 ADT^A03^ADT_A03</p>
<p style=”padding-left: 30px;”>Segment order being sent from system</p>
<p style=”padding-left: 30px;”>MSH</p>
<p style=”padding-left: 30px;”>EVN</p>
<p style=”padding-left: 30px;”>PID</p>
<p style=”padding-left: 30px;”>PV1</p>
<p style=”padding-left: 30px;”>DG1</p>
<p style=”padding-left: 30px;”>OBX</p>

Attachments:

You must be logged in to view attached files.

Topic

[Vince Angulo]

is this a 2.5.1 interface?  i’ve run into this because the 2.5.1 A03 has the DG1 before OBX and in A01, A04 and A08, DG1 it is after the OBX.  so you have to have an A03 as the basis for the A03 translation configuration.

[Stewart]

It is.  I have found (so far) that A03 in 2.5.1 is the only message that generates the DG1 before OBX.  I’ll update the translation to use this as the bases and see if it resolves the issue.

However, it was my understanding that Cloverleaf would look to the actual message type in MSH|9 to determine what format in the custom hl7 to use.

[Author]

Replies