DICOM PS3.4 2020c - Service Class Specifications

CC.2.8.3 Service Class Provider Behavior

All C-FIND SCPs shall be capable of processing queries that meet the requirements of the "Worklist" Search (see Section CC.2.8.3.1). This does not imply that an SCP that supports the UPS Watch SOP Class or the UPS Query SOP Class must also be an SCP of the UPS Pull SOP Class.

The SCP shall support Attribute matching as described in Section C.2.2.2.

An SCP conveys the following semantics using the C-FIND requests and responses:

Note

  1. No Identifier is contained in a response with a status of Success. For a complete definition, see PS3.7.

  2. When there are no matches, then no responses with a status of Pending are sent, only a single response with a status of Success.

Bi-directional Authentication of machines/users/applications is possible at association time (see PS3.7 and PS3.15). PS3.7 provides a "Refused: Refused: Not authorized" error code. Further requiring or documenting authentication and/or authorization features from the SCU or SCP is beyond the scope of this SOP Class.

CC.2.8.3.1 Worklist Search Method

The following steps are used to generate match responses.

  • Match the key match Attributes contained in the Identifier of the C-FIND request against the values of the Key Attributes for each worklist entity.

  • If there are no matching keys, then there are no matches, return a response with a status equal to Success and with no Identifier.

  • Otherwise,

    • For each entity for which the Attributes match all of the specified matching key Attributes, construct an Identifier. This Identifier shall contain all of the values of the Attributes for this entity that correspond to the return keys specified in the C-FIND request.

    • Return a response for each remaining Identifier.

Table CC.2.5-3 defines the Attributes of the Unified Procedure Step Information Model, the requirements for key matching, and the requirements for return keys.

DICOM PS3.4 2020c - Service Class Specifications