OsiriX: STOW-RS operation failed...

[Luiz Eduardo Guida Valmont]

... silently but not quite failed.

Hi!

When trying to export a series from OsiriX into Orthanc, OsiriX reports STOW-RS operation failure. But Orthanc reports no errors (or warnings) and the new series itself does get properly stored in Orthanc as far as I can tell.

I'm probably overlooking something trivial and it's probably OsiriX related, so I'd like to ask for help.

I'm running docker jodogne/orthanc-plugins:1.3.2 exposing port 8042 as 9999. OsiriX is configured to access this node as a DICOMweb and points to the /dicom-web path (and the orthanc:orthanc user from the stock configuration).

Thanks in advance!

Luiz

[Sébastien Jodogne]

Hello,

All the information I personally have about OsiriX and Orthanc is located at this place of the Orthanc Book:

http://book.orthanc-server.com/integrations.html

Regards,

Sébastien-

[p.b...@radpoint.pl]

What version of Osirix are you using? I have the same issue (only when I send through WADO) in 9.5.2 Osirix version. 
That happens all the time. I was going to test it on other Osirix version. 

Pawel

[Luiz Eduardo Guida Valmont]

Hi, Pawel!

I'm using "OsiriX MD ANVISA", which is a version based off of 8.5.2 for brazilian hospitals.

What I came to find out is actually a bug in OsiriX, I suppose. As it is, OsiriX sends "Accept: */*" and an XML body and content type header. Orthanc in turn defaults to JSON when it receives "*/*". That should be no problem because of the Accept header.

BUT

OsiriX expects an XML response.

How can you see this happening / fix it? Configure a dicomweb node pointing to localhost and a random port, like 8888. Set up a netcat "server" redirecting the output to a file. Fire the export. Edit the capture file to "Accept: application/xml" while also recreating the gzip'ed content. Push that to a running Orthanc while capturing the the response with a netcat. Now set up a final netcat "server that will respond with Orthanc's response (which should be a proper one for OsiriX to understand). Fire the same export again. OsiriX should accept with no problems.

In our project I will change a few lines in Orthanc so its default is configurable.

Now that I wrote it it sounds overly complicated. And it is in a sense. Come Monday I'll try and record a video explaining the process. It'll make things clear.

In any case, if you have any questions (and by the way I wrote, you'll most certainly have), please do hit reply and write. I'll gladly answer.

Have a good one! =)

Security Clause
Please note that the contents of this message including its attachments is the information protected from disclosure. If this message is not meant for you, please be warned that disclosing, copying, publishing or using it or any attachments is prohibited. If you received this message by mistake, please inform sender immediately, send the message back and delete it from your system including all the attachments.

--

Luiz Valmont

http://luizvalmont.com

[Sébastien Jodogne]

Hello,

Thanks Luiz for your investigation.

In the current DICOMweb specification, the QIDO-RS answers are expected to be in the JSON format by default ("application/dicom+json" if no "Accept" HTTP header). Check out the following reference:

http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.7.html

This explains why the Orthanc DICOMweb switched from XML to JSON in its 0.5 release. The relevant changeset is the following:

https://bitbucket.org/sjodogne/orthanc-dicomweb/commits/28d017f770a30639088aace2cecc21d1cc4206cc

Would it be possible for you to give a try with the DICOMweb 0.4 release (that was still using XML by default)?

https://www.orthanc-server.com/browse.php?path=/plugin-dicom-web

If this works, we could consider adding a configuration option for the DICOMweb plugin to bypass this part of the specification, and force the use of XML answers.

Regards,

Sébastien-

[Antoine Rosset]

There is currently a bug in Orthanc: 

HTTP Content-Type should be :

type="application/dicom”;

instead of

type=application/dicom

(http://dicom.nema.org/medical/dicom/current/output/html/part18.html)

The "type" parameter is required. It contains the media type of the "root" body part. It always contains the special character "/" and thus requires quote marks.

[Paweł Bożek]

I confirm that the issue exists with the older versions of OsiriX. However the latests and older Osirix's versions works fine (through WADO) with dcm4chee and one more local-WADO pacs. The problem seems to be connected with Orthanc itself - it exist only with orthanc. 

Thank you Luiz for workaround.
Antoine is there a way to view detailed DICOM communication logs in OsiriX (not general ones from GUI/Menu level)? 

Reagrds

Paweł 

[Sébastien Jodogne]

Thanks for the feedback, Antoine and Paweł!

According to Antoine's answer, compatibility with OsiriX requires fixing the following issue once for all:

https://bitbucket.org/sjodogne/orthanc/issues/54/decide-what-to-do-wrt-quoting-of-multipart

I'll give a look at it asap.

Unfortunately, I don't have access to an Apple computer, so I'll entirely rely on your help to validate the fix.

Regards,

Sébastien-

[Sébastien Jodogne]

Hello,

The fix has been committed to the Orthanc mainline, and will be part of forthcoming release 1.4.2:

https://bitbucket.org/sjodogne/orthanc/commits/e02af4ca8003

Precompiled binaries including the fix can be found in the Docker image "jodogne/orthanc-plugins" and in the Linux Standard Base repository:

http://book.orthanc-server.com/users/docker.html

http://lsb.orthanc-server.com/orthanc/mainline/

Please let us know whether this improves compatibility with OsiriX!

Regards,

Sébastien-

[Paweł Bożek]

HI all 

Sebastien - today will give you feedback if release 1.4.2  works fine with the newest version of OsiriX 9.5.2 - Rev. 20180726

Paweł Bożek 

Prezes Zarządu | CEO

T: +48 739 289 739

E:  p.b...@radpoint.pl

Radpoint Sp. z o.o.
Kościuszki 173 | 40-524 Katowice | Poland

T: +48 14 69 60 112 | F: +48 14 69 60 119
NIP: 993-065-24-57 | REGON: 122859564
E: bi...@radpoint.pl | www.radpoint.pl

If you prefer to use encrypted email, my public key fingerprint is:
01B8 A45B EA36 B619 F3F8  0F04 401F 2993 217E 3C8C

[p.b...@radpoint.pl]

Sébastien, I have tested provided Orthanc - 1.4.2 release.
The problem still exists. I can send studies with WADO (with success), but in the end, Osirix display Error window with STOW-RS operation failed. 

[Sébastien Jodogne]

Sorry, I can't provide further help by myself without having OsiriX at hand.

Regards,

Sébastien-

[Sébastien Jodogne]

You could try and post full Orthanc logs in "--verbose" mode, together with OsiriX logs, as they might contain useful information:

http://book.orthanc-server.com/faq/log.html

[p.b...@radpoint.pl]

Please find console logs from Osirix 9.5.2 sending operation attached.

[Sébastien Jodogne]

Thanks, but please could you also share the Orthanc logs in "--verbose" mode?