Xlate issue

[Ken Seachrist]

🙄   I am encountering a problem that I have seen in this forum in differing “flavors”.  I am using one variant for an inbound MDM^T02 message and another variant for an outbound ORU message.  When I test it in the testing tool, I get a message that says:  The # 4 segment encountered ‘OBR’ is not defined for message type ‘MDM_T02’.  Segment ignored.  There is no OBR segment either defined or in the inbound message.  There IS an OBR segment on the outbound message.  I tried moving something to the ORC segment, just in case it would error out if the ORC was blank, but that didn’t help either.  Has anybody else run into this and found a solution?  Thanks.

Topic

[Mike Grieger]

That would then mean that your outbound variant has OBR defined as a REQUIRED segment, correct?  If your messages do not contain a segment that is required, change the variant so the segments in question are OPTIONAL.

[Ken Seachrist]

That is what I thought, but the OBR IS optional in the outbound variant.  I even went so far as to add the OBR to the inbound variant as optional, but I still have the same message.  What was most confusing was that before I put the OBR in the MDM (inbound) variant, the message was telling me that the OBR can’t be found in the MDM, even though there was no OBR in the inbound message!

[James Cobane]

Ken,

One thing I would double-check is the actual value in the Message Type field (MSH:9) compared to the message type HL7 layout you are using in the xlate.  If you are doing a PATHCOPY, or copying the input value in MSH:9 to the output record, the testing tool is going to validate against the record layout based on the value in MSH:9; i.e. if MDM^T02 is being copied to MSH:9 in the outbound record, then I think the tester is going to validate against the MDM_T02 outbound layout in your variant, rather than the ORU layout that is defined in your xlate.

Hope this helps.

Jim Cobane

Henry Ford Health

[Author]

Replies