DICOM PS3.4 2024e - Service Class Specifications

U.6 SOP Class Definitions

U.6.1 Hanging Protocol Information Model

U.6.1.1 E/R Model

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

Hanging Protocol Information Model E-R Diagram

Figure U.6-1. Hanging Protocol Information Model E-R Diagram


U.6.1.2 Hanging Protocol Attributes

Table U.6-1 defines the Attributes of the Hanging Protocol Information Model:

Table U.6-1. Attributes for the Hanging 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

Hanging Protocol Definition

Hanging Protocol Name

(0072,0002)

R

1

This Attribute shall be retrieved with Single Value Matching, Wild Card Matching or Universal Matching.

Hanging Protocol Description

(0072,0004)

-

1

Hanging Protocol Level

(0072,0006)

R

1

This Attribute shall be retrieved with Single Value Matching or Universal Matching.

Hanging Protocol Creator

(0072,0008)

-

1

Hanging Protocol Creation DateTime

(0072,000A)

-

1

Hanging Protocol Definition Sequence

(0072,000C)

R

1

This Attribute shall be retrieved with Sequence Matching or Universal Matching.

>Modality

(0008,0060)

R

2

This Attribute shall be retrieved with Single Value Matching or Universal Matching.

>Anatomic Region Sequence

(0008,2218)

R

2

This Attribute shall be retrieved with Sequence Matching or Universal Matching.

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

>Laterality

(0020,0060)

R

2

This Attribute shall be retrieved with Single Value Matching or Universal Matching.

>Procedure Code Sequence

(0008,1032)

R

2

This Attribute shall be retrieved with Sequence Matching or Universal Matching.

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

>Reason for Requested Procedure Code Sequence

(0040,100A)

R

2

This Attribute shall be retrieved with Sequence Matching or Universal Matching.

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

Number of Priors Referenced

(0072,0014)

R

1

This Attribute shall be retrieved with Single Value Matching or Universal Matching.

Hanging Protocol User Identification Code Sequence

(0072,000E)

R

2

This Attribute shall be retrieved with Sequence Matching or Universal Matching.

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

Hanging Protocol User Group Name

(0072,0010)

R

3

Hanging Protocol Environment

Number of Screens

(0072,0100)

R

2

Nominal Screen Definition Sequence

(0072,0102)

-

2

>Number of Vertical Pixels

(0072,0104)

-

1

>Number of Horizontal Pixels

(0072,0106)

-

1

>Display Environment Spatial Position

(0072,0108)

-

1

>Screen Minimum Grayscale Bit Depth

(0072,010A)

-

1C

Required if Screen Minimum Color Bit Depth (0072,010C) is not present.

>Screen Minimum Color Bit Depth

(0072,010C)

-

1C

Required if Screen Minimum Grayscale Bit Depth (0072,010A) is not present.

>Application Maximum Repaint Time

(0072,010E)

-

3


U.6.1.3 Conformance Requirements

An implementation may conform to one of the Hanging Protocol Information Model SOP Classes as an SCU, SCP or both. The Conformance Statement shall be in the format defined in PS3.2.

U.6.1.3.1 SCU Conformance
U.6.1.3.1.1 C-FIND SCU Conformance

An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes shall support queries against the Hanging 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 U.4.1).

An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes 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 one of the Hanging Protocol Information Model SOP Classes 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.

U.6.1.3.1.2 C-MOVE SCU Conformance

An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes as an SCU shall support transfers against the Hanging 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 U.4.2).

U.6.1.3.1.3 C-GET SCU Conformance

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

U.6.1.3.2 SCP Conformance
U.6.1.3.2.1 C-FIND SCP Conformance

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

An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes 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 one of the Hanging Protocol Information Model SOP Classes 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.

U.6.1.3.2.2 C-MOVE SCP Conformance

An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes as an SCP shall support transfers against the Hanging Protocol 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 one of the Hanging Protocol Information Model SOP Classes as an SCP, which generates transfers using the C-MOVE operation, shall state in its Conformance Statement the Hanging Protocol Storage Service Class SOP Class under which it shall support the C-STORE sub-operations generated by the C-MOVE.

U.6.1.3.2.3 C-GET SCP Conformance

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

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

U.6.1.4 SOP Classes

The SOP Classes of the Hanging Protocol Information Model in the Hanging Protocol Query/Retrieve Service Class identify the Hanging Protocol Information Model, and the DIMSE-C operations supported. The following Standard SOP Classes are identified:

Table U.6.1.4-1. Hanging Protocol SOP Classes

SOP Class Name

SOP Class UID

Hanging Protocol Information Model - FIND

1.2.840.10008.5.1.4.38.2

Hanging Protocol Information Model - MOVE

1.2.840.10008.5.1.4.38.3

Hanging Protocol Information Model - GET

1.2.840.10008.5.1.4.38.4


DICOM PS3.4 2024e - Service Class Specifications