PS-2020a / part11

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

Offers confidentiality, integrity and, depending on the File-set​ creator's choice, data origin authentication.​

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

J.2 Clinical Context​

ThisApplicationProfileClassfacilitatestheinterchangeofimagesandrelateddataonUSB,CF,MMCorSDmedia.Typicalinterchange​ would be between acquisition devices, archives and workstations.​

ThisApplicationProfileClassfacilitatesthecreationofamulti-modalitymediumforimageinterchange,usefulforclinical,patientrecord,​ 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.​

J.2.1 Roles and Service Class Options​

This Application Profile Class uses the Media Storage Service Class defined in PS3.4.​

- Standard -​

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

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

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-GEN-USB, STD-GEN-SEC-USB STD-GEN-MMC, STD-GEN-SEC-MMC, STD-GEN-CF, STD-GEN-SEC-CF, STD-GEN-SD​ or STD-GEN-SEC-SD Application 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).​

J.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 this Interchange Class of​ ApplicationProfiles.Typicalentitiesusingthisrolewouldincludeimagegeneratingsystems,displayworkstations,andarchivesystems​ 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.​

J.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 Applic-​ ation 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 Conform-​ ance Statement is made, and to read and update the DICOMDIR file.​

J.3 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 Profile​

Classes​

J.3.1 SOP Classes and Transfer Syntaxes​

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

- Standard -​

Table J.3-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 SOP Classes and Transfer Syntaxes​

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

J.3.2 Physical Medium and Medium Format​

TheSTD-GEN-USB-JPEG,STD-GEN-SEC-USB-JPEG,STD-GEN-USB-J2KandSTD-GEN-SEC-USB-J2Kapplicationprofilesrequire​ any of the USB Connected Removable Devices, as defined in PS3.12.​

The STD-GEN-MMC-JPEG, STD-GEN-SEC-MMC-JPEG, STD-GEN-MMC-J2K and STD-GEN-SEC-MMC-J2K application profiles​ require any of the Multimedia Card Removable Devices, as defined in PS3.12.​

The STD-GEN-CF-JPEG, STD- GEN-SEC-CF-JPEG, STD-GEN-CF-J2K and STD-GEN-SEC-CF-J2K application profiles require​ any of the CompactFlash Removable Devices, as defined in PS3.12.​

TheSTD-GEN-SD-JPEG,STD-GEN-SEC-SD-JPEG,STD-GEN-SD-J2KandSTD-GEN-SEC-SD-J2Kapplicationprofilesrequireany​ of the Secure Digital Card Removable Devices, as defined in PS3.12.​

- Standard -​

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

J.3.3.1 Additional Keys​

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

TableH.3-2specifiestheadditionalassociatedkeysthatshallalsobeapplicabletotheprofilesdefinedinthisAnnex.Ateachdirectory​ 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.​

J.3.4 Other Parameters​

J.3.4.2 Multi-frame JPEG Format​

The JPEG encoding of pixel data shall use Interchange Format (with table specification) for all frames.​

J.3.5 Security Parameters​

The STD-GEN-SEC-USB-JPEG, STD-GEN-SEC-MMC-JPEG, STD-GEN-SEC-CF-JPEG, STD-GEN-SEC-SD-JPEG, STD-GEN-​ SEC-USB-J2K, STD-GEN-SEC-MMC-J2K, STD-GEN-SEC-CF-J2K and STD-GEN-SEC-SD-J2K 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 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.​

- Standard -​

- Standard -​

K Dental Application Profile (Normative)​

K.1 Class and Profile Identification​

This Annex defines Application Profiles for Dental Media Storage applications.​

Table K.1-1. Dental Application Profile identifiers​

K.2 Clinical Context​

This Application Profile facilitates the interchange of dental data on media. Typical interchanges would be between dental systems,​ between a dental system and a display workstation, between display workstations, or between a dental system and a data archive.​ This context is shown in Figure K.2-1.​

Hospital or Physician

Removable Media

Figure K.2-1. Dental Clinical Context​

The operational use of the media transfer is potentially between private practitioners and an institution, intra-institutional and inter-​ institutional.​

K.2.1 Roles​

K.2.1.1 File Set Creator​

The role of File Set Creator shall be used by Application Entities that generate a File Set under the STD-DEN-CD Application Profile.​ Typical entities using this role would include dental imaging equipment, workstations, and archive systems that generate a patient​ record for transfer. File Set Creators shall be able to generate the Basic Directory SOP Class Instance in the DICOMDIR file and Di-​ gital Intra-oral X-Ray and Digital X-Ray Image Storage SOP Class Instances in the File Set.​

- Standard -​

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

Note​

A multiple volume (a logical volume that can cross multiple physical media) is not supported by this Application Profile Class.​ If a set of Files, e.g., a Study, cannot be written entirely on one CD-R, the FSC will create multiple independent DICOM File-​ sets such that each File-set can reside on a single CD-R media controlled by its individual DICOMDIR file. The user of the​ FSC can opt to use written labels on the discs to indicate that there is more than one disc for this set of files (e.g., a study).​

K.2.1.2 File Set Reader​

The role of File Set Reader shall be used by Application Entities that receive a transferred File Set. Typical entities using this role​ would include dental systems, display workstations, and archive systems that receive a patient record from a piece of media. File Set​ Readers shall be able to read the DICOMDIR directory file and all SOP Class Instances defined for this Application Profile, using the​ defined Transfer Syntaxes.​

K.2.1.3 File Set Updater​

The role of File Set Updater is not supported by this profile.​

K.3 General Class Profile​

K.3.1 SOP Classes and Transfer Syntaxes​

The Application Profile STD-DEN-CD shall support the SOP Classes and Transfer Syntaxes in the following table.​

Table K.3-1. Dental Abstract and Transfer Syntaxes​

Note​

The Digital X-Ray Image Storage and Digital Intra-oral X-Ray Image Storage For Presentation SOP Classes can also be​ used for scanned film.​

A File Set Creator (FSC) shall support at least one of the specified image storage SOP Classes.​

- Standard -​