These Application Profiles facilitate the interchange and storage of primary CT and MR images as well as related Secondary Capture Images with certain defined attributes, including grayscale and palette color images. CT, MR and SC images may co-exist within the same File-set.
Typical interchanges would be between acquisition devices, archives and workstations, within and between institutions.
These Application Profiles uses the Media Storage Service Class defined in PS 3.4.
The Application Entity shall support one or more of the roles of File-set Creator, File-set Reader, and File-set Updater, defined in PS 3.10.
The Application entity acting as a File-Set Creator generates a File Set under a STD-CTMR Application Profile. Typical entities using this role would include CT or MR equipment, and archive systems which generate a patient record for transfer to another institution. File Set Creators shall be able to generate the Basic Directory SOP Class in the DICOMDIR File with all types of Directory Records related to the SOP Classes stored in the File-set.
An FSC shall offer the ability to either finalize the disc at the completion of the most recent write session (no additional information can be subsequently added to the disc) or to allow multi-session (additional information may be subsequently added to the disc) or to allow packet-writing, if supported by the media and file system specified in the profile.
Note: A multiple volume (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, the FSC will create multiple independent DICOM File-sets such that each File-set can reside on a single physical volume 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 is used by Application Entities that receive a transferred File Set. Typical entities using this role would include display workstations, and archive systems that receive a patient record transferred from another institution. File Set Readers shall be able to read all the SOP Classes defined for the specific Application Profile for which a Conformance Statement is made, using all the defined Transfer Syntaxes.
The role of File Set Updater is used by Application Entities that receive a transferred File Set and update it by the addition of information. Typical entities using this role would include analytic workstations, which, for instance, may add to the File-set an information object containing a processed image. Stations that update patient information objects would also use this role. File-set Updaters do not have to read the images. File-set Updaters shall be able to generate one or more of the SOP Instances defined for the specific Application Profile for which a conformance statement is made, and to read and update the DICOMDIR file.
An FSU shall offer the ability to either finalize the disc at the completion of the most recent write session (no additional information can be subsequently added to the disc) or to allow multi-session (additional information may be subsequently added to the disc) 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.
The FSU role is not defined for the STD-CTMR-DVD profile.