Worklist push or pull, upload folder structure and translated UI

[tosch...@gmail.com]

Hi,

I am playing around with Orthanc and its great!

Now that I understood the basics and all is running as expected, I have still three questions that haven’t been answered in the documentation (or at least I haven’t found it).

1. How does a Worklist in Orthanc come to a modality?
http://book.orthanc-server.com/plugins/worklists-plugin.html is quite clear how to create worklists and let Orthanc store and deliver them. But what I need is a way to “push” a Worklist to a certain modality. Or is it always the way that the user at the modality have to query a Worklist server for a certain Worklist first?
My assumption about the process with Worklists is as follows: user triggers in their RIS or MIS next procedure for a certain patient. That creates a Worklist and the Worklist is send automatically to the modality. At the modality, user sees all received Worklists, selects one, executes the procedure. As the Worklist contains the result target (typically the Orthanc PACS) the modality sends the DICOM files automatically to it after the procedure was completed.
So, my core question is: are Worklists pushed to modalities or do each modality pull Worklists from server?

2. The webUI of Orthanc and the Webviewer plugin from Osimis are in english language. Is there a file where I can either add or replace german language terms?

3. Is there a way to upload a whole DICOM folder structure instead of instance files?
I have tried the whole folder but that leads to an error. Adding instance files and upload works, but I have to traverse the folder structure manually what I want to avoid.

Thanks in advance

Torsten

[Levin Alexander]

Hi,

> 1. How does a Worklist in Orthanc come to a modality?
> http://book.orthanc-server.com/plugins/worklists-plugin.html is quite clear how to create worklists and let Orthanc store and deliver them. But what I need is a way to “push” a Worklist to a certain modality. Or is it always the way that the user at the modality have to query a Worklist server for a certain Worklist first?
> My assumption about the process with Worklists is as follows: user triggers in their RIS or MIS next procedure for a certain patient. That creates a Worklist and the Worklist is send automatically to the modality. At the modality, user sees all received Worklists, selects one, executes the procedure. As the Worklist contains the result target (typically the Orthanc PACS) the modality sends the DICOM files automatically to it after the procedure was completed.
> So, my core question is: are Worklists pushed to modalities or do each modality pull Worklists from server?

Worklists are pulled by your devices from the worklist server.

- the worklist contains a list of patients/procedures that should to be done
- you configure ip/port/aetitle of your worklist server on your modality
- now your modailiy should show a "query worklist" button or some other interface, this will query the worklist server for the current list of patients/procedures and you can select the one that you want to do and start it.

The worklist does not contain the result target where completed studies should be sent, you need to configure that on your devices separately.


--Levin Alexander

[tosch...@gmail.com]

Thank you Levin - worklist concept is now clear for me

[tosch...@gmail.com]

> 3. Is there a way to upload a whole DICOM folder structure instead of instance files?
> I have tried the whole folder but that leads to an error. Adding instance files and upload works, but I have to traverse the folder structure manually what I want to avoid.

found the answer to that here already
https://groups.google.com/forum/#!topic/orthanc-users/TZDqxH_PD24

[Sébastien Jodogne]

Dear Torsten,

I read that your (1) and (3) questions have already been answered above. Back to the remaining one:

2. The webUI of Orthanc and the Webviewer plugin from Osimis are in english language. Is there a file where I can either add or replace german language terms?

I kindly invite you to carefully read the following FAQ:

http://book.orthanc-server.com/faq/improving-interface.html

In a nutshell, the Web user interface of Orthanc (aka. "Orthanc Explorer") is a low-level, administrative, English-speaking interface. We are still looking for funding/donations/contributors in order to create a plugin that would add a more high-level, user-friendly Web interface to Orthanc. This plugin could obviously add multi-language support, among other features.

HTH,

Sébastien-