Implementations providing conformance to any of the UPS SOP Classes (UPS Pull, UPS Push, UPS Watch and UPS Event) 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 Annex A “DICOM Conformance Statement Template (Normative)”.
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 formatted as defined in Annex A “DICOM Conformance Statement Template (Normative)”.
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 or UPS Watch 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).
An implementation that is conformant to any of the UPS SOP Classes as an SCP shall meet conformance requirements for the operations that it performs.
The SCP Conformance Statement shall be formatted as defined in Annex A “DICOM Conformance Statement Template (Normative)”.
The SCP Conformance Statement shall provide information on the behavior of the SCP at the following occurrences:
The creation of a new Instance of the UPS Push SOP Class with the status "SCHEDULED". The result of that process on the scheduling information and on the Attribute Values of the Unified Procedure Step shall be specified.
The conditions for the update of the Attribute "Procedure Step State" (0074,1000), i.e., the change to the state "IN PROGRESS" or to "CANCELED" or to "COMPLETED".
Which Attributes the SCP may update after the state has been set to "IN PROGRESS" or "CANCELED" or "COMPLETED".
For how long the UPS Instance will persist on the SCP, and how long it will be available for N-GETs once its state has been set to "COMPLETED" or "CANCELED".
Whether the SCP supports priority for C-FIND. If the SCP supports priority for C-FIND, then the meaning of the different priority levels shall be specified.
Whether the SCP supports case-insensitive matching for PN VR Attributes for C-FIND. If the SCP supports case-insensitive matching of PN VR Attributes, then the Attributes for which this applies shall be specified.
Whether the SCP supports extended negotiation of fuzzy semantic matching of person names for C-FIND. If the SCP supports extended negotiation of fuzzy semantic matching of person names, then the mechanism for fuzzy semantic matching shall be specified.
How the SCP makes use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when interpreting C-FIND queries, performing matching and encoding responses.
What rules the SCP may use to perform additional filtering during a C-FIND (e.g., limiting returns based on the requesting user and the confidentiality settings of the workitems, or limiting the return to a single item already selected on the SCP) and under what conditions those rules are invoked.
Whether the SCP might refuse Subscription requests and/or Deletion Locks and for what reasons.
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).