N.2 Clinical Context

N.2 Clinical Context (Current)
Prev	N General Purpose BD With MPEG-4 AVC/H.264 Level 4.2 Compression Interchange Profiles (Normative)	Next

This Application Profile Class facilitates the interchange of images and related data on BD media. Typical interchange would be between acquisition devices, archives and workstations.

This Application Profile Class 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.

Note

The creation of a 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.
Each BD Rewritable/Recordable contains a unique ID, which can be read by a BD drive. This ID can be used for referring to a BD, for example in a database.

N.2.1 Roles and Service Class Options

This Application Profile Class uses the Media Storage Service Class defined in PS3.4 with the Interchange Option.

The Application Entity shall support one or more of the roles of File-set Creator (FSC) or File-set Reader (FSR) , or File-set Updater (FSU) defined in PS3.10.

N.2.1.1 File-set Creator

The role of File-set Creator shall be used by Application Entities that generate a File-set under this 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-BD-MPEG4-LV42 or STD-GEN-SEC-BD-MPEG4-LV42 Application Profile.

An FSC shall offer the ability to finalize the physical volume at the completion of the most recent write session (no additional information can be subsequently added to the volume) , 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).

N.2.1.2 File-set Reader

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 all the defined Transfer Syntaxes for the Profile.

Note

All Transfer Syntaxes defined in the profile must be supported by the FSR. It is not permissible to only support one or other of the uncompressed or the compressed Transfer Syntaxes.

N.2.1.3 File-set Updater

The role of File-set Updater is used by Application Entities that receive a transferred File-set under this Interchange 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.

An FSU shall offer the ability to finalize the physical volume at the completion of the most recent write session (no additional information can be subsequently added to the volume) , 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 PS3.12.