C.22 Media Creation Management Specific Modules
Prev | C Information Module Definitions (Normative) | Next

## C.22 Media Creation Management Specific Modules

The following Sections specify Modules used for Media Creation Management.

### C.22.1 Media Creation Management Module

Table C.22.1-1. Media Creation Management Module Attributes

Attribute name | Tag | Attribute Description
--- | --- | ---
Storage Media File-Set ID | (0088,0130) | User or implementation specific human readable identification of the Storage Media to be created.
Storage Media File-Set UID | (0088,0140) | Uniquely identifies a Storage Media to be created.
Number of Copies | (2000,0010) | Number of copies of set of media to be created for storing this file-set. ### Note If the entire request fits on a single piece of media per copy, then this value corresponds to the actual number of pieces of media to be created.
Request Priority | (2200,0020) | Specifies the priority of the request. Enumerated Values: HIGH MED LOW
Label Using Information Extracted From Instances | (2200,0001) | Specifies whether or not to extract label information from the instances. Enumerated Values: YES NO
Label Text | (2200,0002) | Unformatted free text to include in the label instead of or in addition to information extracted from the instances.
Label Style Selection | (2200,0003) | An implementation-dependent code string that may be used as a hint to select a particular layout or format of label.
Media Disposition | (2200,0004) | Unstructured text that describes where and to whom the media is to be sent.
Barcode Value | (2200,0005) | 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).
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.
Allow Media Splitting | (2200,0007) | A flag indicating if the SCP is allowed to split this request over more than one piece of media. Enumerated Values: YES NO ### Note The SCP is not required to support the split of a media creation request across more than one piece of media. If the size of the set of SOP instances is greater than the media storage capacity, and this flag has been set to NO, the SCP shall refuse to process the request.
Allow Lossy Compression | (2200,000F) | A flag indicating if the SCP is allowed to perform lossy compression. Enumerated Values: YES NO
Include Non-DICOM Objects | (2200,0008) | A flag indicating if the SCP should include in the media additional Non-DICOM information/objects Defined Terms: NO FOR_PHYSICIAN FOR_PATIENT FOR_TEACHING FOR_RESEARCH
Include Display Application | (2200,0009) | A flag indicating if the SCP should include on the media a DICOM Instance Display Application. Enumerated Values: YES NO
Preserve Composite Instances After Media Creation | (2200,000A) | 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). Enumerated Values: YES NO
Referenced SOP Sequence | (0008,1199) | A sequence of Items where each Item references a single SOP Instance, the Media Application Profile to be used, and, where applicable, the icon representing the referenced image
>Include Table 10-11 “SOP Instance Reference Macro Attributes” |
>Requested Media Application Profile | (2200,000C) | The Media Application Profile to be used for this SOP Instance. ### Note This is the label of the profile as defined in PS3.11, e.g., "STD-XABC-CD".
>Icon Image Sequence | (0088,0200) | This Icon Image is representative of the Image. Only a single Item is permitted in this Sequence.
>>Include Table C.7-11b “Image Pixel Macro Attributes” | See Section C.7.6.1.1.6 for further explanation.
Execution Status | (2100,0020) | Execution status of a request. See Section C.22.1.2 for Enumerated Values
Execution Status Info | (2100,0030) | Additional information about Execution Status (2100,0020). Defined Terms if Execution Status (2100,0020) is DONE, CREATING or IDLE: NORMAL See Section C.22.1.3 for Defined Terms when the Execution Status is PENDING or FAILURE.
Total Number of Pieces of Media Created | (2200,000B) | Number of pieces of media that have been successfully created, in order to store all copies of the requested file-set. ### Note If the entire request fits on a single piece of media per copy, then this value corresponds to the number of copies of media created.
Failed SOP Sequence | (0008,1198) | A sequence of Items describing SOP Instances for which media creation failed.
>Include Table 10-11 “SOP Instance Reference Macro Attributes” |
>Requested Media Application Profile | (2200,000C) | The Media Application Profile used for this SOP Instance. ### Note This is the label of the profile as defined in PS3.11, e.g., "STD-XABC-CD".
>Failure Reason | (0008,1197) | The reason that media creation failed for this SOP Instance. See Section C.22.1.4.
>Failure Attributes | (2200,000E) | Attributes associated with Failure Reason (0008,1197). See Section C.22.1.4.
Referenced Storage Media Sequence | (2200,000D) | A Sequence describing the identifiers of all pieces of media created to satisfy the request. One or more items are allowed. ### Note If the SCP splits a media creation request across more than one piece of media (e.g., if it doesn't fit on one), then all the created pieces of media will be included in this Sequence.
> Storage Media File-Set ID | (0088,0130) | User or implementation specific human readable identification of the Storage Media that has been created.
> Storage Media File-Set UID | (0088,0140) | Uniquely identifies the Storage Media that has been created.

#### C.22.1.1 Barcode Symbology

Defined Terms:

CODE128

  ISO/IEC 15417:2000 Information technology - Automatic identification and data capture techniques - Bar code symbology specification - Code128

CODE39

  ISO/IEC 16388:1999 Information technology - Automatic identification and data capture techniques - Bar code symbology specifications - Code 39

INTER_2_5

  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)

HIBC

  ANSI/HIBC 1-1996 Health Industry Bar Code (HIBC) Provider Applications Standard

### Note

This doesn't list all the bar code symbologies in use (there are currently more than 400). Implementations supporting other symbologies can extend this list. Implementation specific code values shall be defined in the Conformance Statement.

#### C.22.1.2 Execution Status

Enumerated Values:

IDLE

  The SCP has created the media creation management instance, but it has not been yet scheduled.

PENDING

  This media creation management instance is still scheduled for processing

CREATING

  This media creation management instance is being processed

DONE

  This media creation management instance has been successfully processed

FAILURE

  This media creation management instance failed to be processed

### Note

IDLE describes the status of a new media creation management instance (N-CREATE operation performed) for which the N-ACTION action has not been yet issued.

#### C.22.1.3 Execution Status Info

Defined Terms:

CHECK_MCD_OP

  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)

CHECK_MCD_SRV

  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)

DIR_PROC_ERR

  The DICOMDIR building process failed for some unspecified reason (e.g., mandatory attributes or values missing)

DUPL_REF_INST

  Duplicated instances in the Referenced SOP Sequence (0008,1199)

INST_AP_CONFLICT

  One or more of the elements in the Referenced SOP Sequence (0008,1199) are in conflict (e.g., the SOP Class specified is not consistent with the requested Application Profile)

INST_OVERSIZED

  A single instance size exceeds the actual media capacity

INSUFFIC_MEMORY

  There is not enough memory available to complete this request

MCD_BUSY

  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

MCD_FAILURE

  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

NO_INSTANCE

  One or more of the SOP Instances in the Referenced SOP Sequence (0008,1199) are not available

NOT_SUPPORTED

  One or more of the Application Profiles, and/or SOP Classes, referenced in the Referenced SOP Sequence (0008,1199) are not supported by the SCP

OUT_OF_SUPPLIES

  No more supplies (e.g., blank media, labeling ink) are available for the media creation device; operator intervention is required to replenish the supply

PROC_FAILURE

  A general processing failure was encountered

QUEUED

  This Media Creation Management instance is still in queue

SET_OVERSIZED

  The file-set size exceeds the actual media capacity, and the device is not capable of splitting across multiple pieces of media

UNKNOWN

  There is an unspecified problem

### Note

1. With respect to INST_OVERSIZED, DICOM media does not support spanning of instances across volumes.

2. 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.

3. 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).

#### C.22.1.4 Failure Reason

Defined Terms:

0110H

  Processing failure; a general failure in processing the operation was encountered

0112H

  No such object instance; one or more of the instances listed in the Referenced SOP Sequence (0008,1199) was not available

0122H

  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

0119H

  Class/Instance conflict; the SOP Class of an instance in the Referenced SOP Instance Sequence did not correspond to the SOP class of the SOP Instance stored at the SCP

0201H

  Media Application Profiles conflict; one or more of the Media 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)

0202H

  Media 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 Application Profiles

0203H

  Media 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

0204H

  Media Application Profile not supported; media creation has been requested for an Application Profile that is not supported by the SCP

0205H

  Instance size exceeded; a single instance size exceeds the actual media capacity

0120H

  Missing attribute; a required Attribute (e.g., Patient ID) was not supplied; the missing Attribute(s) shall be listed in Failure Attributes (2200,000E)

0121H

  issing 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)

### Note

With respect to 0205H Instance size exceeded, DICOM media does not support spanning of instances across volumes.

Prev | Up | Next
C.21 Spatial Fiducials | Home | C.23 Hanging Protocol Specific Modules