Orthanc Plugins

Hello ,

I installed the Docker image on Linux and I noticed a particular behavior while uploading a DICOM image (with uncompressed transfer syntax 1.2.840.10008.1.2.1 Explicit VR Little Endian) to Orthanc, when I get this particular image I am receiving image with a different transfer syntax which (1.2.840.10008. JPEG Lossless, Nonhierarchical, First- Order Prediction). Even though I disabled the “accepted transfer syntax” Orthanc config file still I see the above behavior.

On further investigation I found that Orthanc does not support automatic conversion of transfer syntax of incoming DICOM images (https://groups.google.com/forum/#!topic/orthanc-users/WyHcABcj4OA

) however, it is mentioned that it can be possible using Script or Plugin (to convert the transfer syntax). My question to you is, whether the Docker image which you provide has any script or Plugin which does this conversion (uncompressed → Jpeg)?

Please let me know if further information is needed.

Thanks in advance

No, by default, there’s no lua script or no re-compression

You might be interested in the following Lua sample that is part of the Orthanc source distribution:

I installed docker using this command from this source:

docker -D -d -v [LOCAL-STORAGE-DIRECTORY]:/var/lib/orthanc/db -p 4242:4242 -p 8042:8042 --name pacs-with-plugins jodogne/orthanc-plugins

Does this repo contains any plugins which is compressing the image before getting it ?

In the plugin folder which is generated there were no plugins

As already answered by Alain, no, there is no such script/plugin installed by default on the Docker images.

Install the Lua script by fine-tuning the Docker configuration:

Sorry but still I am not clear that why I am getting image with a different transfer syntax which (1.2.840.10008. JPEG Lossless, Nonhierarchical, First- Order Prediction) on doing WADO query. I didn’t install any plugin separately.

Why are you talking about WADO now? This is fully unrelated to your original post.

Please carefully, precisely and completely explain your use case, and give the exact steps to reproduce your issue: