[Reprint] printed content in DICOM protocol

Print Management Service
H.1 range
The print management service class defines the application-level service class, which simplifies the printing of hard copy media images and image-related data.
H.2 print Management Model
H.2.1 print Management Data Process Model
H.2.1.1 Global Data Flow Model
Figure H.2.1.1-1: Print Management Data Flow Model

The print Management Data Flow Model (graph H.2.1.1-1) consists of three main processes:
-Film session management process
-Queue management process
-Printing process

Note: The term "film" is used as a general name for different types of hard copies (for example, photographic films and photo and paper.

The film session management process is responsible for obtaining the information required for all printed film sessions. A film session is an atomic Work Package for printing and managing applications and contains one or more films related to a user-defined method (for example, the same exam, patient, these films are from a host (such as a workstation, analysis device) and printed on a hard copy printer.

Each film includes one or more images and zero or more annotation-related films.

Each image has pixel data and zero or multiple overwriting planes. You can specify the value of the print parameter to control the appearance of the film.

The print parameters are defined at the film session level, film level, image level, and comment level respectively. The parameter level determines the operation range of the print parameter. For example, the image-level print parameter is valid for the corresponding image.

Input to the film session management process is:
-Set of image and image-related data
-Describe the data of the visible appearance of a film.

The output of the film session management process is printing, which includes all the information of the film session.

Queue Management Process Management Various printing work. Users can process queue content, such as deleting and printing, and optimizing printing.

The printing process prints a set of films based on printed information. The printing process is a specific implementation and its management is beyond the DICOM standard.
H.2.1.2. grayscale Transformation
The print Management Service supports converting the original image to the grayscale and spatial conversion sequence of the printed image.

The sequence of spatial transformations (for example, amplification and image annotation merging) and their relationship with grayscale transformations are specific implementations and follow the DICOM standard range.

Due to the non-orthogonal nature of different transformations, the sequence of grayscale transformations is important for archival continuous images. Figure H.2.1.2-1 describes the sequence of grayscale Transformation

Figure H.2.1.2-1: Print Management Data Flow Model

The following is the definition of the grayscale conversion type:
-Device LUT conversion: converts the manufacturer-related pixel values to pixel values that are meaningful to the device and irrelevant to the manufacturer (for example, the hounsfield Number of the CT device and the OD of the film Digital Converter. The device LUT is related to the device and is part of the image IOD. In the case of linear transformation, the device LUT is described by rescale slope () and rescale intercept. In the case of nonlinear transformation, the device LUT is described by the device LUT module.
-Transform: Convert the device pixel value to a pixel value that is meaningful to the user or application. The semantics of the voi pixel is defined by the photometric interpolation (3rd) (see Part 1). If the photometric interpolation is monochrome1, the smallest voi pixel value will be displayed in white. If the photometric interpolation is monochrome2, the smallest voi pixel value will be displayed in black. Voi LUT is either an image IOD or a part of the IOD in the image box. In the case of linear transformation, the voi LUT image frame is described by the window space () and the window width. In the case of nonlinear transformation, voi LUT is described by the voi LUT module (as part of the image IOD) or by the voi LUT box IOD (referred by the IOD in the image box. Voi LUT should not have any negative slope. If voi LUT is a part of the image iod and graph iod, The vol lut associated with the image shall take precedence over voi LUT associated with the image.
-Polarity change: indicates whether the minimum voi pixel value should be displayed in black or white. If the polarity (2020,0020) is normal, the voi pixel will be displayed with the specified photometric interpolation; if the polarity is reverse, the voi pixel will be displayed with the negative pole specified by the photometric interpolation. Polarity (,) is the attribute of the IOD in the image box.
-Perceptual LUT Transformation: converts polar pixel values to light density values that are most suitable for human perception. The perceived LUT depends on the type of Display (such as soft copy and hard copy. Perception LUT is not mentioned in this DICOM standard version.
H.2.2 print Management Service Class Structure
The print management service class structure is displayed in the graph H.2.2-1.

Figure H.2.2-1: Print Management Service Class Structure

Print management SCU and print management SCP are equivalent DICOM print management application entities. Print management Scp application entity with one or more hard copy printers. If the Scp application entity corresponds to multiple printers, the Scp application entity selects a printer for each print operation, on which the print operation will be printed.

Print management SCU and print management SCP establish an association by using the associated services of the OSI high-level service. During association establishment, DICOM printing manages SOP classes that can be supported by application entity negotiation. The negotiation process is defined in h.5.

The figure H.2.2-2 shows an optional configuration of printed images and image-related data from one host to multiple printers ..

Figure H.2.2-2: configuration printed on multiple printers

Configuration 1: One SCU application entity corresponds to one host, and one SCP application entity corresponds to multiple printers. SCU cannot control the print parameters of each printer, nor control the printing purpose of the print operation.

Configuration 2: a scu application corresponds to the host, and an SCP application corresponds to a printer. SCU explicitly controls the print parameters of each printer and the purpose of printing the printer. Each Scp application entity is associated with the SCU application entity and identified by the application entity name.
H.2.3 print management Sop
Print management SCU controls the print process by using the DIMSE service to manipulate the print management SOP class. The print management SOP class is managed by the print management SCP.

The categories of print management SOP are as follows:
-Content-related sop: These SOP classes are the abstraction of film content (such as pixel data and text strings. The text-related SOP class corresponds to the image-related SOP class described in H.4.
-Representation-related SOP classes: These SOP classes are the abstraction of the representation of film (for example, layout information) and are defined by standardized iods and standardized DIMSE-N services. Indicates that the SOP class is defined in H.4 of this section.
-Queue-related SOP classes: These SOP classes are printed queue abstractions and defined by standardized iods and standardized DIMSE-N services. The queue-related SOP class is defined in H.4 of this section.
-Printer sop: These SOP classes are the abstraction of printer configurations and statuses and are defined by standardized iods. The printer SOP class is defined in H.4 of this section.
H.2.4 usage instructions
Modules and DIMSE services constitute the SOP class. The module contains the or optional attributes of related commands. SCU usage can be different from SCP usage. Description: The former indicates SCU usage, and the latter indicates SCP usage.

The DIMSE service can be the (M) or optional (u) of the commands described in section 5.4 in this section ).

The meaning and behavior of printing the attribute usage instructions of the management service class are as follows:

M/m scu should provide a value for the property. If SCU does not support this value, SCP should return the failure status ("missing attribute", code 0120 H ).
SCP should support at least one attribute value. If SCP does not support a value specified by SCU, it should return the failure state ("invalid attribute value", code 0106 H ).

-The SCU usage of the/M attribute is not defined.
SCP should support at least one attribute value.

U/m scu can provide a property value.
If SCP does not support the value specified by SCU, it should return either a failure status or a warning status ("invalid attribute value", code 0106 H ). In a warning state, SCP applies the default value defined in The SCP consistency statement.

U/u can provide a value for the property.
If SCP does not support the value specified by SCU but supports attributes, it should return either the failure status or the warning status ("invalid attribute value", code 0106 H ). In a warning state, SCP applies the default value defined in The SCP consistency statement.

If SCP does not support attributes specified by SCU, it should return either the failure status or the warning status ("No such attribute", code 0105 H ). In the case of a warning state, SCP behavior is defined in the SCP consistency statement.

If the usage type name is "C"