DICOM PS3.18 2020a - Web Services

9.4 Retrieve DICOM Instance Transaction (Current)
Prev | 9 URI Service | Next

## 9.4 Retrieve DICOM Instance Transaction

This transaction retrieves a single Instance in the application/dicom media type. See Section 8.7.3.

### 9.4.1 Request

The request shall have the following syntax:

    GET SP / ?{requestType}&{study}&{series}&{instance}

             {&accept}

             {&charset}

             {&anonymize}

             {&transferSyntax}

             SP HTTP/1.1 CRLF

    Accept: uri-media-type CRLF

    *(header-field CRLF)

    CRLF

#### 9.4.1.1 Target Resource

The Target Resource shall be an Instance of a Composite Storage SOP class defined in PS3.4.

#### 9.4.1.2 Query Parameters

The origin server shall support Query Parameters as required in Table 9.4.1-1 .

The user agent shall supply in the request Query Parameters as required in Table 9.4.1-1 .

Table 9.4.1-1. Optional Query Parameters

Key | Values | Usage | Section
--- | --- | --- | ---
User Agent | Origin Server
anonymize | "yes" | O | O | Section 9.4.1.2.1
annotation | "patient" "technique" | O | O | Section 9.4.1.2.2
transferSyntax | uid | O | O | Section 9.4.1.2.3

##### 9.4.1.2.1 Anonymize

    anonymize = %s"anonymize=" token

    token = "yes"

This parameter specifies that the returned representations shall have all Individually Identifiable Information (III) removed, as defined in Annex E “Attribute Confidentiality Profiles” in PS3.15 Basic Profile with Clean Pixel Data Option. Its name is "anonymize" and its value is a token. The defined token is "yes". If this parameter is not present, no anonymization is requested.

##### 9.4.1.2.2 Annotation

    annotation = 1#( %s"patient" / %s"technique" )

This parameter specifies that the rendered images shall be annotated with patient and/or procedure information. Its value is a comma-separated list of one or more keywords.

Where

    "patient"
| indicates that the rendered images shall be annotated with patient information (e.g., patient name, birth date, etc.).
    "technique"
| indicates that the rendered images shall be annotated with information about the procedure that was performed (e.g., image number, study date, image position, etc.).

The origin server may support additional keywords, which should be included in the Conformance Statement and the Retrieve Capabilities response.

##### 9.4.1.2.3 Transfer Syntax

    transfer-syntax = %s"transferSyntax" "=" transfer-syntax-uid

This parameter specifies a Transfer Syntax UID. Its name is "transferSyntax" and its value is a single Transfer Syntax UID. It is optional for both the user agent and origin server. See Section 8.7.3.5 for details.

#### 9.4.1.3 Request Header Fields

The origin server shall support header fields as required in Table 9.4.1-2 in the request.

The user agent shall supply in the request header fields as required in Table 9.4.1-2.

Table 9.4.1-2. Request Header Fields

Name | Values | Usage | Description
--- | --- | --- | ---
User Agent | Origin Server
Accept | media-type | O | M | The Acceptable Media Types for the response payload
Accept-Charset | charset | O | M | The Acceptable Character Sets of the response payload

See also Section 8.4.

#### 9.4.1.4 Request Payload

The request has no payload.

Prev | Up | Next
9.3 Transactions Overview | Home | 9.4.2 Behavior

DICOM PS3.18 2020a - Web Services