Mismatched IR Tag error

[Robert Denny]

One process logs all these Warning messages. Any suggestions on how to troubleshoot this issue? We would like to fix what ever is causing this issue.

I have talked with Support and they suggested that I turn on ‘Enable All” in the EO config control.

12/01/2009 10:04:31 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:31 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:31 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:31 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:31 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:31 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:31 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:31 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:31 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:31 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:31 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:31 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:31 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:31 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:31 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:31 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:31 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:31 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:32 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:32 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:32 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:32 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:32 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:32 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:34 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:34 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:34 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:44 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:44 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:44 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:44 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:44 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

12/01/2009 10:04:44 [msg :RecD:WARN/0:   Pacs_xlate] Mismatched IR Tags

Topic

[Max Drown (Infor)]

I usually see that error when I have a syntax problem with an IF statement in an xlate.

-- Max Drown (Infor)

[Tom Rioux]

You may also see that if your variant has changed or is different somehow from what is being shown in an existing xlate.  I’d check the field notations in the pacs_xlate to make sure they match what is expected from the variant.

Hope this helps…

Tom Rioux

[Bob Richardson]

Greetings,

   Another problem may be that the data type of the receiving field may be numeric and the inbound data is a string type.  This can generate the IR Mismatched error as well.   Usually, you can change the data types in your variant to match what is sent.

  Tracking down which field is causing this error may be your biggest problem to solve – if you are running CIS5.6, you can deactivate lines of logic; run the tester using the problem message; and identify the culprit.

Otherwise, maybe create a clone xlate and remove lines of logic as needed to isolate the xlate action involved.

  Good luck!

[Tom Rioux]

In tracking down the error in the xlate, if I’m not mistaken, I believe the testing tool will give you a hint where it is.  In running messages through a xlate tester with this error, the error will start at the segment where it first encounters the error.  

For example, I’ve seen it where my error was in the PV1 segment and when I run the message throug the tester, the MSH, EVN, and PID segments were returned as normal but then it was followed by the Mismatch IR Tags error.

Hope this helps…

Tom Rioux

[Robert Denny]

I have pulled a message from the inbound thread and using the testing tool, tested the message on two of the translation files that used in this thread.

In both translations files I get the Mismatched IR tag message before any of the segments are listed. Here is an example of the output from one translation.

Please Wait ……

Command Issued: hcixlttest -d 1 -f eof med_ord_pacs_in.xlt E:/quovadx/qdx5.3/integrator/shslive/resend/pacsormirtag.txt

Command output:

MESSAGE 1

[0:TEST] Mismatched IR Tags

[0:TEST] Mismatched IR Tags

[0:TEST] Mismatched IR Tags

0(0).MSH(0)  :  >|^~&||AGH|||200912011030||ADT^A08|PACS-ADT.1.28640892|P|2.3|||AL|NE<

Would this suggest that the error is within the variant, or could it still be within the translation? I ask because the warnings appear before the MSH segment of the message.

[Dirk Engels]

Hi Robert,

you’ll have to check all the hl7 pathnames. The mismatch IR tag error usually indicates that you are using a wrong pathname in your translation. This mostly occurs if you change the record definition of your inbound or outbound hl7 variant, so that the segments or fields or now in a different group then before.

Just check out all pathname by just clicking it in the translation inbound or outbound message format column and check what it is you action summary. Then you will find the problem.

By the way: The problem could also occur if you are using a tcl proc which uses the hl7 pathname in an xpmfetch or xpmstore or grmfetch or grmstore command.

If you’re using tcl or java procs you may also check out these.

Greetings from good old Germany.

Dirk

[Author]

Replies