DICOM PS3.18 2024e - Web Services |
---|
This Transaction uses the GET method to Search for Studies, Series, and Instances managed by the origin server.
The request shall have the following syntax:
GET SP "/" {/resource} {?search*} SP version CRLF
Accept: 1#search-media-type CRLF
*(header-field CRLF)
CRLF
search-media-type =multipart/related; type="application/dicom+xml"/ dicom-json
The Target Resource Path component of the Target URI specifies the collection of resources that is the target of the search.
An origin server that is a native implementation shall support all Mandatory (M) resources specified in the Native column in Table 10.6.1-1.
An origin server that is a DIMSE Proxy implementation shall support all Mandatory (M) resources specified in the Proxy column in Table 10.6.1-1.
Table 10.6.1-1. Search Transaction Resources
/studies{?search*} |
||||
/studies/{study}/series{?search*} |
||||
/studies/{study}/instances{?search*} |
||||
/series{?search*} |
||||
/studies/{study}/series/{series}/instances{?search*} |
||||
/instances{?search*} |
For more information about Hierarchical Queries see Section C.4.1.3.1.1 “Hierarchical Search Method” in PS3.4. For more information about Relational Queries see Section C.4.1.2.2.1 “Relational-Queries” in PS3.4 and Section C.4.1.3.2.1 “Relational-Queries” in PS3.4.
Table 10.6.1-2 shows the resources supported by the Search transaction along with a description of the search performed and the results returned.
Table 10.6.1-2. Search Resource Descriptions
The origin server shall support Query Parameters as required in Table 8.3.4-1.
The user agent shall supply Query Parameters as required in Table 8.3.4-1.
DICOM Attribute/Value pairs included as Query Parameters in the request shall satisfy the requirements in Section 8.3.4.1.
The user agent may include the following Attributes in the request:
Patient IE Attributes (see Section 10.6.1.2.3)
Study IE Attributes (only allowed if the resource is All Studies, All Series, All Instances)
Series IE Attributes (only allowed if the resource is Study's Series, All Series, Study's Instances, or All Instances)
Composite Instance IE Attributes (only allowed if the resource is Study's Instances, Study Series' Instances, or All Instances)
Additional Query/Retrieve Attributes (see Section C.3.4 in PS3.4 )
Private Data Element Tags and their corresponding Private Creator Element Tags
The following are examples of Search URIs with valid Attribute/value pairs:
/studies?PatientID=11235813
/studies?PatientID=11235813&StudyDate=20130509
/studies?00100010=SMITH*&00101002.00100020=11235813&limit=25
/studies?00100010=SMITH*&OtherPatientIDsSequence.00100020=11235813
/studies?PatientID=11235813&includefield=00081048,00081049,00081060
/studies?PatientID=11235813&includefield=00081048&includefield=00081049&includefield=00081060
/studies?PatientID=11235813&StudyDate=20130509-20130510
/studies?StudyInstanceUID=1.2.392.200036.9116.2.2.2.2162893313.1029997326.94587,1.2.392.200036.9116.2.2.2.2162893313.1029997326.94583
/studies?00230010=AcmeCompany&includefield=00231002&includefield=00231003
/studies?00230010=AcmeCompany&00231001=001239&includefield=00231002&includefield=00231003
Table 10.6.1-3 defines the Search Key Types and their requirements.
The origin server shall support the IE Levels specified in Table 10.6.1-4.
The origin server shall support the matching Attributes specified in Table 10.6.1-5 for each supported IE Level.
While some of the Data Elements in Table 10.6.1-5 in are optional in Section C.6.2.1 in PS3.4 , the above list is consistent with those required for IHE RAD-14. See [IHE RAD TF Vol2] Table 4.14-1.
The origin server may support the matching Repository Query Attributes in Table 10.6.1.2.4-1 (see Section C.6.4.2 in PS3.4 ).
The origin server shall support Header Fields as required in Table 10.6.1-6 in the request.
The user agent shall supply in the Request Header Fields as required in Table 10.6.1-6.
See also Section 8.4.
DICOM PS3.18 2024e - Web Services |
---|