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 CC.2.8.3.1). This does not imply that an SCP which supports the UPS Watch 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:

— When all matches have been sent, the SCP generates a C-FIND response which contains a status of Success. A status of Success shall indicate that a response has been sent for each match known to the SCP.

Notes: 1. No Identifier is contained in a response with a status of Success. For a complete definition, see PS 3.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.

— The SCP shall generate a response with a status of Failure if it is unable to process the request. A Failure response shall contain no Identifier.

— If the SCP receives C-FIND-CANCEL indication before it has completed the processing of the matches it shall interrupt the matching process and return a status of Cancel.

Bi-directional Authentication of machines/users/applications is possible at association time (see PS 3.7 and PS 3.15). PS 3.7 provides a “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.

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.