1 / 7

Email Transport Requirements: Maximal Re-Use and Enhanced Security

This visual highlights the requirements for email transport, focusing on maximal re-use of existing email clients and enhanced security features. It also covers the incorporation of non-DICOM content, multiple email messages, encryption, and handling of large files.

parkersons
Download Presentation

Email Transport Requirements: Maximal Re-Use and Enhanced Security

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Email transport requirements Example of an opening slide Feel free to use this visual on your opening slide, or change it according to the subject of the presentation

  2. Goals • Maximal re-use of existing email clients recipient side • Single-click save (security must support), single click per email if split over multiple emails • (optional) Integrable into DICOM app • 64-yr old high school dropout operator • Maximal re-use of existing dental CDROM receiving software training. • Incorporate non-DICOM content, especially for transfer to insurers. (E.g., PDI approach of send DICOM with optional equivalent JPEG) • Multiple email messages to deal with size (Should also work across small media) • (integrity check) • Send image by image or full study • Support return receipt requested • ?? Encryption different than CMS envelope ?? • PGP • Naïve S/MIME • ?? Compression different than DICOM/CMS ?? • Survive firewall administrators, spam filters • Include non-DICOM stuff as part of the package

  3. ISO Image/ CMS coded (zip, tar, iso, etc.) Multi-part integrity Per DICOM object Use media security Set validation DICOMDIR ? Part 86 manifest ? Both? S/MIME per email Multi-part integrity Per DICOM object? Per email? Use part 86 signed manifest for full set Images/studies will be split into multiple emails

  4. Other • Insurer, individual practice, individual person must provide a public key (encoded as X.509 cert) to anyone who will send media. Either PKI or out-of-band. (Administrative issue. N.B. SPC paper on certificates) • Multi-recipient encryption (all mechanisms do this) • Recommend same encryption algorithm rules as in Supplement 51/55. • Require encryption, (security, spam filters) • Mandate neutral, recognizable subject titles

  5. Return Receipt • For streaming, “when I see the manifest the transmission is done.” (out of order arrival, use manifest to tell when done if manifest is sent early.) Manifest timeout value? Other failure modes. • Use a manifest as the return receipt? Use X-tags? Use another normalized-object? (n.b., generating a return receipt requires a DICOM aware application.)

  6. Do’s and Don’ts (cont’d) • Do • Create an additional slide in stead • Use keywords and explain while presenting • Specify date and presenter’s name below (via Slide Master) • Don’t • Use a slide as a speaker note

  7. Do’s and Don’ts (cont’d) • Don’t • Vary excessively with colors • Do • Use the colors pre-defined in your palette. They correspond with the Agfa Style Guide, use them for backgrounds, frames etc.

More Related