D.3 STD-GEN Profile Class

D.3.1 SOP Classes and Transfer Syntaxes

This Application Profile is based on the Media Storage Service Class (see PS 3.4).

Table D.3-1STD-GEN SOP Classes and Transfer Syntaxes

Information Object Definition Service Object Pair Class UID Transfer Syntax and UID FSC Requirement FSR Requirement FSU Requirement
Basic Directory 1.2.840.10008.1.3.10 Explicit VR Little Endian Uncompressed 1.2.840.10008.1.2.1 Mandatory Mandatory Mandatory
Composite Image & Stand-alone Storage Refer to: PS 3.4 for SOPs UID definitions Explicit VR Little Endian Uncompressed 1.2.840.10008.1.2.1 Defined in Conformance Statement Defined in Conformance Statement Optional
The SOP Classes and corresponding Transfer Syntax supported by this Application Profile are specified in the Table D.3-1. The supported Storage SOP Class(es) shall be listed in the Conformance Statement using a table of the same form.

D.3.2 Physical Medium And Medium Format

The STD-GEN-CD and STD-GEN-SEC-CD application profiles require the 120 mm CD-R physical medium with the ISO/IEC 9660 Media Format, as defined in PS3.12.

The STD-GEN-DVD-RAM and STD-GEN-SEC-DVD-RAM application profiles require the 120 mm DVD-RAM medium, as defined in PS 3.12.

The STD-GEN-BD and STD-GEN-SEC-BD application profiles require any of the 120 mm BD media, as defined in PS 3.12.

D.3.3 Directory Information in DICOMDIR

Conformant Application Entities shall include in the DICOMDIR File the Basic Directory IOD containing Directory Records at the Patient and the subsidiary Study and Series levels, appropriate to the SOP Classes in the File Set.

All DICOM files in the File Set incorporating SOP Instances defined for the specific Application Profile shall be referenced by Directory Records.

Note: DICOMDIRs with no directory information are not allowed by this Application Profile.

All implementations shall include the DICOM Media Storage Directory in the DICOMDIR file. There shall only be one DICOMDIR file per File Set. The DICOMDIR file shall be in the root directory of the medium. The Patient ID at the patient level shall be unique for each patient directory record in one File Set.

D.3.3.1 Additional Keys

File Set Creators and Updaters are required to generate the mandatory elements specified in PS 3.3.

Table D.3-2 specifies the additional associated keys. At each directory record level other additional data elements can be added, but it is not required that File Set Readers be able to use them as keys. Refer to the Basic Directory IOD in PS 3.3.

Table D.3-2STD-GEN Additional DICOMDIR Keys

Key Attribute Tag Directory Record Type Type Notes
Image Type (0008,0008) IMAGE 1C Required if present in image object.
Referenced Image Sequence (0008,1140) IMAGE 1C Required if present in image object.
>Referenced SOP Class UID (0008,1150) IMAGE 1C Required if Referenced Image Sequence (0008,1140) is present
>Referenced SOP Instance UID (0008,1155) IMAGE 1C Required if Referenced Image Sequence (0008,1140) is present.

Note: The requirements with respect to the mandatory DICOMDIR keys in PS 3.3 imply that either these attributes are present in the Image IOD, or they are in some other way supplied by the File-set Creator. These attributes are (0010,0020) Patient ID, (0008,0020) Study Date, (0008,0030) Study Time, (0020,0010) Study ID, (0020,0011) Series Number, and (0020,0013) Instance Number.

D.3.3.2 Attribute value precedence

Retired. See PS 3.11 2004.

Note: The retired Detached Patient Management SOP Class was previously suggested to allow patient identification and demographic information to be updated without changing the composite Image IOD files. This usage is now retired.

D.3.4 Other Parameters

Not applicable.

D.3.5 Security Parameters

The STD-GEN-SEC-CD, STD-GEN-SEC-DVD-RAM and STD-GEN-SEC-BD application profiles require that all DICOM Files in the File-set including the DICOMDIR be Secure DICOM Files encapsulated in accordance with the requirements of the Basic DICOM Media Security Profile as defined in PS 3.15.

Note: These Application Profiles do not place any consistency restrictions on the use of the Basic DICOM Media Security Profile with different DICOM Files of one File-set. For example, readers should not assume that all Files in the File-set can be decoded by the same set of recipients. Readers should also not assume that all secure Files use the same approach (hash key or digital signature) to ensure Integrity or carry the same originators’ signatures.