DICOM PS3.4 2020c - Service Class Specifications

CC.2.7.3 Service Class Provider Behavior (Current)
Prev | CC.2.7 Get Unified Procedure Step Information (N-GET) | Next

#### CC.2.7.3 Service Class Provider Behavior

The SOP Class UID of the specified UPS instance will always be the UPS Push SOP Class UID, which might not match the UPS SOP Classes negotiated with the SCU. See Section CC.3.1 for further details.

The SCP shall return, via the N-GET response primitive, the selected Attribute Values from the indicated Unified Procedure Step Instance to the SCU.

### Note

The requirement for the SCP to respond to N-GET requests for UPS Instances that have moved to the COMPLETED or CANCELED state is limited. See Section CC.2.1.3 Service Class Provider Behavior.

The SCP shall not return the Transaction UID (0008,1195) Attribute. This is necessary to preserve this Attribute's role as an access lock.

The SCP shall return, via the N-GET response primitive, the N-GET Response Status Code applicable to the associated request. A Failure Code shall indicate that the SCP has not retrieved the SOP Instance.

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.

Prev | Up | Next
CC.2.7.2 Service Class User Behavior | Home | CC.2.7.4 Status Codes

DICOM PS3.4 2020c - Service Class Specifications