The OrderManager has a feature which enables the user to create a DICOM worklist from an existing order. This order can be one of the orders received from a system under test or created by the Order Filler functionnality of the application. The user has also the possibility to create an new order if his/her purpose is only to test a modality. 

This functionnality of the application is available from the menu Worklist management, divided into four sub menus:

• Create a DICOM Worklist
• View all DICOM Worklist entries
• Worklist query messages
• Worklist query logs

Create a DICOM Worklist

When you enter this page, you are first of all asked to select the Integration profile for which you want to test your modality (required fields are not the same from an integration profile to an other). Then, you are offered three ways to select the order for which creating the associated worklist:

• Use an existing order : Select one of the orders displayed in the table. You can add some search criteria for restraining the search.
• Create a new order for an existing patient: The list of patients known by the application will be displayed, pick one, an encounter is automatically generated using the PAM Simulator and you are asked to fill the newly created order. Use the randomly fill order button if you do not want to select all values one by one; if some are sets, only the empty attributes are valued.
• Create a new order for an existing encounter: The list of encounters known by the application will be displayed, pick one. Then, you are asked to fill the newly created order. Use the randomly fill order button if you do not want to select all values one by one; if some of them are set, only the empty attributes are valued.

Once the order is selected and filled, the worklist is created. You are asked to add some additional attributes in order to help the application with creating the DICOM worklist. Note that the procedure and protocol codes and descriptions are selected in behalf of the Universal Service Id attribute of the order. The matching is done thanks to the spread sheet used during the connectathon, available here. If the order contains a Universal Service Id unkown from the application, you will be asked to fill a brief form. You can choose to enable the application to store those data in its database for a later reuse. Once all the required fields are valued, hit the "Generate DICOM worklist" button.

The worklist is created and you can download the result of the generation. An XML file and the DICOM object are both available for download. Note that the worklist is first created in an XML form that match the DTD defined by OFFIS and then converting to a DICOM object using the xml2dcm tool from the DICOM toolkit DCMTK developed by OFFIS.

In another panel, the configuration of the SCP in which is stored the DICOM worklist is given. For more details about how works the SCP, see the next section.

View all DICOM Worklist entries

This page gathers all the worklists which are available in the SCP. For each worklist, you will retrieve the link to download the DICOM object and the associated XML file. In the same way, the configuration of the SCP to query is displayed again.

Worklist query messages

We have put in place a little proxy as a front-end of our SCP. Our SCP is played by the DICOM Basic worklist management SCP (wlmscpfs) developed by OFFIS and available in the DCMTK toolkit. The given port is one of those the OrderManager is listening on. When you send your DICOM query to the given configuration, the OrderManager stores the data set part of the message in its database after some processing (extracts some informations stored beside the request) and forwards it to the DICOM SCP. When the SCP sends you the response, it is first received by the OrderManager which saves it and then forwards the response to your system. The DICOM messages intercepted by the OrderManager are all available here, menu Worklist management --> Worklist query messages. 

For each message, we have extracted the data set and its content is converted into an XML file using the dcm2xml tool from OFFIS's toolkit. This file is displayed in the application using an XSL transformation, the XSL file we have written is available here.

In the same way, for a given message you will find a table gathering all the other messages received within the same channel of the proxy. It appears that a new channel is openned for each new association.

Worklist query logs

The error output of wlmscpfs tool is regularly parsed and the results of the parsing are stored in the database. You can view these logs in this page here.