Written by

Sales Engineer at InterSystems Iberia
MOD
Article Luis Angel Pérez Ramos · 4 hr ago 2m read

Problems linking IRIS with DICOM modalities?

As you all probably know, Health Connect / IRIS for Health natively supports DICOM messaging, and many of you will have used it daily. Well, I recently discovered a rather insidious little issue that our beloved @Alberto Fuentes gave me the solution.

We (I) will call this phenomenon the Creosote effect (those of you who know Monty Python will understand the reference, for the rest you can see the sketch here )

Why Monty Python's Mr Creosote is the ultimate gross-out icon - Yahoo  Movies UK

Mr. Creosote is a voluminous gentleman accustomed to sumptuous meals, and after having ingested the equivalent of the gross domestic product of Burkina Faso, it is a fine chocolate bar that finally makes him explode.

Well, after this circumlocution, let's get to the issue.

Failures linking modalities with IRIS

Sometimes, after having a DICOM integration working perfectly, when adding a new mode to send or receive DICOM messages, it doesn't work, returning an error like this:

 
ERROR <EnsDICOM>AbstractSyntaxNotAccepted: Abstract Syntax '1.2.840.10008.5.1.4.31' rejected between between peers 'IRIS' and 'ORTHANC'


In this example we have a PACS called ORTHANC and our IRIS instance that tries to send a Worklist request using its corresponding DICOM message, as you can see it clearly indicates that the connection is being rejected with the indicated Abstract Syntax.

If we go to our settings we will see that we have correctly configured the connection between IRIS and ORTHANC:


And furthermore, in the Presentation Context option we have defined said Abstract Syntax:


So why isn't it detecting our configuration? Well, it's the Creosote effect. We've added so many Abstract Syntax to our configuration that when it tries to find the last one we added, IRIS is unable to locate it and throws the error we showed earlier.

How can we avoid this error? It's very simple: by avoiding overloading our association context configuration with syntax that we won't be using. In my case, I created a new name for my IRIS called IRIS_WL:


To which I added only the Abstract Syntax corresponding to the Worklist request:


And that was enough to get my production working properly again.

I hope you find this advice helpful!