Secondary captures make Orthanc unusable with Osimis WebViewer 1.2.0.0 and Orthanc 1.5

Google Groups archive
1

Hi,

have just tried Osimis WebViewer 1.2.0.0-0d4bfbd5 together with Orthanc 1.5.0
(Problem exists in earlier versions as well)

The secondary capture feature in the Osimis WebViewer is still producing and storing damaged DICOM files.

Although the Orthanc Explorer (using REST) can list and open the secondary captures, a C-FIND (I have tried with Osirix 8) fails.

In this case, Orthanc server log shows:
Dec 20 16:41:23 CIPRCS orthanc: E1220 16:41:23.988133 FindScp.cpp:272] C-FIND request handler has failed: Internal error

This has the following effects:

  • with the first secondary capture you make and save, you make Orthanc more or less unusable
  • users running a C-FIND without filter ends up in Osirix (and I guess every other DICOM viewer too) in “unable to process”
  • users running a C-FIND with a filter (e.g. patientname) show at least the list, but attempt to open the secondary captures fail (while attempt to load the primary capture works as expected)
    The following screenshot shows Osirix with C-FIND and patientname filter. Resultlist shows the primary capture and two secondary captures.

Attempt to open behaves as mentioned above.

This is a serious bug (IMHO) and means, secondary captures are dangerous, i.e. cannot be activated for users.

btw, it would also be nice to name secondary captures not “undefined” but use the secondary capture note (that can be entered in Osimis Webviewer) instead.

seccapt_problem.jpg

thanks and regards
Torsten

2

Hello,

If I get you right, your question is twofold:

  1. The Osimis Web viewer generates broken DICOM files.
  2. In the Orthanc core, the C-FIND SCP fails if encountering such a broken DICOM file.

I let Alain answer regarding part (1) of your question. You remark about the “undefined” tag most probably refers to the Osimis Web viewer.

As far as part (2) is concerned, please could you provide a broken DICOM file, so that I can work on a fix in the Orthanc core?

Regards,
Sébastien-

3

Hi Thorsten,

I’ve just generated such a file and tried to C-Find it with findscu at both STUDY level and SERIES level; I did not get any issues.
I also tried to find/retrieve and visualize the data from Radiant: no problem. So it looks like Orthanc is somehow usable.
For the record, I tested with both 1.5.0 and a mainline version close to 1.5.1.

Could you send us the Orthanc logs in verbose mode such that we know what exact query is being made by OSIRIX.
Seb, I’m sending you some files. Thorsten, you’re still welcome to send yours in case there’s something special about them.

Best regards,

Alain.

4

Hello Sebastien,

sorry for late response (xmas …).

I attach such a dicom file, that was created with secondary capture feature of Osimis WebViewer.

I am not sure what is going here exactly, but at least found two more facts:

  • if I download the file and open from Osirix via filesystem it opens
  • it seems to be a Structured Report!? Interesting, because I expected a normal instance with annotations

Maybe Alain has a clue what the secondary capture generates or should generate really.

best Torsten

9b9e76ef-8e1a-4c60-87ac-e5dd26dd8e04.dcm (757 KB)

5

Hi Torsten,

Could you send us the Orthanc logs in verbose mode such that we know what exact query is being made by OSIRIX.

Without that, we can not debug the issue.

Best regards,

Alain