Cannot query worklist from Siemens Bonsai

Google Groups archive
1

Hello,

I created a worklist in the Orthanc and it works perfectly. I can also use C-find command to get the worklists. However, I cannot get to this worklist by another machine even though it is connected. When I create a query in the machine I received the log below in the Orthanc. (It can get the worklists here but in the machine, it says no worklist found)

So my question is how can I solve this problem? Is there anything that I have to do additionally in the config.json for the Orthanc. Because I already added Bonsai as a Dicom Modality.

Thank you,

Log:

I0826 11:29:32.641183 PluginsManager.cpp:172] (plugins) Received worklist query from remote modality ACUSON Bonsai:

{

“0008,0050” : “”,

“0008,0090” : “”,

“0008,1080” : “”,

“0008,1110” : [],

“0008,1120” : [],

“0010,0010” : “”,

“0010,0020” : “”,

“0010,0030” : “”,

“0010,0032” : “”,

“0010,0040” : “”,

“0010,1000” : “”,

“0010,1010” : “”,

“0010,1020” : “”,

“0010,1030” : “”,

“0010,2000” : “”,

“0010,2110” : “”,

“0010,2160” : “”,

“0010,21b0” : “”,

“0010,21c0” : null,

“0010,21d0” : “”,

“0010,4000” : “”,

“0020,000d” : “”,

“0032,1032” : “”,

“0032,1033” : “”,

“0032,1060” : “”,

“0032,1064” : [],

“0038,0010” : “”,

“0038,0020” : “”,

“0038,0021” : “”,

“0038,0050” : “”,

“0038,0300” : “”,

“0038,0500” : “”,

“0040,0100” :

[

{

“0008,0060” : “US”,

“0032,1070” : “”,

“0040,0001” : “VASOLABS”,

“0040,0002” : “20210127-20210827”,

“0040,0003” : “”,

“0040,0004” : “”,

“0040,0005” : “”,

“0040,0006” : “”,

“0040,0007” : “”,

“0040,0008” : [],

“0040,0009” : “”,

“0040,0010” : “”,

“0040,0011” : “”,

“0040,0012” : “”,

“0040,0020” : “”,

“0040,0400” : “”

}

],

“0040,1001” : “”,

“0040,1003” : “”,

“0040,1004” : “”,

“0040,1010” : “”,

“0040,1400” : “”,

“0040,2400” : “”,

“0040,3001” : “”

}

I0826 11:29:32.641688 PluginsManager.cpp:172] (plugins) Worklist matched: /var/lib/orthanc/worklists/worklist_jwm.wl

I0826 11:29:32.642035 PluginsManager.cpp:172] (plugins) Worklist matched: /var/lib/orthanc/worklists/cem2.wl

I0826 11:29:32.642370 PluginsManager.cpp:172] (plugins) Worklist matched: /var/lib/orthanc/worklists/cem00.wl

I0826 11:29:32.643019 PluginsManager.cpp:172] (plugins) Worklist C-Find: parsed 6 files, found 3 match(es)

2

Hello,

I created a worklist in the Orthanc and it works perfectly. I can also use C-find command to get the worklists. However, I cannot get to this worklist by another machine even though it is connected. When I create a query in the machine I received the log below in the Orthanc. (It can get the worklists here but in the machine, it says no worklist found)

So my question is how can I solve this problem? Is there anything that I have to do additionally in the config.json for the Orthanc. Because I already added Bonsai as a Dicom Modality. […]

I0826 11:29:32.641183 PluginsManager.cpp:172] (plugins) Received worklist query from remote modality ACUSON Bonsai: […]

I0826 11:29:32.641688 PluginsManager.cpp:172] (plugins) Worklist matched: /var/lib/orthanc/worklists/worklist_jwm.wl

I0826 11:29:32.642035 PluginsManager.cpp:172] (plugins) Worklist matched: /var/lib/orthanc/worklists/cem2.wl

I0826 11:29:32.642370 PluginsManager.cpp:172] (plugins) Worklist matched: /var/lib/orthanc/worklists/cem00.wl

I0826 11:29:32.643019 PluginsManager.cpp:172] (plugins) Worklist C-Find: parsed 6 files, found 3 match(es)

From the last line of your log, you can see that Orthanc has found 3 matches, so the remote Siemens Bonsai shouldn’t say that no worklist was found.

This is definitely the topic of the following FAQ:
https://book.orthanc-server.com/faq/proprietary.html

Summarizing, you should get in touch with your Siemens support team in order to ask them to investigate the problem. Indeed, as Orthanc is free and open-source software, they can identify the cause of the issue. The converse is not true, as the Orthanc development team has no access to a Siemens Bonsai modality.

You could also try with the “–trace-dicom” command-line option, maybe you could get more low-level information from the DICOM protocol that could help identify the cause of the issue:
https://book.orthanc-server.com/faq/log.html

Regards,
Sébastien-

3

Thank you very much, Sébastien.