DICOM PS3.2 2022d - Conformance

E.4 Networking

E.4.1 Implementation Model

E.4.1.1 Application Data Flow

This implementation model uses the DICOM Basic Print Management Meta SOP Class to receive studies for the Medical Imager. Multiple associations to Print SCUs are supported.

Application Data Flow Diagram

Figure E.4.1-1. Application Data Flow Diagram

The Print Server is receiving the Images with the Presentation and Annotation information, it Apply it on the images and creates a print-job within the print queue, containing one or more film pages composed from images selected by the client Print SCU. Furthermore, it also manages the Printer Status and Configuration.

E4.1.2 Functional Definition of AEs

E. Functional Definition of Print Server (SCP) Application Entity

The Print Server System acquires the images with the demographics and presentation information from the connected Print Composer (SCU) that is Grouped with a Workstation or an Archive device. Studies are temporarily stored on disk. The images are then processed and formatted and finally queued as a print job on the Printer queue. If the Printer is operating normally, then the film sheets described in the print-job will be printed. Changes in the Printer operation status will be detected (e.g., film Magazine empty) and reported back to the Print SCU. If the Printer is not operating normally, then the print-job will be set to an error state and can be restarted by the user via the job control interface.

The Print Server Management includes:

  • DICOM Association and Negotiation Management

  • Image Buffering

  • Image Processing (Windowing level, P-LUT, GSDF, Annotation, etc)

  • Image Formatting (Film sheet format)

  • Printing

  • Print Job Status Tracking

  • Print Status Tracking

  • Printer Configuration Tracking

The Printer Status and Configuration can be requested at any time by the Print SCU, while the Print Server will update the Print SCU asynchronously whenever the Printer status get changed. Furthermore, the Print Server provides in addition a Service operation of checking the networking connectivity to it's Print SCU using the Verification SOP Class.

E.4.1.3 Sequencing of Real-World Activities

Print Server Management Sequence

Figure E.4.1-2. Print Server Management Sequence


  1. The Print Job N-GET and N-EVENT-REPORT are Asynchronous messages that may occur at any time after the Print Job was created.

  2. The Printer Status & Configuration N-GET and the N-EVENT-REPORT are Asynchronous messages that may occur at any time it is needed during the Print sequence.

The Print Server Management workflow activities in the sequence order as described in Figure E.4.1-2 apply:

  1. DICOM Film Session N-CREATE

  2. DICOM Presentation LUT N-CREATE

  3. DICOM Film Box N-CREATE

  4. Create Image Boxes & Annotation Boxes

  5. DICOM Image Box N-SET

  6. DICOM Annotation Box N-SET

  7. DICOM Film Session N-ACTION, A print job is created for each Film Session N-action.

  8. DICOM Film Box N-ACTION, A print job is created for each Film Box N-action.

  9. Create Print Job

  10. DICOM Film Session N-DELETE.

The following additional activities are asynchronous mode and they can be send any time the Print Server is up and running:

* DICOM Print Job N-GET, request the execution status of a Print Job.

* DICOM Print Job N-EVENT-REPORT, report an update on the execution status of a Print Job.

** DICOM Printer Status N-GET - Request a Printer Status, anytime the Printer is ON.

** DICOM Printer Configuration N-GET - Request the Printer configuration, anytime the Printer is ON.

** DICOM Printer Status N-EVENT-REPORT - Report the Printer Status Changed.

DICOM PS3.2 2022d - Conformance