C.6.2 Study Root SOP Class Group

In the Study Root Query/Retrieve Information Model, the information is arranged into three levels which 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.

[pic]

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.

Notes: 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 mis-identified.

Table C.6-5STUDY LEVEL KEYS FOR THE STUDYROOT 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:

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 PS 3.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 which 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 which 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