| DICOM PS3.4 2025b - Service Class Specifications |
|---|
Implementations providing conformance to any of the UPS SOP Classes (UPS Pull, UPS Push, UPS Watch, UPS Event and UPS Query) shall be conformant as described in the following sections and shall include within their Conformance Statement information as described below.
An implementation may conform to any of the UPS SOP Classes as an SCU or as an SCP. The Conformance Statement shall be in the format defined in PS3.2.
An implementation, which is conformant to any of the UPS SOP Classes as an SCU, shall meet conformance requirements for the operations that it invokes.
The SCU Conformance Statement shall be in the format defined in PS3.2.
An implementation, that conforms to any of the UPS Push, UPS Pull or UPS Watch SOP Classes as an SCU, shall specify under which conditions it will request the modification of the value of the Procedure Step State (0074,1000) Attribute to "IN PROGRESS", "COMPLETED", and "CANCELED".
An implementation that conforms to the UPS Pull, UPS Watch or UPS Query SOP Classes as an SCU shall state in its Conformance Statement
Whether it requests matching on Optional Matching Key Attributes for C-FIND.
Whether it requests Type 3 Return Key Attributes. If it requests Type 3 Return Key Attributes, then it shall list these Optional Return Key Attributes.
Whether or not it supports Extended Negotiation of fuzzy semantic matching of person names for C-FIND.
How it makes use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when encoding queries and interpreting responses for C-FIND.
What access mechanisms the SCP is capable of using for retrieving input data and/or making output data available. (see Table 10-3b “Referenced Instances and Access Macro Attributes” in PS3.3 for details on the different Retrieval Sequences).
| DICOM PS3.4 2025b - Service Class Specifications |
|---|