The SCP shall create and maintain UPS instances as instructed by N-CREATE requests and as specified by Table CC.2.5-3.
The SCP shall return, via the N-CREATE response primitive, the N-CREATE Response Status Code applicable to the associated request.
The SCP shall accept N-CREATE request primitives only if the value of the Procedure Step State (0074,1000) attribute is “SCHEDULED”. If the Procedure Step State attribute has another value, the SCP shall fail the N-CREATE.
The SCP may modify Attributes of a UPS instance, e.g., to correct invalid attribute values. A description of the modifications the SCP may perform shall be documented in the conformance statement of the SCP.
The SCP may also create and maintain UPS instances without receiving a UPS instance N-CREATE request, e.g., based on internal logic, operator inputs or HL7 messages. The contents of the instance created by the SCP must still comply with the N-CREATE requirements in Table CC.2.5-3.
Upon creating a new UPS Instance, the SCP shall update UPS Subscription Status of the Instance for each AE with a Global Subscription as described in CC.2.3.
Upon creating a new UPS Instance, the SCP shall send UPS State Reports (if it supports the UPS Event SOP Class) as described in CC.2.4.3 regardless of whether the creation was based on an N-CREATE or on internal logic.
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. There are no specific requirements to perform authorization.