Annex L (Normative) – ZIP File over Email Interchange Profiles

L.1 Profile Identification

This Annex defines three Application Profiles for interchange of a DICOM Data Set, encapsulated in a ZIP File, through email.

Two Application Profiles support all defined Media Storage SOP Classes. These are intended to be used for the interchange of Composite SOP Instances via email for general purpose applications. Objects from multiple modalities may be included on the same email. The email may also include non-DICOM objects. One of these general profiles supports encryption of the email.

A detailed list of the Media Storage SOP Classes is defined in PS 3.4

The other application profile is specialized for dental applications and adds mandatory requirements for dental images to the general secure email profile.

The specific Application Profiles are shown in Table L.1-1:

Table L.1-1

STD-x-ZIP-MAIL Application Profiles

Application Profile Identifier Description
General Purpose ZIP Email STD-GEN-ZIP-MAIL Interchange of Composite SOP Instances by email.
General Purpose Secure ZIP Email STD-GEN-SEC-ZIP-MAIL Interchange of Composite SOP Instances by encrypted email.
Dental Radiograph ZIP Email STD-DTL-SEC-ZIP-MAIL Interchange of dental radiographic images by encrypted email

L.2 CLINICAL CONTEXT

These Application Profiles facilitate the interchange of images and related data through email.

The STD-GEN-ZIP-MAIL and STD-GEN-SEC-ZIP-MAIL profiles are intended for general purpose applications. They are not intended as a replacement for specific Application Profiles that may be defined for a particular clinical context. The STD-DTL-SEC-ZIP-MAIL profile is intended for the clinical context of the exchange of dental radiographs.

Note: It is possible to use email transport without using the encrypted secure profile. This would make sense for mailing DICOM objects that do not need protection.

L.2.1 Roles

L.2.1.1 File Set Creator

The role of File Set Creators shall be used by Application Entities that generate a File-set under any of the profiles listed in Table L.1-1. Typical entities that will use this role would include systems assigned to send images by email attachment to other systems. File Set Creators shall be able to generate the DICOMDIR directory file, and any supported DICOM Storage SOP Class Information Object files.

L.2.1.2 File Set Reader

The role of File Set Reader shall be used by Application Entities that receive a transferred File Set. File Set Readers shall be able to read the DICOMDIR directory file and all Information Objects defined for the specific Application Profiles, using the defined Transfer Syntaxes.

L.2.1.3 File Set Updater

The role of File Set Updater is not defined for these Application Profiles.

L.3 GENERAL CLASS PROFILE

L.3.1 STD-GEN-ZIP-MAIL and STD-GEN-SEC-ZIP-MAIL Abstract and Transfer Syntaxes

Applications interchanging data under the STD-GEN-ZIP-MAIL and STD-GEN-SEC-ZIP-MAIL profiles shall support the Information Object Definitions (IOD) and Transfer Syntaxes for the Media Storage SOP Class specified in Table L.3-1.

Table L.3-1

STD-GEN-ZIP-MAIL and STD-GEN-SEC-ZIP-MAIL SOP Classes and Transfer Syntaxes

Information Object Definition Service Object Pair Class UID Transfer Syntax and UID FSC Requirement FSR Requirement
Basic Directory 1.2.840.10008.1.3.10 Explicit VR Little Endian Uncompressed 1.2.840.10008.1.2.1 Mandatory Mandatory
Composite Image & Stand-alone Storage Refer to: PS 3.4 for SOPs UID definitions Defined in Conformance Statement Defined in Conformance Statement Defined in Conformance Statement

Equipment claiming conformance to these Application Profiles shall list the subset of Media Storage SOP Classes and transfer syntaxes that it supports in its Conformance Statement.

L.3.2 Medium Format

The STD-GEN-ZIP-MAIL and STD-GEN-SEC-ZIP-MAIL application profiles shall use the ZIP File Media interchanged using the Email Media format as defined in PS3.12. This Email media shall comply with the following requirements:

  1. The content shall be identified as: Content-Type: application/zip

  2. The attachment shall be identified as: id="DICOM.ZIP"; name="DICOM.ZIP"

  3. The disposition shall be: Content-Disposition: attachment; filename="DICOM.ZIP"

  4. The email shall not be compressed.

  5. The subject line shall contain the phrase: DICOM-ZIP

Note: An additional content type, file extension and file name may be defined by the Standard in the future to accomodate a DICOM specific zip file.

L.3.3 Directory Information in DICOMDIR

The Directory shall include Directory Records of PATIENT, STUDY, SERIES, IMAGE corresponding to the information object files in the File Set. All DICOM files in the File Set incorporating SOP Instances (Information Objects) defined for the specific Application Profile shall be referenced by Directory Records.

Note: 1. DICOMDIRs with no directory information are not allowed by these Application Profiles.

There may only be one DICOMDIR file per File Set. The Patient ID at the patient level shall be unique for each patient directory record in one File Set.

L.3.3.1 Additional Keys

No additional keys are specified.

L.3.4 Secure Transport

The Email Media interchange under the STD-GEN-SEC-ZIP-MAIL profile shall use the Secure Use of Email Transport profile specified in PS3.15.

L.4 DENTAL CLASS PROFILE

L.4.1 STD-DTL-SEC-ZIP-MAIL Abstract and Transfer Syntaxes

Applications interchanging data under the STD-DTL-SEC-ZIP-MAIL profile shall support the Information Object Definitions (IOD) and Transfer Syntaxes for the Media Storage SOP Class specified in Table L.3-2. File Set Creators for the STD-FTL-SEC-ZIP-MAIL shall support at least one of the optional IODs.

Table L.3-2STD-DTL-SEC-ZIP-MAIL ABSTRACT AND TRANSFER SYNTAXES

Information Object Definition SOP Class UID Transfer Syntax and UID FSC Require ment FSR Require ment
Basic Directory 1.2.840.10008.1.3.10 Explicit VR Little Endian Uncompressed 1.2.840.10008.1.2.1 Mandatory Mandatory
Digital Intra-oral X-Ray Image Storage – For Presentation 1.2.840.10008.5.1.4.1.1.1.3 Explicit VR Little Endian Uncompressed 1.2.840.10008.1.2.1 Optional Mandatory
Digital X-Ray Image Storage – For Presentation 1.2.840.10008.5.1.4.1.1.1.1 Explicit VR Little Endian Uncompressed 1.2.840.10008.1.2.1 Optional Mandatory

L.4.2 Medium Format

The STD-DTL-SEC-ZIP-MAIL application profile shall use the ZIP File Media interchanged using the Email Media format as defined in PS3.12. This Email media shall comply with the following requirements:

  1. The content shall be identified as: Content-Type: application/zip

  2. The attachment shall be identified as: id="DICOM.ZIP"; name="DICOM.ZIP"

  3. The disposition shall be: Content-Disposition: attachment; filename="DICOM.ZIP"

  4. The email shall not be compressed.

  5. The subject line shall contain the phrase: DICOM-ZIP

Note: An additional content type, file extension and file name may be defined by the Standard in the future to accomodate a DICOM specific zip file.

L.4.3 Directory Information in DICOMDIR

The Directory shall include Directory Records of PATIENT, STUDY, SERIES, IMAGE corresponding to the information object files in the File Set. All DICOM files in the File Set incorporating SOP Instances (Information Objects) defined for the specific Application Profile shall be referenced by Directory Records.

Note: 1. DICOMDIRs with no directory information are not allowed by these Application Profiles.

There may only be one DICOMDIR file per File Set. The Patient ID at the patient level shall be unique for each patient directory record in one File Set.

L.4.4.1 Additional Keys

No additional keys are specified.

L.4.5 Specific Image Requirements for STD-DTL-SEC-ZIP-MAIL

For Digital Intra-oral X-Ray Image and Digital X-Ray Image Instances interchanged under the STD-DTL-SEC-ZIP-MAIL profile, the Attributes listed in Table L.4-1 used within the image instances shall take the values specified.

Table L.4-1STD-DTL-ZIP-MAIL - REQUIRED IMAGE ATTRIBUTE VALUES

Attribute Tag Value
Bits Allocated (0028,0100) If Bits Stored (0028,0101) is 8, then 8; otherwise 16.
Bits Stored (0028,0101) 8, 10, 12 or 16

The Attributes listed in Table L.4-2 shall have their Types specialized.

Table L.4-2STD-DTL-ZIP-MAIL - REQUIRED IMAGE ATTRIBUTE TYPES

Attribute Tag Type
Institution Name (0008,0080) 2
Manufacturer’s Model Name (0008,1090) 2
Detector ID (0018,700A) 2
Detector Manufacturer Name (0018,702A) 2
Detector Manufacturer’s Model Name (0018,702B) 2

Note: These Type 3 attributes of the General Equipment and DX Detector Module are specialized in order to encourage FSC’s to include values for them, recognizing that there are situations in which values may be unknown.

L.4.6 Secure Transport

The Email Media interchange under the STD-DTL-SEC-ZIP-MAIL profiles shall use the Secure Use of Email Transport profile specified in PS3.15.