The SOP Class UID identifies the Query/Retrieve Information Model against which the C-GET is to be performed. Support for the SOP Class UID is implied by the Abstract Syntax UID of the Presentation Context used by this C-GET operation.
The Priority Attribute defines the requested priority of the C-GET operation and corresponding C-STORE sub-operations with respect to other DIMSE operations being performed by the same SCP.
Processing of priority requests is not required of SCPs. Whether or not an SCP supports priority processing, and the meaning of the different priority levels shall be stated in the Conformance Statement of the SCP. The same priority shall be used for all C-STORE sub-operations.
The C-GET request shall contain an Identifier. The C-GET response shall conditionally contain an Identifier as required in C.22.214.171.124.2.
Note: The Identifier is specified as U in the definition of the C-GET primitive in PS 3.7 but is specialized for use with this service.
An Identifier in a C-GET request shall contain:
– the Query/Retrieve Level (0008,0052) that defines the level of the retrieval
– SOP Instance UID(s) (0008,0018)
Query/Retrieve Level (0008,0052) shall be IMAGE.
Specific Character Set (0008,0005) shall not be present.
The Keys at each level of the hierarchy and the values allowable for the level of the retrieval are defined in the SOP Class definition for the Query/Retrieve Information Model.
The status code values that might be returned in a C-GET response shall be as specified in Table Z.4-1
Table Z.4-1 C-GET RESPONSE STATUS VALUES FOR INSTANCE ROOT RETRIEVE
|Service Status||Further Meaning||Status Codes||Related Fields|
|Failure||Refused: Out of Resources – Unable to calculate number of matches||A701||(0000,0902)|
|Refused: Out of Resources – Unable to perform sub-operations||A702||(0000,1020) (0000,1021) (0000,1022) (0000,1023)|
|Identifier does not match SOP Class||A900||(0000,0901) (0000,0902)|
|Unable to process||Cxxx||(0000,0901) (0000,0902)|
|Cancel||Sub-operations terminated due to Cancel Indication||FE00||(0000,1020) (0000,1021) (0000,1022) (0000,1023)|
|Warning||Sub-operations Complete – One or more Failures or Warnings||B000||(0000,1020) (0000,1021) (0000,1022) (0000,1023)|
|Success||Sub-operations Complete – No Failures or Warnings||0000||(0000,1020) (0000,1021) (0000,1022) (0000,1023)|
|Pending||Sub-operations are continuing||FF00||(0000,1020) (0000,1021) (0000,1022) (0000,1023)|
Inclusion of the Number of Remaining Sub-operations shall be as specified in C.126.96.36.199
Inclusion of the Number of Completed Sub-operations shall be as specified in C.188.8.131.52
Inclusion of the Number of Failed Sub-operations shall be as specified in C.184.108.40.206
Inclusion of the Number of Warning Sub-operations shall be as specified in C.220.127.116.11.