By default, the “/studies/…/series/…/instances/…/frames/…” URI of DICOMweb transcodes the frame content to transfer syntax “1.2.840.10008.1.2.1” (explicit VR Little Endian). This explains why your frame is larger that the source DICOM file.
If you want to control the transfer syntax for the resulting frame, you can set the “Accept” HTTP header. For instance, here is how to transcode to JPEG:
You could also consider using the “/studies/…/series/…/instances/…” URI, as this one won’t transcode the DICOM file.
It would be very nice and extremely useful if you could consider contributing to the Orthanc project by writing an article on your deployment for public hospitals in Chile. We need this kind of information to sustain the development of Orthanc in the long-term!
Thanks for your answer. We will surely write about our experience using Orthanc and Ohif.
Chile is a very long country. Especially in the south, there are regions in extreme areas with 100,000 inhabitants (or less). This implies that it is not possible to have all the specialists in each of our cities. In this context, telemedicine plays an important role, allowing professionals from other cities to diagnose patients in one hour. This is a huge leap for patients who, a few years ago, had to travel 2,000 km for an exam.
About the solution that you comment, adding the header gives me the following error and then the application crashes: “DCT coefficient out of range orthanc”.
About using the “/studies/…/series/…/instances/…” URI, work fine but OHIF use the other endpoint. There is any case of OHIF configured without the “frames/1” path?