DICOM PS3.4 2021c - Service Class Specifications

HH.6 SOP Class Definitions (Current)
Prev | HH Defined Procedure Protocol Query/Retrieve Service Classes | Next

## HH.6 SOP Class Definitions

### HH.6.1 Defined Procedure Protocol Information Model

#### HH.6.1.1 E/R Models

The Defined Procedure Protocol Information Model consists of a single entity. In response to a given C-FIND request, the SCP shall send one C-FIND response per matching Defined Procedure Protocol Instance.

Figure HH.6-1. Defined Procedure Protocol Information Model E/R Diagram

#### HH.6.1.2 Defined Procedure Protocol Attributes

Table HH.6-1 defines the Attributes of the Defined Procedure Protocol Information Model.

Table HH.6-1. Attributes for the Defined Procedure Protocol Information Model

Description / Module | Tag | Matching Key Type | Return Key Type | Remark / Matching Type
--- | --- | --- | --- | ---
SOP Common
Specific Character Set | (0008,0005) | - | 1C | This Attribute is required if expanded or replacement character sets are used. See Section C.2.2.2 and Section C.4.1.1.
SOP Class UID | (0008,0016) | R | 1 |
SOP Instance UID | (0008,0018) | U | 1 |
Protocol Context
Custodial Organization Sequence | (0040,A07C) | R | 2 |
>Institution Name | (0008,0080) | R | 2 |
>Institution Code Sequence | (0008,0082) | R | 2 | This Attribute shall be retrieved with Sequence or Universal matching.
>>Include Table 8-1a “Enhanced SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning”
Responsible Group Code Sequence | (0008,0220) | R | 2 | This Attribute shall be retrieved with Sequence or Universal matching.
>Include Table 8-1a “Enhanced SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning”
Protocol Name | (0018,1030) | R | 1 | Shall be retrieved with Single Value, Wild Card, or Universal Matching.
Potential Scheduled Protocol Code Sequence | (0018,9906) | R | 1 | This Attribute shall be retrieved with Sequence or Universal matching.
>Include Table 8-1a “Enhanced SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning”
Potential Requested Procedure Code Sequence | (0018,9907) | R | 1 | This Attribute shall be retrieved with Sequence or Universal matching.
>Include Table 8-1a “Enhanced SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning”
Potential Reasons for Procedure | (0018,9908) | - | 2 |
Potential Reasons for Procedure Code Sequence | (0018,9909) | R | 2 | This Attribute shall be retrieved with Sequence or Universal matching.
>Include Table 8-1a “Enhanced SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning”
Potential Diagnostic Tasks | (0018,990A) | - | 2 |
Predecessor Protocol Sequence | (0018,990E) | R | 2 |
>Referenced SOP Class UID | (0008,1150) | R | 1 | Shall be retrieved with List of UID Matching.
>Referenced SOP Instance UID | (0008,1155) | R | 1 | Shall be retrieved with List of UID Matching.
Content Creator's Name | (0070,0084) | R | 1 | Shall be retrieved with Single Value, Wild Card, or Universal Matching.
Instance Creation Date | (0008,0012) | R | 1 | Shall be retrieved with Single Value or Range Matching. See Instance Creation Time for further details.
Instance Creation Time | (0008,0013) | R | 1 | Shall be retrieved with Single Value or Range Matching. If both Instance Creation Date and Instance Creation Time are specified for Range Matching, they are to be treated as as if they were a single DateTime Attribute e.g.,the date range July 5 to July 7 and the time range 10am to 6pm specifies the time period starting on July 5, 10am until July 7, 6pm.
Clinical Trial Context
Clinical Trial Sponsor Name | (0012,0010) | R | 1 | Shall be retrieved with Single Value, Wild Card, or Universal Matching.
Clinical Trial Protocol ID | (0012,0020) | R | 1 | Shall be retrieved with Single Value, Wild Card, or Universal Matching.
Equipment Specification
Equipment Modality | (0008,0221) | R | 1 |
Model Specification Sequence | (0018,9912) | R | 2 |
>Manufacturer | (0008,0070) | R | 1 | Shall be retrieved with Single Value, Wild Card, or Universal Matching.
>Manufacturer's Related Model Group | (0008,0222) | R | 2 | Shall be retrieved with Single Value, Wild Card, or Universal Matching.
>Manufacturer's Model Name | (0008,1090) | R | 2 | Shall be retrieved with Single Value, Wild Card, or Universal Matching.
>Software Versions | (0018,1020) | R | 2 | Shall be retrieved with Single Value, Wild Card, or Universal Matching.
>Device Serial Number | (0018,1000) | - | 2 |
Patient Positioning
Anatomic Region Sequence | (0008,2218) | R | 2 | This Attribute shall be retrieved with Sequence or Universal matching.
>Include Table 8-1a “Enhanced SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning”
Primary Anatomic Structure Sequence | (0008,2228) | R | 2 | This Attribute shall be retrieved with Sequence or Universal matching.
>Include Table 8-1a “Enhanced SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning”

#### HH.6.1.3 Conformance Requirements

An implementation may conform to one or more of the Defined Procedure Protocol Query/Retrieve SOP Classes as an SCU or SCP. The Conformance Statement shall be in the format defined in PS3.2.

##### HH.6.1.3.1 SCU Conformance

###### HH.6.1.3.1.1 C-FIND SCU Conformance

An implementation that conforms to the Defined Procedure Protocol Information Model - FIND SOP Class shall support queries against the Defined Procedure Protocol Information Model using the C-FIND SCU Behavior described for the Basic Worklist Management Service Class (see Section K.4.1.2 and Section HH.4.1).

An implementation that conforms to the Defined Procedure Protocol Information Model - FIND SOP Class as an SCU shall state in its Conformance Statement whether it requests Type 3 Return Key Attributes, and shall list these Optional Return Key Attributes.

An implementation that conforms to the Defined Procedure Protocol Information Model - FIND SOP Class as an SCU shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when encoding queries and interpreting responses.

###### HH.6.1.3.1.2 C-MOVE SCU Conformance

An implementation that conforms to the Defined Procedure Protocol Information Model - MOVE SOP Class as an SCU shall support transfers against the Defined Procedure Protocol Information Model, using the C-MOVE SCU baseline behavior described for the Query/Retrieve Service Class (see Section C.4.2.2.1 and Section HH.4.2).

###### HH.6.1.3.1.3 C-GET SCU Conformance

An implementation that conforms to the Defined Procedure Protocol Information Model - GET SOP Class as an SCU shall support transfers against the Defined Procedure Protocol Information Model, using the C-GET SCU baseline behavior described for the Query/Retrieve Service Class (see Section C.4.3.2).

##### HH.6.1.3.2 SCP Conformance

###### HH.6.1.3.2.1 C-FIND SCP Conformance

An implementation that conforms to the Defined Procedure Protocol Information Model - FIND SOP Class as an SCP shall support queries against the Defined Procedure Protocol Information Model, using the C-FIND SCP Behavior described for the Basic Worklist Management Service Class (see Section K.4.1.3).

### Note

The contents of the Model Specification Sequence (0018,9912) would be useful to index for systems that support query or selection of appropriate Protocols for specific systems.

An implementation that conforms to the Defined Procedure Protocol Information Model - FIND SOP Class as an SCP shall state in its Conformance Statement whether it supports Type 3 Return Key Attributes, and shall list these Optional Return Key Attributes.

An implementation that conforms to the Defined Procedure Protocol Information Model - FIND SOP Class as an SCP shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when interpreting queries, performing matching and encoding responses.

###### HH.6.1.3.2.2 C-MOVE SCP Conformance

An implementation that conforms to the Defined Procedure Protocol Information Model - MOVE SOP Class as an SCP shall support transfers against the Defined Procedure Protocol Information Model, using the C-MOVE SCP baseline behavior described for the Query/Retrieve Service Class (see Section C.4.2.3.1).

### Note

It is expected that a device that does not match the contents of the Model Specification Sequence (0018,9912) will not execute the Protocol.

An implementation that conforms to the Defined Procedure Protocol Information Model - MOVE SOP Class as an SCP, which generates transfers using the C-MOVE operation, shall state in its Conformance Statement appropriate Storage Service Class, under which it shall support the C-STORE sub-operations generated by the C-MOVE.

###### HH.6.1.3.2.3 C-GET SCP Conformance

An implementation that conforms to the Defined Procedure Protocol Information Model - GET SOP Class as an SCP shall support retrievals against the Defined Procedure Protocol Information Model using the C-GET SCP baseline behavior described for the Query/Retrieve Service Class in Section C.4.3.3.

#### HH.6.1.4 SOP Classes

The SOP Classes of the Defined Procedure Protocol Query/Retrieve Service Class identify the Information Models, and the DIMSE-C operations supported.

Table HH.6.1.4-1. Defined Procedure Protocol SOP Classes

SOP Class Name | SOP Class UID
--- | ---
Defined Procedure Protocol Information Model - FIND | 1.2.840.10008.5.1.4.20.1
Defined Procedure Protocol Information Model - MOVE | 1.2.840.10008.5.1.4.20.2
Defined Procedure Protocol Information Model - GET | 1.2.840.10008.5.1.4.20.3

Prev | Up | Next
HH.5 Association Negotiation | Home | II Protocol Approval Query/Retrieve Service Classes

DICOM PS3.4 2021c - Service Class Specifications