DICOM interface setup

So the PACS system is not providing a file stored on disk?

I have never worked with the DICOM protocol but if it is a type of real time connection, then is there a specific acknowledgment they require (such as one finds with HL/7)? If so you will need a Tcl proc to create the acknowledgment I would think.

If your intent is to simply pass the DICOM data as is, then a file based integration might work best if the PACS system can indeed place a DICOM ‘message’ in a file.

I suspect some of the time delay being experienced is what appears to be parsing of the message as it arrives. I am thinking in a Fileset protocol that would not occur. I also suspect the DICOM messages can be quite large so you need to be sure to integrate in a properly sized Cloverleaf environment.

Also it is quite possible you will need to set the encoding at least for the OB.

It looks like no one responded to the original post.

Hopefully there is someone in the community who has experienced what you are trying to do and has a recommendation or 2.

In Looking at your attachment I see the last thing in the log is:

[msg :Msg :ERR /0:rad_dicom_xlate:01/17/2020 08:34:09] CommandField is expected to be the third element in the dicom message, but the third one in message content is <000E,0000>.

[xlt :rout:ERR /0:rad_dicom_xlate:01/17/2020 08:34:09] Failed to get Dicom Trxid. failed: Cannot get CommandCode from message content

So I suspect nothing is going to the destination thread. The ‘message’ is ending up in the Error Database I suspect.

Here is the encoding section from the DICOM standard (link:

http://dicom.nema.org/dicom/2013/output/chtml/part05/chapter_6.html

)

That link can be a starting point to the entire DICOM standard if you want to dig deeper.

Each provider/receiver of the DICOM message is supposed to provide a conformance report. I suspect that should tell you a lot about how they are using DICOM including the encoding scheme in use and expected.

I am not sure if you need anything besides hci_static raw route but if you do need a TrxId perhaps the doc will help you decide which field, etc. should contain the TrxId.

Please note that we continue to maintain our DICOM support.  Both 19.1.1 and 6.2.4+ patches have some fixes for DICOM, mainly around support for private tags.