PS3.4

DICOM PS3.4 2021e - Service Class Specifications

DICOM Standards Committee

A DICOM® publication


Table of Contents

Notice and Disclaimer
Foreword
1. Scope and Field of Application
2. Normative References
Bibliography
3. Definitions
Glossary
4. Symbols and Abbreviations
5. Conventions
5.1. Entity-Relationship Model
5.1.1. Entity
5.1.2. Relationship
5.2. Sequences
5.3. Response Status Values
5.4. Usage Specification
5.4.1. Use of DIMSE Services
5.4.2. Use of Attributes in Normalized Services
5.4.2.1. DIMSE Service N-CREATE, N-SET, N-ACTION
5.4.2.2. DIMSE Service N-GET, N-EVENT-REPORT
5.4.2.3. Other Requirements
6. DICOM Information Model
6.1. Information Object Definition
6.1.1. Composite IOD
6.1.2. Normalized IOD
6.2. Attributes
6.3. On-Line Communication and Media Storage Services
6.3.1. DIMSE-C Services
6.3.2. DIMSE-N Services
6.4. DIMSE Service Group
6.5. Service-Object Pair (SOP) Class
6.5.1. Normalized and Composite SOP Classes
6.6. Association Negotiation
6.7. Service Class Specification
7. DICOM Model of the Real World
8. Coded Entry Usage in Service Specifications
A. Verification Service Class (Normative)
A.1. Overview
A.1.1. Scope
A.2. SCU/SCP Behavior
A.3. DIMSE-C Service Group
A.4. Verification SOP Class
A.5. Association Negotiation
A.6. Conformance
A.6.1. Conformance Supporting the SCU Role
A.6.2. Conformance Supporting the SCP Role
A.6.3. Conformance Statement
B. Storage Service Class (Normative)
B.1. Overview
B.1.1. Scope
B.1.2. Service Definition
B.2. Behavior
B.2.1. Behavior of an SCU
B.2.2. Behavior of an SCP
B.2.3. Statuses
B.3. Association Negotiation
B.3.1. Extended Negotiation
B.3.1.1. Service-Class-Application-Information (A-ASSOCIATE-RQ)
B.3.1.2. Service-Class-Application-Information (A-ASSOCIATE-AC)
B.3.1.3. Service Class UID (A-ASSOCIATE-RQ)
B.3.1.4. Related General SOP Classes (A-ASSOCIATE-RQ)
B.4. Conformance
B.4.1. Conformance as an SCP
B.4.1.1. Levels of Conformance
B.4.1.2. Support of Additional SOP Classes
B.4.1.3. Coercion of Attributes
B.4.1.4. Levels of Digital Signature
B.4.2. Conformance as an SCU
B.4.2.1. SCU Fall-Back Behavior
B.4.3. Conformance Statement Requirements
B.4.3.1. Conformance Statement for an SCU
B.4.3.2. Conformance Statement for an SCP
B.4.4. Specialized Conformance
B.4.4.1. Specialized SOP Class Identification
B.4.4.2. Specialized Information Object Definition
B.5. Standard SOP Classes
B.5.1. Specialization for Standard SOP Classes
B.5.1.1. Digital X-Ray Image Storage SOP Classes
B.5.1.2. Digital Mammography X-Ray Image Storage SOP Classes
B.5.1.3. Digital Intra-Oral X-Ray Image Storage SOP Classes
B.5.1.4. Softcopy Presentation State Storage SOP Classes
B.5.1.5. Structured Reporting Storage SOP Classes
B.5.1.6. Enhanced MR Image Storage and Legacy Converted Enhanced MR Image Storage SOP Class
B.5.1.7. Enhanced CT Image Storage and Legacy Converted Enhanced CT Image Storage SOP Class
B.5.1.8. Enhanced MR Color Image Storage SOP Class
B.5.1.9. Basic Structured Display
B.5.1.10. Implant Template Storage SOP Classes
B.5.1.11. Ophthalmic Axial Measurements Storage SOP Class
B.5.1.12. IOL Calculation Storage SOP Class
B.5.1.13. Intravascular OCT Image Storage SOP Classes
B.5.1.14. Ophthalmic Thickness Map Storage SOP Class
B.5.1.15. Enhanced PET Image Storage and Legacy Converted Enhanced PET Image Storage SOP Class
B.5.1.16. Enhanced PET Image Storage SOP Classes
B.5.1.17. Corneal Topography Map Storage SOP Class
B.5.1.18. Breast Projection X-Ray Image Storage SOP Classes
B.5.1.19. Planar MPR Volumetric Presentation State Storage SOP Classes
B.5.1.20. Content Assessment Results Storage SOP Classes
B.5.1.21. CT and XA Performed Procedure Protocol Storage SOP Classes
B.5.1.22. Raw Data Storage SOP Class
B.5.1.23. Enhanced Multi-Frame Image SOP Classes
B.5.1.24. Volume Rendering Volumetric Presentation State Storage SOP Classes
B.6. Retired Standard SOP Classes
C. Query/Retrieve Service Class (Normative)
C.1. Overview
C.1.1. Scope
C.1.2. Conventions
C.1.3. Query/Retrieve Information Model
C.1.4. Service Definition
C.2. Query/Retrieve Information Model Definition
C.2.1. Entity-Relationship Model Definition
C.2.2. Attributes Definition
C.2.2.1. Attribute Types
C.2.2.1.1. Unique Keys
C.2.2.1.2. Required Keys
C.2.2.1.3. Optional Keys
C.2.2.2. Attribute Matching
C.2.2.2.1. Single Value Matching
C.2.2.2.1.1. Attributes of VR of PN
C.2.2.2.1.2. Attributes of VR of AE, CS, LO, LT, PN, SH, ST, UC, UR and UT
C.2.2.2.1.3. Attributes of VR of DA, DT or TM
C.2.2.2.2. List of UID Matching
C.2.2.2.3. Universal Matching
C.2.2.2.4. Wild Card Matching
C.2.2.2.5. Range Matching
C.2.2.2.5.1. Range Matching of Attributes of VR of DA
C.2.2.2.5.2. Range Matching of Attributes of VR of TM
C.2.2.2.5.3. Range Matching of Attributes of VR of DT
C.2.2.2.5.4. Range Matching General Rules
C.2.2.2.6. Sequence Matching
C.2.2.3. Matching Multiple Values
C.3. Standard Query/Retrieve Information Models
C.3.1. Patient Root Query/Retrieve Information Model
C.3.2. Study Root Query/Retrieve Information Model
C.3.3. Patient/Study Only Query/Retrieve Information Model
C.3.4. Additional Query/Retrieve Attributes
C.3.5. New Instance Creation for Enhanced Multi-Frame Image Conversion
C.4. DIMSE-C Service Groups
C.4.1. C-FIND Operation
C.4.1.1. C-FIND Service Parameters
C.4.1.1.1. SOP Class UID
C.4.1.1.2. Priority
C.4.1.1.3. Identifier
C.4.1.1.3.1. Request Identifier Structure
C.4.1.1.3.2. Response Identifier Structure
C.4.1.1.4. Status
C.4.1.2. C-FIND SCU Behavior
C.4.1.2.1. Baseline Behavior of SCU
C.4.1.2.2. Extended Behavior of SCU
C.4.1.2.2.1. Relational-Queries
C.4.1.2.2.2. Enhanced Multi-Frame Image Conversion
C.4.1.3. C-FIND SCP Behavior
C.4.1.3.1. Baseline Behavior of SCP
C.4.1.3.1.1. Hierarchical Search Method
C.4.1.3.2. Extended Behavior of SCP
C.4.1.3.2.1. Relational-Queries
C.4.1.3.2.2. Relational Search Method
C.4.1.3.2.3. Enhanced Multi-Frame Image Conversion
C.4.2. C-MOVE Operation
C.4.2.1. C-MOVE Service Parameters
C.4.2.1.1. SOP Class UID
C.4.2.1.2. Priority
C.4.2.1.3. Move Destination
C.4.2.1.4. Identifier
C.4.2.1.4.1. Request Identifier Structure
C.4.2.1.4.2. Response Identifier Structure
C.4.2.1.5. Status
C.4.2.1.6. Number of Remaining Sub-Operations
C.4.2.1.7. Number of Completed Sub-Operations
C.4.2.1.8. Number of Failed Sub-Operations
C.4.2.1.9. Number of Warning Sub-Operations
C.4.2.2. C-MOVE SCU Behavior
C.4.2.2.1. Baseline Behavior of SCU
C.4.2.2.2. Extended Behavior of SCU
C.4.2.2.2.1. Relational-Retrieve
C.4.2.2.2.2. Enhanced Multi-Frame Image Conversion
C.4.2.3. C-MOVE SCP Behavior
C.4.2.3.1. Baseline Behavior of SCP
C.4.2.3.2. Extended Behavior of SCP
C.4.2.3.2.1. Relational-Retrieve
C.4.2.3.2.2. Enhanced Multi-Frame Image Conversion
C.4.3. C-GET Operation
C.4.3.1. C-GET Service Parameters
C.4.3.1.1. SOP Class UID
C.4.3.1.2. Priority
C.4.3.1.3. Identifier
C.4.3.1.3.1. Request Identifier Structure
C.4.3.1.3.2. Response Identifier Structure
C.4.3.1.4. Status
C.4.3.1.5. Number of Remaining Sub-Operations
C.4.3.1.6. Number of Completed Sub-Operations
C.4.3.1.7. Number of Failed Sub-Operations
C.4.3.1.8. Number of Warning Sub-Operations
C.4.3.2. C-GET SCU Behavior
C.4.3.2.1. Baseline Behavior of SCU
C.4.3.2.2. Extended Behavior of SCU
C.4.3.2.2.1. Relational-Retrieve
C.4.3.2.2.2. Enhanced Multi-Frame Image Conversion
C.4.3.3. C-GET SCP Behavior
C.4.3.3.1. Baseline Behavior of SCP
C.4.3.3.2. Extended Behavior of SCP
C.4.3.3.2.1. Relational-Retrieve
C.4.3.3.2.2. Enhanced Multi-Frame Image Conversion
C.5. Association Negotiation
C.5.1. Association Negotiation for C-FIND SOP Classes
C.5.1.1. SOP Class Extended Negotiation
C.5.1.1.1. SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-RQ)
C.5.1.1.2. SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-AC)
C.5.2. Association Negotiation for C-MOVE SOP Classes
C.5.2.1. SOP Class Extended Negotiation
C.5.2.1.1. SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-RQ)
C.5.2.1.2. SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-AC)
C.5.3. Association Negotiation for C-GET SOP Classes
C.5.3.1. SOP Class Extended Negotiation
C.6. SOP Class Definitions
C.6.1. Patient Root SOP Class Group
C.6.1.1. Patient Root Query/Retrieve Information Model
C.6.1.1.1. E/R Model
C.6.1.1.2. Patient Level
C.6.1.1.3. Study Level
C.6.1.1.4. Series Level
C.6.1.1.5. Composite Object Instance Level
C.6.1.1.5.1. Alternate Representation Sequence
C.6.1.1.5.2. Available SOP Transfer Syntax UID
C.6.1.1.6. Scope of the C-GET and C-MOVE Commands and Sub-Operations
C.6.1.2. Conformance Requirements
C.6.1.2.1. SCU Conformance
C.6.1.2.1.1. C-FIND SCU Conformance
C.6.1.2.1.2. C-MOVE SCU Conformance
C.6.1.2.1.3. C-GET SCU Conformance
C.6.1.2.2. SCP Conformance
C.6.1.2.2.1. C-FIND SCP Conformance
C.6.1.2.2.2. C-MOVE SCP Conformance
C.6.1.2.2.3. C-GET SCP Conformance
C.6.1.3. SOP Classes
C.6.2. Study Root SOP Class Group
C.6.2.1. Study Root Query/Retrieve Information Model
C.6.2.1.1. E/R Model
C.6.2.1.2. Study Level
C.6.2.1.3. Series Level
C.6.2.1.4. Composite Object Instance Level
C.6.2.1.5. Scope of the Get and Move Commands and Sub-Operations
C.6.2.2. Conformance Requirements
C.6.2.2.1. SCU Conformance
C.6.2.2.1.1. C-FIND SCU Conformance
C.6.2.2.1.2. C-MOVE SCU Conformance
C.6.2.2.1.3. C-GET SCU Conformance
C.6.2.2.2. SCP Conformance
C.6.2.2.2.1. C-FIND SCP Conformance
C.6.2.2.2.2. C-MOVE SCP Conformance
C.6.2.2.2.3. C-GET SCP Conformance
C.6.2.3. SOP Classes
C.6.3. Patient/Study Only SOP Class Group
D. Study Content Notification Service Class (Normative)
E. Patient Management Service Class (Normative)
F. Procedure Step SOP Classes (Normative)
F.1. Overview
F.1.1. Scope
F.1.2. Study Management Functional Model
F.1.3. Study Management Information Model
F.1.4. Study Management States
F.1.5. Modality Performed Procedure Step Management States
F.1.6. General Purpose Scheduled Procedure Step Management States (Retired)
F.1.7. General Purpose Performed Procedure Step Management States (Retired)
F.2. Conformance Overview
F.2.1. Association Negotiation
F.3. Detached Study Management SOP Class(Retired)
F.4. Study Component Management SOP Class(Retired)
F.5. Study Management Meta SOP Class(Retired)
F.6. Specialized SOP Class Conformance(Retired)
F.7. Modality Performed Procedure Step SOP Class
F.7.1. DIMSE Service Group
F.7.2. Operations
F.7.2.1. Create Modality Performed Procedure Step SOP Instance
F.7.2.1.1. Modality Performed Procedure Step Subset Specification
F.7.2.1.2. Service Class User
F.7.2.1.3. Service Class Provider
F.7.2.1.4. Status Codes
F.7.2.2. Set Modality Performed Procedure Step Information
F.7.2.2.1. Modality Performed Procedure Step IOD Subset Specification
F.7.2.2.2. Service Class User
F.7.2.2.3. Service Class Provider
F.7.2.2.4. Status Codes
F.7.3. Modality Performed Procedure Step SOP Class UID
F.7.4. Conformance Requirements
F.7.4.1. SCU Conformance
F.7.4.1.1. Operations
F.7.4.2. SCP Conformance
F.7.4.2.1. Operations
F.8. Modality Performed Procedure Step Retrieve SOP Class
F.8.1. DIMSE Service Group
F.8.2. Operations
F.8.2.1. Get Performed Procedure Step Information
F.8.2.1.1. Modality Performed Procedure Step Retrieve IOD Subset Specifications
F.8.2.1.2. Service Class User
F.8.2.1.3. Service Class Provider
F.8.2.1.4. Status Codes
F.8.3. Modality Performed Procedure Step Retrieve SOP Class UID
F.8.4. Conformance Requirements
F.8.4.1. SCU Conformance
F.8.4.1.1. Operations
F.8.4.2. SCP Conformance
F.8.4.2.1. Operations
F.9. Modality Performed Procedure Step Notification SOP Class
F.9.1. DIMSE Service Group
F.9.2. Notifications
F.9.2.1. Receive Modality Performed Procedure Step Event Notification
F.9.2.2. Provide Modality Performed Procedure Step Event Notification
F.9.2.3. Status Codes
F.9.3. Modality Performed Procedure Step Notification SOP Class UID
F.9.4. Conformance Requirements
F.9.4.1. SCU Conformance
F.9.4.1.1. Notifications
F.9.4.2. SCP Conformance
F.9.4.2.1. Notifications
F.10. General Purpose Scheduled Procedure Step SOP Class (Retired)
F.11. General Purpose Performed Procedure Step SOP Class (Retired)
G. Results Management Service Class (Normative)
H. Print Management Service Class (Normative)
H.1. Scope
H.2. Print Management Model
H.2.1. Print Management Data Flow Model
H.2.1.1. Global Data Flow Model
H.2.1.2. Grayscale Transformations
H.2.1.2.1. Modality and User Specific Transformations
H.2.1.2.2. Polarity
H.2.1.2.3. Presentation LUT
H.2.2. Print Management Service Class Structure
H.2.3. Print Management SOP Classes
H.2.4. Usage Specifications
H.2.5. Status Code Categories
H.3. Print Management Conformance
H.3.1. Scope
H.3.2. Print Management Meta SOP Classes
H.3.2.1. Description
H.3.2.2. Meta SOP Class Definitions
H.3.2.2.1. Basic Grayscale Print Management Meta SOP Class
H.3.2.2.2. Basic Color Print Management Meta SOP Class
H.3.2.2.3. Referenced Grayscale Print Management Meta SOP Class (Retired)
H.3.2.2.4. Referenced Color Print Management Meta SOP Class (Retired)
H.3.2.2.5. Pull Stored Print Management Meta SOP Class(Retired)
H.3.3. Optional SOP Classes
H.3.3.1. Description
H.3.3.2. List of Optional SOP Classes
H.3.4. Conformance Statement
H.4. Print Management SOP Class Definitions
H.4.1. Basic Film Session SOP Class
H.4.1.1. IOD Description
H.4.1.2. DIMSE Service Group
H.4.1.2.1. N-CREATE
H.4.1.2.1.1. Attributes
H.4.1.2.1.2. Status
H.4.1.2.1.3. Behavior
H.4.1.2.2. N-SET
H.4.1.2.2.1. Attributes
H.4.1.2.2.2. Status
H.4.1.2.2.3. Behavior
H.4.1.2.3. N-DELETE
H.4.1.2.3.1. Status
H.4.1.2.3.2. Behavior
H.4.1.2.4. N-ACTION
H.4.1.2.4.1. Attributes
H.4.1.2.4.2. Status
H.4.1.2.4.3. Behavior
H.4.1.3. SOP Class Definition and UID
H.4.2. Basic Film Box SOP Class
H.4.2.1. IOD Description
H.4.2.2. DIMSE Service Group
H.4.2.2.1. N-CREATE
H.4.2.2.1.1. Attributes
H.4.2.2.1.2. Status
H.4.2.2.1.3. Behavior
H.4.2.2.2. N-SET
H.4.2.2.2.1. Attributes
H.4.2.2.2.2. Status
H.4.2.2.2.3. Behavior
H.4.2.2.3. N-DELETE
H.4.2.2.3.1. Behavior
H.4.2.2.3.2. Status
H.4.2.2.4. N-ACTION
H.4.2.2.4.1. Attributes
H.4.2.2.4.2. Status
H.4.2.2.4.3. Behavior
H.4.2.3. SOP Class Definition and UID
H.4.3. Image Box SOP Classes
H.4.3.1. Basic Grayscale Image Box SOP Class
H.4.3.1.1. IOD Description
H.4.3.1.2. DIMSE Service Group
H.4.3.1.2.1. N-SET
H.4.3.1.2.1.1. Attributes
H.4.3.1.2.1.2. Status
H.4.3.1.2.1.3. Behavior
H.4.3.1.3. SOP Class Definition and UID
H.4.3.2. Basic Color Image Box SOP Class
H.4.3.2.1. IOD Description
H.4.3.2.2. DIMSE Service Group
H.4.3.2.2.1. N-SET
H.4.3.2.2.1.1. Attributes
H.4.3.2.2.1.2. Status
H.4.3.2.2.1.3. Behavior
H.4.3.2.3. SOP Class Definition and UID
H.4.3.3. Referenced Image Box SOP Class (Retired)
H.4.4. Basic Annotation Box SOP Class
H.4.4.1. IOD Description
H.4.4.2. DIMSE Service Group
H.4.4.2.1. N-SET
H.4.4.2.1.1. Attributes
H.4.4.2.1.2. Status
H.4.4.2.1.3. Behavior
H.4.4.3. SOP Class Definition and UID
H.4.5. Print Job SOP Class
H.4.5.1. IOD Description
H.4.5.2. DIMSE Service Group
H.4.5.2.1. N-EVENT-REPORT
H.4.5.2.1.1. Attributes
H.4.5.2.1.2. Behavior
H.4.5.2.1.3. Status
H.4.5.2.2. N-GET
H.4.5.2.2.1. Attributes
H.4.5.2.2.2. Behavior
H.4.5.2.2.3. Status
H.4.5.3. Execution Status Information
H.4.5.4. SOP Class Definition and UID
H.4.6. Printer SOP Class
H.4.6.1. IOD Description
H.4.6.2. DIMSE Service Group
H.4.6.2.1. N-EVENT-REPORT
H.4.6.2.1.1. Attributes
H.4.6.2.1.2. Behavior
H.4.6.2.1.3. Status
H.4.6.2.2. N-GET
H.4.6.2.2.1. Attributes
H.4.6.2.2.2. Behavior
H.4.6.2.2.3. Status
H.4.6.3. Printer Status Information
H.4.6.4. SOP Class Definition and UID
H.4.6.5. Reserved Identifications
H.4.7. VOI LUT Box SOP Class(Retired)
H.4.8. Image Overlay Box SOP Class(Retired)
H.4.9. Presentation LUT SOP Class
H.4.9.1. Information Object Description
H.4.9.1.1. Mapping of P-Values to Optical Density
H.4.9.2. DIMSE Service Group
H.4.9.2.1. N-CREATE
H.4.9.2.1.1. Attributes
H.4.9.2.1.1.1. LUT Descriptor
H.4.9.2.1.2. Status
H.4.9.2.1.3. Behavior
H.4.9.2.2. N-DELETE
H.4.9.2.2.1. Status
H.4.9.2.2.2. Behavior
H.4.9.2.4. SOP Class Definition and UID
H.4.10. Pull Print Request SOP Class(Retired)
H.4.11. Printer Configuration Retrieval SOP Class
H.4.11.1. IOD Description
H.4.11.2. DIMSE Service Group
H.4.11.2.2. N-GET
H.4.11.2.2.1. Attributes
H.4.11.2.2.2. Behavior
H.4.11.2.2.3. Status
H.4.11.3. SOP Class Definition and UID
H.4.11.4. Reserved Identifications
H.4.12. Basic Print Image Overlay Box SOP Class(Retired)
H.5. Association Negotiation
H.6. Example of Print Management SCU Session (Informative)
H.6.1. Simple Example
H.6.2. Advanced Example(Retired)
H.7. Example of the Pull Print Request Meta SOP Class (Informative)
H.8. Overlay Examples (Informative)
I. Media Storage Service Class (Normative)
I.1. Overview
I.1.1. Scope
I.1.2. Service Definition
I.2. Behavior
I.2.1. Behavior of an FSC
I.2.2. Behavior of an FSR
I.2.3. Behavior of an FSU
I.3. Conformance
I.3.1. Conformance as an FSC
I.3.2. Conformance as an FSR
I.3.3. Conformance as an FSU
I.3.4. Conformance Statement Requirements
I.3.5. Standard Extended, Specialized, and Private Conformance
I.4. Media Storage SOP Classes
I.4.1. Specialization for Standard SOP Classes (Retired)
I.5. Retired Standard SOP Classes
J. Storage Commitment Service Class (Normative)
J.1. Overview
J.1.1. Scope
J.1.2. Models Overview
J.2. Conformance Overview
J.2.1. Association Negotiation
J.3. Storage Commitment Push Model SOP Class
J.3.1. DIMSE Service Group
J.3.2. Operations
J.3.2.1. Storage Commitment Request
J.3.2.1.1. Action Information
J.3.2.1.1.1. Storage Media File Set ID Attributes
J.3.2.1.1.2. Referenced Performed Procedure Step Sequence Attribute (Retired)
J.3.2.1.1.3. SOP Instance Reference
J.3.2.1.2. Service Class User Behavior
J.3.2.1.3. Service Class Provider Behavior
J.3.2.1.4. Status Codes
J.3.3. Notifications
J.3.3.1. Storage Commitment Result
J.3.3.1.1. Event Information
J.3.3.1.1.1. Retrieve AE Title Attribute
J.3.3.1.1.2. Storage Media File Set ID Attributes
J.3.3.1.2. Service Class Provider Behavior
J.3.3.1.3. Service Class User Behavior
J.3.3.1.4. Status Codes
J.3.4. Storage Commitment Push Model SOP Class UID
J.3.5. Storage Commitment Push Model Reserved Identification
J.3.6. Conformance Requirements
J.3.6.1. SCU Conformance
J.3.6.1.1. Operations
J.3.6.1.2. Notifications.
J.3.6.2. SCP Conformance.
J.3.6.2.1. Operations
J.3.6.2.2. Notifications
J.4. Storage Commitment Pull Model SOP Class(Retired)
J.5. Storage Commitment Examples (Informative)
K. Basic Worklist Management Service (Normative)
K.1. Overview
K.1.1. Scope
K.1.2. Conventions
K.1.3. Worklist Information Model
K.1.4. Service Definition
K.2. Worklist Information Model Definition
K.2.1. Entity-Relationship Model Definition
K.2.2. Attributes Definition
K.2.2.1. Attribute Types
K.2.2.1.1. Matching Key Attributes
K.2.2.1.1.1. Required Matching Key Attributes
K.2.2.1.1.2. Optional Matching Key Attributes
K.2.2.1.2. Return Key Attributes
K.2.2.2. Attribute Matching
K.2.2.3. Matching Multiple Values
K.3. Worklist Information Model
K.4. DIMSE-C Service Group
K.4.1. C-FIND Operation
K.4.1.1. C-FIND Service Parameters
K.4.1.1.1. SOP Class UID
K.4.1.1.2. Priority
K.4.1.1.3. Identifier
K.4.1.1.3.1. Request Identifier Structure
K.4.1.1.3.2. Response Identifier Structure
K.4.1.1.4. Status
K.4.1.2. C-FIND SCU Behavior
K.4.1.3. C-FIND SCP Behavior
K.4.1.3.1. "Worklist" Search Method
K.5. Association Negotiation
K.5.1. SOP Class Extended Negotiation
K.5.1.1. SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-RQ)
K.5.1.2. SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-AC)
K.6. SOP Class Definitions
K.6.1. Modality Worklist SOP Class
K.6.1.1. Modality Worklist SOP Class Overview
K.6.1.2. Modality Worklist Information Model
K.6.1.2.1. E/R Model
K.6.1.2.2. Modality Worklist Attributes
K.6.1.3. Conformance Requirements
K.6.1.3.1. SCU Conformance
K.6.1.3.2. SCP Conformance
K.6.1.4. SOP Class
K.6.2. General Purpose Worklist SOP Class (Retired)
K.7. Examples for the Usage of the Modality Worklist (Informative)
K.8. General Purpose Worklist Example (Informative) (Retired)
L. Queue Management Service Class (Normative)
M. Handling of Identifying Parameters (Informative)
N. Softcopy Presentation State Storage SOP Classes (Normative)
N.1. Overview
N.1.1. Scope
N.2. Pixel Transformation Sequence
N.2.1. Grayscale Transformations
N.2.1.1. Modality LUT
N.2.1.2. Mask
N.2.1.3. VOI LUT
N.2.1.4. Presentation LUT
N.2.2. Color Transformations
N.2.2.1. Profile Connection Space Transformation
N.2.2.2. White Point (Informative)
N.2.3. Common Spatial and Annotation Transformations
N.2.3.1. Shutter
N.2.3.2. Pre-Spatial Transformation Annotation
N.2.3.3. Spatial Transformation
N.2.3.4. Post-Spatial Transformation Annotation
N.2.4. Blending Transformations
N.2.4.1. Underlying Image Pixels
N.2.4.2. Superimposed Image Pixels
N.2.4.3. Blending Operation
N.2.4.4. Conversion to Profile Connection Space
N.2.5. Angiography Grayscale Transformations
N.2.5.1. Mask
N.2.5.2. Edge Enhancement
N.2.6. Advanced Blending Transformations
N.3. Behavior of an SCP
N.4. Conformance
N.4.1. Conformance Statement for an SCU
N.4.2. Conformance Statement for an SCP
O. Structured Reporting Storage SOP Classes (Normative)
O.1. Overview
O.2. Structured Reporting Storage SOP Class SCU and SCP Behavior
O.2.1. Behavior of an SCU
O.2.1.1. CAD SR SOP Classes
O.2.1.2. Extensible SR SOP Class
O.2.2. Behavior of an SCP
O.2.2.1. CAD SR SOP Classes
O.2.2.2. Extensible SR SOP Class
O.3. Modification of SR Document Content
O.4. Conformance
O.4.1. Conformance Statement for an SCU
O.4.1.1. CAD SR SOP Classes
O.4.1.2. Ultrasound SR SOP Classes
O.4.2. Conformance Statement for an SCP
O.4.2.1. CAD SR SOP Classes
O.4.2.2. Extensible SR SOP Class
P. Application Event Logging Service Class (Normative)
P.1. Overview
P.1.1. Scope
P.1.2. Service Definition
P.2. Procedural Event Logging SOP Class Definition
P.2.1. DIMSE Service Group
P.2.2. Operation
P.2.2.1. Action Information
P.2.2.1.1. Study Matching Attributes
P.2.2.1.2. Synchronization Frame of Reference UID
P.2.2.1.3. Constraints on Attributes of the SR Document Content Module
P.2.2.2. Service Class User Behavior
P.2.2.3. Service Class Provider Behavior
P.2.2.4. Status Codes
P.2.2.5. Action Reply
P.2.3. Procedural Event Logging SOP Class UID
P.2.4. Procedural Event Logging Instance Identification
P.2.5. Conformance Requirements
P.2.5.1. SCU Conformance
P.2.5.2. SCP Conformance
P.3. Substance Administration Logging SOP Class Definition
P.3.1. DIMSE Service Group
P.3.2. Operation
P.3.2.1. Substance Administration Log Action Information
P.3.2.2. Service Class User Behavior
P.3.2.3. Service Class Provider Behavior
P.3.2.4. Status Codes
P.3.3. Substance Administration Logging SOP Class UID
P.3.4. Substance Administration Logging Instance UID
P.3.5. Conformance Requirements
P.3.5.1. SCU Conformance
P.3.5.2. SCP Conformance
Q. Relevant Patient Information Query Service Class (Normative)
Q.1. Overview
Q.2. DIMSE-C Service Group
Q.2.1. C-FIND Operation
Q.2.1.1. C-FIND Service Parameters
Q.2.1.1.1. SOP Class UID
Q.2.1.1.2. Priority
Q.2.1.1.3. Identifier
Q.2.1.1.3.1. Request Identifier Structure
Q.2.1.1.3.2. Response Identifier Structure
Q.2.1.1.3.3. Relevant Patient Information Templates
Q.2.1.1.4. Status
Q.3. Association Negotiation
Q.4. DIMSE-C C-FIND Service
Q.4.1. Conventions
Q.4.2. Service Definition
Q.4.3. Relevant Patient Information Model SOP Classes
Q.4.3.1. Relevant Patient Information Model
Q.4.3.1.1. E/R Model
Q.4.3.1.2. Relevant Patient Information Attributes
Q.4.3.1.2.1. Relevant Patient Information Attribute Descriptions
Q.4.3.2. Conformance Requirements
Q.4.3.2.1. SCU Conformance
Q.4.3.2.2. SCP Conformance
Q.4.3.3. SOP Classes
Q.5. Relevant Patient Information Query Example (Informative)
R. Instance Availability Notification Service Class (Normative)
R.1. Overview
R.1.1. Scope
R.2. Conformance Overview
R.3. Instance Availability Notification SOP Class
R.3.1. DIMSE Service Group
R.3.2. Operations
R.3.2.1. N-CREATE Instance Availability Notification SOP Instance
R.3.2.1.1. Attributes
R.3.2.1.2. Service Class User
R.3.2.1.3. Service Class Provider
R.3.2.1.4. Status Codes
R.3.3. Instance Availability Notification SOP Class UID
R.3.4. Conformance Requirements
R.3.4.1. SCU Conformance
R.3.4.1.1. Operations
R.3.4.2. SCP Conformance
R.3.4.2.1. Operations
S. Media Creation Management Service Class (Normative)
S.1. Overview
S.1.1. Scope
S.2. Conformance Overview
S.2.1. Association Negotiation
S.3. Media Creation Management SOP Class
S.3.1. DIMSE Service Group
S.3.2. Operations
S.3.2.1. Create a Media Creation Request
S.3.2.1.1. Attributes
S.3.2.1.1.1. Storage Media File-Set Attributes
S.3.2.1.1.2. Requested Media Application Profile
S.3.2.1.1.3. Icon Image Sequence
S.3.2.1.1.4. Labeling
S.3.2.1.1.5. Media Disposition
S.3.2.1.1.6. Allow Media Splitting
S.3.2.1.1.7. Include Non-DICOM Objects
S.3.2.1.1.8. Include Display Application
S.3.2.1.1.9. Allow Lossy Compression
S.3.2.1.2. Service Class User Behavior
S.3.2.1.3. Service Class Provider Behavior
S.3.2.1.4. Status Codes.
S.3.2.2. Initiate Media Creation
S.3.2.2.1. Action Information
S.3.2.2.1.1. Priority
S.3.2.2.2. Service Class User Behavior
S.3.2.2.3. Service Class Provider Behavior
S.3.2.2.4. Status Codes
S.3.2.3. Cancel Media Creation
S.3.2.3.1. Action Information
S.3.2.3.2. Service Class User Behavior
S.3.2.3.3. Service Class Provider Behavior
S.3.2.3.4. Status Codes
S.3.2.4. Get Media Creation Result
S.3.2.4.1. Attributes
S.3.2.4.2. Service Class User
S.3.2.4.3. Service Class Provider
S.3.2.4.4. Status Codes
S.3.3. Media Creation Management SOP Class UID
S.4. Conformance Requirements
S.4.1. SCU Conformance
S.4.1.1. Operations
S.4.2. SCP Conformance
S.4.2.1. Operations
T. Hanging Protocol Storage Service Class
U. Hanging Protocol Query/Retrieve Service Class
U.1. Overview
U.1.1. Scope
U.1.2. Conventions
U.1.3. Query/Retrieve Information Model
U.1.4. Service Definition
U.2. Hanging Protocol Information Model Definition
U.3. Hanging Protocol Information Model
U.4. DIMSE-C Service Groups
U.4.1. C-FIND Operation
U.4.2. C-MOVE Operation
U.4.3. C-GET Operation
U.5. Association Negotiation
U.6. SOP Class Definitions
U.6.1. Hanging Protocol Information Model
U.6.1.1. E/R Model
U.6.1.2. Hanging Protocol Attributes
U.6.1.3. Conformance Requirements
U.6.1.3.1. SCU Conformance
U.6.1.3.1.1. C-FIND SCU Conformance
U.6.1.3.1.2. C-MOVE SCU Conformance
U.6.1.3.1.3. C-GET SCU Conformance
U.6.1.3.2. SCP Conformance
U.6.1.3.2.1. C-FIND SCP Conformance
U.6.1.3.2.2. C-MOVE SCP Conformance
U.6.1.3.2.3. C-GET SCP Conformance
U.6.1.4. SOP Classes
V. Substance Administration Query Service Class (Normative)
V.1. Overview
V.1.1. Scope
V.1.2. Conventions
V.1.3. Substance Administration Query Information Model
V.1.4. Service Definition
V.2. Substance Administration Query Information Model Definition
V.2.1. Entity-Relationship Model Definition
V.2.2. Attributes Definition
V.2.2.1. Attribute Types
V.2.2.1.1. Matching Key Attributes
V.2.2.1.1.1. Required Matching Key Attributes
V.2.2.1.1.2. Optional Matching Key Attributes
V.2.2.1.2. Return Key Attributes
V.2.2.2. Attribute Matching
V.3. Query Information Models
V.4. DIMSE-C Service Group
V.4.1. C-FIND Operation
V.4.1.1. C-FIND Service Parameters
V.4.1.1.1. SOP Class UID
V.4.1.1.2. Priority
V.4.1.1.3. Identifier
V.4.1.1.3.1. Request Identifier Structure
V.4.1.1.3.2. Response Identifier Structure
V.4.1.1.4. Status
V.4.1.2. C-FIND SCU Behavior
V.4.1.3. C-FIND SCP Behavior
V.4.1.3.1. Query Search Method
V.5. Association Negotiation
V.6. SOP Class Definitions
V.6.1. Product Characteristics Query SOP Class
V.6.1.1. Product Characteristics Query SOP Class Overview
V.6.1.2. Product Characteristics Query Information Model
V.6.1.2.1. E/R Model
V.6.1.2.2. Product Characteristics Query Attributes
V.6.1.3. Conformance Requirements
V.6.1.3.1. SCU Conformance
V.6.1.3.2. SCP Conformance
V.6.1.4. SOP Class
V.6.2. Substance Approval Query SOP Class
V.6.2.1. Substance Approval Query SOP Class Overview
V.6.2.2. Substance Approval Query Information Model
V.6.2.2.1. E/R Model
V.6.2.2.2. Substance Approval Query Attributes
V.6.2.2.3. Substance Approval Query Responses
V.6.2.3. Conformance Requirements
V.6.2.3.1. SCU Conformance
V.6.2.3.2. SCP Conformance
V.6.2.4. SOP Class
W. Color Palette Storage Service Class
X. Color Palette Query/Retrieve Service Class
X.1. Overview
X.1.1. Scope
X.1.2. Conventions
X.1.3. Query/Retrieve Information Model
X.1.4. Service Definition
X.2. Color Palette Information Model Definition
X.3. Color Palette Information Model
X.4. DIMSE-C Service Groups
X.4.1. C-FIND Operation
X.4.2. C-MOVE Operation
X.4.3. C-GET Operation
X.5. Association Negotiation
X.6. SOP Class Definitions
X.6.1. Color Palette Information Model
X.6.1.1. E/R Model
X.6.1.2. Color Palette Attributes
X.6.1.3. Conformance Requirements
X.6.1.3.1. SCU Conformance
X.6.1.3.1.1. C-FIND SCU Conformance
X.6.1.3.1.2. C-MOVE SCU Conformance
X.6.1.3.1.3. C-GET SCU Conformance
X.6.1.3.2. SCP Conformance
X.6.1.3.2.1. C-FIND SCP Conformance
X.6.1.3.2.2. C-MOVE SCP Conformance
X.6.1.3.2.3. C-GET SCP Conformance
X.6.1.4. SOP Classes
Y. Composite Instance Root Retrieve Service Class (Normative)
Y.1. Overview
Y.1.1. Scope
Y.1.2. Composite Instance Root Retrieve Information Model
Y.1.3. Service Definition
Y.2. Composite Instance Root Retrieve Information Model Definition
Y.2.1. Entity-Relationship Model Definition
Y.2.2. Attributes Definition
Y.3. Standard Composite Instance Root Retrieve Information Model
Y.3.1. Composite Instance Root Information Model
Y.3.2. Construction and Interpretation of Frame Range Keys
Y.3.2.1. Frame List definitions
Y.3.2.1.1. Simple Frame List
Y.3.2.1.2. Calculated Frame List
Y.3.2.1.3. Time Range
Y.3.3. New Instance Creation At the Frame Level
Y.4. DIMSE-C Service Groups
Y.4.1. C-MOVE Operation
Y.4.1.1. C-MOVE Service Parameters
Y.4.1.1.1. SOP Class UID
Y.4.1.1.2. Priority
Y.4.1.1.3. Identifier
Y.4.1.1.3.1. Request Identifier Structure
Y.4.1.1.4. Status
Y.4.1.1.5. Number of Remaining Sub-Operations
Y.4.1.1.6. Number of Completed Sub-Operations
Y.4.1.1.7. Number of Failed Sub-Operations
Y.4.1.1.8. Number of Warning Sub-Operations
Y.4.1.2. C-MOVE SCU Behavior
Y.4.1.2.1. Baseline Behavior of SCU
Y.4.1.2.2. Extended Behavior of SCU
Y.4.1.3. C-MOVE SCP Behavior
Y.4.1.3.1. Baseline Behavior of SCP
Y.4.1.3.2. Extended Behavior of SCP
Y.4.2. C-GET Operation
Y.4.2.1. C-GET Service Parameters
Y.4.2.1.1. SOP Class UID
Y.4.2.1.2. Priority
Y.4.2.1.3. Identifier
Y.4.2.1.3.1. Request Identifier Structure
Y.4.2.1.4. Status
Y.4.2.1.5. Number of Remaining Sub-Operations
Y.4.2.1.6. Number of Completed Sub-Operations
Y.4.2.1.7. Number of Failed Sub-Operations
Y.4.2.1.8. Number of Warning Sub-Operations
Y.4.2.2. C-GET SCU Behavior
Y.4.2.2.1. Baseline Behavior of SCU
Y.4.2.2.2. Extended Behavior of SCU
Y.4.2.3. C-GET SCP Behavior
Y.4.2.3.1. Baseline Behavior of SCP
Y.4.2.3.2. Extended Behavior of SCP
Y.5. Association Negotiation
Y.5.1. Association Negotiation for C-MOVE and C-GET SOP Classes
Y.5.1.1. SOP Class Extended Negotiation
Y.5.1.1.1. SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-RQ)
Y.5.1.1.2. SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-AC)
Y.6. SOP Class Definitions
Y.6.1. Composite Instance Root SOP Class Group
Y.6.1.1. Composite Instance Root Retrieve Only Information Model
Y.6.1.1.1. E/R Model
Y.6.1.1.2. Composite Instance Level
Y.6.1.1.3. Frame Level
Y.6.1.1.4. Scope of the C-MOVE or C-GET Commands and Sub-Operations
Y.6.1.2. Conformance Requirements
Y.6.1.2.1. SCU Conformance
Y.6.1.2.1.1. C-MOVE SCU Conformance
Y.6.1.2.1.2. C-GET SCU Conformance
Y.6.1.2.2. SCP Conformance
Y.6.1.2.2.1. C-MOVE SCP Conformance
Y.6.1.2.2.2. C-GET SCP Conformance
Y.6.1.3. SOP Classes
Z. Composite Instance Retrieve Without Bulk Data Service Class (Normative)
Z.1. Overview
Z.1.1. Scope
Z.1.2. Composite Instance Retrieve Without Bulk Data Information Model
Z.1.3. Attributes Not Included
Z.1.4. Service Definition
Z.2. Composite Instance Retrieve Without Bulk Data Information Model Definition
Z.2.1. Entity-Relationship Model Definition
Z.2.2. Attributes Definition
Z.3. Standard Composite Instance Retrieve Without Bulk Data Information Model
Z.3.1. Composite Instance Retrieve Without Bulk Data Information Model
Z.4. DIMSE-C Service Groups
Z.4.1. C-GET Operation
Z.4.2.1. C-GET Service Parameters
Z.4.2.1.1. SOP Class UID
Z.4.2.1.2. Priority
Z.4.2.1.3. Identifier
Z.4.2.1.3.1. Request Identifier Structure
Z.4.2.1.4. Status
Z.4.2.1.5. Number of Remaining Sub-Operations
Z.4.2.1.6. Number of Completed Sub-Operations
Z.4.2.1.7. Number of Failed Sub-Operations
Z.4.2.1.8. Number of Warning Sub-Operations
Z.4.2.2. C-GET SCU and C-STORE SCP Behavior
Z.4.2.2.1. Baseline Behavior of SCU
Z.4.2.2.2. Extended Behavior of SCU
Z.4.2.3. C-GET SCP and C-STORE SCU Behavior
Z.4.2.3.1. Baseline Behavior of SCP
Z.4.2.3.2. Extended Behavior of SCP
Z.5. Association Negotiation
Z.5.1. Association Negotiation for C-GET SOP Classes
Z.6. SOP Class Definitions
Z.6.1. Composite Instance Retrieve Without Bulk Data SOP Class Group
Z.6.1.1. Composite Instance Retrieve Without Bulk Data Information Model
Z.6.1.1.1. E/R Model
Z.6.1.1.2. Composite Instance Level
Z.6.1.1.3. Scope of the C-GET Commands and Sub-Operations
Z.6.1.2. Conformance Requirements
Z.6.1.2.1. SCU Conformance
Z.6.1.2.2. SCP Conformance
Z.6.1.3. SOP Classes
AA. Ophthalmic Refractive Measurements Storage SOP Classes (Normative)
AA.1. Scope
AA.2. Behavior of a SCP
BB. Implant Template Query/Retrieve Service Classes
BB.1. Overview
BB.1.1. Scope
BB.1.2. Conventions
BB.1.3. Query/Retrieve Information Model
BB.1.4. Service Definition
BB.2. Implant Template Information Models Definitions
BB.3. Implant Template Information Models
BB.4. DIMSE-C Service Groups
BB.4.1. C-FIND Operation
BB.4.1.1. Service Class User Behavior
BB.4.1.2. Service Class Provider Behavior
BB.4.2. C-MOVE Operation
BB.4.3. C-GET Operation
BB.5. Association Negotiation
BB.6. SOP Class Definitions
BB.6.1. Implant Template Information Model
BB.6.1.1. E/R Models
BB.6.1.2. Implant Template Attributes
BB.6.1.2.1. Generic Implant Template Attributes
BB.6.1.2.2. Implant Assembly Template Attributes
BB.6.1.2.3. Implant Template Group Attributes
BB.6.1.3. Conformance Requirements
BB.6.1.3.1. SCU Conformance
BB.6.1.3.1.1. C-FIND SCU Conformance
BB.6.1.3.1.2. C-MOVE SCU Conformance
BB.6.1.3.1.3. C-GET SCU Conformance
BB.6.1.3.2. SCP Conformance
BB.6.1.3.2.1. C-FIND SCP Conformance
BB.6.1.3.2.2. C-MOVE SCP Conformance
BB.6.1.3.2.3. C-GET SCP Conformance
BB.6.1.4. SOP Classes
CC. Unified Procedure Step Service and SOP Classes (Normative)
CC.1. Overview
CC.1.1. Unified Procedure Step States
CC.2. DIMSE Service Groups
CC.2.1. Change UPS State (N-ACTION)
CC.2.1.1. Action Information
CC.2.1.2. Service Class User Behavior
CC.2.1.3. Service Class Provider Behavior
CC.2.1.4. Status Codes
CC.2.2. Request UPS Cancel (N-ACTION)
CC.2.2.1. Action Information
CC.2.2.2. Service Class User Behavior
CC.2.2.3. Service Class Provider Behavior
CC.2.2.4. Status Codes
CC.2.3. Subscribe/Unsubscribe to Receive UPS Event Reports (N-ACTION)
CC.2.3.1. Action Information
CC.2.3.2. Service Class User Behavior
CC.2.3.3. Service Class Provider Behavior
CC.2.3.3.1. Filtered Global Subscription
CC.2.3.4. Status Codes
CC.2.4. Report a Change in UPS Status (N-EVENT-REPORT)
CC.2.4.1. Event Report Information
CC.2.4.2. Service Class User Behavior
CC.2.4.3. Service Class Provider Behavior
CC.2.4.4. Status Codes
CC.2.5. Create a Unified Procedure Step (N-CREATE)
CC.2.5.1. Unified Procedure Step Attribute Specification
CC.2.5.1.1. UPS Final State Requirements
CC.2.5.1.2. UPS Macros
CC.2.5.1.3. UPS Attribute Service Requirements
CC.2.5.1.3.1. UPS SOP Class UID
CC.2.5.1.3.2. Unified Procedure Step Performed Procedure Sequence
CC.2.5.2. Service Class User Behavior
CC.2.5.3. Service Class Provider Behavior
CC.2.5.4. Status Codes
CC.2.6. Set Unified Procedure Step Information (N-SET)
CC.2.6.1. Unified Procedure Step IOD Subset Specification
CC.2.6.2. Service Class User Behavior
CC.2.6.3. Service Class Provider Behavior
CC.2.6.4. Status Codes
CC.2.7. Get Unified Procedure Step Information (N-GET)
CC.2.7.1. Unified Procedure Step IOD Subset Specification
CC.2.7.2. Service Class User Behavior
CC.2.7.3. Service Class Provider Behavior
CC.2.7.4. Status Codes
CC.2.8. Search for Unified Procedure Step (C-FIND)
CC.2.8.1. Operation
CC.2.8.1.1. E/R Model
CC.2.8.1.2. C-FIND Service Parameters
CC.2.8.1.2.1. SOP Class UID
CC.2.8.1.2.2. Priority
CC.2.8.1.3. Identifier
CC.2.8.1.3.1. Request Identifier Structure
CC.2.8.1.3.2. Response Identifier Structure
CC.2.8.2. Service Class User Behavior
CC.2.8.3. Service Class Provider Behavior
CC.2.8.3.1. Worklist Search Method
CC.2.8.4. Status Codes
CC.3. UPS SOP Classes
CC.3.1. Service Class and SOP Class UIDs
CC.3.1.1. DIMSE Implications for UPS (Informative)
CC.3.1.2. Global Instance Subscription UID
CC.3.2. Association Negotiation
CC.4. Conformance Requirements
CC.4.1. SCU Conformance
CC.4.1.1. Operations
CC.4.2. SCP Conformance
CC.4.2.1. Operations
DD. RT Machine Verification Service Classes (Normative)
DD.1. Scope
DD.2. RT Machine Verification Model
DD.2.1. RT Machine Verification Data Flow
DD.3. Machine Verification SOP Class Definitions
DD.3.1. IOD Description
DD.3.2. DIMSE Service Group
DD.3.2.1. N-CREATE and N-SET
DD.3.2.1.1. Attributes
DD.3.2.1.1.1. Beam Modifiers
DD.3.2.1.2. Status
DD.3.2.1.3. Behavior
DD.3.2.1.3.1. N-CREATE
DD.3.2.1.3.2. N-SET
DD.3.2.2. N-GET
DD.3.2.2.1Verification. Parameters Selector Attribute Macro
DD.3.2.2.2. Attributes
DD.3.2.2.3. Status
DD.3.2.2.4. Behavior
DD.3.2.3. N-ACTION
DD.3.2.3.1. Attributes
DD.3.2.3.2. Status
DD.3.2.3.3. Behavior
DD.3.2.4. N-DELETE
DD.3.2.4.1. Attributes
DD.3.2.4.2. Status
DD.3.2.4.3. Behavior
DD.3.2.5. N-EVENT-REPORT
DD.3.2.5.1. Attributes
DD.3.2.5.2. Status
DD.3.2.5.3. Behavior
EE. Display System Management Service Class (Normative)
EE.1. Scope
EE.2. Display System SOP Class
EE.2.1. IOD Description
EE.2.2. DIMSE Service Group
EE.2.2.1. N-GET
EE.2.2.1.1. Attributes
EE.2.2.1.1.1. Display Subsystem Macros
EE.2.2.1.1.2. Display System N-GET Attribute Requirements
EE.2.2.1.2. SCU Behavior
EE.2.2.1.3. SCP Behavior
EE.2.3. SOP Class Definitions and UIDs
EE.2.4. Reserved Identifications
EE.3. Conformance
EE.3.1. Conformance Statement
FF. Volumetric Presentation State Storage SOP Classes (Normative)
FF.1. Overview
FF.1.1. Scope
FF.2. Volume Transformation Processes
FF.2.1. Volumetric Transformations
FF.2.1.1. Planar MPR Volumetric Transformations
FF.2.1.2. Volume Rendering Volumetric Transformations
FF.2.1.2.1. Volume Rendering Pipelines
FF.2.1.2.2. Volume Rendering Component
FF.2.1.2.3. Graphic Projection Component
FF.2.2. Volumetric Inputs, Registration and Cropping
FF.2.3. Volumetric Presentation State Display
FF.2.3.1. Volumetric Presentation State Display Overview
FF.2.3.2. Description of Display Components
FF.2.3.2.1. Classification Component Components
FF.2.3.2.2. Compositor Components
FF.2.3.3. Internal Structure of Components
FF.2.3.3.1. Internal Structure of Classification Components
FF.2.3.3.2. Internal Structure of RGB and RGBA Compositor Components
FF.2.4. Additional Volumetric Considerations
FF.2.4.1. Annotations in Volumetric Presentations States
FF.2.4.2. Volumetric Animation
FF.2.4.2.1. Input Sequence Animation
FF.2.4.2.2. Presentation Sequence Animation
FF.2.4.2.3. Crosscurve Animation
FF.2.4.2.4. Flythrough Animation
FF.2.4.2.5. Swivel Animation
FF.2.5. Display Layout
FF.3. Behavior of An SCP
FF.4. Conformance
FF.4.1. Conformance Statement For An SCU
FF.4.2. Conformance Statement For An SCP
GG. Non-Patient Object Storage Service Class
GG.1. Overview
GG.1.1. Scope
GG.1.2. Service Definition
GG.2. Association Negotiation
GG.3. SOP Classes
GG.4. Behavior
GG.4.1. Service Class User
GG.4.2. Service Class Provider
GG.5. Conformance Statement Requirements
GG.5.1. SCU Conformance Requirements
GG.5.2. SCP Conformance Requirements
GG.6. Application Behavior for Standard SOP Classes
GG.6.1. Hanging Protocol SOP Class
GG.6.1.1. Instance Creator
GG.6.1.2. Display Application
GG.6.2. Color Palette Storage SOP Class
GG.6.2.1. Instance Creator
GG.6.2.2. Display Application
GG.6.3. Template Storage SOP Classes
GG.6.4. CT and XA Defined Procedure Protocol Storage SOP Class
GG.6.5. Protocol Approval Storage SOP Class
HH. Defined Procedure Protocol Query/Retrieve Service Classes
HH.1. Overview
HH.1.1. Scope
HH.1.2. Conventions
HH.1.3. Query/Retrieve Information Model
HH.1.4. Service Definition
HH.2. Defined Procedure Protocol Information Models Definitions
HH.3. Defined Procedure Protocol Information Models
HH.4. DIMSE-C Service Groups
HH.4.1. C-FIND Operation
HH.4.1.1. Service Class User Behavior
HH.4.1.2. Service Class Provider Behavior
HH.4.2. C-MOVE Operation
HH.4.3. C-GET Operation
HH.5. Association Negotiation
HH.6. SOP Class Definitions
HH.6.1. Defined Procedure Protocol Information Model
HH.6.1.1. E/R Models
HH.6.1.2. Defined Procedure Protocol Attributes
HH.6.1.3. Conformance Requirements
HH.6.1.3.1. SCU Conformance
HH.6.1.3.1.1. C-FIND SCU Conformance
HH.6.1.3.1.2. C-MOVE SCU Conformance
HH.6.1.3.1.3. C-GET SCU Conformance
HH.6.1.3.2. SCP Conformance
HH.6.1.3.2.1. C-FIND SCP Conformance
HH.6.1.3.2.2. C-MOVE SCP Conformance
HH.6.1.3.2.3. C-GET SCP Conformance
HH.6.1.4. SOP Classes
II. Protocol Approval Query/Retrieve Service Classes
II.1. Overview
II.1.1. Scope
II.1.2. Conventions
II.1.3. Query/Retrieve Information Model
II.1.4. Service Definition
II.2. Protocol Approval Information Models Definitions
II.3. Protocol Approval Information Models
II.4. DIMSE-C Service Groups
II.4.1. C-FIND Operation
II.4.1.1. Service Class User Behavior
II.4.1.2. Service Class Provider Behavior
II.4.2. C-MOVE Operation
II.4.3. C-GET Operation
II.5. Association Negotiation
II.6. SOP Class Definitions
II.6.1. Protocol Approval Information Model
II.6.1.1. E/R Models
II.6.1.2. Protocol Approval Attributes
II.6.1.3. Conformance Requirements
II.6.1.3.1. SCU Conformance
II.6.1.3.1.1. C-FIND SCU Conformance
II.6.1.3.1.2. C-MOVE SCU Conformance
II.6.1.3.1.3. C-GET SCU Conformance
II.6.1.3.2. SCP Conformance
II.6.1.3.2.1. C-FIND SCP Conformance
II.6.1.3.2.2. C-MOVE SCP Conformance
II.6.1.3.2.3. C-GET SCP Conformance
II.6.1.4. SOP Classes

List of Figures

5-1. Entity Convention
5-2. Relationship Convention
6-1. Major Structures of DICOM Information Model
C.5-1. An Example of the Sub-Operation SCU/SCP Roles
C.5-2. An Example of the Retrieve (C-GET) Negotiation
C.6-1. Patient Root Query/Retrieve Information Model E/R Diagram
C.6-2. Study Root Query/Retrieve Information Model E/R Diagram
H.2-1. Print Management Data Flow Model
H.2-2. Print Management Data Flow Model
H.2-3. Print Management Service Class Structure
H.2-4. Configurations for Printing On Multiple Printers
K.6-1. Modality Worklist Information Model E/R Diagram
N.2-1. Grayscale and Color Image Transformation Models
N.2-2. Common Spatial and Annotation Transformation Model
N.2-3. Grayscale to Color Blending Transformation Model
N.2.5-1. XA/XRF Grayscale Image Transformation Model
N.2.6-1. Color and Threshold Application
N.2.6-2. Foreground Blending
N.2.6-3. Equal Blending
Q.4-1. Relevant Patient Information E/R Model
U.6-1. Hanging Protocol Information Model E/R Diagram
V.6-1. Product Characteristics E-R Diagram
V.6-2. Substance Approval E-R Diagram
X.6-1. Color Palette Information Model E/R Diagram
Y.6-1. Composite Instance Root Retrieve Information Model E/R Diagram
Z.3.1-1. Retrieve Without Bulk Data Information Model E/R Diagram
BB.6-1. Implant Template Information Model E/R Diagram
BB.6-2. Implant Assembly Template Information Model E/R Diagram
BB.6-3. Implant Template Group Information Model E/R Diagram
CC.1.1-1. Unified Procedure Step State Diagram
CC.2.8-1. Unified Procedure Step E-R Diagram
DD.2-1. RT Verification Data Flow
EE.1-1. Display System Management Data Flow
FF.2-1. Grayscale Planar MPR Volumetric Pipeline
FF.2-2. Compositing Planar MPR Volumetric Pipeline
FF.2.1.2.1-1. Volume Rendering Volumetric Pipeline
FF.2.1.2.1-2. Segmented Volume Rendering Volumetric Pipeline
FF.2.1.2.1-3. Multiple Volume Rendering Volumetric Pipeline
FF.2-3. One Input -> RGBA Component
FF.2-4. Two Inputs ->RGBA Component
FF.2-5. RGB Compositor Component
FF.2.3.2.2-2. RGBA Compositor Component
FF.2-6. Internal Structure of One Input -> RGBA Component
FF.2-7. Internal Structure of Two Input -> RGBA Component
FF.2-8. Internal Structure of RGB Compositor Component
FF.2.3.3.2-1. Internal Structure of RGB and Opacity Compositor Component
FF.3.2-1. Input Sequence Animation
FF.3.2-2. Presentation Sequence Animation
FF.3.2-3. Crosscurve Animation
FF.2.4.2.4-1. Flythrough Animation
HH.6-1. Defined Procedure Protocol Information Model E/R Diagram
II.6-1. Protocol Approval Information Model E/R Diagram

List of Tables

8-1a. Enhanced SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning
8-1b. Basic SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning
8-2a. Enhanced Coded Entry Macro with Optional Matching Key Support and Optional Meaning
8-2b. Basic Coded Entry Macro with Optional Matching Key Support and Optional Meaning
8-3a. Enhanced SCU/SCP Coded Entry Macro with no SCU Support and no Matching Key Support
8-3b. Basic SCU/SCP Coded Entry Macro with no SCU Support and no Matching Key Support
8-4a. Enhanced Coded Entry Macro with Optional Matching Key Support and Mandatory Meaning
8-4b. Basic Coded Entry Macro with Optional Matching Key Support and Mandatory Meaning
8-5a. Enhanced SCU/SCP Coded Entry Macro with no SCU Support and Optional Meaning for SCP
8-5b. Basic SCU/SCP Coded Entry Macro with no SCU Support and Optional Meaning for SCP
B.2-1. C-STORE Status
B.3-1. Service-Class-Application-Information (A-ASSOCIATE-RQ)
B.3-2. Service-Class-Application-Information (A-ASSOCIATE-AC)
B.3-3. Standard and Related General SOP Classes
B.4-1. Attributes Subject to Coercion
B.5-1. Standard SOP Classes
B.6-1. Retired Standard SOP Classes
C.1.2-1. Key Type Conventions for Query/Retrieve Information Models
C.3-1. Additional Query/Retrieve Attributes
C.3.5-1. Modality-Specific SOP Class Conversions
C.4-1. C-FIND Response Status Values
C.4-2. C-MOVE Response Status Values
C.4-3. C-GET Response Status Values
C.5-1. SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - A-ASSOCIATE-RQ
C.5-2. SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - A-ASSOCIATE-AC
C.5-3. SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - A-ASSOCIATE-RQ
C.5-4. SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - A-ASSOCIATE-AC
C.6.1-1. Query/Retrieve Level Values for Patient Root
C.6-1. Patient Level Attributes for the Patient Root Query/Retrieve Information Model
C.6-2a. Enhanced Code Value Keys Macro with Optional Keys
C.6-2b. Basic Code Value Keys Macro with Optional Keys
C.6-2. Study Level Keys for the Patient Root Query/Retrieve Information Model
C.6-3. Series Level Attributes for the Patient Root Query/Retrieve Information Model
C.6-4. Composite Object Instance Level Keys for the Patient Root Query/Retrieve Information Model
C.6.1.3-1. SOP Classes for Patient Root Query/Retrieve
C.6.2-1. Query/Retrieve Level Values for Study Root
C.6-5. Study Level Keys for the Study Root Query/Retrieve Information Model
C.6.2.3-1. SOP Classes for Study Root Query/Retrieve
F.1-3. Modality Performed Procedure Step States
F.1-4. Modality Performed Procedure Step State Transition Diagram
F.7.1-1. DIMSE Service Group Applicable to Modality Performed Procedure Step
F.7.2-1a. Modality Performed Procedure Step Enhanced Code Value Macro with no N-SET
F.7.2-1b. Modality Performed Procedure Step Simple Code Value Macro with no N-SET
F.7.2-1c. Modality Performed Procedure Step Enhanced Code Value Macro with N-SET, Mandatory Meaning
F.7.2-1d. Modality Performed Procedure Step Simple Code Value Macro with N-SET, Mandatory Meaning
F.7.2-1e. Modality Performed Procedure Step Enhanced Code Value Macro with N-SET, Optional Meaning
F.7.2-1f. Modality Performed Procedure Step Simple Code Value Macro with N-SET, Optional Meaning
F.7.2-1. Modality Performed Procedure Step SOP Class N-CREATE, N-SET and Final State Attributes
F.7.2-2. N-SET Status
F.8.1-1. DIMSE Service Group Applicable to Modality Performed Procedure Step Retrieve
F.8.2-1. Modality Performed Procedure Step Retrieve SOP Class N-GET Attributes
F.8.2-2. Response Status
F.9.1-1. DIMSE Service Group Applicable to Modality Performed Procedure Step Notification
F.9.2-1. Performed Procedure Step Notification Event Information
H.3.2.2.1-1. SOP Classes of Basic Grayscale Print Management Meta SOP Class
H.3.2.2.2-1. SOP Classes of Basic Color Print Management Meta SOP Class
H.3.3.2-1. List of Optional SOP Classes for Basic Print Management Meta SOP Classes
H.4-1. DIMSE Service Group Applicable to Basic Film Session
H.4-2. N-CREATE Attribute List
H.4.1.2.1.2-1. Status Values for Basic Film Session SOP Class
H.4-3. N-ACTION Arguments
H.4-4. SOP Class Status Values
H.4-5. DIMSE Service Group Applicable to Basic Film Box
H.4-6. N-CREATE Attribute List
H.4.2.2.1.2-1. Status Values for Basic Film Box SOP Class
H.4-7. N-SET Attributes
H.4-8. N-ACTION Arguments
H.4-9. Status Values
H.4.3.1.2-1. DIMSE Service Group Applicable to Basic Grayscale Image Box
H.4-10. N-SET Attributes
H.4.3.1.2.1.2-1. Status Values for Basic Grayscale Image Box SOP Class
H.4.3.2.2-1. DIMSE Service Group Applicable to Basic Color Image Box
H.4-11. N-SET Attributes
H.4.3.2.2.1.2-1. Status Values for Basic Color Image Box SOP Class
H.4.4.2-1. DIMSE Service Group Applicable to Basic Annotation Box
H.4-13. N-SET Attributes
H.4.5.2-1. DIMSE Service Group Applicable to Print Job
H.4-14. Notification Event Information
H.4-15. N-GET Attributes
H.4.6.2-1. DIMSE Service Group Applicable to Printer
H.4-16. Notification Event Information
H.4-17. N-GET Attributes
H.4.9.2-1. DIMSE Service Group Applicable to Presentation LUT
H.4-23. N-CREATE Attribute List
H.4.9.2.1.2-1. Status Values for Presentation LUT SOP Class
H.4.11.2-1. DIMSE Service Group Applicable to Printer Configuration Retrieval
H.4-26. N-GET Attributes
I.3-1. Allowed Combinations of Roles
I.4-1. Media Storage Standard SOP Classes
J.3.1-1. DIMSE Service Group Applicable to Storage Commitment Push Model
J.3-1. Storage Commitment Request - Action Information
J.3-2. Storage Commitment Result - Event Information
K.4-1. C-FIND Response Status Values
K.5.1-1. SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - A-ASSOCIATE-RQ
K.5.1-2. SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - A-ASSOCIATE-AC
K.6-1. Attributes for the Modality Worklist Information Model
K.6-1a. Attributes for the Modality Worklist C-FIND Identifier
K.6.1.4-1. Modality Worklist SOP Class
N.2.5.1-1. Summary of Providing a LUT Function for Subtraction
P.2-1. DIMSE Service Group Applicable to Procedural Event Logging
P.2-2. Procedural Event Logging Action Information
P.2-3. Response Status
P.2-4. Procedural Event Logging Action Reply
P.3-1. DIMSE Service Group Applicable to Substance Administration Logging
P.3-2. Substance Administration Logging N-ACTION Information
P.3-3. Response Status
Q.2-1. C-FIND Response Status Values
Q.4-1. Attributes for the Relevant Patient Information Model
Q.4-2. Additional C-FIND Identifier Attributes
Q.4-3. SOP Classes for the Relevant Patient Information Model
R.3.1-1. DIMSE Service Group Applicable to Instance Availability Notification
R.3.2-1. Instance Availability Notification SOP Class N-CREATE Attributes
S.3.1-1. DIMSE Service Group Applicable to Media Creation Management
S.3.2.1.1-1. Media Creation Management - N-CREATE Attributes
S.3.2.2.4-1. SOP Class Status Values
S.3.2.2.1-1. Media Creation Request - Action Information
S.3.2.3.1-1. Media Creation Request - Action Information
S.3.2.3.4-1. Response Statuses
S.3.2.4.1-1. Media Creation Management SOP Class N-GET Attributes
S.3.2.4.4-1. Response Statuses
U.6-1. Attributes for the Hanging Protocol Information Model
U.6.1.4-1. Hanging Protocol SOP Classes
V.4-1. C-FIND Response Status Values
V.6-1. Attributes for the Product Characteristics Query Information Model
V.6.1.4-1. Product Characteristics Query SOP Classes
V.6-2. Attributes for the Substance Approval Query Information Model
V.6.2.4-1. Substance Approval Query SOP Classes
X.6-1. Attributes for the Color Palette Information Model
X.6.1.4-1. Color Palette SOP Classes
Y.4-1. C-MOVE Response Status Values for Composite Instance Root Retrieve
Y.4-2. C-GET Response Status Values for Composite Instance Root Retrieve
Y.5.1-1. SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - A-ASSOCIATE-RQ
Y.5.1-2. SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - A-ASSOCIATE-AC
Y.6.1-1. Retrieve Level Values for Composite Instance Root Retrieve
Y.6-1. Composite Instance Level Keys for the Composite Instance Root Retrieve Information Model
Y.6-2. Frame Level Keys for the Composite Instance Root Retrieve Information Model
Y.6.1.3-1. SOP Classes for Composite Instance Root Retrieve
Z.1-1. Attributes Not to Be Included in Instances Sent
Z.4-1. C-GET Response Status Values for Composite Instance Retrieve Without Bulk Data
Z.6.1-1. Retrieve Level Value for Composite Instance Retrieve Without Bulk Data
Z.6-1. Composite Instance Level Keys for the Composite Instance Retrieve Without Bulk Data Information Model
Z.6.1.3-1. SOP Classes for Composite Instance Retrieve Without Bulk Data
BB.6-1. Attributes for the Implant Template Information Model
BB.6-2. Attributes for the Implant Assembly Template Information Model
BB.6-3. Attributes for the Implant Template Group Information Model
BB.6.1.4-1. Implant Template SOP Classes
CC.1.1-1. Unified Procedure Step (UPS) States
CC.1.1-2. Unified Procedure Step State Transition Table
CC.2-1. DIMSE Service Group Applicable to UPS Push
CC.2-2. DIMSE Service Group Applicable to UPS Pull
CC.2-3. DIMSE Service Group Applicable to UPS Watch
CC.2-4. DIMSE Service Group Applicable to UPS Event
CC.2-5. DIMSE Service Group Applicable to UPS Query
CC.2.1-1. Change UPS State - Action Information
CC.2.1-2. N-ACTION Response Status Values [for Change UPS State]
CC.2.2-1. Request UPS Cancel - Action Information
CC.2.2-2. N-ACTION Response Status Values [for Request UPS Cancel]
CC.2.3-1. Subscribe/Unsubscribe to Receive UPS Event Reports - Action Information
CC.2.3-2. UPS Subscription State Transition Table
CC.2.3-3. N-ACTION Response Status Values [for Subscribe/Unsubscribe to Receive UPS sEvent Reports]
CC.2.4-1. Report a Change in UPS Status - Event Report Information
CC.2.5-1. Final State Codes
CC.2.5-2a. UPS Code Sequence Macro
CC.2.5-2b. UPS Content Item Macro
CC.2.5-2c. Referenced Instances and Access Macro
CC.2.5-2d. HL7V2 Hierarchic Designator Macro
CC.2.5-2e. Issuer of Patient ID Macro
CC.2.5-2f. SOP Instance Reference Macro
CC.2.5-2g. Storage Macro
CC.2.5-3. UPS SOP Class N-CREATE/N-SET/N-GET/C-FIND Attributes
CC.2.5-4. N-CREATE Response Status Values [for Create a Unified Procedure Step]
CC.2.6-1. N-SET Response Status Values [for Set Unified Procedure Step Information]
CC.2.7-1. N-GET Response Status Values [for Get Unified Procedure Step Information]
CC.2.8-2. C-FIND Response Status Values [for Search for Unified Procedure Step]
DD.3.2-1. DIMSE Service Group Applicable to Machine Verification
DD.3.2.1-1. N-CREATE and N-SET Attribute List - RT Conventional Machine Verification SOP Class
DD.3.2.1-2. N-CREATE and N-SET Attribute List - RT Ion Machine Verification SOP Class
DD.3.2.1.2-1. RT Ion Machine Verification SOP Class N-CREATE Status Values
DD.3.2.1.2-2. RT Ion Machine Verification SOP Class N-SET Status Values
DD.3.2.2.1-1. Verification Parameters Selector Attribute Macro
DD.3.2.2.2-1. N-GET Attribute List- RT Conventional Machine Verification SOP Class and RT Ion Machine Verification SOP Class
DD.3.2.2.3-1. RT Conventional Machine and RT Ion Machine Verification SOP Class N-GET Status Values
DD.3.2.3-1. Action Event Information
DD.3.2.3-2. RT Conventional Machine and RT Ion Machine Verification SOP Class N-ACTION Status Values
DD.3.2.5-1. Notification Event Information
EE.2.2-1. DIMSE Service Group Applicable to Display System
EE.2.2.1-1. Table Result Context Macro
EE.2.2.1-2. Display System N-GET Attributes
GG.3-1. Standard SOP Classes
GG.4-1. C-STORE Response Status Values
HH.6-1. Attributes for the Defined Procedure Protocol Information Model
HH.6.1.4-1. Defined Procedure Protocol SOP Classes
II.6-1. Attributes for the Protocol Approval Information Model
II.6.1.4-1. Protocol Approval SOP Classes

Notice and Disclaimer

The information in this publication was considered technically sound by the consensus of persons engaged in the development and approval of the document at the time it was developed. Consensus does not necessarily mean that there is unanimous agreement among every person participating in the development of this document.

NEMA standards and guideline publications, of which the document contained herein is one, are developed through a voluntary consensus standards development process. This process brings together volunteers and/or seeks out the views of persons who have an interest in the topic covered by this publication. While NEMA administers the process and establishes rules to promote fairness in the development of consensus, it does not write the document and it does not independently test, evaluate, or verify the accuracy or completeness of any information or the soundness of any judgments contained in its standards and guideline publications.

NEMA disclaims liability for any personal injury, property, or other damages of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resulting from the publication, use of, application, or reliance on this document. NEMA disclaims and makes no guaranty or warranty, expressed or implied, as to the accuracy or completeness of any information published herein, and disclaims and makes no warranty that the information in this document will fulfill any of your particular purposes or needs. NEMA does not undertake to guarantee the performance of any individual manufacturer or seller's products or services by virtue of this standard or guide.

In publishing and making this document available, NEMA is not undertaking to render professional or other services for or on behalf of any person or entity, nor is NEMA undertaking to perform any duty owed by any person or entity to someone else. Anyone using this document should rely on his or her own independent judgment or, as appropriate, seek the advice of a competent professional in determining the exercise of reasonable care in any given circumstances. Information and other standards on the topic covered by this publication may be available from other sources, which the user may wish to consult for additional views or information not covered by this publication.

NEMA has no power, nor does it undertake to police or enforce compliance with the contents of this document. NEMA does not certify, test, or inspect products, designs, or installations for safety or health purposes. Any certification or other statement of compliance with any health or safety-related information in this document shall not be attributable to NEMA and is solely the responsibility of the certifier or maker of the statement.

Foreword

This DICOM Standard was developed according to the procedures of the DICOM Standards Committee.

The DICOM Standard is structured as a multi-part document using the guidelines established in [ISO/IEC Directives, Part 2].

DICOM® is the registered trademark of the National Electrical Manufacturers Association for its standards publications relating to digital communications of medical information, all rights reserved.

HL7® and CDA® are the registered trademarks of Health Level Seven International, all rights reserved.

SNOMED®, SNOMED Clinical Terms®, SNOMED CT® are the registered trademarks of the International Health Terminology Standards Development Organisation (IHTSDO), all rights reserved.

LOINC® is the registered trademark of Regenstrief Institute, Inc, all rights reserved.

1 Scope and Field of Application

This Part of the DICOM Standard specifies the set of Service Class Definitions that provide an abstract definition of real-world activities applicable to communication of digital medical information. For each Service Class Definition, this Part specifies:

  • the semantic description of the activities of the Service Class Definition

  • the group of DIMSE Service operations and notifications applicable to the Service Class Description

  • one or more functionally-related Service-Object Pair (SOP) Classes that are supported by the Service Class Definition and may be performed between peer DICOM Application Entities

  • the relationship of each Service-Object Pair (SOP) Classes to applicable Information Object Definitions specified in PS3.3.

For each Service Class Definition, this Part does not specify:

  • any necessary information for the semantic description of the IOD

  • relationships to associated real-world objects relevant to the IOD

  • Attributes that describe the characteristics of the IOD

This Part is related to other parts of the DICOM Standard in that:

2 Normative References

The following standards contain provisions which, through reference in this text, constitute provisions of this Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this Standard are encouraged to investigate the possibilities of applying the most recent editions of the standards indicated below.

[ISO/IEC Directives, Part 2] ISO/IEC. 2016/05. 7.0. Rules for the structure and drafting of International Standards. http://www.iec.ch/members_experts/refdocs/iec/isoiecdir-2%7Bed7.0%7Den.pdf .

[ISO 7498-1] ISO. 1994. Information Processing Systems - Open Systems Interconnection - Basic Reference Model.

[RFC3986] IETF. Uniform Resource Identifiers (URI): Generic Syntax. http://tools.ietf.org/html/rfc3986 .

[ISO/TR 8509] ISO. Information Processing Systems - Open Systems Interconnection - Service Conventions. ISO/TR 8509 has been withdrawn. See ISO/IEC 2382-26:1993 Information technology - Vocabulary - Part 26: Open systems interconnection .

[RFC7230] IETF. June 2014. Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing. http://tools.ietf.org/html/rfc7230 .

[Porter and Duff 1984] Computer Graphics. Porter, Thomas and Duff, Tom. 1984. 18. 3. 253-259. “Compositing Digital Images”. doi:10.1145/800031.808606 http://keithp.com/~keithp/porterduff/p253-porter.pdf .

3 Definitions

For the purposes of this Standard the following definitions apply.

3.1 Reference Model Definitions

This Part of the Standard makes use of the following terms defined in [ISO 7498-1]:

Application Entity

See [ISO 7498-1].

Service

See [ISO 7498-1].

Application Entity Title (AET)

See [ISO 7498-1].

3.2 Service Conventions Definitions

This Part of the Standard makes use of the following terms defined in [ISO/TR 8509]:

Primitive

See [ISO/TR 8509].

3.3 DICOM Introduction and Overview Definitions

This Part of the Standard makes use of the following terms defined in PS3.1:

Attribute

Attribute.

Command

Command.

Data Dictionary

Data Dictionary.

Information Object

Information Object.

Message

Message.

Service-Object Pair Class (SOP Class)

Service-Object Pair Class (SOP Class).

3.4 DICOM Upper Layer Service Definitions

This Part of the Standard makes use of the following terms defined in PS3.8:

DICOM Upper Layer Service

DICOM Upper Layer Service.

3.5 DICOM Message Exchange Definitions

This Part of the Standard makes use of the following terms defined in PS3.7:

DICOM Message Service Element (DIMSE)

DICOM Message Service Element (DIMSE).

DIMSE-N Services

DIMSE-N Services.

DIMSE-C Services

DIMSE-C Services.

DIMSE Service Group (DSG)

DIMSE Service Group (DSG).

3.6 DICOM Information Object Definitions

This Part of the Standard makes use of the following terms defined in PS3.3:

Attribute Tag

AttributeTag.

Composite IOD

Composite IOD.

DICOM Application Model

DICOM Application Model.

DICOM Information Model

DICOM Information Model.

Information Object Definition (IOD)

Information Object Definition.

Module

Module.

Normalized IOD

Normalized IOD.

Functional Group

Functional Group.

3.7 DICOM Conformance

This Part of the Standard makes use of the following terms defined in PS3.2:

Conformance Statement

Conformance Statement.

Standard SOP Class

Standard SOP Class.

Specialized SOP Class

Specialized SOP Class.

Standard Extended SOP Class

Standard Extended SOP Class.

Private SOP Class

Private SOP Class.

Standard Attribute

Standard Attribute.

Private Attribute

Private Attribute.

3.8 DICOM Data Structures and Encoding

This Part of the Standard makes use of the following terms defined in PS3.5:

Data Element

Data Element.

Data Set

Data Set.

Unique Identifier (UID)

Unique Identifier (UID).

3.9 DICOM Service Class Definitions

The following definitions are commonly used in this Part of the DICOM Standard:

Classic Image Storage SOP Class

An Image Storage SOP Class that is defined by an IOD that stores a single frame and defines the majority of the Attributes in the top-level Data Set.

Combined Print Image

A pixel matrix created by superimposing an image and an overlay, the size of which is defined by the smallest rectangle enclosing the superimposed image and overlay.

Enhanced Image Storage SOP Class

An Image Storage SOP Class that is defined by an IOD that stores multiple frames and defines the majority of the Attributes in Functional Group Sequences.

Legacy Converted Enhanced Image Storage SOP Class

A modality-specific Enhanced Image Storage SOP Class that is defined by an IOD that defines only generic Functional Group Sequences, which does not require information that is not present in Classic Image Storage SOP Class Instances, and is intended for storage of converted Classic Image Storage SOP Class Instances when there is insufficient information to use a True Enhanced Image Storage SOP Class.

Meta Service-Object Pair Class (Meta SOP Class)

A pre-defined set of SOP Classes that may be associated under a single SOP for the purpose of negotiating the use of the set with a single item.

Performed Procedure Step SOP Class

Any SOP Class that encodes the details about the performance of a procedure step.

Performed Procedure Step SOP Instance

An instance of a Performed Procedure Step SOP Class. Note that all UPS instances are instances of the UPS Push SOP Class, which is capable of encoding details about the performance of a procedure step (in addition to details about the scheduled procedure step) and thus qualify as an instance of a Performed Procedure Step SOP Class.

Preformatted Grayscale Image

An image where all annotation, graphics, and grayscale transformations (up to and including the VOI LUT) expected in the printed image have been burnt in or applied before being sent to the SCP. It is a displayable image where the polarity of the intended display is specified by Photometric Interpretation (0028,0004).

Preformatted Color Image

An image where all annotation, graphics, and color transformations expected in the printed image have been burnt in or applied before being sent to the SCP.

Real-World Activity

That which exists in the real world that pertains to specific area of information processing within the area of interest of the DICOM Standard. Such a Real-World Activity may be represented by one or more computer information metaphors called SOP Classes.

Real-World Object

That which exists in the real world upon which operations may be performed that are within the area of interest of the DICOM Standard. Such a Real-World Object may be represented through a computer information metaphor called a SOP Instance.

Related General SOP Class

A SOP Class that is related to another SOP Class as being more generalized in terms of behavior defined in the Standard, and that may be used to identically encode an instance with the same Attributes and values, other than the SOP Class UID. In particular, this may be the SOP Class from which a Specialized SOP Class (see PS3.2) is derived.

Service Class User (SCU)

The role played by a DICOM Application Entity (DIMSE-Service-User) that invokes operations and performs notifications on a specific Association.

Service Class Provider (SCP)

The role played by a DICOM Application Entity (DIMSE-Service-User) that performs operations and invokes notifications on a specific Association.

Service Class

A collection of SOP Classes and/or Meta SOP Classes that are related in that they are described together to accomplish a single application.

Service-Object Pair Instance (SOP Instance)

A concrete occurrence of an Information Object that is managed by a DICOM Application Entity and may be operated upon in a communication context defined by a specific set of DIMSE Services (on a network or interchange media). A SOP Instance is persistent beyond the context of its communication.

True Enhanced Image Storage SOP Class

A modality-specific Enhanced Image Storage SOP Class that is defined by an IOD that defines modality-specific Functional Group Sequences, Attributes and sets of values, and is intended for creation by acquisition devices.

3.10 Device Independent Pixel Values

This Part of the Standard makes use of the following terms defined in PS3.3:

P-Value

P-Value.

Profile Connection Space Value (PCS-Value)

Profile Connection Space Value (PCS-Value).

3.11 HTTP Definitions

This Part of the Standard makes use of the following terms defined in [RFC7230]:

Origin-Server

See [RFC7230].

User-Agent

See [RFC7230].

4 Symbols and Abbreviations

The following symbols and abbreviations are used in this Part of the DICOM Standard.

ACR American College of Radiology

ASCII American Standard Code for Information Interchange

AE Application Entity

ANSI American National Standards Institute

CDS Clinical Decision Support

CEN TC251 Comité Européen de Normalisation - Technical Committee 251 - Medical Informatics

Chest CAD Computer-Aided Detection and/or Computer-Aided Diagnosis for chest radiography

DICOM Digital Imaging and Communications in Medicine

DIMSE DICOM Message Service Element

DIMSE-C DICOM Message Service Element-Composite

DIMSE-N DICOM Message Service Element-Normalized

HL7 Health Level 7

IE Information Entity

IEEE Institute of Electrical and Electronics Engineers

IOD Information Object Definition

IS Information System

ISO International Standards Organization

JIRA Japan Medical Imaging and Radiological Systems Industries Association

JPIP JPEG 2000 Interactive Protocol

MAR Medication Administration Record

NEMA National Electrical Manufacturers Association

OSI Open Systems Interconnection

SCP Service Class Provider

SCU Service Class User

SOP Service-Object Pair

UID Unique Identifier

5 Conventions

5.1 Entity-Relationship Model

5.1.1 Entity

An entity is used in an Entity-Relationship (E-R) model to represent a Real-World Object, class of Real-World Objects, or DICOM data representation (such as IOD or Module). An entity is depicted as a box within this Part of the DICOM Standard as shown in Figure 5-1.

Entity Convention

Figure 5-1. Entity Convention


5.1.2 Relationship

A relationship, which defines how entities are related, is depicted as a diamond within this Standard as shown in Figure 5-2.

Relationship Convention

Figure 5-2. Relationship Convention


The relationship is read from source to destination entity as indicated by the arrows. The a and b show the source and destination cardinality of the relationship respectively. The following cardinalities are permitted:

  1. (a = 1, b = 1) -one source entity is related to one destination entity

  2. (a = 1, b = 0-n) -one source entity is related to zero or more destination entities

  3. (a = 1, b = 1-n) -one source entity is related to one or more destination entities

  4. (a = 1-n, b = 1) -one or more source entities are related to one destination entity

  5. (a = 1-n, b = 0-n) -one or more source entities are related to zero or more destination entities

  6. (a = 1-n, b = 1-n) -one or more source entities are related to one or more destination entities

In a relationship where (a = 1-n, b = 1-n) the values of the source and destination cardinalities may be different. The value "n" simply denotes one or more.

Note

DICOM has added the use of arrows to the E-R diagramming conventions often used in other literature. This has been done to avoid the possibility of inferring an incorrect relationship that can result from reading a relationship in the reverse order of that intended. For example, a relationship "Cat Catches Mouse" could be read "Mouse Catches Cat" if the arrows were not present.

A relationship may be bi-directional (i.e., the relationship is true in both directions). In such a case, the convention used is arrows pointing toward both the source and the destination entities.

5.2 Sequences

Certain tables in this Part of the DICOM Standard denote a Sequence of Items by using the symbol: '>.'

In Annex A, '>' is used to identify a 'Sequence of Modules.' Nested Sequences of Modules are identified by '>>'. In Annex B and Annex C, '>' is used to identify a 'Sequence of Attributes'. See PS3.5 for the complete specification of how Sequences of Items shall be encoded.

Note

Information Object Definitions (IODs) that include the Sequence of Module construct are often called folders. The use of 'Sequences of Attributes' is not limited to 'Folders.'

5.3 Response Status Values

Certain tables in this Part of the DICOM Standard denote an implementation specific response status code by using the symbol 'xx' or 'xxx' as part of the code.

Note

Each 'x' symbol may be replaced by an implementation with a hexadecimal digit in the range from 0 to F.

5.4 Usage Specification

The building blocks of SOP Classes are Modules and DIMSE Services. The DIMSE Services associated with a SOP Class may be Mandatory (M) or Optional (U). The usage may be different for the SCU and SCP. The usage is specified as a pair of letters: the former indicating the SCU usage, the latter indicating the SCP usage.

5.4.1 Use of DIMSE Services

The meaning and behavior of the usage specification for DIMSE Services are:

M/M

The SCU shall support the DIMSE Service but is not required to use it on an Association. The SCP shall support the DIMSE Service.

U/M

The SCU may support and use the DIMSE Service. The SCP shall support the DIMSE Service.

U/U

The SCU may support and use the DIMSE Service. The SCP may support the DIMSE Service. If the SCP does not support the DIMSE Service used by the SCU, it shall return a Failure status.

5.4.2 Use of Attributes in Normalized Services

Modules and their usage in Composite IODs are defined in PS3.3. Normalized IODs are also constructed from Modules but usage is specified on an Attribute basis in this Part of the DICOM Standard. The following usage specification applies to all Attributes of Normalized IODs unless superseded by a usage specification in a particular SOP Class Specification.

The term ‘receive’ means the following: the value shall be stored; under certain circumstances (e.g. coercion) the value returned may have changed.

5.4.2.1 DIMSE Service N-CREATE, N-SET, N-ACTION

The following Requirements apply when specifying the use of DIMSE services N-CREATE, N-SET, N-ACTION.

The convention used in the table below are as follows:

SCU Behaviour

Mandatory

The SCU shall provide the Attribute.

Optional

The SCU may or may not provide the Attribute.

Undefined

The SCU's usage of the Attribute is undefined.

SCP Behaviour

Mandatory

The SCP shall support receiving the Attribute.

Mandatory with Default

The SCP shall support receiving the Attribute. Upon receiving zero-length values, the SCP shall assign values as defined by the specification of the Service Class.

Optional

The SCP may or may not support receiving the Attribute.

Undefined

The SCP’s support of the Attribute is undefined.

SCU

SCP

Usage

Requirement

Zero Length

Requirement

1/1

Mandatory

Not Permitted

Mandatory

2/1

Mandatory

Permitted

Mandatory with Default

2/2

Mandatory

Permitted

Mandatory

3/1

Optional

Not Permitted

Mandatory

3/2

Optional

Not Permitted

Optional

3/3

Optional

Not Permitted

Optional

-/-

Undefined

Undefined

Undefined

If the SCU does not provide an Attribute that is Mandatory for the SCU, the SCP shall respond with the error code "Missing Attribute" (0120H).

If the SCU provides a zero-length value for a Mandatory Attribute when zero length is not permitted, the SCP shall respond with the error code "Missing Attribute Value" (0121H).

5.4.2.2 DIMSE Service N-GET, N-EVENT-REPORT

The following Requirements apply when specifying the use of DIMSE services N-GET, N-EVENT-REPORT.

The convention used in the table below are as follows:

SCU Behaviour

Optional

The SCU may retrieve the Attribute.

Undefined

The SCU's usage of the Attribute is undefined.

SCP Behaviour

Mandatory

The SCP shall support retrieval of the Attribute.

Optional

The SCP may or may not support retrieval of the Attribute.

Undefined

The SCP’s support of the Attribute is undefined.

SCU

SCP

Usage

Requirement

Requirement

Zero Length

3/1

Optional

Mandatory

Not Permitted

3/2

Optional

Mandatory

Permitted

3/3

Optional

Optional

Not Permitted

-/1

Undefined

Mandatory

Not Permitted

-/2

Undefined

Mandatory

Permitted

-/3

Undefined

Optional

Not Permitted

If support of an Attribute by the SCP is optional and the SCP does not support the Attribute and the Attribute is requested by the SCU, the SCP shall respond with the error code "Invalid Attribute Value" (0106H) or "Attribute Value out of range" (0116H).

5.4.2.3 Other Requirements

If the SCP usage type designation is modified by a "C" (e.g., 3/1C) the specification stated above shall be modified to include the requirement that the SCP shall support the Attribute if the specified condition is met.

For all N-CREATE, N-SET, N-GET, N-DELETE, N-ACTION and N-EVENT-REPORT operations, the SOP Class is conveyed in the request primitive in Affected SOP Class UID (0000,0002). The SOP Class UID (0008,0016) Attribute shall not be present in the Data Set.

For N-CREATE operations and N-EVENT-REPORT notifications, the SOP Instance is conveyed in Affected SOP Instance UID (0000,1000). The SOP Instance UID (0008,0018) Attribute shall not be present in the Data Set.

Note

In some Service Classes, the SOP Class definition may override the general provision in PS3.7 that allows the SOP Instance UID to be specified or omitted in the N-CREATE request primitive, and require that the SCU be responsible for specifying the SOP Instance UID.

For N-SET, N-GET, N-ACTION and N-DELETE operations, the SOP Instance is conveyed in Requested SOP Instance UID (0000,1001). The SOP Instance UID (0008,0018) Attribute shall not be present in the Data Set.

6 DICOM Information Model

The DICOM Information Model defines the structure and organization of the information related to the communication of medical images. Figure 6-1 shows the relationships between the major structures of the DICOM Information Model.

6.1 Information Object Definition

An Information Object Definition (IOD) is an object-oriented abstract data model used to specify information about Real-World Objects. An IOD provides communicating Application Entities with a common view of the information to be exchanged.

Major Structures of DICOM Information Model

Figure 6-1. Major Structures of DICOM Information Model


An IOD does not represent a specific instance of a Real-World Object, but rather a class of Real-World Objects that share the same properties. An IOD used to represent a single class of Real-World Objects is called a Normalized Information Object. An IOD that includes information about related Real-World Objects is called a Composite Information Object.

6.1.1 Composite IOD

A Composite IOD is an Information Object Definition that represents parts of several entities in the DICOM Model of the Real-World. (see PS3.3.) Such an IOD includes Attributes that are not inherent in the Real-World Object that the IOD represents but rather are inherent in related Real-World Objects.

These related Real-World Objects provide a complete context for the exchanged information. When an instance of a Composite IOD is communicated, this entire context is exchanged between Application Entities. Relationships between Composite IOD Instances shall be conveyed in this contextual information.

Note

  1. Actual communication of IOD Instances is via SOP Instances.

  2. Whenever Composite SOP Instances are in fact related, some of the contextual information is redundant (i.e., the same information about the same Real-World Objects is contained in multiple SOP Instances).

The Composite IODs are specified in PS3.3.

6.1.2 Normalized IOD

A Normalized IOD is an Information Object Definition that generally represents a single entity in the DICOM Model of the Real-World.

When an instance of a Normalized IOD is communicated, the context for that instance is not actually exchanged. Instead, the context is provided through the use of pointers to related Normalized IOD Instances.

The Normalized IODs are specified in PS3.3.

6.2 Attributes

The Attributes of an IOD describe the properties of a Real-World Object Instance. Related Attributes are grouped into Modules that represents a higher level of semantics documented in the Module Specifications found in PS3.3.

Attributes are encoded as Data Elements using the rules, the Value Representation and the Value Multiplicity concepts specified in PS3.5. For specific Data Elements, the Value Representation and Value Multiplicity of Data Elements are specified in the Data Dictionary in PS3.6.

6.3 On-Line Communication and Media Storage Services

For on-line communication the DIMSE Services and Web Services allow a DICOM Application Entity to invoke an operation or notification across a network or a point-to-point interface. DIMSE Services are defined in PS3.7 and Web Services are defined in PS3.18.

For media storage interchange, Media Storage Services allow a DICOM Application Entity to invoke media storage related operations.

Media Storage Services are discussed in PS3.10.

6.3.1 DIMSE-C Services

DIMSE-C Services are services applicable only to a Composite IOD. DIMSE-C provides only operation services.

6.3.2 DIMSE-N Services

DIMSE-N Services are services applicable only to a Normalized IOD. DIMSE-N provides both operation and notification services.

6.4 DIMSE Service Group

A DIMSE Service Group specifies one or more operations/notifications defined in PS3.7 that are applicable to an IOD.

DIMSE Service Groups are defined in this Part of the DICOM Standard, in the specification of a Service-Object Pair Class.

6.5 Service-Object Pair (SOP) Class

The SOP Class definitions in PS3.4 contain the rules and semantics that may restrict the use of the services in the DIMSE Service Group or the Attributes of the IOD. PS3.10 and PS3.18 contain the rules and semantics that may restrict the Attributes of the IOD or the use of the services in the Media Storage Services and the Web Services respectively.

The selection of SOP Classes is used by Application Entities to establish an agreed set of capabilities to support their interaction for SOP Classes based on DIMSE Services. This negotiation is performed at Association establishment time as described in PS3.7. An extended negotiation allows Application Entities to further agree on specific options within a SOP Class.

Note

  1. The SOP Class as defined in the DICOM Information Model is equivalent in ISO/OSI terminology to the Managed Object Class. Readers familiar with object-oriented terminology will recognize the SOP Class operations (and notifications) as comprising the methods of an object class.

  2. SOP Class Specifications play a central role in defining DICOM conformance. They allow DICOM Application Entities to select a well-defined application level subset of this Standard to which they may claim conformance. See PS3.2.

6.5.1 Normalized and Composite SOP Classes

DICOM defines two types of SOP Classes, Normalized and Composite. For DIMSE Services, Normalized SOP Classes are defined as the union of a Normalized IOD and a set of DIMSE-N Services, while Composite SOP Classes are defined as the union of a Composite IOD and a set of DIMSE-C Services. Media Storage Services only support Composite IODs and Web Services support both Normalized and Composite SOP Classes.

6.6 Association Negotiation

Association establishment is the first phase of communication between peer DICOM compliant Application Entities. The Application Entities shall use Association establishment to negotiate which SOP Classes can be exchanged and how this data will be encoded.

Association Negotiation is defined in PS3.7.

6.7 Service Class Specification

A Service Class Specification defines a group of one or more SOP Classes related to a specific function that is to be accomplished by communicating Application Entities. A Service Class Specification also defines rules that allow implementations to state some pre-defined level of conformance to one or more SOP Classes. Applications may conform to network SOP Classes as a Service Class User (SCU), Service Class Provider (SCP), User Agent or Origin Server, and to media exchange SOP Classes as a File Set Creator (FSC), File Set Reader (FSR), or File Set Updater (FSU).

Service Class Specifications are defined in this Part of the DICOM Standard.

Note

Network interaction between peer Application Entities work on a 'client/server model.' The SCU or User Agent acts as the 'client,' while the SCP or Origin Server acts as the 'server'. For DIMSE based services the SCU/SCP roles are determined during Association establishment.

7 DICOM Model of the Real World

The DICOM view of the Real-World that identifies the relevant Real-World Objects and their relationships within the scope of the DICOM Standard is described in the DICOM Model of the Real-World Section of PS3.3.

This section also describes the DICOM Information Model that identifies the various IODs specified by the DICOM Standard and their relationship.

8 Coded Entry Usage in Service Specifications

The Macros in this Section specify the usage of the Attributes that correspond to Coded Entries as defined by Table 8.8-1 Code Sequence Macro Attributes.

Not all invocations make use of all the columns. For example, in some invocations, only the "Requirement Type SCU/SCP" is relevant; in others, only the Matching Key Type and Return Key Type columns are used.

Table 8-1a. Enhanced SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning


Table 8-1b. Basic SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning

Attribute Name

Tag

Requirement Type

SCU/SCP

Matching Key Type

Return Key Type

Code Value

(0008,0100)

1C/1C

Shall be present if the code value length is 16 characters or less, and the code value is not a URN or URL.

RC

Required if the code value length is 16 characters or less, and the code value is not a URN or URL.

1C

Shall be present if the code value length is 16 characters or less, and the code value is not a URN or URL.

Coding Scheme Designator

(0008,0102)

1C/1C

Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise.

RC

Required if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise.

1C

Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise.

Coding Scheme Version

(0008,0103)

1C/1C

Required if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise.

RC

Required if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise.

1C

Required if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise.

Code Meaning

(0008,0104)

1/1

-

1

Long Code Value

(0008,0119)

1C/1C

Shall be present if Code Value (0008,0100) is not present, and the code value is not a URN or URL.

RC

Required if Code Value (0008,0100) is not present, and the code value is not a URN or URL.

1C

Required if Code Value (0008,0100) is not present, and the code value is not a URN or URL.

URN Code Value

(0008,0120)

1C/1C

Shall be present if Code Value (0008,0100) is not present, and the code value is a URN or URL.

RC

Required if Code Value (0008,0100) is not present, and the code value is a URN or URL.

1C

Require if Code Value (0008,0100) is not present, and the code value is a URN or URL.

Mapping Resource

(0008,0105)

3/3

-

3

Mapping Resource UID

(0008,0118)

3/3

-

3

Context Group Version

(0008,0106)

3/3

-

3

Context Group Extension Flag

(0008,010B)

3/3

-

3

Context Group Local Version

(0008,0107)

3/3

-

3

Context Group Extension Creator UID

(0008,010D)

3/3

-

3


Table 8-2a. Enhanced Coded Entry Macro with Optional Matching Key Support and Optional Meaning


Table 8-2b. Basic Coded Entry Macro with Optional Matching Key Support and Optional Meaning

Attribute Name

Tag

Matching Key Type

Return Key Type

Code Value

(0008,0100)

O

1C

Shall be present if the code value length is 16 characters or less, and the code value is not a URN or URL.

Coding Scheme Designator

(0008,0102)

O

1C

Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present.

Coding Scheme Version

(0008,0103)

OC

May be present only if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously.

3

Applicable only if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously.

Code Meaning

(0008,0104)

O

3

Long Code Value

(0008,0119)

O

1C

Shall be present if Code Value (0008,0100) is not present, and the code value is not a URN or URL.

URN Code Value

(0008,0120)

O

1C

Shall be present only if Code Value (0008,0100) is not present, and the code value is a URN or URL.

Mapping Resource

(0008,0105)

O

3

Mapping Resource UID

(0008,0118)

O

3

Context Group Version

(0008,0106)

O

3

Context Group Extension Flag

(0008,010B)

O

3

Context Group Local Version

(0008,0107)

O

3

Context Group Extension Creator UID

(0008,010D)

O

3


Table 8-3a. Enhanced SCU/SCP Coded Entry Macro with no SCU Support and no Matching Key Support

Attribute Name

Tag

Requirement Type

SCU/SCP

Matching Key Type

Return Key Type

Include Table 8-3b “Basic SCU/SCP Coded Entry Macro with no SCU Support and no Matching Key Support”

Equivalent Code Sequence

(0008,0121)

-/3

-

>Include Table 8-3b “Basic SCU/SCP Coded Entry Macro with no SCU Support and no Matching Key Support”


Table 8-3b. Basic SCU/SCP Coded Entry Macro with no SCU Support and no Matching Key Support

Attribute Name

Tag

Requirement Type

SCU/SCP

Matching Key Type

Return Key Type

Code Value

(0008,0100)

-/1C

Shall be present if the code value length is 16 characters or less, and the code value is not a URN or URL.

-

1C

Shall be present if the code value length is 16 characters or less, and the code value is not a URN or URL.

Coding Scheme Designator

(0008,0102)

-/1C

Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise.

-

1C

Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise.

Coding Scheme Version

(0008,0103)

-/1C

Required if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise.

-

1C

Shall be present if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise.

Code Meaning

(0008,0104)

-/1

-

1

Long Code Value

(0008,0119)

-/1C

Shall be present if Code Value (0008,0100) is not present, and the code value is not a URN or URL.

-

1C

Shall be present if Code Value (0008,0100) is not present, and the code value is not a URN or URL.

URN Code Value

(0008,0120)

-/1C

Shall be present if Code Value (0008,0100) is not present, and the code value is a URN or URL.

-

1C

Shall be present if Code Value (0008,0100) is not present, and the code value is a URN or URL.

Mapping Resource

(0008,0105)

-/3

-

3

Mapping Resource UID

(0008,0118)

-/3

-

3

Context Group Version

(0008,0106)

-/3

-

3

Context Group Extension Flag

(0008,010B)

-/3

-

3

Context Group Local Version

(0008,0107)

-/3

-

3

Context Group Extension Creator UID

(0008,010D)

-/3

-

3


Table 8-4a. Enhanced Coded Entry Macro with Optional Matching Key Support and Mandatory Meaning


Table 8-4b. Basic Coded Entry Macro with Optional Matching Key Support and Mandatory Meaning

Attribute Name

Tag

Matching Key Type

Return Key Type

Code Value

(0008,0100)

O

1C

Shall be present if the code value length is 16 characters or less, and the code value is not a URN or URL.

Coding Scheme Designator

(0008,0102)

O

1C

Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise.

Coding Scheme Version

(0008,0103)

RC

Required if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise.

1C

Shall be present if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise.

Code Meaning

(0008,0104)

O

1

Long Code Value

(0008,0119)

O

1C

Shall be present if Code Value (0008,0100) is not present, and the code value is not a URN or URL.

URN Code Value

(0008,0120)

O

1C

Shall be present if Code Value (0008,0100) is not present, and the code value is a URN or URL.

Mapping Resource

(0008,0105)

O

3

Mapping Resource UID

(0008,0118)

O

3

Context Group Version

(0008,0106)

O

3

Context Group Extension Flag

(0008,010B)

O

3

Context Group Local Version

(0008,0107)

O

3

Context Group Extension Creator UID

(0008,010D)

O

3


Table 8-5a. Enhanced SCU/SCP Coded Entry Macro with no SCU Support and Optional Meaning for SCP


Table 8-5b. Basic SCU/SCP Coded Entry Macro with no SCU Support and Optional Meaning for SCP

Attribute Name

Tag

Requirement Type

SCU/SCP

Code Value

(0008,0100)

-/1C

Shall be present if the code value length is 16 characters or less, and the code value is not a URN or URL.

Coding Scheme Designator

(0008,0102)

-/1C

Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise.

Coding Scheme Version

(0008,0103)

-/1C

May be present if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise.

Code Meaning

(0008,0104)

-/3

Long Code Value

(0008,0119)

-/1C

Shall be present if Code Value (0008,0100) is not present, and the code value is not a URN or URL.

URN Code Value

(0008,0120)

1C/1C

Shall be present if Code Value (0008,0100) is not present, and the code value is a URN or URL.

Mapping Resource

(0008,0105)

-/3

Mapping Resource UID

(0008,0118)

-/3

Context Group Version

(0008,0106)

-/3

Context Group Extension Flag

(0008,010B)

-/3

Context Group Local Version

(0008,0107)

-/3

Context Group Extension Creator UID

(0008,010D)

-/3


A Verification Service Class (Normative)

A.1 Overview

A.1.1 Scope

The Verification Service Class defines a service that verifies application level communication between peer DICOM AEs. This verification is accomplished on an established Association using the C-ECHO DIMSE-C service.

A.2 SCU/SCP Behavior

A DICOM AE, supporting the Verification SOP Class SCU role, requests verification of communication to a remote DICOM AE. This request is performed using the C-ECHO request primitive. The remote DICOM AE, supporting the Verification SOP Class SCP role, issues an C-ECHO response primitive. Upon receipt of the C-ECHO confirmation, the SCU determines that verification is complete. See PS3.7 for the specification of the C-ECHO primitives.

A.3 DIMSE-C Service Group

The C-ECHO DIMSE-C service shall be the mechanism used to verify communications between peer DICOM AEs. The C-ECHO service and protocol parameters shall be required as defined in PS3.7.

A.4 Verification SOP Class

The Verification SOP Class consists of the C-ECHO DIMSE-C service. No associated Information Object Definition is defined. The SOP Class UID shall be "1.2.840.10008.1.1".

No Specialized SOP Classes and/or Meta SOP Classes shall be defined for the Verification SOP Class.

A.5 Association Negotiation

Association establishment is the first phase of any instance of communication between peer DICOM AEs. The following negotiation rules apply to DICOM AEs that support the Verification SOP Class

  • The Association-requester (verification SCU role) in the A-ASSOCIATE request shall convey an Abstract Syntax, in a Presentation Context, for the Verification SOP Class. The Abstract Syntax Name shall be equivalent to the Verification SOP Class UID.

  • The Association-acceptor (verification SCP role) in the A-ASSOCIATE response shall accept the Abstract Syntax, in a Presentation Context, for the supported Verification SOP Class.

No Application Association Information specific to the Verification SOP Class shall be used.

A.6 Conformance

A.6.1 Conformance Supporting the SCU Role

Implementations that conform to the Verification SOP Class SCU role shall meet the:

  • C-ECHO service requirements as defined by the DIMSE Service Group, Section A.3

  • Association negotiation rules as defined in Section A.5

A.6.2 Conformance Supporting the SCP Role

Implementations that conform to the Verification SOP Class SCP role shall meet the:

  • C-ECHO operation rules as defined by the DIMSE Service Group, Section A.3

  • Association negotiation rules as defined in Section A.5

A.6.3 Conformance Statement

An implementation may conform to the Verification SOP Class as an SCU, SCP, or both. The Conformance Statement shall be in the format defined in PS3.2.

B Storage Service Class (Normative)

B.1 Overview

B.1.1 Scope

The Storage Service Class defines an application-level class-of-service that 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 PS3.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.

Note

  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 PS3.7.

B.2.1 Behavior of an SCU

The SCU invokes a C-STORE DIMSE Service with a SOP Instance that 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 that might be returned in a C-STORE response. General status code values and fields related to status code values are defined for C-STORE DIMSE Service in PS3.7.

Table B.2-1. C-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

Success

0000

None


Some Failure Status Codes are implementation specific.

An SCP implementation shall assign specific failure status codes by replacing each 'x' symbol with a hexadecimal digit in the range from 0 to F. An SCP implementation wishing to differentiate between causes within the same Failure Meaning shall assign those causes specific Status Code Values within valid range specified in Table B.2-1.

An SCU implementation shall recognize any Failure Status Code within the value range specified in Table B.2-1 as an indicator of the Failure Meaning stated in the table. There is no requirement for an SCU implementation to differentiate between specific Status Codes within the valid range.

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 PS3.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 PS3.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 PS3.7 and PS3.8. SCUs and SCPs may use the SOP Class Extended Negotiation Sub-Item Structure as described in Section D.3.3.5 in PS3.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 Section D.3.3.6 in PS3.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 PS3.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 PS3.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-2. Service-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 PS3.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 X-Ray Image Storage - For Presentation

Digital X-Ray Image Storage - For Presentation

Digital Mammography X-Ray 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

Comprehensive 3D SR

Extensible SR

Enhanced SR

Comprehensive SR

Comprehensive 3D SR

Extensible SR

Comprehensive SR

Comprehensive 3D SR

Extensible SR

Comprehensive 3D SR

Extensible SR

Procedure Log

Enhanced SR

Comprehensive SR

Comprehensive 3D SR

Extensible SR

Simplified Adult Echo SR

Enhanced SR

Comprehensive SR

Comprehensive 3D SR

Extensible SR

X-Ray Radiation Dose SR

Enhanced SR

Comprehensive SR

Comprehensive 3D SR

Extensible SR

Radiopharmaceutical Radiation Dose SR

Enhanced SR

Comprehensive SR

Comprehensive 3D SR

Extensible SR

Patient Radiation Dose SR

Enhanced SR

Comprehensive SR

Comprehensive 3D SR

Extensible SR

Enhanced X-Ray Radiation Dose SR

Enhanced SR

Comprehensive SR

Comprehensive 3D SR

Extensible SR

Acquisition Context SR

Enhanced SR (see note)

Comprehensive SR (see note)

Comprehensive 3D SR

Extensible SR

Spectacle Prescription Report

Enhanced SR

Macular Grid Thickness and Volume Report

Enhanced SR

Enhanced CT Image Storage

Legacy Converted Enhanced CT Image Storage

Enhanced MR Image Storage

Legacy Converted Enhanced MR Image Storage

Enhanced PET Image Storage

Legacy Converted Enhanced PET Image Storage


Note

The Acquisition Context SR may be encoded as Enhanced or Comprehensive only if it does not contain stereotactic coordinates (SCOORD3D).

B.4 Conformance

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

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

B.4.1.1 Levels of Conformance

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 implementer.

  • 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.

  • Level 2 (Full). Level 2 conformance indicates that all Type 1, Type 2, and Type 3 Attributes defined in the Information Object Definition associated with the SOP Class, as well as any Standard Extended Attributes (including Private Attributes) included in the SOP Instance, will be stored and may be accessed. The SCP may, but is not required to validate that the Attributes of the SOP Instance meet 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 PS3.5 definition of "Type 3 Optional Data Elements".

B.4.1.2 Support of Additional SOP Classes

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 (see Section B.3.1.3), without asserting conformance to that SOP Class in its Conformance Statement.

Note

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

  2. This Extended Negotiation allows an SCP to determine that a Private SOP Class in a proposed Presentation Context follows the semantics of the Storage Service Class, and may be handled accordingly.

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.

Note

  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.

  3. An SCP that has access to the current content of Table B.5-1 might use that to determine acceptance of proposed Presentation Context SOP Classes. This allows an SCP, even without Extended Negotiation, to be able to identify all Standard SOP Classes of the Storage Service Class. Access to Table B.5-1 may be through private means, or to the publication of PS3 on the web site of the DICOM Standards Committee. This provides an automated alternative to manually editing a table of supported Storage SOP Classes.

B.4.1.3 Coercion of Attributes

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 that may be modified are shown in Table B.4-1.

Table B.4-1. Attributes Subject to Coercion

Attribute Name

Tag

Patient ID

(0010,0020)

Issuer of Patient ID

(0010,0021)

Other Patient IDs Sequence

(0010,1002)

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.

Note

  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 that 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 retired Code Values with a Coding Scheme Designator value of "99SDM", "SNM3" or "SRT" to the corresponding SCT Code Values and use the "SCT" Coding Scheme Designator, 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.

B.4.1.4 Levels of Digital Signature

Three levels of Digital Signature support are defined for an SCP that 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 that 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 PS3.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.

  • The optional elements that may be included in Storage SOP Instances for each IOD supported shall be listed.

  • The standard and privately defined Functional Groups that may be included in Storage SOP Instances for each Multi-frame IOD that support Functional Groups.

  • The behavior of the SCU in the case of a C-STORE operation using a referenced pixel data transfer syntax such as JPIP Referenced Pixel Data Transfer Syntax shall be described. This includes the duration of validity of the reference

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 level of conformance, as defined by Section B.4.1, shall be stated.

  • The level of Digital Signature support, as defined by Section B.4.1, shall be stated.

  • The optional elements that will be discarded (if any) shall be listed for each IOD supported.

  • The mechanisms by which additional SOP Classes are dynamically supported, as defined by Section B.4.1.2, shall be stated.

  • The Conformance Statement shall document the policies concerning the Attribute Lossy Image Compression (0028,2110).

  • 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 PS3.2.

B.4.4.1 Specialized SOP Class Identification

Any implementation that 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 PS3.2, declaring a SOP Name and SOP Class UID that identify the Specialized SOP Class. The SOP Name is not guaranteed to be unique (unless the implementer 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 PS3.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 PS3.2. Following this statement shall be the list of Attributes that 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 PS3.3)

Specialization

Computed Radiography Image Storage

1.2.840.10008.5.1.4.1.1.1

Computed Radiography Image IOD

Digital X-Ray Image Storage - For Presentation

1.2.840.10008.5.1.4.1.1.1.1

Digital X-Ray Image IOD

B.5.1.1

Digital X-Ray Image Storage - For Processing

1.2.840.10008.5.1.4.1.1.1.1.1

Digital X-Ray Image IOD

B.5.1.1

Digital Mammography X-Ray Image Storage - For Presentation

1.2.840.10008.5.1.4.1.1.1.2

Digital Mammography X-Ray Image IOD

B.5.1.2

Digital Mammography X-Ray Image Storage - For Processing

1.2.840.10008.5.1.4.1.1.1.2.1

Digital Mammography X-Ray Image IOD

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 Image IOD

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 Image IOD

B.5.1.3

CT Image Storage

1.2.840.10008.5.1.4.1.1.2

CT Image IOD

Enhanced CT Image Storage

1.2.840.10008.5.1.4.1.1.2.1

Enhanced CT Image IOD

B.5.1.7

B.5.1.23

Legacy Converted Enhanced CT Image Storage

1.2.840.10008.5.1.4.1.1.2.2

Legacy Converted Enhanced CT Image IOD

B.5.1.7

B.5.1.23

Ultrasound Multi-frame Image Storage

1.2.840.10008.5.1.4.1.1.3.1

Ultrasound Multi-frame Image IOD

MR Image Storage

1.2.840.10008.5.1.4.1.1.4

MR Image IOD

Enhanced MR Image Storage

1.2.840.10008.5.1.4.1.1.4.1

Enhanced MR Image IOD

B.5.1.6

B.5.1.23

MR Spectroscopy Storage

1.2.840.10008.5.1.4.1.1.4.2

MR Spectroscopy IOD

Enhanced MR Color Image Storage

1.2.840.10008.5.1.4.1.1.4.3

Enhanced MR Color Image IOD

B.5.1.8

B.5.1.23

Legacy Converted Enhanced MR Image Storage

1.2.840.10008.5.1.4.1.1.4.4

Legacy Converted Enhanced MR Image IOD

B.5.1.6

B.5.1.23

Ultrasound Image Storage

1.2.840.10008.5.1.4.1.1.6.1

Ultrasound Image IOD

Enhanced US Volume Storage

1.2.840.10008.5.1.4.1.1.6.2

Enhanced US Volume IOD

Secondary Capture Image Storage

1.2.840.10008.5.1.4.1.1.7

Secondary Capture Image IOD

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 IOD

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 IOD

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 IOD

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 IOD

12-lead ECG Waveform Storage

1.2.840.10008.5.1.4.1.1.9.1.1

12-Lead ECG IOD

General ECG Waveform Storage

1.2.840.10008.5.1.4.1.1.9.1.2

General ECG IOD

Ambulatory ECG Waveform Storage

1.2.840.10008.5.1.4.1.1.9.1.3

Ambulatory ECG IOD

Hemodynamic Waveform Storage

1.2.840.10008.5.1.4.1.1.9.2.1

Hemodynamic Waveform IOD

Cardiac Electrophysiology Waveform Storage

1.2.840.10008.5.1.4.1.1.9.3.1

Basic Cardiac Electrophysiology Waveform IOD

Basic Voice Audio Waveform Storage

1.2.840.10008.5.1.4.1.1.9.4.1

Basic Voice Audio Waveform IOD

General Audio Waveform Storage

1.2.840.10008.5.1.4.1.1.9.4.2

General Audio Waveform IOD

Arterial Pulse Waveform Storage

1.2.840.10008.5.1.4.1.1.9.5.1

Arterial Pulse Waveform IOD

Respiratory Waveform Storage

1.2.840.10008.5.1.4.1.1.9.6.1

Respiratory Waveform IOD

Multi-channel Respiratory Waveform Storage

1.2.840.10008.5.1.4.1.1.9.6.2

Multi-channel Respiratory Waveform IOD

Routine Scalp Electroencephalogram Waveform Storage

1.2.840.10008.5.1.4.1.1.9.7.1

Routine Scalp Electroencephalogram IOD

Electromyogram Waveform Storage

1.2.840.10008.5.1.4.1.1.9.7.2

Electromyogram IOD

Electrooculogram Waveform Storage

1.2.840.10008.5.1.4.1.1.9.7.3

Electrooculogram IOD

Sleep Electroencephalogram Waveform Storage

1.2.840.10008.5.1.4.1.1.9.7.4

Sleep Electroencephalogram IOD

Body Position Waveform Storage

1.2.840.10008.5.1.4.1.1.9.8.1

Body Position Waveform IOD

Grayscale Softcopy Presentation State Storage

1.2.840.10008.5.1.4.1.1.11.1

Grayscale Softcopy Presentation State IOD

Color Softcopy Presentation State Storage

1.2.840.10008.5.1.4.1.1.11.2

Color Softcopy Presentation State IOD

Pseudo-Color Softcopy Presentation State Storage

1.2.840.10008.5.1.4.1.1.11.3

Pseudo-color Softcopy Presentation State IOD

Blending Softcopy Presentation State Storage

1.2.840.10008.5.1.4.1.1.11.4

Blending Softcopy Presentation State IOD

XA/XRF Grayscale Softcopy Presentation State Storage

1.2.840.10008.5.1.4.1.1.11.5

XA/XRF Grayscale Softcopy Presentation State IOD

Grayscale Planar MPR Volumetric Presentation State Storage

1.2.840.10008.​5.​1.​4.​1.​1.​11.​6

Planar MPR Volumetric Presentation State IOD

B.5.1.19

Compositing Planar MPR Volumetric Presentation State Storage

1.2.840.10008.​5.​1.​4.​1.​1.​11.​7

Planar MPR Volumetric Presentation State IOD

B.5.1.19

Advanced Blending Presentation State Storage

1.2.840.10008.5.1.4.1.1.11.8

Advanced Blending Presentation State IOD

Volume Rendering Volumetric Presentation State Storage

1.2.840.10008.5.1.4.1.1.11.9

Volume Rendering Volumetric Presentation State IOD

B.5.1.24

Segmented Volume Rendering Volumetric Presentation State Storage

1.2.840.10008.5.1.4.1.1.11.10

Volume Rendering Volumetric Presentation State IOD

B.5.1.24

Multiple Volume Rendering Volumetric Presentation State Storage

1.2.840.10008.5.1.4.1.1.11.11

Volume Rendering Volumetric Presentation State IOD

B.5.1.24

X-Ray Angiographic Image Storage

1.2.840.10008.5.1.4.1.1.12.1

X-Ray Angiographic Image IOD

Enhanced XA Image Storage

1.2.840.10008.5.1.4.1.1.12.1.1

Enhanced XA Image IOD

X-Ray Radiofluoroscopic Image Storage

1.2.840.10008.5.1.4.1.1.12.2

X-Ray Radiofluoroscopic Image IOD

Enhanced XRF Image Storage

1.2.840.10008.5.1.4.1.1.12.2.1

Enhanced XRF Image IOD

X-Ray 3D Angiographic Image Storage

1.2.840.10008.5.1.4.1.1.13.1.1

X-Ray 3D Angiographic Image IOD

X-Ray 3D Craniofacial Image Storage

1.2.840.10008.5.1.4.1.1.13.1.2

X-Ray 3D Craniofacial Image IOD

Breast Tomosynthesis Image Storage

1.2.840.10008.5.1.4.1.1.13.1.3

Breast Tomosynthesis Image IOD

Breast Projection X-Ray Image Storage - For Presentation

1.2.840.10008.5.1.4.1.1.13.1.4

Breast Projection X-Ray Image IOD

B.5.1.18

Breast Projection X-Ray Image Storage - For Processing

1.2.840.10008.5.1.4.1.1.13.1.5

Breast Projection X-Ray Image IOD

B.5.1.18

Intravascular Optical Coherence Tomography Image Storage - For Presentation

1.2.840.10008.5.1.4.1.1.14.1

Intravascular Optical Coherence Tomography IOD

B.5.1.13

Intravascular Optical Coherence Tomography Image Storage - For Processing

1.2.840.10008.5.1.4.1.1.14.2

Intravascular Optical Coherence Tomography IOD

B.5.1.13

Nuclear Medicine Image Storage

1.2.840.10008.5.1.4.1.1.20

Nuclear Medicine Image IOD

Parametric Map Storage

1.2.840.10008.5.1.4.1.1.30

Parametric Map IOD

Raw Data Storage

1.2.840.10008.5.1.4.1.1.66

Raw Data IOD

B.5.1.22

Spatial Registration Storage

1.2.840.10008.5.1.4.1.1.66.1

Spatial Registration IOD

Spatial Fiducials Storage

1.2.840.10008.5.1.4.1.1.66.2

Spatial Fiducials IOD

Deformable Spatial Registration Storage

1.2.840.10008.5.1.4.1.1.66.3

Deformable Spatial Registration IOD

Segmentation Storage

1.2.840.10008.5.1.4.1.1.66.4

Segmentation IOD

Surface Segmentation Storage

1.2.840.10008.5.1.4.1.1.66.5

Surface Segmentation IOD

Tractography Results Storage

1.2.840.10008.5.1.4.1.1.66.6

Tractography Results IOD

Real World Value Mapping Storage

1.2.840.10008.5.1.4.1.1.67

Real World Value Mapping IOD

Surface Scan Mesh Storage

1.2.840.10008.5.1.4.1.1.68.1

Surface Scan Mesh IOD

Surface Scan Point Cloud Storage

1.2.840.10008.5.1.4.1.1.68.2

Surface Scan Point Cloud IOD

VL Endoscopic Image Storage

1.2.840.10008.5.1.4.1.1.77.1.1

VL Endoscopic Image IOD

Video Endoscopic Image Storage

1.2.840.10008.5.1.4.1.1.77.1.1.1

Video Endoscopic Image IOD

VL Microscopic Image Storage

1.2.840.10008.5.1.4.1.1.77.1.2

VL Microscopic Image IOD

Video Microscopic Image Storage

1.2.840.10008.5.1.4.1.1.77.1.2.1

Video Microscopic Image IOD

VL Slide-Coordinates Microscopic Image Storage

1.2.840.10008.5.1.4.1.1.77.1.3

VL Slide-Coordinates Microscopic Image IOD

VL Photographic Image Storage

1.2.840.10008.5.1.4.1.1.77.1.4

VL Photographic Image IOD

Video Photographic Image Storage

1.2.840.10008.5.1.4.1.1.77.1.4.1

Video Photographic Image IOD

Ophthalmic Photography 8 Bit Image Storage

1.2.840.10008.5.1.4.1.1.77.1.5.1

Ophthalmic Photography 8 Bit Image IOD

Ophthalmic Photography 16 Bit Image Storage

1.2.840.10008.5.1.4.1.1.77.1.5.2

Ophthalmic Photography 16 Bit Image IOD

Stereometric Relationship Storage

1.2.840.10008.5.1.4.1.1.77.1.5.3

Stereometric Relationship IOD

Ophthalmic Tomography Image Storage

1.2.840.10008.5.1.4.1.1.77.1.5.4

Ophthalmic Tomography Image IOD

Wide Field Ophthalmic Photography Stereographic Projection Image Storage

1.2.840.10008.5.1.4.1.1.77.1.5.5

Wide Field Ophthalmic Photography Stereographic Projection Image IOD

Wide Field Ophthalmic Photography 3D Coordinates Image Storage

1.2.840.10008.5.1.4.1.1.77.1.5.6

Wide Field Ophthalmic Photography 3D Coordinates Image IOD

Ophthalmic Optical Coherence Tomography En Face Image Storage

1.2.840.10008.5.1.4.1.1.77.1.5.7

Ophthalmic Optical Coherence Tomography En Face Image IOD

Ophthalmic Optical Coherence Tomography B-scan Volume Analysis Storage

1.2.840.10008.5.1.4.1.1.77.1.5.8

Ophthalmic Optical Coherence Tomography B-scan Volume Analysis IOD

VL Whole Slide Microscopy Image Storage

1.2.840.10008.5.1.4.1.1.77.1.6

VL Whole Slide Microscopy Image IOD

Dermoscopic Photography Image Storage

1.2.840.10008.5.1.4.1.1.77.1.7

Dermoscopic Photography Image IOD

Lensometry Measurements Storage

1.2.840.10008.5.1.4.1.1.78.1

Lensometry Measurements IOD

Autorefraction Measurements Storage

1.2.840.10008.5.1.4.1.1.78.2

Autorefraction Measurements IOD

Keratometry Measurements Storage

1.2.840.10008.5.1.4.1.1.78.3

Keratometry Measurements IOD

Subjective Refraction Measurements Storage

1.2.840.10008.5.1.4.1.1.78.4

Subjective Refraction Measurements IOD

Visual Acuity Measurements Storage

1.2.840.10008.5.1.4.1.1.78.5

Visual Acuity Measurements IOD

Spectacle Prescription Report Storage

1.2.840.10008.5.1.4.1.1.78.6

Spectacle Prescription Report IOD

Ophthalmic Axial Measurements Storage

1.2.840.10008.5.1.4.1.1.78.7

Ophthalmic Axial Measurements IOD

Intraocular Lens Calculations Storage

1.2.840.10008.5.1.4.1.1.78.8

Intraocular Lens Calculations IOD

Macular Grid Thickness and Volume Report

1.2.840.10008.5.1.4.1.1.79.1

Macular Grid Thickness and Volume Report IOD

Ophthalmic Visual Field Static Perimetry Measurements Storage

1.2.840.10008.5.1.4.1.1.80.1

Ophthalmic Visual Field Static Perimetry Measurements IOD

Ophthalmic Thickness Map Storage

1.2.840.10008.5.1.4.1.1.81.1

Ophthalmic Thickness Map IOD

Corneal Topography Map Storage

1.2.840.10008.5.1.4.1.1.82.1

Corneal Topography Map IOD

B.5.1.17

Basic Text SR Storage

1.2.840.10008.5.1.4.1.1.88.11

Basic Text SR IOD

Enhanced SR Storage

1.2.840.10008.5.1.4.1.1.88.22

Enhanced SR IOD

Comprehensive SR Storage

1.2.840.10008.5.1.4.1.1.88.33

Comprehensive SR IOD

Comprehensive 3D SR Storage

1.2.840.10008.5.1.4.1.1.88.34

Comprehensive 3D SR IOD

Extensible SR Storage

1.2.840.10008.5.1.4.1.1.88.35

Extensible SR IOD

Procedure Log Storage

1.2.840.10008.5.1.4.1.1.88.40

Procedure Log IOD

Mammography CAD SR Storage

1.2.840.10008.5.1.4.1.1.88.50

Mammography CAD SR IOD

Key Object Selection Document Storage

1.2.840.10008.5.1.4.1.1.88.59

Key Object Selection Document IOD

Chest CAD SR Storage

1.2.840.10008.5.1.4.1.1.88.65

Chest CAD SR IOD

X-Ray Radiation Dose SR Storage

1.2.840.10008.5.1.4.1.1.88.67

X-Ray Radiation Dose SR IOD

Radiopharmaceutical Radiation Dose SR Storage

1.2.840.10008.5.1.4.1.1.88.68

Radiopharmaceutical Radiation Dose SR IOD

Colon CAD SR Storage

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 IOD

Acquisition Context SR Storage

1.2.840.10008.5.​1.​4.​1.​1.​88.​71

Acquisition Context SR IOD

Simplified Adult Echo SR Storage

1.2.840.10008.5.​1.​4.​1.​1.​88.​72

Simplified Adult Echo SR IOD

Patient Radiation Dose SR Storage

1.2.840.10008.5.​1.​4.​1.​1.​88.​73

Patient Radiation Dose SR IOD

Planned Imaging Agent Administration SR Storage

1.2.840.10008.5.​1.​4.​1.​1.​88.​74

Planned Imaging Agent Administration SR IOD

Performed Imaging Agent Administration SR Storage

1.2.840.10008.5.​1.​4.​1.​1.​88.​75

Performed Imaging Agent Administration SR IOD

Enhanced X-Ray Radiation Dose SR Storage

1.2.840.10008.5.​1.​4.​1.​1.​88.​76

Enhanced X-Ray Radiation Dose SR IOD

Content Assessment Results Storage

1.2.840.10008.5.1.4.1.1.90.1

Content Assessment Results IOD

B.5.1.20

Microscopy Bulk Simple Annotations Storage

1.2.840.10008.5.1.4.1.1.91.1

Microscopy Bulk Simple Annotations IOD

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

Encapsulated STL Storage

1.2.840.10008.5.1.4.1.1.104.3

Encapsulated STL IOD

Encapsulated OBJ Storage

1.2.840.10008.5.1.4.1.1.104.4

Encapsulated OBJ IOD

Encapsulated MTL Storage

1.2.840.10008.5.1.4.1.1.104.5

Encapsulated MTL IOD

Positron Emission Tomography Image Storage

1.2.840.10008.5.1.4.1.1.128

Positron Emission Tomography Image IOD

Enhanced PET Image Storage

1.2.840.10008.5.1.4.1.1.130

Enhanced PET Image IOD

B.5.1.16

B.5.1.23

Legacy Converted Enhanced PET Image Storage

1.2.840.10008.5.1.4.1.1.128.1

Legacy Converted Enhanced PET Image IOD

B.5.1.23

Basic Structured Display Storage

1.2.840.10008.5.1.4.1.1.131

Basic Structured Display IOD

B.5.1.9

CT Performed Procedure Protocol Storage

1.2.840.10008.5.1.4.1.1.200.2

CT Performed Procedure Protocol IOD

B.5.1.21

XA Performed Procedure Protocol Storage

1.2.840.10008.5.1.4.1.1.200.8

XA Performed Procedure Protocol IOD

B.5.1.21

RT Image Storage

1.2.840.10008.5.1.4.1.1.481.1

RT Image IOD

RT Dose Storage

1.2.840.10008.5.1.4.1.1.481.2

RT Dose IOD

RT Structure Set Storage

1.2.840.10008.5.1.4.1.1.481.3

RT Structure Set IOD

RT Beams Treatment Record Storage

1.2.840.10008.5.1.4.1.1.481.4

RT Beams Treatment Record IOD

RT Plan Storage

1.2.840.10008.5.1.4.1.1.481.5

RT Plan IOD

RT Brachy Treatment Record Storage

1.2.840.10008.5.1.4.1.1.481.6

RT Brachy Treatment Record IOD

RT Treatment Summary Record Storage

1.2.840.10008.5.1.4.1.1.481.7

RT Treatment Summary Record IOD

RT Ion Plan Storage

1.2.840.10008.5.1.4.1.1.481.8

RT Ion Plan IOD

RT Ion Beams Treatment Record Storage

1.2.840.10008.5.1.4.1.1.481.9

RT Ion Beams Treatment Record IOD

RT Physician Intent Storage

1.2.840.10008.5.1.4.1.1.481.10

RT Physician Intent IOD

RT Segment Annotation Storage

1.2.840.10008.5.1.4.1.1.481.11

RT Segment Annotation IOD

RT Radiation Set Storage

1.2.840.10008.5.1.4.1.1.481.12

RT Radiation Set IOD

C-Arm Photon-Electron Radiation Storage

1.2.840.10008.5.1.4.1.1.481.13

C-Arm Photon-Electron Radiation IOD

Tomotherapeutic Radiation Storage

1.2.840.10008.5.1.4.1.1.481.14

Tomotherapeutic Radiation IOD

Robotic-Arm Radiation Storage

1.2.840.10008.5.1.4.1.1.481.15

Robotic-Arm Radiation IOD

RT Radiation Record Set Storage

1.2.840.10008.5.1.4.1.1.481.16

RT Radiation Record Set IOD

RT Radiation Salvage Record Storage

1.2.840.10008.5.1.4.1.1.481.17

RT Radiation Salvage Record IOD

Tomotherapeutic Radiation Record Storage

1.2.840.10008.5.1.4.1.1.481.18

Tomotherapeutic Radiation Record IOD

C-Arm Photon-Electron Radiation Record Storage

1.2.840.10008.5.1.4.1.1.481.19

C-Arm Photon-Electron Radiation Record IOD

Robotic Radiation Record Storage

1.2.840.10008.5.1.4.1.1.481.20

Robotic-Arm Radiation Record IOD

RT Radiation Set Delivery Instruction Storage

1.2.840.10008.5.1.4.1.1.481.21

RT Radiation Set Delivery Instruction IOD

RT Treatment Preparation Storage

1.2.840.10008.5.1.4.1.1.481.22

RT Treatment Preparation IOD

RT Beams Delivery Instruction Storage

1.2.840.10008.5.1.4.34.7

RT Beams Delivery Instruction IOD

RT Brachy Application Setup Delivery Instruction Storage

1.2.840.10008.5.1.4.34.10

RT Brachy Application Setup Delivery Instruction IOD


Note

The Generic Implant Template Storage, Implant Assembly Template Storage, and Implant Template Group Storage SOP Classes were formerly specified in this table, incorrectly since they do not use the Patient / Study / Series / Instance information model. Those have been consolidated into the Non-Patient Object Storage Service Class (see Annex GG).

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 in the same role.

Note

  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 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 X-Ray Image Storage SOP Classes

The Digital Mammography X-Ray 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 X-Ray 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 X-Ray Image Storage - For Processing SOP Class shall also support the Digital Mammography X-Ray Image Storage - For Presentation SOP Class in the same role.

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 in the same role.

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:

  • Basic Text SR

  • Extensible SR, Enhanced SR, and SOP Classes for which it is the Related General SOP Class

  • Comprehensive 3D SR, Comprehensive SR, and SOP Classes for which they are the Related General SOP Classes

  • Mammography CAD SR

  • Chest CAD SR

  • Procedure Log

  • X-Ray Radiation Dose SR

  • Radiopharmaceutical Radiation Dose SR

  • Patient Radiation Dose SR

  • Enhanced X-Ray Radiation Dose SR Storage

  • Spectacle Prescription Report

  • Colon CAD SR

  • Macular Grid Thickness and Volume Report

  • Implantation Plan SR Document

  • Acquisition Context SR

  • Simplified Adult Echo SR

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

B.5.1.6 Enhanced MR Image Storage and Legacy Converted Enhanced MR Image Storage SOP Class

An SCP of the Enhanced MR Image Storage or Legacy Converted Enhanced MR Image Storage SOP Class shall also support the Grayscale Softcopy Presentation State Storage SOP Class as an SCP.

Note

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

B.5.1.7 Enhanced CT Image Storage and Legacy Converted Enhanced CT Image Storage SOP Class

An SCP of the Enhanced CT Image Storage or Legacy Converted Enhanced CT Image Storage SOP Class shall also support the Grayscale Softcopy Presentation State Storage SOP Class as an SCP.

Note

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

B.5.1.8 Enhanced MR Color Image Storage SOP Class

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

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 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.

Note

  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 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

See Annex GG.

Note

The requirements of this section have been consolidated into the Non-Patient Object Storage Service Class (see Section GG.6.3).

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 Section 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 Section 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 in the same role.

Note

  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 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.14 Ophthalmic Thickness Map Storage SOP Class

The Ophthalmic Thickness Map SOP Class encodes a topographic representation of the thickness/height measurements of the posterior eye.

For a device that is both a SCU and a SCP of the Ophthalmic Thickness Map Storage SOP Class, in addition to the behavior for the Storage Service Class specified in Section B.2.2, the following additional requirements are specified for Ophthalmic Thickness Map 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.15 Enhanced PET Image Storage and Legacy Converted Enhanced PET Image Storage SOP Class

An SCP of the Enhanced PET Image Storage or Legacy Converted Enhanced PET Image Storage SOP Class shall also support the Grayscale Softcopy Presentation State Storage SOP Class as an SCP.

Note

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

B.5.1.16 Enhanced PET Image Storage SOP Classes

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

Note

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

B.5.1.17 Corneal Topography Map Storage SOP Class

The Corneal Topography Map SOP Class encodes a topographic representation of the curvature and/or elevation measurements of corneal anterior and posterior surfaces (e.g., maps that display corneal curvatures, corneal elevations, and corneal power, etc.).

For a device that is both a SCU and a SCP of the Corneal Topography Map Storage SOP Class, in addition to the behavior for the Storage Service Class specified in Section B.2.2, the following additional requirements are specified for Corneal Topography Map 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.18 Breast Projection X-Ray Image Storage SOP Classes

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

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

An SCU or SCP of the Breast Projection X-Ray Image Storage - For Processing SOP Class shall also support the Breast Projection X-Ray Image Storage - For Presentation SOP Class in the same role.

B.5.1.19 Planar MPR Volumetric Presentation State Storage SOP Classes

The requirements of Section FF.2.1.1 apply to the following SOP Classes:

  • Grayscale Planar MPR Volumetric Presentation State Storage

  • Compositing Planar MPR Volumetric Presentation State Storage

The Grayscale Planar MPR Volumetric Presentation State Storage SOP Class shall use the Planar MPR Volumetric Presentation State IOD with an Enumerated Value of MONOCHROME for Pixel Presentation (0008,9205) and shall have only a single item in the Volumetric Presentation State Input Sequence (0070,1201).

The Compositing Planar MPR Volumetric Presentation State Storage SOP Class shall use the Planar MPR Volumetric Presentation State IOD with an Enumerated Value of TRUE COLOR for Pixel Presentation (0008,9205).

B.5.1.20 Content Assessment Results Storage SOP Classes

An SCU of the Content Assessment Results S