This Annex defines an Application Profile Class potentially inclusive of all defined Media Storage SOP Classes. This class is intended to be used for the interchange of Composite SOP Instances via CD-R, DVD-RAM and BD media for general purpose applications.Objects from multiple modalities may be included on the same media.
A detailed list of the Media Storage SOP Classes that may be supported is defined in PS 3.4.
Table D.1-1 STD-GEN Profile
|General Purpose CD-R Interchange||STD-GEN-CD||Handles interchange of Composite SOP Instances such as Images, Structured Reports, Presentation States and Waveforms.|
|General Purpose Interchange on DVD-RAM Media||STD-GEN-DVD-RAM||Handles interchange of Composite SOP Instances such as Images, Structured Reports, Presentation States and Waveforms.|
|General Purpose Secure CD-R Interchange||STD-GEN-SEC-CD||Handles interchange of Composite SOP Instances such as Images, Structured Reports, Presentation States and Waveforms. Offers confidentiality, integrity and, depending on the File-set creator’s choice, data origin authentication.|
|General Purpose Secure Interchange on DVD-RAM Media||STD-GEN-SEC-DVD-RAM||Handles interchange of Composite SOP Instances such as Images, Structured Reports, Presentation States and Waveforms. Offers confidentiality, integrity and, depending on the File-set creator’s choice, data origin authentication.|
|General Purpose Interchange on BD Media||STD-GEN-BD||Handles Interchange of Composite SOP Instances such as Images, Structured Reports, Presentation States and Waveforms.|
|General Purpose Secure Interchange on BD Media||STD-GEN-SEC-BD||Handles Interchange of Composite SOP Instances such as Images, Structured Reports, Presentation States and Waveforms. Offers confidentiality, integrity and, depending on the File-set creator’s choice, data origin authentication.|
The identifier for this General Purpose Image Exchange profile class shall be STD-GEN.
Equipment claiming conformance to this Application Profile shall list the subset of Media Storage SOP Classes that it supports in its Conformance Statement.
Note: Since it is not required to support all Media Storage Classes the user should carefully consider the subset of supported Media Storage SOP Classes in the Conformance Statements of such equipment to establish effective object interchange.
This Application Profile facilitates the interchange of images and related data on CD-R, DVD-RAM and BD media. Typical interchange would be between acquisition devices, archives and workstations.
This Application Profile facilitates the creation of a multi-modality medium for image interchange, useful for clinical, patient record, teaching and research applications, within and between institutions.
This profile is intended only for general purpose applications. It is not intended as a replacement for specific Application Profiles that may be defined for a particular clinical context. The latter may support compression transfer syntaxes, limitations on the form and content of SOP Class instances, and specific media choices that preclude the use of the General Purpose Interchange Profile.
Note: The creation of a CD, DVD-RAM or BD is considerably more complex than the reading thereof. Therefore the clinical context for this Application profile is likely to be asymmetric, with a sophisticated File Set Creator and relatively simple File Set Readers.
This Application Profile uses the Media Storage Service Class defined in PS3.4.
The Application Entity shall support one or more of the roles of File Set Creator (FSC), File Set Reader (FSR), and File Set Updater (FSU), defined in PS 3.10.
The role of File Set Creator shall be used by Application Entities which generate a File Set under this Image Interchange Class of Application Profiles.
File Set Creators shall be able to generate the Basic Directory SOP Class in the DICOMDIR file with all the subsidiary Directory Records related to the Image SOP Classes stored in the File Set.The Application Entity acting as a File Set Creator generates a File Set under a STD-GEN Application Profile.
FSC shall offer the ability to either finalize the physical volume at the completion of the most recent write session (no additional information can be subsequently added to the volume) or to allow multi-session (additional information may be subsequently added to the volume) or to allow packet-writing, if supported by the media and file system specified in the profile.
Note: A multiple volume (i.e. a logical volume that can cross multiple physical media) is not supported by this class of Application profile. If a set of Files, e.g., a Study, cannot be written entirely on one physical volume (side of one piece of media), the FSC will create multiple independent DICOM File Sets such that each File Set can reside on a single physical volume (side of a single piece of media) controlled by its individual DICOMDIR file. The user of the FSC can opt to use written labels on the physical volumes to indicate that there is more than one physical volume for this set of files (e.g., a study).
The role of File Set Reader shall be used by Application Entities that receive a transferred File Set under the Image Interchange Class of Application Profiles. Typical entities using this role would include image generating systems, display workstations, and archive systems that receive a patient record; e.g. transferred from another institution.
File Set Readers shall be able to read the DICOMDIR directory file and all the SOP Instance files defined for this Application Profile, for which a Conformance Statement is made, using the defined Transfer Syntax.
The role of File Set Updater is used by Application Entities which receive a transferred File Set under the Image Exchange Class of Application Profiles and update it by the addition (or deletion) of images or information to (or from) the medium. Typical entities using this role would include image generating systems and workstations that process or modify images.
File Set Updaters shall be able to generate one or more of the SOP Instances defined for this Application Profile, for which a Conformance Statement is made, and to read and update the DICOMDIR file.
FSU shall offer the ability to either finalize the physical volume at the completion of the most recent write session (no additional information can be subsequently added to the volume) or to allow multi-session (additional information may be subsequently added to the volume) or to allow packet-writing. if supported by the media and file system specified in the profile.
Note: If the volume has not been finalized, the File Set Updater will be able to update information assuming there is enough space on the volume to write a new DICOMDIR file, the information, and the fundamental volume control structures. Volume control structures are the structures that are inherent to the standards of the physical volume, see PS 3.12.
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 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.
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.
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.
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.
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.