DICOM PS3.4 2024d - Service Class Specifications
C.6 SOP Class Definitions (Current)
Prev  C Query/Retrieve Service Class (Normative)  Next
PS3.4 > Query/Retrieve Service Class (Normative) > SOP Class Definitions

C.6 SOP Class Definitions

C.6.1 Patient Root SOP Class Group

In the Patient Root Query/Retrieve Information Model, the information is arranged into four levels that correspond to one of the four values in element (0008,0052) shown in Table C.6.1-1.

Table C.6.1-1. Query/Retrieve Level Values for Patient Root

Query/Retrieve Level

Value in (0008,0052)

Patient Information

PATIENT

Study Information

STUDY

Series Information

SERIES

Composite Object Instance Information

IMAGE

Note

The use of the word "Images" rather than "Composite Object Instances" is historical to allow backward compatibility with previous editions of the standard. It should not be taken to mean that Composite Object Instances of other than image type are not included at the level indicated by the value IMAGE.

C.6.1.1 Patient Root Query/Retrieve Information Model

C.6.1.1.1 E/R Model

The Patient Root Query/Retrieve Information Model may be represented by the entity relationship diagram shown in Figure C.6-1.

Patient Root Query/Retrieve Information Model E-R Diagram

Figure C.6-1. Patient Root Query/Retrieve Information Model E-R Diagram


C.6.1.1.2 Patient Level

Table C.6-1 defines the Attributes at the Patient Query/Retrieve level of the Patient Root Query/Retrieve Information Model.

Note

  1. A description of the Attributes of this Information Model is contained in Section C.3 of this Part.

  2. Although the Patient ID may not be globally unique, the Study Instance UID is globally unique ensuring that no two studies may be misidentified. The scope of uniqueness of the Patient ID may be specified using the Issuer of Patient ID (0010,0021).

  3. Previously, Other Patient IDs (0010,1000) was included in this table. This Attribute have been retired. See PS3.4 2017a.

Table C.6-1. Patient Level Attributes for the Patient Root Query/Retrieve Information Model

Attribute Name

Tag

Type

Patient's Name

(0010,0010)

R

Patient ID

(0010,0020)

U

Issuer of Patient ID

(0010,0021)

O

Referenced Patient Sequence

(0008,1120)

O

>Referenced SOP Class UID

(0008,1150)

O

>Referenced SOP Instance UID

(0008,1155)

O

Patient's Birth Date

(0010,0030)

O

Patient's Birth Time

(0010,0032)

O

Patient's Sex

(0010,0040)

O

Other Patient IDs Sequence

(0010,1002)

O

Other Patient Names

(0010,1001)

O

Ethnic Group

(0010,2160)

O

Patient Comments

(0010,4000)

O

Number of Patient Related Studies

(0020,1200)

O

Number of Patient Related Series

(0020,1202)

O

Number of Patient Related Instances

(0020,1204)

O

All other Attributes at Patient Level

O

C.6.1.1.3 Study Level

Table C.6-2 defines the keys at the Study Information level of the Patient Root Query/Retrieve Information Model.

Note

  1. A description of the Attributes of this Information Model is contained in Section C.3 of this Part.

  2. Although the Patient ID may not be globally unique, the Study Instance UID is globally unique ensuring that no two studies may be misidentified. The scope of uniqueness of the Patient ID may be specified using the Issuer of Patient ID (0010,0021).

Table C.6-2a. Enhanced Code Value Keys Macro with Optional Keys

Attribute Name

Tag

Requirement Type

Include Table C.6-2b “Basic Code Value Keys Macro with Optional Keys”

Equivalent Code Sequence

(0008,0121)

O

>Include Table C.6-2b “Basic Code Value Keys Macro with Optional Keys”


Table C.6-2b. Basic Code Value Keys Macro with Optional Keys

Attribute Name

Tag

Requirement Type

Code Value

(0008,0100)

OC - May be present only 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

Coding Scheme Version

(0008,0103)

O

Code Meaning

(0008,0104)

O

Long Code Value

(0008,0119)

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

URN Code Value

(0008,0120)

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

Context Identifier

(0008,010F)

O

Context UID

(0008,0117)

O

Mapping Resource

(0008,0105)

O

Mapping Resource UID

(0008,0118)

O

Context Group Version

(0008,0106)

O

Context Group Extension Flag

(0008,010B)

O

Context Group Local Version

(0008,0107)

O

Context Group Extension Creator UID

(0008,010D)

O

Table C.6-2. Study Level Keys for the Patient Root Query/Retrieve Information Model

Attribute Name

Tag

Type

Study Date

(0008,0020)

R

Study Time

(0008,0030)

R

Accession Number

(0008,0050)

R

Study ID

(0020,0010)

R

Study Instance UID

(0020,000D)

U

Modalities in Study

(0008,0061)

O

SOP Classes in Study

(0008,0062)

O

Anatomic Regions in Study Code Sequence

(0008,0063)

O

>Include Table C.6-2a “Enhanced Code Value Keys Macro with Optional Keys”

Referring Physician's Name

(0008,0090)

O

Study Description

(0008,1030)

O

Procedure Code Sequence

(0008,1032)

O

>Include Table C.6-2a “Enhanced Code Value Keys Macro with Optional Keys”

Name of Physician(s) Reading Study

(0008,1060)

O

Admitting Diagnoses Description

(0008,1080)

O

Referenced Study Sequence

(0008,1110)

O

>Referenced SOP Class UID

(0008,1150)

O

>Referenced SOP Instance UID

(0008,1155)

O

Patient's Age

(0010,1010)

O

Patient's Size

(0010,1020)

O

Patient's Weight

(0010,1030)

O

Occupation

(0010,2180)

O

Additional Patient History

(0010,21B0)

O

Other Study Numbers

(0020,1070)

O

Number of Study Related Series

(0020,1206)

O

Number of Study Related Instances

(0020,1208)

O

Study Update DateTime

(0008,041F)

O

All other Attributes at Study Level

O

C.6.1.1.4 Series Level

Table C.6-3 defines the keys at the Series Information level of the Patient Root Query/Retrieve Information Model.

Table C.6-3. Series Level Attributes for the Patient Root Query/Retrieve Information Model

Attribute Name

Tag

Type

Modality

(0008,0060)

R

Series Number

(0020,0011)

R

Series Instance UID

(0020,000E)

U

Number of Series Related Instances

(0020,1209)

O

All other Attributes at Series Level

O

Note

The Attribute Number of Series Related Instances is an optional key. It is, however recognized as a broadly needed key and return Attribute, which SCPs are strongly encouraged to support.

C.6.1.1.5 Composite Object Instance Level

Table C.6-4 defines the keys at the Composite Object Instance Information level of the Patient Root Query/Retrieve Information Model.

Table C.6-4. Composite Object Instance Level Keys for the Patient Root Query/Retrieve Information Model

Attribute Name

Tag

Type

Instance Number

(0020,0013)

R

SOP Instance UID

(0008,0018)

U

SOP Class UID

(0008,0016)

O

Available Transfer Syntax UID

(0008,3002)

O

Alternate Representation Sequence

(0008,3001)

O

>Series Instance UID

(0020,000E)

O

>SOP Class UID

(0008,1150)

O

>SOP Instance UID

(0008,1155)

O

>Purpose of Reference Code Sequence

(0040,A170)

O

>>Include Table C.6-2a “Enhanced Code Value Keys Macro with Optional Keys”

Related General SOP Class UID

(0008,001A)

O

Concept Name Code Sequence

(0040,A043)

O

>Include Table C.6-2a “Enhanced Code Value Keys Macro with Optional Keys”

Content Template Sequence

(0040,A504)

O

>Template Identifier

(0040,DB00)

O

>Mapping Resource

(0008,0105)

O

Container Identifier

(0040,0512)

O

Specimen Description Sequence

(0040,0560)

O

>Specimen Identifier

(0040,0551)

O

>Specimen UID

(0040,0554)

O

All other Attributes at Composite Object Instance Level

O

Note

  1. SOP Class UID (0008,0016) is an optional key, but it is strongly recommended that it always be returned by all SCPs, if matching is requested.

  2. The Concept Name Code Sequence (0040,A043) and Content Template Sequence (0040,A504) are optional keys that are useful for identifying instances of various Structured Reporting Storage SOP Classes. It is strongly recommended that these keys be supported by the SCP for query against such instances.

C.6.1.1.5.1 Alternate Representation Sequence

The Alternate Representation Sequence (0008,3001) encodes a reference to an alternate encoding of the composite image identified in the Query response item. This alternate encoding may utilize a different SOP Class or have different image quality characteristics, but it shall be the same image.

Note

The Alternate Representation Sequence (0008,3001) allows the query response about an original image to reference a lossy compressed version, and vice versa.

An image may be lossy compressed, e.g., for long-term archive purposes, and its SOP Instance UID changed. An application processing a SOP Instance that references the original image UID, e.g., a Structured Report, may query the C-FIND SCP for the image. The SCP returns a reference to an accessible version of the image even if the original SOP Instance is no longer available.

The Alternate Representation Sequence (0008,3001), if present in a Query Request Identifier, shall be zero-length, or shall contain a single zero-length Item. That is, only Universal Matching is defined for this Attribute.

The Alternate Representation Sequence (0008,3001), if present in the Query Response Identifier, may include zero or more Items. Each Alternate Representation Sequence Item in the Query Response Identifier shall include

  • the Series Instance UID (0020,000E) if the alternately encoded image is in a different Series.

  • the SOP Class UID (0008,0016) and SOP Instance UID (0008,0018) of the alternately encoded image.

  • the Purpose of Reference Code Sequence (0040,A170), which shall describe the nature of the alternate encoding of the image. The Purpose of Reference Code Sequence (0040,A170) shall include only one Item. The Baseline Context Group for this Code Sequence is CID 7205.

C.6.1.1.5.2 Available SOP Transfer Syntax UID

The Available Transfer Syntax UID (0008,3002) describes one or more Transfer Syntaxes that the SCP can assure will be supported for retrieval of the SOP Instance. This may, but is not required to, include the Transfer Syntax in which the SCP has stored the instance. For all Transfer Syntaxes listed, no loss shall be involved in transcoding from whatever is stored.

The Attribute is multi-valued, and if more than one value is present, then the SCU may interpret those Transfer Syntaxes listed earlier as being preferred by the SCP over those listed later. E.g., the order might reflect the amount of effort required to convert from the stored form, and the first listed might be the stored form.

There is no requirement to include every Transfer Syntax in which the instance may be retrieved without loss. E.g., the Default Transfer Syntax as specified in Section 10.1 in PS3.5 , if it is applicable, might be omitted if it is not the Transfer Syntax in which the instance happens to be stored.

Note

The value of this Attribute may be useful, for example, to determine if the the instance is stored in a lossy Transfer Syntax that is not supported by the SCU, and for which decompression or conversion into a different compressed form would involve loss and be inappropriate, and require use of an Alternate Representation.

C.6.1.1.6 Scope of the C-GET and C-MOVE Commands and Sub-Operations

A C-MOVE or C-GET request may be performed to any level of the Query/Retrieve Model. However, the transfer of Stored SOP Instances shall always take place at the Composite Object Instance level. A C-MOVE or C-GET where the Query/Retrieve level is the:

  • PATIENT level indicates that all Composite Object Instances related to a Patient shall be transferred.

  • STUDY level indicates that all Composite Object Instances related to a Study shall be transferred.

  • SERIES level indicates that all Composite Object Instances related to a Series shall be transferred.

  • IMAGE level indicates that selected individual Composite Object Instances shall be transferred.

Note

In the Baseline behavior, more than one entity may be retrieved if the Query/Retrieve Level is IMAGE, SERIES or STUDY, using List of UID matching, but only Single Value Matching value may be specified for Patient ID (0010,0020).

C.6.1.2 Conformance Requirements

An implementation may conform to one of the SOP Classes of the Patient Root SOP Class Group as an SCU, SCP or both. The Conformance Statement shall be in the format defined in PS3.2.

C.6.1.2.1 SCU Conformance
C.6.1.2.1.1 C-FIND SCU Conformance

An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group shall support queries against the Query/Retrieve Information Model described in Section C.6.1.1 using the baseline C-FIND SCU Behavior described in Section C.4.1.2.

An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCU shall state in its Conformance Statement whether it supports Optional Keys. If it supports Optional Keys, then it shall list the Optional Keys that it supports.

An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCU shall state in its Conformance Statement whether it may generate Relational-queries. If it supports Relational-queries, then it shall also support Extended Negotiation of relational-queries as an SCU.

An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCU shall state in its Conformance Statement whether or not it supports Extended Negotiation of combined date-time matching, fuzzy semantic matching of person names, Empty Value Matching, and/or Multiple Value Matching.

An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCU shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when encoding queries and interpreting responses.

C.6.1.2.1.2 C-MOVE SCU Conformance

An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCU shall support transfers against the Query/Retrieve Information Model described in Section C.6.1.1 using the C-MOVE SCU Behavior described in Section C.4.2.2.

C.6.1.2.1.3 C-GET SCU Conformance

An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCU shall support retrievals against the Query/Retrieve Information Model described in Section C.6.1.1 using the C-GET SCU Behavior described in Section C.4.3.2.

An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCU, which generates retrievals using the C-GET operation, shall state in its Conformance Statement the Storage Service Class SOP Classes under which it shall support the C-STORE sub-operations generated by the C-GET.

C.6.1.2.2 SCP Conformance
C.6.1.2.2.1 C-FIND SCP Conformance

An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group shall support queries against the Query/Retrieve Information Model described in Section C.6.1.1 using the C-FIND SCP Behavior described in Section C.4.1.3.

An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall state in its Conformance Statement whether it supports Optional Keys. If it supports Optional Keys, then it shall list the Optional Keys that it supports.

An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall state in its Conformance Statement whether it supports Relational-queries. If it supports Relational-queries, then it shall also support Extended Negotiation of relational-queries as an SCP.

An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall state in its Conformance Statement whether or not it supports Extended Negotiation of combined date-time matching, fuzzy semantic matching of person names, Empty Value Matching, and/or Multiple Value Matching. If fuzzy semantic matching of person names is supported, then the mechanism for fuzzy semantic matching shall be specified.

An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall state in its Conformance Statement whether it supports case-insensitive matching for PN VR Attributes and list the Attributes for which this applies.

An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when interpreting queries, performing matching and encoding responses.

An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall state in its Conformance Statement the manner in which Single Value Matching is performed for DS and IS VR Attributes (if supported) and list the Attributes for which this applies.

C.6.1.2.2.2 C-MOVE SCP Conformance

An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall support transfers against the Query/Retrieve Information Model described in Section C.6.1.1 using the C-MOVE SCP Behavior described in Section C.4.2.3.

An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCP, which generates transfers using the C-MOVE operation shall state in its Conformance Statement the Storage Service Class SOP Classes under which it shall support the C-STORE sub-operations generated by the C-MOVE.

C.6.1.2.2.3 C-GET SCP Conformance

An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall support retrievals against the Query/Retrieve Information Model described in Section C.6.1.1 using the C-GET SCP Behavior described in Section C.4.3.3.

An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCP, which generates retrievals using the C-GET operation, shall state in its Conformance Statement the Storage Service Class SOP Classes under which it shall support the C-STORE sub-operations generated by the C-GET.

C.6.1.3 SOP Classes

The SOP Classes in the Patient Root Query SOP Class Group of the Query/Retrieve Service Class identify the Patient Root Query/Retrieve Information Model, and the DIMSE-C operations supported. The Standard SOP Classes are listed in Table C.6.1.3-1.

Table C.6.1.3-1. SOP Classes for Patient Root Query/Retrieve

SOP Class Name

SOP Class UID

Patient Root Query/Retrieve Information Model - FIND

1.2.840.10008.5.1.4.1.2.1.1

Patient Root Query/Retrieve Information Model - MOVE

1.2.840.10008.5.1.4.1.2.1.2

Patient Root Query/Retrieve Information Model - GET

1.2.840.10008.5.1.4.1.2.1.3

Prev  Up  Next
C.5.3 Association Negotiation for C-GET SOP Classes  Home  C.6.2 Study Root SOP Class Group
DICOM PS3.4 2024d - Service Class Specifications