Материал: part02

K.3 Introduction​

K.3.1 Revision History​

Table K.3.1-1. Revision History​

K.3.2 Audience, Remarks, Terms and Definitions, Basics of DICOM Communication, Abbrevi-​ ations, References​

See example text in Section A.3.​

K.3.3 Additional Remarks for This Example​

ThisdocumentisasampleDICOMConformanceStatementcreatedforDICOMPS3.2.Itistobeusedsolelyasanexampletoillustrate​ howtocreateaDICOMConformanceStatementforaDICOMServiceClassProvider(SCP).Thesubjectofthedocument,EXAMPLE-​ QIDO-SERVICE, is a fictional product.​

K.4 Networking​

K.4.1 Implementation Model​

K.4.1.1 Application Data Flow​

DICOM HTTP Interface

Figure K.4.1-1. Application Data Flow Diagram​

TheQIDO-RSProviderApplicationreceivesQIDOrequestsfromaremoteAE.TheserequestsareHTTPGETrequests.Itisassociated​ with the local real-world activity "Query Remote Device". It uses the request to select matching Studies, Series or Instances. It then​ returns a set of matching Studies, Series or Instances or a response code indicating warning or failure back to the requesting device.​

K.4.1.2 Functional Definition of AEs​

K.4.1.2.1 Functional Definition of QIDO Service Application​

The reception of a QIDO-RS GET request will activate the QIDO-RS Provider. An internal query request is sent to the search capab-​ ilitiesoftheassociatedPACSorVendorNeutralArchive(VNA).ThesearchresultisbasedupontheURLoftheQIDO-RSGETrequest.​ The response is a status code indicating the success, warning, or failure of the search along with any matching results stored in the​ Remote PACS or VNA.​

K.4.2 AE Specifications​

This AE complies with Section 10.6 in PS3.18, specification for QIDO-RS.​

- Standard -​

K.4.2.1 QIDO-RS Specifications​

K.4.2.1.1 QIDO-RS Search for Studies​

Table K.4.2-1. QIDO-RS Search for Studies Specification​

Table K.4.2-1a. QIDO-RS Study Attribute Matching​

Types of Matching (see Section C.2.2.2 “Attribute Matching” in PS3.4) :​

"S" indicates the identifier attribute uses Single Value Matching​

"L" indicates UID List Matching​

"U" indicates Universal Matching.​

- Standard -​

Note​

If only Universal Matching is supported for an attribute then that attribute can only be passed as an "includefield" query key​

"*" indicates wild card matching​

"R" indicates Range Matching​

"SEQUENCE" indicates Sequence Matching​

"NONE" indicates that no matching is supported, but that values for this Element requested will be returned with all requests​

"UNIQUE" indicates that this is the Unique Key for that query level, in which case Universal Matching or Single Value Matching is​ used depending on the query level (see Section C.2.2.1.1 “Unique Keys” in PS3.4).​

K.4.2.1.2 QIDO-RS Search for Series​

Table K.4.2-2. QIDO-RS Search for Series Specification​

Table K.4.2-2a. QIDO-RS Series Attribute Matching​

Types of matching: Section Section K.4.2.1.1 “QIDO-RS Search for Studies”.​

- Standard -​

K.4.2.1.3 QIDO-RS Search for Instances​

Table K.4.2-3. QIDO-RS Search for Instances Specification​

Table K.4.2-3a. QIDO-RS Instance Attribute Matching​

Types of matching: Section Section K.4.2.1.1 “QIDO-RS Search for Studies”.​

K.4.2.1.4 Connection Policies​

K.4.2.1.4.1 General​

All standard RS connection policies apply. There are no extensions for RS options.​

- Standard -​

K.4.2.1.4.2 Number of Connections​

EXAMPLE-QIDO-SERVICE limits the number of simultaneous RS requests. Additional requests will be queued after the HTTP con-​ nection is accepted. When an earlier request completes, a pending request will proceed.​

Table K.4.2-4. Number of HTTP Requests Supported​

EXAMPLE-QIDO-SERVICE does not support RS asynchronous response.​

K.4.2.1.4.4 Response Status​

TheEXAMPLE-QIDO-SERVICEshallprovidearesponsemessageheadercontainingtheappropriatestatuscodeindicatingsuccess,​ warning, or failure as shown in Table K.4.2-5.​

Table K.4.2-5. HTTP Standard Response Codes​

K.4.2.2 Extended Negotiation​

EXAMPLE-QIDO-SERVICE does not support the "fuzzymatching" query key.​

EXAMPLE-QIDO-SERVICE will perform case insensitive matching for PN VR attributes but will not perform other forms of fuzzy​ matching. This applies to the following attributes:​

•​Referring Physician's Name (0008,0090)​

•​Physician(s) of Record (0008,1048)​

•​Patient's Name (0010,0010)​

K.4.3 Network Interfaces​

K.4.3.1 Physical Network Interface​

EXAMPLE-QIDO-SERVICE uses the network interface from the hosting EXAMPLE-PACS-ARCHIVE. See its conformance claim for​ details.​

- Standard -​