DICOM PS3.2 2023a - Conformance
N.5.3.2.4 Search Transaction (QIDO-RS)
N.5.3.2.4.1 User Agent

The Search Transaction user agent can request resources listed in Table N.5-82.

[List the supported resources for your Search Transaction user agent. Remove the non-supported resources rows. Fill in specific details of your implementation if available in the "Comments" column.]

Table N.5-82. Resources Search Transaction - User Agent

Resource

Comments

See resource path in Table 10.6.1-1 in PS3.18

All studies

All series

All instances

Study's Series

Study's instances

Study Series's Instances


The Search Transaction user agent supports query parameters listed in Table N.5-83.

[Indicate the supported parameters and their supported Values. For detail on the implementation possibilities see Table 8.3.4-1 in PS3.18. Fill in specific details of your implementation if available in the "Comments" column.]

Table N.5-83. Query Parameters for Search Transaction - User Agent

Query Parameter

Supported Values

Comments

match

Attribute Values to address the search (matching key). See the supported DICOM Attribute in the Table N.5-84

includefield

Attributes to be included in the response (return key). See the supported DICOM Attributes in the Table N.5-84

fuzzymatching

<<true

false>>

Limit

[Maximum number of results the server returns.]

Offset

[Number of results the server skips before the first returned result.]


[Indicate which DICOM query Attributes are supported and if they are supported as Matching and/or Return (include) key. Add or remove Attributes according to your implementation. If the tables are the same as used in DIMSE Services, you can enter a reference to Table N.5-17 and remove the text and table below. Otherwise provide the following text and Table N.5-84.]

Table N.5-84 lists the DICOM query Attributes supported by the Search Transaction user agent.

Table N.5-84. Supported Query Attributes User Agent

Attribute Name

Tag

Matching Key

Return Key

Comments

Study Level (May be used for All studies, All series, All instance resource query)

SpecificCharacterSet

(0008,0005)

StudyDate

(0008,0020)

StudyTime

(0008,0030)

AccessionNumber

(0008,0050)

ModalitiesInStudy

(0008,0061)

ReferringPhysicianName

(0008,0090)

TimezoneOffsetFromUTC

(0008,0201)

PatientName

(0010,0010)

PatientID

(0010,0020)

PatientBirthDate

(0010,0030)

PatientSex

(0010,0040)

StudyInstanceUID

(0020,000D)

StudyID

(0020,0010)

NumberOfStudyRelatedSeries

(0020,1206)

NumberOfStudyRelatedInstances

(0020,1208)

Series Level (May be used for All Series, Study's Series, Study's Instances, All Instances resource query)

SpecificCharacterSet

(0008,0005)

Modality

(0008,0060)

TimezoneOffsetFromUTC

(0008,0201)

SeriesDescription

(0008,103E)

SeriesInstanceUID

(0020,000E)

SeriesNumber

(0020,0011)

NumberOfSeriesRelatedInstances

(0020,1209)

PerformedProcedureStepStartDate

(0040,0244)

PerformedProcedureStepStartTime

(0040,0245)

RequestAttributeSequence

(0040,0275)

> RequestedProcedureID

(0040,1001)

> ScheduledProcedureStepID

(0040,0009)

Instance Level (May be used for All instances, Study's instance, Study Series's instance resource query)

SpecificCharacterSet

(0008,0005)

SOPClassUID

(0008,0016)

SOPInstanceUID

(0008,0018)

InstanceAvailability

(0008,0056)

TimezoneOffsetFromUTC

(0008,0201)

RetrieveURL

(0008,1190)

InstanceNumber

(0020,0013)

Rows

(0028,0010)

Columns

(0028,0011)

BitsAllocated

(0028,0100)

NumberOfFrames

(0028,0008)


The Search Transaction user agent supports Header Fields listed in Table N.5-85.

[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-85. Header Fields for Search Transaction - User Agent

Header Field

Supported Values

Comments

Accept

<<multipart/related; type="application/dicom+xml"

application/dicom+json>>

Accept-charset

See Section N.5.7for supported Values


N.5.3.2.4.2 Origin Server

The Search Transaction origin server receives GET requests to search for studies, series or instances.

[Specify here if this is a native or a DIMSE proxy implementation.]

The user agent specifies the Target Resource as part of the URI and the acceptable response Content-Type in the HTTP Header (i.e., dicom+xml or dicom+json).

The URI is composed by a Base URI: See Base URI for the origin server in Section A.6.3.2.3.

The Search Transaction origin server supports resources listed in Table N.5-86.

[Fill in information on your implementation in the Comments column when necessary.]

Table N.5-86. Resources Search Transaction - Origin Server

Transaction

Resource

Comments

See resource path in Table 10.6.1-1 in PS3.18

Search

All studies

All series

All instances

Study's Series

Study's instances

Study Series's Instances


The Search Transaction origin server supports query parameters listed in Table N.5-87.

[List the supported parameters and their supported Values. For detail on the implementation possibilities see Table 8.3.4-1 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-87. Query Parameters for Search Transaction - Origin Server

Query Parameter

Supported Values

Comments

match

Attribute Values to address the search (matching key). See the supported DICOM Attributes provided in the response in the Table N.5-89

includefield

Attributes to be included in the response (return key). See the supported DICOM Attributes provided in the response in the Table N.5-89

fuzzymatching

<<true

false>>

limit

offset

Number of results the server skips before the first returned result


The Search Transaction origin server supports Header Fields listed in Table N.5-88.

[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-88. Header Fields for Search Transaction - Origin Server

Header Field

Supported Values

Comments

Accept

Received in the user agent request:

multipart/related; type="application/dicom+xml"

application/dicom+json

Content-Type

Application/dicom+json (Default)

Multipart/related; type="application/dicom+xml"

Content-Length

[If Content-Encoding is not present.]

Content-Encoding

[If Content-Length is not present.]


[Indicate which DICOM query Attributes are supported / returned in the response and if they are supported as Matching and/or Return (include) key. If the tables are the same as used in DIMSE Services, you can enter a reference to Table N.5-18 and remove the text and table below. Otherwise provide the following text and Table N.5-89, and add or remove Attributes according to your implementation. In the table below, Attributes / matching /return keys in regular font style are mandatory to be supported.]

Table N.5-89 lists the DICOM query / returned Attributes supported by the Search Transaction origin server.

Table N.5-89. Query / Return Key Search Transaction - Origin Server

Attribute Name

Tag

Matching Key

Return Key

Comments on the Response

Study Level (May be used for All studies, All series, All instance resource query)

StudyDate

(0008,0020)

StudyTime

(0008,0030)

AccessionNumber

(0008,0050)

ModalitiesInStudy

(0008,0061)

ReferringPhysicianName

(0008,0090)

TimezoneOffsetFromUTC

(0008,0201)

Will be returned if known

Retrieve URL

(0008,1190)

Will be present if the Instance is retrievable by the Retrieve Transaction

PatientName

(0010,0010)

PatientID

(0010,0020)

PatientBirthDate

(0010,0030)

PatientSex

(0010,0040)

StudyInstanceUID

(0020,000D)

StudyID

(0020,0010)

NumberOfStudyRelatedSeries

(0020,1206)

NumberOfStudyRelatedInstances

(0020,1208)

Series Level (May be used for All Series, Study's Series, Study's Instances, All Instances resource query)

Modality

(0008,0060)

TimezoneOffsetFromUTC

(0008,0201)

Will be present if known

SeriesDescription

(0008,103E)

Will be present if known

Retrieve URL

(0008,1190)

Will be present if the Instance is retrievable by the Retrieve Transaction

SeriesInstanceUID

(0020,000E)

SeriesNumber

(0020,0011)

NumberOfSeriesRelatedInstances

(0020,1209)

PerformedProcedureStepStartDate

(0040,0244)

Will be present if known

PerformedProcedureStepStartTime

(0040,0245)

Will be present if known

RequestAttributeSequence

(0040,0275)

Will be present if known

> RequestedProcedureID

(0040,1001)

> ScheduledProcedureStepID

(0040,0009)

Instance Level (May be used for All instances, Study's instance, Study Series's instance resource query)

SOPClassUID

(0008,0016)

SOPInstanceUID

(0008,0018)

InstanceAvailability

(0008,0056)

Will be present if known

TimezoneOffsetFromUTC

(0008,0201)

Will be present if known

RetrieveURL

(0008,1190)

Will be present if the Instance is retrievable by the Retrieve Transaction

InstanceNumber

(0020,0013)

Rows

(0028,0010)

Will be present if known

Columns

(0028,0011)

Will be present if known

BitsAllocated

(0028,0100)

Will be present if known

NumberOfFrames

(0028,0008)

Will be present if known


DICOM PS3.2 2023a - Conformance