| DICOM PS3.4 2025a - Service Class Specifications |
|---|
Implementations claiming Standard SOP Class Conformance to the Media Creation Management 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 using the Storage Service Class prior to initiating a request operation shall also be documented, and in particular the Transfer Syntaxes that may be proposed.
The SCU shall document in the Conformance Statement the actions and behavior that cause the SCU to generate an N-CREATE primitive (Create Media Creation Request), an N-ACTION primitive (Initiate Media Creation and Cancel Media Creation) or an N-GET primitive (Get Media Creation Result).
The SCU shall specify the SOP Class UIDs for which it may request media creation.
The SCU shall specify the Media Application Profiles for which it may request media creation.
The SCU shall specify if it supports the optional Storage Media File-Set ID & UID Attributes in the N-CREATE.
The SCU shall specify if it supports the optional Icon Image Sequence Attributes in the N-CREATE.
The SCU shall describe its use of expanded or replacement character sets, both in the N-CREATE, the N-GET and in its use of the Storage Service Class for composite instances.
The SCU shall specify whether or not it retries failed requests.
This allows the reader of a Conformance Statement to determine whether or not human intervention will be needed in the event of transient failures, or whether the SCU may be able to recover automatically.
The Conformance Statement shall be formatted as defined in PS3.2
| DICOM PS3.4 2025a - Service Class Specifications |
|---|