DICOM PS3.4 2019c - Service Class Specifications

II.6 SOP Class Definitions (Current)
Prev | II Protocol Approval Query/Retrieve Service Classes |

## II.6 SOP Class Definitions

### II.6.1 Protocol Approval Information Model

#### II.6.1.1 E/R Models

The Protocol Approval 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 Protocol Approval Instance.

Figure II.6-1. Protocol Approval Information Model E/R Diagram

#### II.6.1.2 Protocol Approval Attributes

Table II.6-1 defines the Attributes of the Protocol Approval Information Model.

### Note

Since protocol approvals are generally relevant only in the context of the protocol instance being approved, many searches will be looking for approvals that list a particular protocol instance in the Approval Subject Sequence (0044,0109).

Table II.6-1. Attributes for the Protocol Approval 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 |
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.
Protocol Approval
Approval Subject Sequence | (0044,0109) | R | 1 |
>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.
Approval Sequence | (0044,0100) | R | 1 |
>Assertion Code Sequence | (0044,0101) | R | 1 |
>>Code Value | (0008,0100) | R | 1 | This Attribute shall be retrieved with Single Value or Universal matching.
>>Coding Scheme Designator | (0008,0102) | R | 1 | This Attribute shall be retrieved with Single Value or Universal matching.
>>Code Meaning | (0008,0104) | - | 1 |
>Assertion UID | (0044,0102) | - | 1 |
>Asserter Identification Sequence | (0044,0103) | R | 1 |
>>Observer Type | (0040,A084) | - | 1 |
>>Person Name | (0040,A123) | R | 1 |
>>Person Idenfication Code Sequence | (0040,1101) | R | 1 |
>>>Code Value | (0008,0100) | R | 1 | This Attribute shall be retrieved with Single Value or Universal matching.
>>>Coding Scheme Designator | (0008,0102) | R | 1 | This Attribute shall be retrieved with Single Value or Universal matching.
>>>Code Meaning | (0008,0104) | - | 1 |
>>Organizational Role Code Sequence | (0044,010A) | R | 2 |
>>>Code Value | (0008,0100) | R | 1 | This Attribute shall be retrieved with Single Value or Universal matching.
>>>Coding Scheme Designator | (0008,0102) | R | 1 | This Attribute shall be retrieved with Single Value or Universal matching.
>>>Code Meaning | (0008,0104) | - | 1 |
>>Station Name | (0008,1010) | - | 3 |
>>Device UID | (0018,1002) | - | 3 |
>>Manufacturer | (0008,0070) | - | 3 |
>>Manufacturer's Model Name | (0008,1090) | - | 3 |
>>Station AE Title | (0008,0055) | - | 3 |
>>Institution Name | (0008,0080) | R | 1 |
>>Institution Code Sequence | (0008,0082) | R | 1 |
>>>Code Value | (0008,0100) | R | 1 | This Attribute shall be retrieved with Single Value or Universal matching.
>>>Coding Scheme Designator | (0008,0102) | R | 1 | This Attribute shall be retrieved with Single Value or Universal matching.
>>>Code Meaning | (0008,0104) | - | 1 |
>>Institutional Department Name | (0008,1040) | U | 2 |
>>Institutional Department Type Code Sequence | (0008,1041) | U | 3
>>>Code Value | (0008,0100) | R | 1 | This Attribute shall be retrieved with Single Value or Universal matching.
>>>Coding Scheme Designator | (0008,0102) | R | 1 | This Attribute shall be retrieved with Single Value or Universal matching.
>>>Code Meaning | (0008,0104) | - | 1 |
>Assertion DateTime | (0044,0104) | R | 1 | This Attribute shall be retrieved with Single Value or Range Matching.
>Assertion Expiration DateTime | (0044,0105) | R | 2 | This Attribute shall be retrieved with Single Value or Range Matching.
>Assertion Comments | (0044,0106) | - | 2 |
>Related Assertion Sequence | (0044,0107) | U | 1 |
>>Referenced Assertion UID | (0044,0108) | U | 1 |
Enhanced General Equipment
Manufacturer | (0008,0070) | - | 1 |
Manufacturer's Model Name | (0008,1090) | - | 2 |
Software Versions | (0018,1020) | - | 2 |

### Note

The Enhanced General Equipment Module describes the equipment that created the Protocol Approval instance, not the equipment on which a referenced Protocol will be performed.

#### II.6.1.3 Conformance Requirements

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

##### II.6.1.3.1 SCU Conformance

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

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

An implementation that conforms to the Protocol Approval 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 Protocol Approval 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.

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

An implementation that conforms to the Protocol Approval Information Model - MOVE SOP Class as an SCU shall support transfers against the Protocol Approval 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 II.4.2).

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

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

##### II.6.1.3.2 SCP Conformance

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

An implementation that conforms to the Protocol Approval Information Model - FIND SOP Class as an SCP shall support queries against the Protocol Approval 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 Referenced SOP Instance UID (0008,1155) in the Approval Subject Sequence (0044,0109) would be useful to index since querying for approvals of a specific Protocol instance will be very common.

An implementation that conforms to the Protocol Approval 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.

- how it makes use of Specific Character Set (0008,0005) when interpreting queries, performing matching and encoding responses.

- any behaviors that involve not returning matching instances (e.g. not returning an older approval instance that has been superceded/overridden by a newer approval instance).

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

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

An implementation that conforms to the Protocol Approval 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.

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

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

#### II.6.1.4 SOP Classes

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

Table II.6.1.4-1. Protocol Approval SOP Classes

SOP Class Name | SOP Class UID
--- | ---
Protocol Approval Information Model - FIND | 1.2.840.10008.5.1.4.1.1.200.4
Protocol Approval Information Model - MOVE | 1.2.840.10008.5.1.4.1.1.200.5
Protocol Approval Information Model - GET | 1.2.840.10008.5.1.4.1.1.200.6

Prev | Up |
II.5 Association Negotiation | Home |

DICOM PS3.4 2019c - Service Class Specifications