| DICOM PS3.4 2024c - Service Class Specifications |
|---|
Implementations claiming Standard SOP Class Conformance to the Storage Commitment Push Model SOP Class shall be conformant as described in this Section and shall include within their Conformance Statement information as described in this Section and sub-Sections.
An implementation may claim conformance to this SOP Class as an SCU, SCP or both. The Conformance Statement shall be in the format defined in PS3.2.
An implementation that is conformant to this SOP Class as an SCU shall meet conformance requirements for
The mechanisms used by the SCU to transfer SOP Instances to the SCP shall be documented.
The SCU shall document in the Conformance Statement the actions and behavior that cause the SCU to generate an N-ACTION primitive (Storage Commitment Request).
The SCU shall specify the SOP Class UIDs for which it may request storage commitment.
The SCU shall specify the duration of applicability of the Transaction UID. This may be specified as a time limit or a policy that defines the end of a transaction (e.g., how long will the SCU wait for a N-EVENT-REPORT).
The SCU shall specify if it supports the optional Storage Media File-Set ID & UID Attributes in the N-ACTION. If these Attributes are supported, the SCU shall also specify which Storage Media Application Profiles are supported.
The Conformance Statement shall be formatted as defined in PS3.2
The SCU shall document in the Conformance Statement the behavior and actions taken by the SCU upon receiving an N-EVENT-REPORT primitive (Storage Commitment Result).
The SCU shall specify the behavior and actions performed when a success status is received (i.e., if and when local SOP Instances copies are deleted).
The SCU shall specify the behavior and actions performed when a failure status is received (i.e., recovery mechanisms, etc.).
The Conformance Statement shall be formatted as defined in PS3.2
| DICOM PS3.4 2024c - Service Class Specifications |
|---|