DICOM PS3.3 2025b - Information Object Definitions |
---|
The following Sections specify Modules used for Media Creation Management.
Table C.22.1-1. Media Creation Management Module Attributes
User or implementation specific human readable identification of the Storage Media to be created. |
||
Number of copies of set of media to be created for storing this file-set. |
||
Specifies whether or not to extract label information from the Instances. |
||
Unformatted free text to include in the label instead of or in addition to information extracted from the Instances. |
||
An implementation-dependent code string that may be used as a hint to select a particular layout or format of label. |
||
Unstructured text that describes where and to whom the media is to be transmitted. |
||
String that describes the bar code value to be printed on the media label. Note It is SCU responsibility to convey a Value for this Attribute coherent in length and content with the requested Barcode Symbology (2200,0006). |
||
Code string that describes the bar code symbology that shall be used for printing Barcode Value (2200,0005). See Section C.22.1.1 for Defined Terms. |
||
A flag indicating if the SCP is allowed to split this request over more than one piece of media. |
||
A flag indicating if the SCP is allowed to perform lossy compression. |
||
A flag indicating if the SCP should include in the media additional Non-DICOM information/objects |
||
A flag indicating if the SCP should include on the media a DICOM Instance Display Application. |
||
A flag to indicate whether or not the SCU intends to issue a subsequent media creation request referencing some or all of the Instances contained in Referenced SOP Sequence (0008,1199). |
||
A Sequence of Items where each Item references a single SOP Instance, the Media Storage Application Profile to be used, and, where applicable, the icon representing the referenced image. |
||
>Include Table 10-11 “SOP Instance Reference Macro Attributes” |
||
The Media Storage Application Profile to be used for this SOP Instance. NoteThis is the label of the profile as defined in PS3.11, e.g., "STD-XABC-CD". |
||
See Section C.7.6.1.1.6 for further explanation. |
||
Execution status of a request. See Section C.22.1.2 for Enumerated Values. |
||
Additional information about Execution Status (2100,0020). See Section C.22.1.3 for Defined Terms when the Execution Status is PENDING or FAILURE. |
||
Number of pieces of media that have been successfully created, in order to store all copies of the requested file-set. |
||
A Sequence of Items describing SOP Instances for which media creation failed. |
||
>Include Table 10-11 “SOP Instance Reference Macro Attributes” |
||
The Media Storage Application Profile used for this SOP Instance. NoteThis is the label of the profile as defined in PS3.11, e.g., "STD-XABC-CD". |
||
The reason that media creation failed for this SOP Instance. See Section C.22.1.4. |
||
Attributes associated with Failure Reason (0008,1197). See Section C.22.1.4. |
||
A Sequence describing the identifiers of all pieces of media created to satisfy the request. One or more Items are allowed. |
||
User or implementation specific human readable identification of the Storage Media that has been created. |
||
Uniquely identifies the Storage Media that has been created. |
The following Values and semantics may be used for Barcode Symbology (2200,0006):
Defined Terms:
ISO/IEC 15417:2000 Information technology - Automatic identification and data capture techniques - Bar code symbology specification - Code128
ISO/IEC 16388:1999 Information technology - Automatic identification and data capture techniques - Bar code symbology specifications - Code 39
ISO/IEC 16390:1999 Information technology - Automatic identification and data capture techniques - Bar code symbology specifications - Interleaved 2 of 5 (also known as USS ITF 2/5, I-2/5, ITF 2of5)
ANSI/HIBC 1-1996 Health Industry Bar Code (HIBC) Provider Applications Standard
The following Values and semantics shall be used for Execution Status (2100,0020):
Enumerated Values:
The SCP has created the Media Creation Management Instance, but it has not yet been scheduled.
This Media Creation Management Instance is still scheduled for processing.
This Media Creation Management Instance has been successfully processed.
This Media Creation Management Instance failed to be processed.
The following Values and semantics may be used for Execution Status Info (2100,0030):
Defined Terms:
The media creation request could not be accomplished since the device is not ready at this time and needs to be checked by an operator (e.g., covers/doors opened or device jammed).
The media creation request could not be accomplished since the device is not ready at this time and needs to be checked by a vendor service engineer (e.g., internal component failure).
The DICOMDIR building process failed for some unspecified reason (e.g., mandatory Attributes or values missing).
Duplicated Instances in the Referenced SOP Sequence (0008,1199).
One or more of the Instances in the Referenced SOP Sequence (0008,1199) are in conflict (e.g., the SOP Class specified is not consistent with the requested Media Storage Application Profile).
The size of a single SOP Instance exceeds the actual media capacity.
There is not enough memory available to complete this request.
Media creation device is not available at this time, but should become ready without user intervention (e.g., the media creation device's buffer capacity is full); the SCU should retry later.
Media creation device fails to operate; this may depend on permanent or transient hardware failures (e.g robot arm broken, DVD writer failed) or because it has been disabled by an operator.
One or more of the SOP Instances in the Referenced SOP Sequence (0008,1199) are not available.
One or more of the Media Storage Application Profiles, and/or SOP Classes, referenced in the Referenced SOP Sequence (0008,1199) are not supported by the SCP.
No more supplies (e.g., blank media, labeling ink) are available for the media creation device; operator intervention is required to replenish the supply.
The file-set size exceeds the actual media capacity, and the device is not capable of splitting across multiple pieces of media.
With respect to INST_OVERSIZED, DICOM media does not support spanning of Instances across volumes.
With respect to OUT_OF_SUPPLIES, This service is not supposed to provide detailed device status information, however sophisticated media creating devices can extend this table to return more information about the supply to be replenished. Implementation specific code values shall be defined in the Conformance Statement.
For most of the above statuses, the SCU can obtain more details about the processing errors (e.g., what are the SOP Instances not available) by using Failure Reason (0008,1197) within the Failed SOP Sequence (0008,1198).
The following Values and semantics may be used for Failure Reason (0008,1197):
Defined Terms:
Processing Failure; a general failure in processing the operation was encountered.
No such SOP Instance; one or more of the SOP Instances listed in the Referenced SOP Sequence (0008,1199) was not available.
Referenced SOP Class not supported; a media creation has been requested for a SOP Instance with a SOP Class that is not supported by the SCP.
Class-Instance conflict; the SOP Class of an Instance in the Referenced SOP Sequence (0008,1199) did not correspond to the SOP Class of the SOP Instance stored at the SCP.
Media Storage Application Profiles conflict; one or more of the Media Storage Application Profiles referenced in the Reference SOP Sequence (0008,1199) are in conflict (e.g., for the same request a STD-GEN-CD and a STD-GEN-DVD is referenced).
Media Storage Application Profile/Instance conflict; the SOP Class of an Instance in the Referenced SOP Sequence (0008,1199) did not correspond to a SOP Class permitted for the requested or supported Media Storage Application Profiles.
Media Storage Application Profile/Compression conflict; the profile for an Instance in the Referenced SOP Sequence (0008,1199) specified lossy compression but Allow Lossy Compression (2200,000F) has a Value of NO.
Media Storage Application Profile not supported; media creation has been requested for an Media Storage Application Profile that is not supported by the SCP.
Instance size exceeded; the size of a single SOP Instance exceeds the actual media capacity.
Missing Attribute; a required Attribute (e.g., Patient ID) was not supplied; the missing Attribute(s) shall be listed in Failure Attributes (2200,000E).
Missing Attribute Value; a required Attribute Value (e.g., the Content Date for a Structured Report) was not supplied; the Attribute(s) with missing values shall be listed in Failure Attributes (2200,000E).
DICOM PS3.3 2025b - Information Object Definitions |
---|