Hi Authors,
I see that dcm4chee supports passing transfer syntax parameter into the wado-rui request. 4.2.6. WADO-URI Specification — DICOM Conformance Statement dcm4che Archive 5 . I wonder if orthanc should support that parameter also ?
Hi Authors,
I see that dcm4chee supports passing transfer syntax parameter into the wado-rui request. 4.2.6. WADO-URI Specification — DICOM Conformance Statement dcm4che Archive 5 . I wonder if orthanc should support that parameter also ?
Hello,
This is not supported in the WADO-URI API as of version 1.17 of the DICOMweb plugin, as can be seen in the Status.txt
file.
However, it is supported WADO-RS API. For instance, the following command will transcode a DICOM instance from our demo server into a JPEG2k DICOM instance:
$ curl https://orthanc.uclouvain.be/demo/dicom-web/studies/1.3.6.1.4.1.14519.5.2.1.2193.7172.847236098565581057121195872945/series/1.3.6.1.4.1.14519.5.2.1.2193.7172.215111709746721743805035350686/instances/1.3.6.1.4.1.14519.5.2.1.2193.7172.214563966745896937235684272125 -H 'Accept: multipart/related; type=application/dicom; transfer-syntax=1.2.840.10008.1.2.4.90' > /tmp/jpeg2k.dcm
As always, if you need such a feature in the context of a scientific project, feel free to contact my research lab to have this feature implemented.
Kind Regards,
Sébastien-
Thanks a lot Sébastien,
I think Wado-rs route returns Multipart response, but not raw dicom file. Hence, There is an extra step to parse Multipart response to get the dicom file. I might think to create a Pull Request to Orthanc team to merge my code of supporting transfer syntax param in wado-uri url.