Файл: part11.pdf

- Standard -​

I DVD MPEG2 Interchange Profiles​ (Normative)​

I.1 Profile Identification​

This Annex defines an Application Profile Class for all multi-frame Media Image Storage SOP Classes compressed with MPEG2.​

Table I.1-1. STD-DVD-MPEG2-MPML and STD-DVD-SEC-MPEG2-MPML Profiles​

Equipment claiming conformance to this Application Profile shall list the subset of Media Storage SOP Classes that it supports in its​ Conformance Statement.​

I.2 Clinical Context​

ThisApplicationProfileClassfacilitatestheinterchangeofimagesdataonDVDmedia.Typicalinterchangewouldbebetweenacquis-​ ition devices, archives and workstations.​

I.2.1 Roles and Service Class Options​

This Application Profile Class 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) or File Set Reader (FSR), defined in PS3.10.​ The File Set Updater (FSU) role is not defined.​

I.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 Image Interchange Class of Ap-​ plication Profiles.​

FileSetCreatorsshallbeabletogeneratetheBasicDirectorySOPClassintheDICOMDIRfilewithallthesubsidiaryDirectoryRecords​ 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-DVD-MPEG2-MPML or STD-DVD-SEC-MPEG2-MPML Application Profile.​

FSCshalloffertheabilitytoeitherfinalizethephysicalvolumeatthecompletionofthemostrecentwritesession(noadditionalinform-​ ation can be subsequently added to the volume) or to allow multi-session (additional information may be subsequently added to the​ volume). An FSC may 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).​

- Standard -​

I.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.​

I.2.1.3 File Set Updater​

The FSU role is not defined for the STD-DVD-MPEG2-MPML and STD-DVD-SEC-MPEG2-MPML profiles.​

I.3 STD-DVD-MPEG2-MPML and STD-DVD-SEC-MPEG2-MPML Profile Classes​

I.3.1 SOP Classes and Transfer Syntaxes​

This Application Profile is based on the Media Storage Service Class (see PS3.4).​

Table I.3-1. STD-DVD-MPEG2-MPML and STD-DVD-SEC-MPEG2-MPML SOP Classes and Transfer​

Syntaxes​

The SOP Classes and corresponding Transfer Syntax supported by this Application Profile are specified in the Table I.3-1. The sup-​ ported Storage SOP Class(es) shall be listed in the Conformance Statement using a table of the same form.​

I.3.2 Physical Medium and Medium Format​

The STD-DVD-MPEG2-MPML and STD-DVD-SEC-MPEG2-MPML application profiles require any of the 120 mm DVD media other​ than DVD-RAM, as defined in PS3.12.​

I.3.3 Directory Information in DICOMDIR​

ConformantApplicationEntitiesshallincludeintheDICOMDIRFiletheBasicDirectoryIODcontainingDirectoryRecordsatthePatient​ 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.​

- Standard -​

I.3.3.1 Additional Keys​

File Set Creators and Updaters are required to generate the mandatory elements specified in PS3.3.​

Table I.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 PS3.3.​

Table I.3-2. STD-DVD-MPEG2-MPML and STD-DVD-SEC-MPEG2-MPML Additional DICOMDIR Keys​

Note​

The requirements with respect to the mandatory DICOMDIR keys in PS3.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) In-​ stance Number.​

I.3.4 Security Parameters​

TheSTD-DVD-SEC-MPEG2-MPMLapplicationprofilesrequirethatallDICOMFilesintheFile-setincludingtheDICOMDIRbeSecure​ DICOM Files encapsulated in accordance with the requirements of the Basic DICOM Media Security Profile as defined in PS3.15.​

Note​

These Application Profiles do not place any consistency restrictions on the use of the Basic DICOM Media Security Profile​ withdifferentDICOMFilesofoneFile-set.Forexample,readersshouldnotassumethatallFilesintheFile-setcanbedecoded​ 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.​

I.3.5 "dual-format" (informative)​

It is desirable that consumer DVD players (and computer software for playing conventional DVD movies) be able to play the video​ data that is encoded on the DICOM DVD. The MPEG2 bit stream that is "encapsulated" by the DICOM Transfer Syntax is potentially​ re-usable by such applications, if the appropriate UDF structure is created to share the same extent between the DICOM file and the​ file format and folder structure used by the consumer DVD Video format. Alternatively, the bit stream could be duplicated and both​ sets of files present on the same piece of media.​

This profile does not require this, nor specify which approach to take. Specifically, this profile does not require that a DVD Video file​ and folder structure be present, though it is recommended.​

- Standard -​

- Standard -​

J General Purpose USB and Flash Memory​ With Compression Interchange Profiles​ (Normative)​

J.1 Profile Identification​

This Annex defines an Application Profile Class potentially inclusive of all defined Media Storage SOP Classes. This class is intended​ tobeusedfortheinterchangeofCompositeSOPInstancesviaUSB,CF,MMCorSDmediaforgeneral-purposeapplications.Objects​ from multiple modalities may be included on the same media. Images may be compressed with or without loss using either JPEG or​ JPEG 2000; all File Set Readers are required to support decompression of all of the compressed Transfer Syntaxes defined for each​ Profile.​

A detailed list of the Media Storage SOP Classes that may be supported is defined in PS3.4.​

Table J.1-1. STD-GEN-USB, STD-GEN-SEC-USB STD-GEN-MMC, STD-GEN-SEC-MMC, STD-GEN-CF,​

STD-GEN-SEC-CF, STD-GEN-SD and STD-GEN-SEC-SD Profiles​

- Standard -​