DICOM PS3.3 2020a - Information Object Definitions |
Page 1461 |
2.WithrespecttoOUT_OF_SUPPLIES,Thisserviceisnotsupposedtoprovidedetaileddevicestatusinformation,however sophisticatedmediacreatingdevicescanextendthistabletoreturnmoreinformationaboutthesupplytobereplenished. 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:
0110HProcessing failure; a general failure in processing the operation was encountered
0112HNosuchobjectinstance;oneormoreoftheinstanceslistedintheReferencedSOPSequence(0008,1199)wasnotavailable 0122HReferenced 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
0119HClass/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
0201HMediaApplicationProfilesconflict;oneormoreoftheMediaApplicationProfilesreferencedintheReferenceSOPSequence (0008,1199) are in conflict (e.g., for the same request a STD-GEN-CD and a STD-GEN-DVD is referenced)
0202HMedia 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
0203HMedia 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
0204HMedia Application Profile not supported; media creation has been requested for an Application Profile that is not supported by the SCP
0205HInstance size exceeded; a single instance size exceeds the actual media capacity
0120HMissing Attribute; a required Attribute (e.g., Patient ID) was not supplied; the missing Attribute(s) shall be listed in Failure Attributes (2200,000E)
0121Hissing Attribute value; a required Attribute Value (e.g., the Content Date for a Structured Report) was not supplied; the Attrib- ute(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.
C.23 Hanging Protocol Specific Modules
The following Sections specify Modules used for Hanging Protocols.
C.23.1 Hanging Protocol Definition Module
Table C.23.1-1 specifies the Attributes that describe and identify the high level definition of a Hanging Protocol, including its overall purpose, and the types of image sets to which it applies. See Annex V “Hanging Protocols (Informative)” in PS3.17 for further explan- ation.
Table C.23.1-1. Hanging Protocol Definition Module Attributes
Attribute Name |
Tag |
Type |
Attribute Description |
Hanging Protocol Name |
(0072,0002) |
1 |
Short descriptor that identifies the Hanging Protocol. |
Hanging Protocol |
(0072,0004) |
1 |
Explanation of the objective or intent of the Hanging Protocol. |
Description |
|
|
|
Hanging Protocol Level |
(0072,0006) |
1 |
Identifies the level at which this Hanging Protocol is defined, and the |
|
|
|
intended use. |
Enumerated Values:
MANUFACTURER
SITE
USER_GROUP
SINGLE_USER