9.1.3.1 C-GET parameters

See Table 9.1-3.

Table 9.1-3 C-GET PARAMETERS

DIMSE-C Parameter Name Req/Ind Rsp/Conf CnclReq/CnclInd
Message ID M U
Message ID Being Responded To M M
Affected SOP Class UID M U(=)
Priority M
Identifier M U
Status M
Number of Remaining Sub-operations C
Number of Completed Sub-operations C
Number of Failed Sub-operations C
Number of Warning Sub-operations C

9.1.3.1.1 Message ID

This parameter identifies the operation. It is used to distinguish this operation from other notifications or operations that the DIMSE-service-provider may have in progress. No two identical values for the Message ID (0000,0110) shall be used for outstanding operations or notifications.

Noteσ: 1. Inclusion of this parameter in the confirmation was permitted in previous versions of this Standard but this mode of use is now retired. This parameter may be included in the confirmation but in such a case the invoking DIMSE-service-user should not attach any semantic significance to this parameter.

2. The Message ID (0000,0110) is recommended to be unique within the scope of an Association, to support debug procedures.

9.1.3.1.2 Message ID being responded to

This parameter specifies the Message ID (0000,0110) of the request/indication to which this response/confirmation applies.

9.1.3.1.3 Affected SOP class UID

For the request/indication, this parameter specifies the SOP Class of the Information Model for the retrieve. It may be included in the response/confirmation. If included in the response/confirmation, this parameter shall be equal to the value in the request/indication.

9.1.3.1.4 Priority

This parameter specifies the priority of the C-GET operation. It shall be one of LOW, MEDIUM or HIGH. This priority shall also be the priority used for all sub-operations.

9.1.3.1.5 Identifier

In the request/indication, this is a list of Attributes to be matched against the values of the Attributes of known composite SOP Instances of the performing DIMSE-service-user. The list of Attributes allowed and the rules for the construction are specified in PS 3.4.

Note: The Identifier is specified as U in the Response/Confirmation, but Services defined in PS 3.4 that use this primitive may impose mandatory or conditional requirements on its presence.

In the response/confirmation, this is a list of Attributes which provide status information about the C-GET operation. The list of Attributes allowed and the rules which define the usage of the Identifier are specified in PS 3.4.

9.1.3.1.6 Status

Indicates the status of the response. It may have any of the following values:

a) Success⎯This indicates that processing of the matches and all sub-operations are complete.

b) Pending⎯This indicates that processing of the matches and sub-operations is initiated or continuing.

c) Refused: Out of Resources⎯Indicates that processing of the C-GET has been terminated because it was out of resources. This may be the initial response to the C-GET or may be sent after a number of Pending statuses.

d) Refused: SOP Class Not Supported⎯Indicates that processing of the C-GET has been terminated because the SOP Class was not supported.

e) Cancel⎯Indicates that processing of the C-GET has been terminated due to a C-GET Cancel indication primitive.

f) Failed⎯Indicates that the C-GET operation failed at the performing DIMSE-service-user.

9.1.3.1.7 Number of remaining sub-operations

This specifies the number of remaining C-STORE sub-operations to be invoked by this C-GET operation. It may be included in any response/confirmation and shall be included if the status is equal to Pending.

9.1.3.1.8 Number of completed sub-operations

This specifies the number of C-STORE sub-operations invoked by this C-GET operation which have completed successfully. It may be included in any response/confirmation and shall be included if the status is equal to Pending.

9.1.3.1.9 Number of failed sub-operations

This specifies the number of C-STORE sub-operations invoked by this C-GET operation which have failed. It may be included in any response/confirmation and shall be included if the status is equal to Pending.

9.1.3.1.10 Number of warning sub-operations

This specifies the number of C-STORE sub-operation invoked by this C-GET operation which generated Warning responses. It may be included in any response/confirmation and shall be included if the status is equal to Pending.