| DICOM PS3.4 2025a - Service Class Specifications |
|---|
An implementation may conform to the Repository Query SOP Class as an SCU, SCP or both. The Conformance Statement shall be in the format defined in PS3.2.
An implementation that conforms to the Repository Query SOP Class as an SCU shall support queries against the Study Root Query/Retrieve Information Model described in Section C.6.2.1 and Section C.6.4.1 using the C-FIND SCU behavior described in Section C.4.1.2 and Section C.6.4.4.
An implementation that conforms to the Repository Query SOP Class as an SCU shall be capable of generating queries using Hierarchical Search. It shall not generate queries using Relational-queries unless the Relational-queries option has been successfully negotiated. An implementation that conforms to the Repository Query SOP Class as an SCU shall state in its Conformance Statement whether it may generate Relational-queries.
An implementation that conforms to the Repository Query SOP Class as an SCU shall state in its Conformance Statement:
Whether or not it supports Extended Negotiation of combined date-time matching, fuzzy semantic matching of person names, empty value matching, and/or multiple value matching.
How it makes use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when encoding queries and interpreting responses.
Any limitations it places on the number of C-FIND responses through the Maximum Number of Records (0008,0429) Attribute.
| DICOM PS3.4 2025a - Service Class Specifications |
|---|