Software - Division CS

The DICOM print management toolkit DCMPRINT consists of three components:

• a C++ class library implementing the DICOM print management communication protocol,
• a print server (Print Management SCP) which creates PostScript code that can be printed on a conventional PostScript laser printer, and
• a simple print client (Print Management SCU) allowing to load DICOM images and to print them on the print server.

The print server implements the DICOM Print Management Service Class and a couple of optional extensions (Annotation Box, Print Job and Presentation LUT). The "Basic Print Management" services are supported in their monochrome and color variants. The behavior of the print server can be adapted to the particular conditions through a comprehensive configuration file.

The print client allows to control all options and features of the print server. The client is a very simple command line application demonstrating the underlying libraries and is not intended as a ready-to-use product.

DCMCHECK is a validation and testing tool for DICOM objects. The program reads a DICOM object from a file, checks the conformance of the object concerning the DICOM standard and creates a test report which describes in detail all detected violations of the standard.

The DICOM standard defines data structures (Information Object Definitions, IODs) for the various supported modalities. In order to test if a DICOM object conforms to its specification, it is necessary to transform the IODs into a formal, machine-readable form. In doing so, the required and optional aspects of the specification as well as the conditions and constraints defined in natural language have to be considered.

For this purpose, DCMCHECK uses a specialized IOD description language which allows to easily add extensions (e. g. private elements or DICOM correction proposals) to the IOD definition without changing the application itself. DICOM objects are tested for conformance with regard to the definitions in part 3 (IODs), part 5 (data structures and encoding) and part 6 (data dictionary) of the DICOM standard. The conformance of the "meta header" according to part 10 of the standard as well as the consistency between header and meta header are also tested.

DCMCHECK currently supports all IODs of the 2003 edition of the DICOM standard, e. g. the following image IODs: CR, CT, DX, MG, MR, NM, RF, RT, SC, US, XA. In addition: DICOMDIR, GSPS, SR, Waveform, Stored Print. Further IODs can be added.

DCMCHECK can test DICOM objects in all uncompressed and JPEG compressed transfer syntaxes, also RLE and Deflated. The structure of embedded pixel data is, however, not tested. DCMCHECK supports files with or without meta-header (DICOM part 10).

The DICOM JPEG 2000 toolkit DCMJP2K consists of three components:

• a C++ class library which implements DICOM JPEG 2000 support,
• an encoder application that converts DICOM images to DICOM JPEG 2000 transfer syntax, and
• a decoder application that decompresses DICOM JPEG 2000 images.

DCMJP2K supports two DICOM JPEG 2000 transfer syntaxes that were introduced into the standard in 2001. JPEG 2000 allows for a better compression than the original "Standard JPEG" support in DICOM. Additionally, the internal structure of the JPEG 2000 format permits some powerful streaming features that can be accessed in DICOM through the JPIP protocol (DICOM JPEG 2000 Interactive Protocol, not part of DCMJP2K), too.

The DCMJP2K class library integrates as a module into DCMTK. Encoder and decoder register themselves at the DCMTK codec registry just like other codecs, e. g. the dcmjpeg module. Thus, a few lines of code are sufficient to change the transfer syntax to JPEG 2000 or for decompression.

The two DCMJP2K applications work at the command line and allow for converting DICOM image files to JPEG2000 transfer syntax and vice versa.

The class library and command line applications provide the following features:

• Lossless and Lossy JPEG 2000 compression for DICOM images
• Tweaking of various compression parameters (compression ratio, quantization, etc.)
• Seamless integration into the DICOM toolkit DCMTK
• Automatic adaption of related DICOM attributes
• Platform independent source code

Two of the DICOM JPEG 2000 transfer syntaxes are supported: "JPEG 2000 Image Compression (Lossless Only)" and "JPEG 2000 Image Compression".

DCM2AVI is a command line application that allows to convert DICOM multi-frame images into AVI format. For example, X-ray angiographic (XA) and ultrasound (US) images can be compressed with a particular codec that is installed on the system (MPEG4, XVID, H.261, etc.). The generated AVI movies can be viewed with a conventional media player or integrated into presentations. Furthermore, compressed AVI files are usually much smaller than the original DICOM files and can, therefore, be transferred in significantly shorter time. However, AVI movies are not appropriate for primary diagnosis since diagnostically relevant details of the image data might get lost during compression.

DCM2AVI provides the following features:

• Support of all DICOM multi-frame image IODs for the generation of AVI movies
• Support of all DICOM single-frame image IODs for the generation of JPEG images
• Generation of BMP or JPEG overview images from DICOM images if required
• Support of uncompressed and compressed (JPEG, RLE, Deflated) DICOM images
• Batch mode and reading from DICOMDIR in addition to single DICOM file processing
• Selection of codecs and some codec parameters (quality, data rate, etc.)
• Automatic generation of output filenames according to a selectable pattern
• Export of particular, configurable DICOM header data into a text file
• Simple image processing operations such as VOI windowing and overlay rendering

DCMPPS implements a DICOM Modality Performed Procedure Step (MPPS) SCP based on a C++ class library. For the program PPSSCPFS being part of this module, MPPS objects are stored and maintained in DICOM file format in a specific file system directory and can be evaluated by other applications. DCMPPS keeps track of each created MPPS object, thus guaranteeing that each object can be created only once and that only existing objects can be updated by an SCU.

DCMPPS / PPSSCPFS provides the following features:

• Receipt of arbitrary MPPS messages and storage of the corresponding MPPS object in file system
• If desired, only messages from "known" SCUs are accepted
• Extensive checking of incoming messages for completeness and validity
• Compatiblity options for specific modalities
• Single and multi process mode (multiple simultanous connections)
• Options for tweaking DICOM network communication parameters

DCMPPSWM implements a DICOM Modality Worklist Management and Modality Performed Procedure Step (MPPS) SCP based on a C++ class library. A special feature of the program PAWSCPFS being part of this module is that both services are available under the same port number. The worklist entries are generated from the content of DICOM files which reside in a particular file system directory. MPPS objects are stored and maintained in DICOM file format in a specific directory and can be evaluated by other applications. DCMPPSWM keeps track of each created MPPS object, thus guaranteeing that each object can be created only once and that only existing objects can be updated by an SCU.

DCMPPSWM / PAWSCPFS provides the following features:

• Modality Worklist Management and Modality Performed Procedure Step SCP under the same port
• Response to worklist queries based on predefined entries that are stored in file system
• Mapping of worklist entries to particular Worklist Management SCU possible
• Receipt of arbitrary MPPS messages and storage of the corresponding MPPS object in file
• If desired, only MPPS messages from "known" SCUs are accepted
• Checking of worklist entries and MPPS messages for completeness and validity
• Compatiblity options for specific modalities
• Single and multi process mode (multiple simultanous connections)
• Options for tweaking DICOM network communication parameters

DCMPPSCU implements a DICOM Modality Performed Procedure Step (MPPS) SCU based on a C++ class library. For the program MPPSSCU being part of this module, MPPS messages are either read from DICOM files or composed from individual data elements. Both mechanisms can also be combined. For each program call, a single MPPS message (N-CREATE or N-SET) is sent. The current state of the MPPS object is documented in a DICOM file, which can be used for checking purposes.

DCMPPSCU / MPPSSCU provides the following features:

• Transmission of MPPS messages and storage of the corresponding MPPS objects in file system
• Usage of pre-defined MPPS messages or composition from individual data elements
• Extensive checking of MPPS messages for completeness and validity
• If desired, archival of the "completed" MPPS objects as DICOM files
• Options for tweaking DICOM network communication parameters

PPSMGR implements an IHE Performed Procedure Step (PPS) Manager, i. e. an DICOM Modality Performed Procedure Step (MPPS) SCU and an MPPS SCP. The received MPPS messages are first stored in a specific file system directory and then forwarded to one or more configurable receivers (MPPS SCP). If an error occurs during forwarding, e. g. in case the receiver cannot be reached, the messages are resend after a particular waiting period. This process is repeated until all MPPS message could be delivered successfully.

PPSMGR provides the following features:

• List of receivers of the MPPS messages configurable in a separate text file
• Queue management for pending MPPS messages
• If desired, forwarding of MPPS messages can be disabled
• Selective shutdown of the server processes by a separate command line application
• Single and multi process mode (multiple simultanous connections)
• Options for tweaking DICOM network communication parameters

DCMSTCOM implements a DICOM Storage Commitment SCU based on a C++ class library. The program STCOMSCU being part of this module accepts the corresponding response messages of a Storage Commitment SCP either on the same association that was used for the request or on a separate association. The DICOM datasets that were sent or received over the network as part of the messages can be stored as DICOM files for further analysis.

DCMSTCOM / STCOMSCU provides the following features:

• Support for Storage Commitment Push Model SOP Class as a Service Class User (SCU)
• Receipt of Storage Commitment response (N-EVENT-REPORT) on the same or a separate association
• Creation of the Storage Commitment request on the basis of given DICOM files
• Alternatively, direct definition of SOP Class UID and SOP Instance UID (class library only)
• Storage of DICOM request and response datasets as DICOM files (including status)
• If desired, detailed checking and report on each transaction in the form of a text file
• Options for tweaking DICOM network communication parameters