Version: 2.0.6.0 Pre-Release

Table of content

  1. System Requirements
  2. Prerequisites
  3. Quick start
  4. Using external database engine
  5. Installing the windows service
  6. Configuration and Maintenance
  7. Integrating with healthcare IT systems
  8. Adding DICOM tags to the Worklist Item
  9. Diagnostics and troubleshooting
  1. System Requirements

***************************

Operating System:
Any windows based operating system, Windows 7 or newer. Recommended: Windows Server 2012 R2.

Hardware:
Any PC, including Virtual Machines, Min 500 MB RAM with network card.

Database:
Worklist Manager supports MS SQL Server, MySQL and SQLite.

 This package comes preconfigured for SQLite database (included).

  1. Prerequisites

***************************

Download and install Visual Studio 2013 runtime libraries: https://www.microsoft.com/en-us/download/details.aspx?id=40784

  1. Quick start

===========================

The quickstarts works with internal SQLite database (DicomServer.db)
Everything you need is found in the bin folder.

  1. From the bin folder, start WorklistManager.exe

    Set the “By period” filter to everything and click the search button

    You should see one record for patient AB^CD

    Add new records using this tool

  1. Start the server from command line: DicomServer.exe -r

    You can also simply double click startservice.bat

    The server is now running in command line listening on port 104 and waiting for incoming connections.

  1. Use any DICOM Modality Worklist SCU to connect to the server and query for the worklist.
    You can use H.R.Z. DICOMIZER in evaluation mode for testing
  1. Using external database engine

=================================

Worklist Manager supports MS SQL Server, MySQL and SQLite.
To use an external database:

  1. Create your database using the SQL scripts in the DBScripts folder. Run the create db script, insert static data and insert test data scripts for your DB server.
  2. Change the connection string in DicomServer.ini to connect to your database.
  3. Change the connection string in WorklistManager.exe.config
  1. Installing the windows service

=================================

The service name in the windows service manager console is “Storage Dicom Service”.
Install Worklist Manager DICOM Server as a windows service:

  1. Start command line prompt with administrator permisions
  2. CD to the bin directory
  3. run: DicomServer.exe -i

To uninstall the service:

  1. Stop the service
  2. from command line prompt with administrator permisions run: DicomServer.exe -u
  1. Configuration and Maintenance

=================================

DicomServer.exe command line parameters

****************

-r Run as command line (in verbose mode)
-i Install service
-u Uninstall service
-v Print version

configuration table

****************

Configure DicomServer’s port and AE title from the CONFIGURATION table in the database. The default values are:

ae_title = DSRSVC (local AE title)
port = 104 (listener’s port)
dicom_log = 1 (stops/starts logging)

Restart the server after configuration change

  1. Integrating with healthcare IT systems

=================================

The worklist manager can get the data from your IT system using the shared database.
Use the insert test data script as basis for creating Worklist Item entries for the server.

Contact us to get the WorklistManager GUI application source code (C#).

  1. Adding DICOM tags to the Worklist Item

=================================

The server reads the data for the Worklist Quert from the database views:

– CFIND_MWL_VIEW
– CFIND_ScheduledProcedureStepSequence_View

You can change these views to point to your tables or you can insert data to the built in tables.

Every column in the views has the exact name of a DICOM tag e.g. PatientID is (0010,0020), StudyInstanceUID is (0020,000d) etc.

You can add more columns by changing the views SQL command and adding more columns, from other tables or computed values.

You can also add sequence tags by adding the Sequence tag name as integer column to the parent and the child views, in the same manner that CFIND_MWL_VIEW and CFIND_ScheduledProcedureStepSequence_View are connected.

  1. Diagnostics and troubleshppting

=================================

Problem: Server doesn’t start in command line
Solutions:

An error with text about “side-by-side assemblies” indicates missing Visual Studio Runtime libraries.

  1. Install VS Runtime libraries (See prerequisites)
  2. Check the connection string

Problem: Server doesn’t start as a service
Solutions:

  1. Check that the server starts in command line
  2. Make sure that the service is running on a user that has permisions on the database (check the Log On tab in the windows service manager)

Problem: Modalities can’t connect to the server
Solutions:

  1. Check that port 104 is not taken by another process
  2. Check the firewall
  3. Check the IP address

Problem: Modalities can connect but don’t get results
Solutions:

  1. Run the server from command line
  2. Make sure dicom_log is on (in the configuration table)
  3. Send a query
  4. Look at the log
  5. Verify that you see a response in the log with results
  6. Check the query values and make sure that there are results in the database that match the query
  7. Check what attributes must your modality get and make sure they are all in the result. If not, add columns to the views.

Problem: Server works but then stops
Solutions:

  1. Buy a license. In evaluation mode without a license, the server works for 100 requests and then stops. You have to kill the process and start it again.

More information about Worklist Manager