C.6 SOP Class Definitions
Prev | C Query/Retrieve Service Class (Normative) | Next

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

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.

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

Description | 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 | (0010,1000) | 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.

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

Description | 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
Referring Physician's Name | (0008,0090) | O
Study Description | (0008,1030) | O
Procedure Code Sequence | (0008,1032) | O
>Code Value | (0008,0100) | O
>Coding Scheme Designator | (0008,0102) | O
>Coding Scheme Version | (0008,0103) | O
>Code Meaning | (0008,0104) | O
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
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

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

Description | Tag | Type
--- | --- | ---
Instance Number | (0020,0013) | R
SOP Instance UID | (0008,0018) | U
SOP Class UID | (0008,0016) | 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
>>Code Value | (0008,0100) | O
>>Coding Scheme Designator | (0008,0102) | O
>>Coding Scheme Version | (0008,0103) | O
>>Code Meaning | (0008,0104) | O
Related General SOP Class UID | (0008,001A) | O
Concept Name Code Sequence | (0040,A043) | O
>Code Value | (0008,0100) | O
>Coding Scheme Designator | (0008,0102) | O
>Coding Scheme Version | (0008,0103) | O
>Code Meaning | (0008,0104) | O
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.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.

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 and/or fuzzy semantic matching of person names.

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.

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 and/or fuzzy semantic matching of person names. 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 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.

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

### C.6.2 Study Root SOP Class Group

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

Table C.6.2-1. Query/Retrieve Level Values for Study Root

Query/Retrieve Level | Value in (0008,0052)
--- | ---
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 versions 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.2.1 Study Root Query/Retrieve Information Model

##### C.6.2.1.1 E/R Model

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

Figure C.6-2. Study Root Query/Retrieve Information Model E/R Diagram

##### C.6.2.1.2 Study Level

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

### Note

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

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.

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

Description | Tag | Type
--- | --- | ---
Study Date | (0008,0020) | R
Study Time | (0008,0030) | R
Accession Number | (0008,0050) | R
Patient's Name | (0010,0010) | R
Patient ID | (0010,0020) | 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
Referring Physician's Name | (0008,0090) | O
Study Description | (0008,1030) | O
Procedure Code Sequence | (0008,1032) | O
>Code Value | (0008,0100) | O
>Coding Scheme Designator | (0008,0102) | O
>Coding Scheme Version | (0008,0103) | O
>Code Meaning | (0008,0104) | O
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
Referenced Patient Sequence | (0008,1120) | O
>Referenced SOP Class UID | (0008,1150) | O
>Referenced SOP Instance UID | (0008,1155) | O
Issuer of Patient ID | (0010,0021) | O
Patient's Birth Date | (0010,0030) | O
Patient's Birth Time | (0010,0032) | O
Patient's Sex | (0010,0040) | O
Other Patient Ids | (0010,1000) | O
Other Patient Names | (0010,1001) | O
Patient's Age | (0010,1010) | O
Patient's Size | (0010,1020) | O
Patient's Weight | (0010,1030) | O
Ethnic Group | (0010,2160) | O
Occupation | (0010,2180) | O
Additional Patient History | (0010,21B0) | O
Patient Comments | (0010,4000) | O
Other Study Numbers | (0020,1070) | 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
Number of Study Related Series | (0020,1206) | O
Number of Study Related Instances | (0020,1208) | O
All other Attributes at Study Level |  | O

### Note

The use of the word "Images" rather than "Composite Object Instances" is historical, and should not be taken to mean that Composite Object Instances of other than image type are not included in the number.

##### C.6.2.1.3 Series Level

Attributes for the Series Level of the Study Root Query/Retrieve Information Model are the same as the Attributes for the Series Level of the Patient Root Query/Retrieve Information Model described in Section C.6.1.1.4.

##### C.6.2.1.4 Composite Object Instance Level

Attributes for the Composite Object Instance Level of the Study Root Query/Retrieve Information Model are the same as the Attributes for the Composite Object Instance Level of the Patient Root Query/Retrieve Information Model described in Section C.6.1.1.5.

##### C.6.2.1.5 Scope of the Get and 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:

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

#### C.6.2.2 Conformance Requirements

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

##### C.6.2.2.1 SCU Conformance

###### C.6.2.2.1.1 C-FIND SCU Conformance

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

An implementation that conforms to one of the SOP Classes of the Study 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 Study Root SOP Class Group as an SCU shall be capable of generating queries using the Hierarchical Search. It shall not generate queries using Relational-queries unless the Relational-queries option has been successfully negotiated.

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

An implementation that conforms to one of the SOP Classes of the Study 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 and/or fuzzy semantic matching of person names.

An implementation that conforms to one of the SOP Classes of the Study 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.2.2.1.2 C-MOVE SCU Conformance

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

###### C.6.2.2.1.3 C-GET SCU Conformance

An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCU shall support retrievals against the Query/Retrieve Information Model described in Section C.6.2.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 Study 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.2.2.2 SCP Conformance

###### C.6.2.2.2.1 C-FIND SCP Conformance

An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group shall support queries against the Query/Retrieve Information Model described in Section C.6.2.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 Study 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 Study Root SOP Class Group as an SCP shall state in its Conformance Statement whether it supports Relational Search. If it supports Relational Search, then it shall also support extended negotiation of relational-queries.

An implementation that conforms to one of the SOP Classes of the Study 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 and/or fuzzy semantic matching of person names. 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 Study 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 Attributes for which this applies.

An implementation that conforms to one of the SOP Classes of the Study 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.

###### C.6.2.2.2.2 C-MOVE SCP Conformance

An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCP shall support transfers against the Query/Retrieve Information Model described in Section C.6.2.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 Study 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.2.2.2.3 C-GET SCP Conformance

An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCP shall support retrievals against the Query/Retrieve Information Model described in Section C.6.2.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 Study 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.2.3 SOP Classes

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

Table C.6.2.3-1. SOP Classes for Study Root Query/Retrieve

SOP Class Name | SOP Class UID
--- | ---
Study Root Query/Retrieve Information Model - FIND | 1.2.840.10008.5.1.4.1.2.2.1
Study Root Query/Retrieve Information Model - MOVE | 1.2.840.10008.5.1.4.1.2.2.2
Study Root Query/Retrieve Information Model - GET | 1.2.840.10008.5.1.4.1.2.2.3

### C.6.3 Patient/Study Only SOP Class Group

Retired. See PS 3.4-2004.

Prev | Up | Next
C.5 Association Negotiation | Home | D Study Content Notification Service Class (Normative)