HL7 xlate Problem

[garry r fisher]

Hi,

I’m xlating a fixed length record to HL7 and I’m having a problem. The same outbound HL7 record is used for a number of maps all without issue except for one. I’ve reworked it a number of times and I still get the same error when I run it through the testing tool on level 1:

MESSAGE 1

[0:TEST] [mid:0x15f48b4] The # 3 segment encountered ‘OBR’ is out of order for message type ‘ORM_O01’.  Segment ignored.

0(0).MSH(0)  :  >|^~&|||||20050823131904||ORM^O01|72|P|2.3< 1(0).0(0).PID(0)  :  >|||11925^^^PAS~HEY0011860^^^HEY~803625^^^ACN< 1(0).1(0).0(0).PV1(0)  :  >|||RXR||||||||||||||||000000001< I’m using HL7 2.3 and ORM_O01 is my outbound format on Cloverleaf v5.3 running on W2K. I can include the input file and the xlate if required. Can anybody help me please? Regards Garry

Topic

[garry r fisher]

Hi,

Attached is the xlate and test file. I don’t think you need the Tcl scripts – they are used in the xlate but I think those lines can be deleted if you don’t want to use them.

Cheers

Garry

[garry r fisher]

Sorry – this may help as well – The FRL for the inbound side of the xlate.

G

[Vince Angulo]

I’m no expert on the orders messages, but I’ve seen this error before when a required segment was missing from an ADT message.   In looking at the standard 2.3 map for an ORM_O01, it looks like an ORC is required for each OBR.  That could be your culprit.

Vince

[garry r fisher]

Resolved – Thanks.

I was mapping to ORC but the inbound field was blank and it was this that was causing me the problem.

Regards

G

[Author]

Replies