· Jul 5

Problem with handling Nacks/Errors on IRIS

Recently, we experienced a very strange behaviour on Healthconnect IRIS:

We used to receive NACKs with the following format from a third party system (Status: completed):

Suddenly, we noticed a change in the behaviour when we receive a NACK, where it's being handled now as an error (status: error).. We haven't changed any configuration on TIE/third party system: 


This is a TCP operation, and we're using the following settings:

Can anyone please provide me a logical explanation of what's going on? Did I miss anything?

Product version: IRIS 2020.1
$ZV: IRIS for Windows (x86-64) 2021.1 (Build 215U) Wed Jun 9 2021 09:39:22 EDT [HealthConnect:3.3.0] [HealthConnect:3.3.0]
Discussion (4)3
Log in or sign up to continue

I'm confused, it seems that the error you have posted it's not from the Business Operation with the setting posted.

The error says that the "Reply Code Action" is ':?R=RF,:?E=S,:~=S,?A=C,*=S,:I?=W' while in your screenshot is E=F.

What was the "Reply Code Action" setting when the error occurred?

In addition, the two traces looks different, the first has a sync incoming request, the second async.

Is the Business Operation the same component/host?

How confident are you that nothing has changed in the NACKs being returned by the remote system? Is it possible that the value in MSA:1 used to be something other than AE? Is it possible that previous NACKs didn't have an MSA segment?

In the HL7 code table for MSA:1, "AE" indicates an error, so IRIS considers that an error and triggers the rule "E=F".