Orthanc is now doing a great advantage for us. Our covid ward scu workstations can now query and retrieve chest x-ray follow ups of all our covid patients. The only problem for us, is that, although orthanc accepts all properly cropped images, we still have about 3000 unproperly cropped history radiographs, that we still can’t send and store. These history radiographs are badly needed for comparison studies. I now have this perplexing problem, if I should uncrop and recrop all these 3000 images one by 1 on my own. I think I can’t accomplish it. Within my 8 hour shift, I still have so many radiography cases to attend to. I have set, Verbose and Trace logs just right after I have sent an example of this unproperly cropped image. And it’s attached on this conversation for everyone to see, including our server’s orthanc.json configuration file. 
orthanc_jason.txt (36 KB)
verbose_trace_logs.txt (26.5 KB)
Hi,
Without looking at the logs, I was going to suggest you to enable the UnknownSopClassAccepted configuration: https://hg.orthanc-server.com/orthanc/file/tip/OrthancServer/Resources/Configuration.json#l159
From the logs, it seems that Orthanc times-out after 30 seconds because the DEVELOPER modality did not send any data. I doubt that increasing the DicomScpTimeout configuration will help.
Best regards,
Alain
Hello Alain,
Thank you very much for helping Alain. I also think very much, you are correct. That it goes along the lines of the S.O.P. class, not being accepted by Orthanc. Because the trace log itself says orthanc can not accept the abstract syntax of every unproperly cropped images, and the abstract syntax pertains to the modality type which also defines the SOP class. And yes, I also think you got it right, orthanc can not accept it as a Computed Radiography modality anymore, every time the image is cropped outside the 14 by 17 cassette border limit. The very sad thing is Alain, I already enabled orthanc.json to accept all unknown SOP classes and have already increased the SCP timeout at 170 seconds, yet still, ORTHANC does not accept unproperly cropped images. Could there be any more settings or any rest API commands that we can tweak?
Hi,
The fact that one abstract syntax is not supported does not mean that the association fails. The logs seem to show that it succeeds (and it also times out later).
For Orthanc, the location of the crop makes no difference but, for the cropping tool it does. In my opinion, the cropping tool just doesn’t send the images that are cropped outside the cassette.
Best regards,
Alain
Sorry for the very late reply. Because of your word of advice, we figured out a setting to send without cropping. We sent it all. Thank you very much.