Annex B STORAGE SERVICE CLASS (Normative)

B.1 Overview

B.1.1 Scope

The Storage Service Class defines an application-level class-of-service which facilitates the simple transfer of information Instances (objects).. It allows one DICOM AE to send images, waveforms, reports, etc., to another.

Information Object Definitions for Instances that are transferred under the Storage Service Class shall adhere to the Composite Instance IOD Information Model specified in PS3.3, and include at least the Patient, Study, and Series Information Entities.

B.1.2 Service Definition

Two peer DICOM AEs implement a SOP Class of the Storage Service Class with one serving in the SCU role and one serving in the SCP role. SOP Classes of the Storage Service Class are implemented using the C-STORE DIMSE-C service. C-STORE is described in PS 3.7. A successful completion of the C-STORE has the following semantics:

— Both the SCU and the SCP support the type of information to be stored.

— The information is stored in some medium.

— For some time frame, the information may be accessed.

Notes: 1. Support for Storage SOP Classes does not necessarily involve support for SOP Classes of the Query/Retrieve Service Class. How the information may be accessed is implementation dependent. It is required that some access method exists. This method may require an implementation dependent operation at the SCP of the Storage Service Class. The duration of the storage is also implementation dependent, but is described in the Conformance Statement of the SCP. Storage SOP Classes are intended to be used in a variety of environments: e.g. for modalities to transfer images to workstations or archives, for archives to transfer images to workstations or back to modalities, for workstations to transfer processed images to archives, etc.

2. For the JPIP Referenced Pixel Data transfer syntaxes, transfers may result in storage of incomplete information in that the pixel data may be partially or completely transferred by some other mechanism at the discretion of the SCP.

B.2 Behavior

This Section discusses the SCU and SCP behavior for SOP Classes of the Storage Service Class. The C-STORE DIMSE-C Service shall be the mechanism used to transfer SOP Instances between peer DICOM AEs as described in PS 3.7.

B.2.1 Behavior of an SCU

The SCU invokes a C-STORE DIMSE Service with a SOP Instance which meets the requirements of the corresponding IOD. The SCU shall recognize the status of the C-STORE service and take appropriate action upon the success or failure of the service.

Note: The appropriate action is implementation dependent. It is required that the SCU distinguish between successful and failed C-STORE responses. Appropriate action may differ according to application, but are described in the Conformance Statement of the SCU.

B.2.2 Behavior of an SCP

An SCP of a Storage SOP Class acts as a performing DIMSE-service-user for the C-STORE Service. By performing this service successfully, the SCP indicates that the SOP Instance has been successfully stored.

B.2.3 Statuses

Table B.2-1 defines the specific status code values which might be returned in a C-STORE response. General status code values and fields related to status code values are defined in PS 3.7.

Table B.2-1C-STORE STATUS

Service Status Further Meaning Status Codes Related Fields
Failure Refused: Out of Resources A7xx (0000,0902)
Error: Data Set does not match SOP Class A9xx (0000,0901) (0000,0902)
Error: Cannot understand Cxxx (0000,0901) (0000,0902)
Warning Coercion of Data Elements B000 (0000,0901) (0000,0902)
Data Set does not match SOP Class B007 (0000,0901) (0000,0902)
Elements Discarded B006 (0000,0901) (0000,0902)
Success 0000 None

B.3 Association negotiation

SCUs and SCPs of Storage SOP Classes operate on SOP Instances specific to the SOP Class. They may use the SOP Class Extended Negotiation Sub-Item defined in PS 3.7. This Sub-Item allows DICOM AEs to exchange application information specific to SOP Class specifications. This is achieved by defining the Service-class-application-information field.

SCUs may use the SOP Class Common Extended Negotiation Sub-Item defined in PS 3.7. This Sub-Item allows DICOM AEs to exchange information about the nature of the SOP Classes.

The SOP Class Extended Negotiation Sub-Item and SOP Class Common Extended Negotiation Sub-Item negotiation is optional for storage based SOP Classes.

The following negotiation rules apply to all DICOM SOP Classes and Specialized SOP Classes of the Storage Service Class.

The Association-requester (Storage SCU role) in the A-ASSOCIATE request shall convey:

— one Abstract Syntax, in a Presentation Context, for each supported SOP Class of the Storage Service Class

— optionally, one SOP Class Extended Negotiation Sub-Item, for each supported SOP Class of the Storage Service Class

— optionally, one SOP Class Common Extended Negotiation Sub-Item, for each supported SOP Class of the Storage Service Class

The Association-acceptor (Storage SCP role) in the A-ASSOCIATE request shall accept:

— one Abstract Syntax, in a Presentation Context, for each supported SOP Class of the Storage Service Class

— optionally, one SOP Class Extended Negotiation Sub-Item, for each supported SOP Class of the Storage Service Class

B.3.1 Extended Negotiation

At the time of Association establishment implementations may exchange information about their respective capabilities, as described in PS 3.7 and PS 3.8. SCUs and SCPs may use the SOP Class Extended Negotiation Sub-Item Structure as described in PS 3.7 to exchange information about the level of conformance and options supported. SCUs may use the SOP Class Common Extended Negotiation Sub-Item defined in PS 3.7 to exchange information about the nature of the SOP Classes.

Extended negotiation is optional. In the event that either the SCU or the SCP does not support extended negotiation, the defaults shall apply.

B.3.1.1 Service-Class-Application-Information (A-ASSOCIATE-RQ)

The SOP Class Extended Negotiation Sub-item is made of a sequence of mandatory fields as defined by PS 3.7. Table B.3-1 shows the format of the Service-class-application-information field of the SOP Class Extended Negotiation Sub-Item for SOP Classes of the Storage Service Class in the A-ASSOCIATE-RQ.

Table B.3-1 SERVICE-CLASS-APPLICATION-INFORMATION (A-ASSOCIATE-RQ)

Item Bytes Field Name Description of Field
1 Level of support This byte field defines the supported storage level of the Association-requester. It shall be encoded as an unsigned binary integer and shall use one of the following values: 0 - level 0 SCP 1 - level 1 SCP 2 - level 2 SCP 3 - N/A Association-requester is SCU only If extended negotiation is not supported, the default shall have a value of 3.
2 Reserved This reserved field shall be sent with a value 00H but not tested to this value when received.
3 Level of Digital Signature support A Level 2 SCP may further define its behavior in this byte field. 0 – The signature level is unspecified, the AE is an SCU only, or the AE is not a level 2 SCP 1 – signature level 1 2 – signature level 2 3 – signature level 3 If extended negotiation is not supported, the default shall have a value of 0.
4 Reserved This reserved field shall be sent with a value 00H but not tested to this value when received.
5 Element Coercion This byte field defines whether the Association-requester may coerce Data Elements. It shall be encoded as an unsigned binary integer and shall use one of the following values: 0 - does not coerce any Data Element 1 - may coerce Data Elements 2 - N/A - Association-requester is SCU only If extended negotiation is not supported, the default shall have a value of 2.
6 Reserved This reserved field shall be sent with a value 00H but not tested to this value when received.

B.3.1.2 Service-Class-Application-Information (A-ASSOCIATE-AC)

The SOP Class Extended Negotiation Sub-item is made of a sequence of mandatory fields as defined by PS 3.7. Table B.3-2 shows the format of the Service-class-application-information field of the SOP Class Extended Negotiation Sub-Item for SOP Classes of the Storage Service Class in the A-ASSOCIATE-AC.

Table B.3-2SERVICE-CLASS-APPLICATION-INFORMATION (A-ASSOCIATE-AC)

Item Bytes Field Name Description of Field
1 Level of support This byte field defines the supported storage level of the Association-acceptor. It shall be encoded as an unsigned binary integer and shall use one of the following values: 0 - level 0 SCP 1 - level 1 SCP 2 - level 2 SCP 3 - N/A - Association-acceptor is SCU only If extended negotiation is not supported, no assumptions shall be made by the Association-requester about the capabilities of the Association-acceptor based upon this extended negotiation.
2 Reserved This reserved field shall be sent with a value 00H but not tested to this value when received.
3 Level of Digital Signature support A Level 2 SCP may further define its behavior in this byte field. 0 – The signature level is unspecified, the AE is an SCU only, or the AE is not a level 2 SCP 1 – signature level 1 2 – signature level 2 3 – signature level 3 If extended negotiation is not supported, no assumptions shall be made by the Association-requester about the capabilities of the Association-acceptor based upon this extended negotiation.
4 Reserved This reserved field shall be sent with a value 00H but not tested to this value when received.
5 Element Coercion This byte field defines whether the Association-acceptor may coerce Data Elements. It shall be encoded as an unsigned binary integer and shall use one of the following values: 0 - does not coerce any Data Element 1 - may coerce Data Elements 2 - N/A - Association-acceptor is SCU only If extended negotiation is not supported, no assumptions shall be made by the Association-requester about the capabilities of the Association-acceptor based upon this extended negotiation.
6 Reserved This reserved field shall be sent with a value 00H but not tested to this value when received.

B.3.1.3 Service Class UID (A-ASSOCIATE-RQ)

SOP Class Common Extended Negotiation Sub-Item allows the SCU to convey the Service Class UID of each proposed SOP Class.

The Storage Service Class UID shall be "1.2.840.10008.4.2".

B.3.1.4 Related General SOP Classes (A-ASSOCIATE-RQ)

A limited set of Standard SOP Classes in the Storage Service Class are defined to have one or more Related General SOP Classes. The Related General SOP Classes may be conveyed using the SOP Class Relationship Extended Negotiation during association establishment as defined in PS 3.7. Table B.3-3 identifies which Standard SOP Classes participate in this mechanism. If a Standard SOP Class is not listed in this table, Related General SOP Classes shall not be included in a Related Storage SOP Class Extended Negotiation Sub-Item.

Note: Implementation-defined Specialized SOP Classes (see PS3.2) of the Storage Service Class may convey a Related General SOP Class.

Table B.3-3 STANDARD AND RELATED GENERAL SOP CLASSES

SOP Class Name Related General SOP Class Name
12-lead ECG Waveform Storage General ECG Waveform Storage
Digital Mammography Image Storage - For Presentation Digital X-Ray Image Storage - For Presentation
Digital Mammography Image Storage - For Processing Digital X-Ray Image Storage - For Processing
Digital Intra-oral X-Ray Image Storage - For Presentation Digital X-Ray Image Storage - For Presentation
Digital Intra-oral X-Ray Image Storage - For Processing Digital X-Ray Image Storage - For Processing
Basic Text SR Enhanced SR
Comprehensive SR
Enhanced SR Comprehensive SR
Procedure Log Enhanced SR
Comprehensive SR
X-Ray Radiation Dose SR Enhanced SR
Comprehensive SR
Spectacle Prescription Report Enhanced SR
Macular Grid Thickness and Volume Report Enhanced SR

B.4 Conformance

An implementation which conforms to Storage SOP Classes shall meet the:

— C-STORE Service requirements as defined in Section B.2

— Association requirements as defined in Section B.3

Note: No SCU or SCP behavior requirements other than those in this section are specified. In particular, an SCP of the Storage SOP Classes may not attach any significance to the particular association or associations over which C-STORE operations are requested, nor the order in which C-STORE operations occur within an association. No constraints are placed on the operations an SCU may perform during any particular association, other than those defined during association negotiation. An SCP may not expect an SCU to perform C-STORE operations in a particular order.

Similarly, no semantics are attached to the closing of an Association, such as the end of a Study or Performed Procedure Step.

B.4.1 Conformance as an SCP

Three levels of conformance to the Storage SOP Classes as an SCP may be provided:

— Level 0 (Local). Level 0 conformance indicates that a user defined subset of the Attributes of the image will be stored, and all others will be discarded. This subset of the Attributes shall be defined in the Conformance Statement of the implementor.

— Level 1 (Base). Level 1 conformance indicates that all Type 1 and 2 Attributes defined in the IOD associated with the SOP Class will be stored, and may be accessed. All other elements may be discarded. The SCP may, but is not required to validate that the Attributes of the SOP Instance meets the requirements of the IOD.

Note: A Level 2 SCP may discard (not store) Type 3 attributes that are empty (zero length and no Value), since the meaning of an empty Type 3 attribute is the same as absence of the attribute. See PS 3.5 definition of "Type 3 Optional Data Elements".

An SCP that claims conformance to Level 2 (Full) support of the Storage Service Class may accept any Presentation Context negotiation of a SOP Class that specifies the Storage Service Class during the SOP Class Common Extended Negotiation, without asserting conformance to that SOP Class in its Conformance Statement.

Note: The SCP may support storage of all SOP Classes of the Storage Service Class, preserving all attributes as a Level 2 SCP.

An SCP that claims conformance to Level 2 (Full) support of a Related General SOP Class may accept any Presentation Context negotiation of a SOP Class that specifies that Related General SOP Class during the SOP Class Common Extended Negotiation, without asserting conformance to that specialized SOP Class in its Conformance Statement.

Notes: 1. The term “specialized” in this section is used generically, including both Implementation-defined Specialized SOP Classes and Standard SOP Classes specified in Table B.3-3.

2. The SCP may handle instances of such specialized SOP Classes using the semantics of the Related General SOP Class, but preserving all additional (potentially Type 1 or 2) attributes as a Level 2 SCP.

At any level of conformance, the SCP of the Storage Service Class may modify the values of certain Attributes in order to coerce the SOP Instance into the Query Model of the SCP. The Attributes which may be modified are shown in Table B.4-1.

Table B.4-1 Attributes Subject to Coercion

Attribute Tag
Patient ID (0010,0020)
Study Instance UID (0020,000D)
Series Instance UID (0020,000E)

The SCP of the Storage Service Class may modify the values of Code Sequence attributes to convert from one coding scheme into another. This includes changing from deprecated values of Coding Scheme Designator (0008,0102) or Code Value (0008,0100) to currently valid values.

If an SCP performs such a modification, it shall return a C-STORE response with a status of Warning.

Notes 1. Modification of these Attributes may be necessary if the SCP is also an SCP of a Query/Retrieve SOP Classes. These SOP Classes are described in this Standard. For example, an MR scanner may be implemented to generate Study Instance UIDs for images generated on the MR. When these images are sent to an archive which is HIS/RIS aware, it may choose to change the UID of the study assigned to the study by the PACS. The mechanism by which it performs this coercion is implementation dependent.

2. An SCP may, for instance, convert Coding Scheme Designator values “SNM3” to “SRT”, in accordance with the DICOM conventions for SNOMED (see PS3.16).

3. Modification of Attributes that may be used to reference a SOP Instance by another SOP Instance (such as Study Instance UID and Series Instance UID attributes) will make that reference invalid. Modification of these Attributes is strongly discouraged.

4. Other Attributes may be modified/corrected by an SCP of a Storage SOP Class.

5. Modification of Attributes may affect digital signatures referencing the content of the SOP Instance.

Three levels of Digital Signature support are defined for an SCP which claims conformance to Level 2 (Full) storage support:

Signature Level 1. SCP may not preserve Digital Signatures and does not replace them.

Signature Level 2. SCP does not preserve the integrity of incoming Digital Signatures, but does validate the signatures of SOP Instances being stored, takes implementation-specific measures for insuring the integrity of data stored, and will add replacement Digital Signatures before sending SOP Instances elsewhere.

Signature Level 3. SCP does preserve the integrity of incoming Digital Signatures (i.e. is bit-preserving and stores and retrieves all Attributes regardless of whether they are defined in the IOD).

B.4.2 Conformance as An SCU

The SCU shall generate only C-STORE requests with SOP Instances which meet the requirements of the IOD associated with the SOP Class.

B.4.2.1 SCU Fall-Back Behavior

During Association Negotiation, an application may propose a specialized SOP Class and its related general SOP Class in separate Presentation Contexts as a Storage SCU. If the Association Acceptor rejects the specialized SOP Class Presentation Context, but accepts the related general SOP Class Presentation Context, the application may send instances of the specialized SOP Class as instances of the related general SOP Class. In this fall-back behavior, the SOP Class UID of the instance shall be the UID of the related general SOP Class, and any special semantics associated with the specialized SOP Class may be lost; the SOP Instance UID shall remain the same.

Note: The SCU may include the SOP Class UID of the original intended specialized SOP Class in the attribute Original Specialized SOP Class UID (0008,001B) of the instance sent under the related general SOP Class. In some cases, e.g., when all intermediate storage applications are Level 2 SCPs, this may allow an ultimate receiver of the instance to recast it as an instance of the specialized SOP Class IOD. However, this transformation is not guaranteed.

B.4.3 Conformance Statement Requirements

An implementation may conform to a SOP Class of the Storage Service Class as an SCU, SCP or both. The Conformance Statement shall be in the format defined in PS 3.2.

B.4.3.1 Conformance Statement for An SCU

The following issues shall be documented in the Conformance Statement of any implementation claiming conformance to the Storage SOP Class as an SCU:

— The behavior of the SCU in the case of a successful C-STORE response status shall be described.

— The behavior of the SCU in each case of an unsuccessful C-STORE response status shall be described.

— The behavior of the SCU in the case of a Warning status received in response to a C-STORE operation.

— Whether extended negotiation is supported.

B.4.3.2 Conformance Statement for An SCP

The following issues shall be documented in the Conformance Statement of any implementation claiming conformance to the Storage Service Class as an SCP:

— The behavior of the SCP in the case of a successful C-STORE operation shall be described. This includes the following:

— the access method for a stored SOP Instance

— the duration of the storage

— The meaning of each case of an unsuccessful C-STORE response status shall be described, as well as appropriate recovery action.

— The meaning of each case of a warning C-STORE response status shall be described, as well as appropriate action.

— If the SCP performs coercion on any Attributes, this shall be stated, and the conditions under which it may occur shall be described.

B.4.4 Specialized Conformance

Implementations may provide Specialized SOP Class conformance by providing a proper superset of the SOP Instances to be stored. Implementations providing Specialized SOP Class Conformance to one of the SOP Classes defined in this Annex shall be conformant as described in the following sections and shall include within their Conformance Statement information as described in the following sections.

An implementation shall be permitted to conform as a Specialization of the standard SOP Class as an SCU, SCP or both. The Conformance Statement shall be in the format defined in PS 3.2.

B.4.4.1 Specialized SOP Class Identification

Any implementation which specializes the standard SOP Class shall define its specialization as an Allomorphic subclass of the standard SOP Class. As such, the specialization shall have its own unique SOP Class identification.

The Conformance Statement shall include a SOP Class Identification Statement as defined in PS 3.2, declaring a SOP Name and SOP Class UID which identify the Specialized SOP Class. The SOP Name is not guaranteed to be unique (unless the implementor chooses to copyright it) but is provided for informal identification of the SOP Class. The SOP Class UID shall uniquely identify the Specialized SOP Class and conform to the DICOM UID requirements as specified in PS 3.5.

B.4.4.2 Specialized Information Object Definition

The standard SOP Class may be specialized by supporting additional private Attributes. The SCU Operations Statement shall describe these specializations and be formatted as defined in PS 3.2. Following this statement shall be the list of Attributes which may be sent or stored with SOP Instances.

B.5 Standard SOP classes

The SOP Classes in the Storage Service Class identify the Composite IODs to be stored. Table B.5-1 identifies Standard SOP Classes.

Table B.5-1 STANDARD SOP CLASSES

SOP Class Name SOP Class UID IOD Specification (defined in PS 3.3)
Computed Radiography Image Storage 1.2.840.10008.5.1.4.1.1.1
Digital X-Ray Image Storage - For Presentation 1.2.840.10008.5.1.4.1.1.1.1 DX IOD (see B.5.1.1)
Digital X-Ray Image Storage - For Processing 1.2.840.10008.5.1.4.1.1.1.1.1 DX IOD (see B.5.1.1)
Digital Mammography Image Storage - For Presentation 1.2.840.10008.5.1.4.1.1.1.2 Digital Mammography IOD (see B.5.1.2)
Digital Mammography Image Storage - For Processing 1.2.840.10008.5.1.4.1.1.1.2.1 Digital Mammography IOD (see B.5.1.2)
Digital Intra-oral X-Ray Image Storage - For Presentation 1.2.840.10008.5.1.4.1.1.1.3 Digital Intra-oral X-Ray IOD (see B.5.1.3)
Digital Intra-oral X-Ray Image Storage - For Processing 1.2.840.10008.5.1.4.1.1.1.3.1 Digital Intra-oral X-Ray IOD (see B.5.1.3)
CT Image Storage 1.2.840.10008.5.1.4.1.1.2
Enhanced CT Image Storage 1.2.840.10008.5.1.4.1.1.2.1 Enhanced CT Image (see B.5.1.7)
Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1
MR Image Storage 1.2.840.10008.5.1.4.1.1.4
Enhanced MR Image Storage 1.2.840.10008.5.1.4.1.1.4.1 Enhanced MR Image (see B.5.1.6)
MR Spectroscopy Storage 1.2.840.10008.5.1.4.1.1.4.2 MR Spectroscopy
Enhanced MR Color Image Storage 1.2.840.10008.5.1.4.1.1.4.3 Enhanced MR Color Image
Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1
Enhanced US Volume Storage 1.2.840.10008.5.1.4.1.1.6.2 Enhanced US Volume
Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7
Multi-frame Single Bit Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7.1 Multi-frame Single Bit Secondary Capture Image
Multi-frame Grayscale Byte Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7.2 Multi-frame Grayscale Byte Secondary Capture Image
Multi-frame Grayscale Word Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7.3 Multi-frame Grayscale Word Secondary Capture Image
Multi-frame True Color Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7.4 Multi-frame True Color Secondary Capture Image
12-lead ECG Waveform Storage 1.2.840.10008.5.1.4.1.1.9.1.1 12-lead ECG Waveform
General ECG Waveform Storage 1.2.840.10008.5.1.4.1.1.9.1.2 General ECG Waveform
Ambulatory ECG Waveform Storage 1.2.840.10008.5.1.4.1.1.9.1.3 Ambulatory ECG Waveform
Hemodynamic Waveform Storage 1.2.840.10008.5.1.4.1.1.9.2.1 Hemodynamic Waveform
Cardiac Electrophysiology Waveform Storage 1.2.840.10008.5.1.4.1.1.9.3.1 Cardiac Electrophysiology Waveform
Basic Voice Audio Waveform Storage 1.2.840.10008.5.1.4.1.1.9.4.1 Basic Voice Audio Waveform
General Audio Waveform Storage 1.2.840.10008.5.1.4.1.1.9.4.2 General Audio Waveform
Arterial Pulse Waveform Storage 1.2.840.10008.5.1.4.1.1.9.5.1 Arterial Pulse Waveform
Respiratory Waveform Storage 1.2.840.10008.5.1.4.1.1.9.6.1 Respiratory Waveform
Grayscale Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.1 Grayscale Softcopy Presentation State Storage
Color Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.2 Color Softcopy Presentation State
Pseudo-Color Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.3 Pseudo-Color Softcopy Presentation State
Blending Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.4 Blending Softcopy Presentation State
XA/XRF Grayscale Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.5 XA/XRF Grayscale Softcopy Presentation State
X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1
Enhanced XA Image Storage 1.2.840.10008.5.1.4.1.1.12.1.1
X-Ray Radiofluoroscopic Image Storage 1.2.840.10008.5.1.4.1.1.12.2
Enhanced XRF Image Storage 1.2.840.10008.5.1.4.1.1.12.2.1
X-Ray 3D Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.13.1.1 X-Ray 3D Angiographic Image
X-Ray 3D Craniofacial Image Storage 1.2.840.10008.5.1.4.1.1.13.1.2 X-Ray 3D Craniofacial Image
Breast Tomosynthesis Image Storage 1.2.840.10008.5.1.4.1.1.13.1.3 Breast Tomosynthesis Image
Intravascular Optical Coherence Tomography Image Storage – For Presentation 1.2.840.10008.5.1.4.1.1.14.1 IVOCT IOD (see B.5.1.13)
Intravascular Optical Coherence Tomography Image Storage – For Processing 1.2.840.10008.5.1.4.1.1.14.2 IVOCT IOD (see B.5.1.13)
Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.20
Raw Data Storage 1.2.840.10008.5.1.4.1.1.66 Raw Data
Spatial Registration Storage 1.2.840.10008.5.1.4.1.1.66.1 Spatial Registration
Spatial Fiducials Storage 1.2.840.10008.5.1.4.1.1.66.2 Spatial Fiducials
Deformable Spatial Registration Storage 1.2.840.10008.5.1.4.1.1.66.3 Deformable Spatial Registration
Segmentation Storage 1.2.840.10008.5.1.4.1.1.66.4 Segmentation
Surface Segmentation Storage 1.2.840.10008.5.1.4.1.1.66.5 Surface Segmentation
Real World Value Mapping Storage 1.2.840.10008.5.1.4.1.1.67 Real World Value Mapping
VL Endoscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.1 VL Endoscopic Image
Video Endoscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.1.1 Video Endoscopic Image
VL Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.2 VL Microscopic Image
Video Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.2.1 Video Microscopic Image
VL Slide-Coordinates Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.3 VL Slide-Coordinates Microscopic Image
VL Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4 VL Photographic Image
Video Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4.1 Video Photographic Image
Ophthalmic Photography 8 Bit Image Storage 1.2.840.10008.5.1.4.1.1.77.1.5.1 Ophthalmic Photography 8 Bit Image
Ophthalmic Photography 16 Bit Image Storage 1.2.840.10008.5.1.4.1.1.77.1.5.2 Ophthalmic Photography 16 Bit Image
Stereometric Relationship Storage 1.2.840.10008.5.1.4.1.1.77.1.5.3 Stereometric Relationship
Ophthalmic Tomography Image Storage 1.2.840.10008.5.1.4.1.1.77.1.5.4 Ophthalmic Tomography Image
VL Whole Slide Microscopy Image Storage 1.2.840.10008.5.1.4.1.1.77.1.6 VL Whole Slide Microscopy Image
Lensometry Measurements Storage 1.2.840.10008.5.1.4.1.1.78.1 Lensometry Measurements
Autorefraction Measurements Storage 1.2.840.10008.5.1.4.1.1.78.2 Autorefraction Measurements
Keratometry Measurements Storage 1.2.840.10008.5.1.4.1.1.78.3 Keratometry Measurements
Subjective Refraction Measurements Storage 1.2.840.10008.5.1.4.1.1.78.4 Subjective Refraction Measurements
Visual Acuity Measurements Storage 1.2.840.10008.5.1.4.1.1.78.5 Visual Acuity Measurements
Spectacle Prescription Report Storage 1.2.840.10008.5.1.4.1.1.78.6 Spectacle Prescription Report
Ophthalmic Axial Measurements Storage 1.2.840.10008.5.1.4.1.1.78.7 Ophthalmic Axial Measurements
Intraocular Lens Calculations Storage 1.2.840.10008.5.1.4.1.1.78.8 Intraocular Lens Calculations
Macular Grid Thickness and Volume Report 1.2.840.10008.5.1.4.1.1.79.1 Macular Grid Thickness and Volume Report
Ophthalmic Visual Field Static Perimetry Measurements Storage 1.2.840.10008.5.1.4.1.1.80.1 Ophthalmic Visual Field Static Perimetry Measurements
Basic Text SR 1.2.840.10008.5.1.4.1.1.88.11 Basic Text SR
Enhanced SR 1.2.840.10008.5.1.4.1.1.88.22 Enhanced SR
Comprehensive SR 1.2.840.10008.5.1.4.1.1.88.33 Comprehensive SR
Procedure Log 1.2.840.10008.5.1.4.1.1.88.40 Procedure Log
Mammography CAD SR 1.2.840.10008.5.1.4.1.1.88.50 Mammography CAD SR IOD
Key Object Selection 1.2.840.10008.5.1.4.1.1.88.59 Key Object Selection Document
Chest CAD SR 1.2.840.10008.5.1.4.1.1.88.65 Chest CAD SR IOD
X-Ray Radiation Dose SR 1.2.840.10008.5.1.4.1.1.88.67 X-Ray Radiation Dose SR
Colon CAD SR 1.2.840.10008.5.1.4.1.1.88.69 Colon CAD SR IOD
Implantation Plan SR Document Storage 1.2.840.10008.5.1.4.1.1.88.70 Implantation Plan SR Document
Encapsulated PDF Storage 1.2.840.10008.5.1.4.1.1.104.1 Encapsulated PDF IOD
Encapsulated CDA Storage 1.2.840.10008.5.1.4.1.1.104.2 Encapsulated CDA IOD
Positron Emission Tomography Image Storage 1.2.840.10008.5.1.4.1.1.128
Enhanced PET Image Storage 1.2.840.10008.5.1.4.1.1.130 Enhanced PET Image
Basic Structured Display Storage 1.2.840.10008.5.1.4.1.1.131 Basic Structured Display IOD
RT Image Storage 1.2.840.10008.5.1.4.1.1.481.1
RT Dose Storage 1.2.840.10008.5.1.4.1.1.481.2
RT Structure Set Storage 1.2.840.10008.5.1.4.1.1.481.3
RT Beams Treatment Record Storage 1.2.840.10008.5.1.4.1.1.481.4
RT Plan Storage 1.2.840.10008.5.1.4.1.1.481.5
RT Brachy Treatment Record Storage 1.2.840.10008.5.1.4.1.1.481.6
RT Treatment Summary Record Storage 1.2.840.10008.5.1.4.1.1.481.7
RT Ion Plan Storage 1.2.840.10008.5.1.4.1.1.481.8 IOD defined in PS 3.3
RT Ion Beams Treatment Record Storage 1.2.840.10008.5.1.4.1.1.481.9 IOD defined in PS 3.3
RT Beams Delivery Instruction Storage 1.2.840.10008.5.1.4.34.7 RT Beams Delivery Instruction
Generic Implant Template Storage 1.2.840.10008.5.1.4.43.1 Generic Implant Template
Implant Assembly Template Storage 1.2.840.10008.5.1.4.44.1 Implant Assembly Template
Implant Template Group Storage 1.2.840.10008.5.1.4.45.1 Implant Template Group

B.5.1 Specialization for Standard SOP Classes

B.5.1.1 Digital X-Ray Image Storage SOP Classes

The Digital X-Ray Image Storage - For Presentation SOP Class shall use the DX IOD with an Enumerated Value of FOR PRESENTATION for Presentation Intent Type (0008,0068).

The Digital X-Ray Image Storage - For Processing SOP Class shall use the DX IOD with an Enumerated Value of FOR PROCESSING for Presentation Intent Type (0008,0068).

An SCU or SCP of the Digital X-Ray Image Storage - For Processing SOP Class shall also support the Digital X-Ray Image Storage - For Presentation SOP Class.

Notes: 1. The intent of this requirement is to ensure a useful level of interoperability by avoiding the situation where an SCU might support only the Digital X-Ray Image Storage - For Processing SOP Class and an SCP only the Digital X-Ray Image Storage - For Presentation SOP Class, or vice versa. The burden is therefore to support the Digital X-Ray Image Storage - For Presentation SOP Class as a “baseline”.

2. The term “support” is used in this section in the sense that an SCU or SCP must be capable of sending or receiving the For Presentation SOP Class. There is no intent to imply that an SCU must always send an instance of the For Presentation SOP Class when an instance of the For Processing SOP Class is sent.

Nor is there any intent to imply that that during Association establishment, that a Presentation Context for the For Presentation SOP Class has to be proposed by the initiator. However, an association acceptor may reject a For Presentation SOP Class Presentation Context if it accepts a For Processing SOP Class Presentation Context, and prefers that SOP Class, in which case it may no longer be able to “pass on” the object later as an SCU unless it is able to generate a For Presentation object.

It is not possible for an SCP to determine from proposed Presentation Contexts whether or not an SCU “supports” (is capable of sending) both For Processing and For Presentation SOP Class Instances. Such a determination requires a priori knowledge of the information contained in the Conformance Statement for the SCU, as well as how the SCU is configured and operated. An SCU that supports both SOP Classes may well choose to only propose one or the other during Association establishment, depending on which Instances it actually intends to send over that particular association (although the SCU must be capable of sending instances of the For Presentation SOP Class if the SCP does not accept the For Processing).

The intent of the requirement is that if an SCU is only capable of sending the For Presentation SOP Class, any SCP will be guaranteed to be able to receive it. Conversely, if an SCP is only capable of receiving the For Presentation SOP Class, any SCU will be guaranteed to be able to send it.

B.5.1.2 Digital Mammography Image Storage SOP Classes

The Digital Mammography Image Storage - For Presentation SOP Class shall use the Digital Mammography IOD with an Enumerated Value of FOR PRESENTATION for Presentation Intent Type (0008,0068).

The Digital Mammography Image Storage - For Processing SOP Class shall use the Digital Mammography IOD with an Enumerated Value of FOR PROCESSING for Presentation Intent Type (0008,0068).

An SCU or SCP of the Digital Mammography Image Storage - For Processing SOP Class shall also support the Digital Mammography Image Storage - For Presentation SOP Class.

B.5.1.3 Digital Intra-oral X-Ray Image Storage SOP Classes

The Digital Intra-oral X-Ray Image Storage - For Presentation SOP Class shall use the Digital Intra-oral X-Ray IOD with an Enumerated Value of FOR PRESENTATION for Presentation Intent Type (0008,0068).

The Digital Intra-oral X-Ray Image Storage - For Processing SOP Class shall use the Digital Intra-oral X-Ray IOD with an Enumerated Value of FOR PROCESSING for Presentation Intent Type (0008,0068).

An SCU or SCP of the Digital Intra-oral X-Ray Image Storage - For Processing SOP Class shall also support the Digital Intra-oral X-Ray Image Storage - For Presentation SOP Class.

B.5.1.4 Softcopy Presentation State Storage SOP Classes

See Annex N.

B.5.1.5 Structured Reporting Storage SOP Classes

The requirements of Annex O apply to the following SOP Classes:

Annex O requirements do not apply to the Key Object Selection Document SOP Class.

B.5.1.6 Enhanced MR Image Storage SOP Class

An SCP of the Enhanced MR Image Storage SOP Class shall also support the Grayscale Softcopy Presentation State Storage SOP Class.

Note: This requirement is present in order to allow the exchange of graphical annotations created by an acquisition device.

B.5.1.7 Enhanced CT Image Storage SOP Class

An SCP of the Enhanced CT Image Storage SOP Class shall also support the Grayscale Softcopy Presentation State Storage SOP Class.

Note: This requirement is present in order to allow the exchange of graphical annotations created by an acquisition device.

B.5.1.8 Enhanced MR Color Image Storage SOP Class

An SCP of the Enhanced MR Image Storage SOP Class shall also support the Color Softcopy Presentation State Storage SOP Class.

Note: This requirement is present in order to allow the exchange of graphical annotations created by an acquisition device.

B.5.1.9 Basic Structured Display

An SCU of the Basic Structured Display Storage SOP Class that creates SOP Instances of the Class shall identify in its Conformance Statement the Composite Storage SOP Classes and Softcopy Presentation State Storage SOP Classes that are also supported by the SCU, and which may be referenced by Basic Structured Display SOP Instances it creates. It shall identify in its Conformance Statement the values it may use in the attributes Image Box Layout Type (0072,0304) and Type of Synchronization (0072,0434).

An SCP of the Basic Structured Display Storage SOP Class, when rendering SOP Instances of the Class, shall preserve the aspect ratio specified by the Nominal Screen Definition Sequence (0072,0102) attributes Number of Vertical Pixels (0072,0104) and Number of Horizontal Pixels (0072,0106) without clipping.

Notes: 1. The SCP is not required to display using the exact number of vertical and horizontal pixels. The SCP may use as much of its display screen as it desires, while maintaining the Structured Display aspect ratio.

2. If the display screen has a different aspect ratio, the positioning of the display on the screen is unspecified (centered, left or right justified, top or bottom justified).

An SCP of the Basic Structured Display Storage SOP Class that is capable of rendering SOP Instances of the Class shall identify in its Conformance Statement the Composite Storage SOP Classes and Softcopy Presentation State Storage SOP Classes that are also supported by the SCP, and which will be rendered when referenced by Basic Structured Display SOP Instances for display. It shall specify in its Conformance Statement the user display controls and interactions for the values of Image Box Layout Type (0072,0304) and Type of Synchronization (0072,0434) that it supports. It shall identify in its Conformance Statement its behavior when encountering a referenced Presentation State or other Composite Storage SOP Instance whose display it does not support, or an unsupported value of Image Box Layout Type or Type of Synchronization; such behavior shall include at a minimum a display to the user of the nature of the incompatibility.

B.5.1.10 Implant Template Storage SOP Classes

A device that is a Generic Implant Template Storage, Implant Assembly Template Storage, or Implant Template Group Storage SOP Class SCU may modify information in a SOP Instance that it has previously sent or received. When this SOP Instance is modified and sent to an SCP, it shall be assigned a new SOP Instance UID if there is addition, removal or update of any attribute within:

Referential integrity between sets of related SOP instances shall be maintained.

B.5.1.11 Ophthalmic Axial Measurements Storage SOP Class

Ophthalmic axial measurements devices are used in the preoperative assessment of every cataract surgery patient. Ophthalmic axial measurements SOP Classes support ophthalmic axial measurements devices.

For a device that is both a SCU and a SCP of the Ophthalmic Axial Measurements Storage SOP Class, in addition to the behavior for the Storage Service Class specified in B.2.2, the following additional requirements are specified for Ophthalmic Axial Measurements Storage SOP Classes:

— A SCP of this SOP Class shall support Level 2 Conformance as defined in Section B.4.1.

Note: This requirement means that all Type 1, Type 2, and Type 3 Attributes defined in the Information Object Definition and Private Attributes associated with the SOP Class will be stored and may be accessed.

B.5.1.12 IOL Calculation Storage SOP Class

IOL (intraocular lens) calculation is used in the preoperative assessment of every cataract surgery patient. IOL Calculation SOP Classes support IOL calculation software, which may be located either on ophthalmic axial measurement devices or on a separate computer.

For a device that is both a SCU and a SCP of the IOL Calculation Storage SOP Class, in addition to the behavior for the Storage Service Class specified in B.2.2, the following additional requirements are specified for IOL Calculation Storage SOP Classes:

— A SCP of this SOP Class shall support Level 2 Conformance as defined in Section B.4.1.

Note: This requirement means that all Type 1, Type 2, and Type 3 Attributes defined in the Information Object Definition and Private Attributes associated with the SOP Class will be stored and may be accessed.

B.5.1.13 Intravascular OCT Image Storage SOP Classes

The Intravascular OCT Image Storage - For Presentation SOP Class shall use the IVOCT IOD with an Enumerated Value of FOR PRESENTATION for Presentation Intent Type (0008,0068).

The Intravascular OCT Image Storage - For Processing SOP Class shall use the IVOCT IOD with an Enumerated Value of FOR PROCESSING for Presentation Intent Type (0008,0068).

An SCU or SCP of the Intravascular OCT Image Storage - For Processing SOP Class shall also support the Intravascular OCT Image Storage - For Presentation SOP Class.

Notes: 1. The intent of this requirement is to ensure a useful level of interoperability by avoiding the situation where an SCU might support only the Intravascular OCT Image Storage - For Processing SOP Class and an SCP only the Intravascular OCT Image Storage - For Presentation SOP Class, or vice versa. The burden is therefore to support the Intravascular OCT Image Storage - For Presentation SOP Class as a “baseline”.

2. The term “support” is used in this section in the sense that an SCU or SCP must be capable of sending or receiving the For Presentation SOP Class. There is no intent to imply that an SCU must always send an instance of the For Presentation SOP Class when an instance of the For Processing SOP Class is sent.

Nor is there any intent to imply that that during Association establishment, that a Presentation Context for the For Presentation SOP Class has to be proposed by the initiator. However, an association acceptor may reject a For Presentation SOP Class Presentation Context if it accepts a For Processing SOP Class Presentation Context, and prefers that SOP Class, in which case it may no longer be able to “pass on” the object later as an SCU unless it is able to generate a For Presentation object.

It is not possible for an SCP to determine from proposed Presentation Contexts whether or not an SCU “supports” (is capable of sending) both For Processing and For Presentation SOP Class Instances. Such a determination requires a priori knowledge of the information contained in the Conformance Statement for the SCU, as well as how the SCU is configured and operated. An SCU that supports both SOP Classes may well choose to only propose one or the other during Association establishment, depending on which Instances it actually intends to send over that particular association (although the SCU must be capable of sending instances of the For Presentation SOP Class if the SCP does not accept the For Processing).

The intent of the requirement is that if an SCU is only capable of sending the For Presentation SOP Class, any SCP will be guaranteed to be able to receive it. Conversely, if an SCP is only capable of receiving the For Presentation SOP Class, any SCU will be guaranteed to be able to send it.

B.6 Retired Standard SOP Classes

The SOP Classes in Table B.6-1 were defined in previous versions of the DICOM Standard. They are now retired and have been replaced by new standard SOP Classes shown in Table B.5-1.

Note: Usage of the retired SOP Classes is permitted by DICOM. However, new implementations are strongly encouraged to implement the newer SOP Classes.

Table B.6-1 RETIRED STANDARD SOP CLASSES

SOP Class Name SOP Class UID
Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.5
Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6
Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3
X-Ray Angiographic Bi-plane Image Storage 1.2.840.10008.5.1.4.1.1.12.3