This Application Profile facilitates the interchange of images and related data through e-mail.

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 present Application Profile does not include any specific mechanism regarding privacy. However it is highly recommended to use secure mechanisms (e.g. S/MIME) when using STD-GEN-MIME Application Profile over networks that are not otherwise secured.

G.2.1 Roles and Service Class Options

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

The Application Entity shall support one or two of the roles of File Set Creator (FSC) and File Set Reader (FSR), defined in PS 3.10. Because the exchange of e-mail does not involve storage, the role of File Set Updater (FSU) is not specified.

G.2.1.1 File Set Creator

The role of File Set Creator may be used by Application Entities which generate a File Set under this Interchange Class of Application Profiles.

File Set Creators may 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 included in the File Set.

The Application Entity acting as a File Set Creator generates a File Set under the STD-GEN-MIME Application Profile.

Note: A multiple volume (i.e. a logical volume that can cross multiple media) is not supported by this class of Application profile. Because MIME is a virtual medium and since e-mail mechanisms include some way of fragmenting MIME parts to be sent through limited size e-mail, there are no needs for multiple volume.

G.2.1.2 File Set Reader

The role of File Set Reader shall be used by Application Entities which receive an exchanged File Set under the Image Interchange Class of Application Profiles.

File Set Readers may be able to read the DICOMDIR directory file and shall be able to read all the SOP Instance files defined for this Application Profile, using the Transfer Syntaxes specified in the Conformance Statement.