Digital Imaging and Communications in Medicine (DICOM) - Application/dicom MIME Sub-type Registration (RFC3240)
Original Publication Date: 2002-Feb-01
Included in the Prior Art Database: 2002-Feb-14
Internet Society Requests For Comment (RFCs)
D. Clunie: AUTHOR [+2]
This document describes the registration of the MIME sub-type application/dicom (Digital Imaging and Communications in Medicine). The baseline encoding is defined by the DICOM Standards Committee in "Digital Imaging and Communications in Medicine".
Network Working Group D. Clunie
Request for Comments: 3240 E. Cordonnier
Category: Informational DICOM Committee
Digital Imaging and Communications in Medicine (DICOM) -
Application/dicom MIME Sub-type Registration
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright (C) The Internet Society (2002). All Rights Reserved.
This document describes the registration of the MIME sub-type
application/dicom (Digital Imaging and Communications in Medicine).
The baseline encoding is defined by the DICOM Standards Committee in
"Digital Imaging and Communications in Medicine".
1. DICOM Definition
Digital Imaging and Communications in Medicine (DICOM) specifies
protocols and formats for the exchange of images, time-based
waveforms, reports, and associated information for medical
Individual DICOM objects (such as images) may be encapulsated in
files and exchanged by e-mail using the Media Type defined herein.
In addition, a set of DICOM files may be described by an index file,
DICOMDIR, which may accompany the files that it references.
2. IANA Registration
MIME media type name: Application
MIME subtype name: dicom
Clunie, et al. Informational [Page 1]
RFC 3240 Application/dicom MIME Sub-type Registration February 2002
"id" is constructed from a DICOM File ID (see DICOM PS3.11). The
total length is limited to 71 characters. Each component is
limited to 8 characters. The delimiter is a forward slash "/".
There is never a leading delimiter (i.e., this is not a
traditional path from a root directory).
If a DICOMDIR (which provides an index of files) is included, then
it will refer to other DICOM files in the file set by use of this
File ID. The File ID is not encoded within each DICOM file. If a
DICOMDIR is not present, then the "id" parameter may be absent.
Note that the DICOMDIR will also have a Media Type of
application/dicom and is distinguished from other files by its ID
Each component shall be character strings made of characters from
a subset of the G0 repertoire of ISO 8859. This subset consists
of uppercase alphabetic characters, numeric characters and
underscore. The following characters are permissable:
A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V,
W, X, Y, Z (uppercase)
1, 2, 3, 4, 5, 6, 7, 8, 9, 0 and _ (underscore)
The DICOM information is binary, therefore the encoding used shall
support lossless transfer of binary information. Typically, the
Content-Transfer-Encoding would be set to "Base64".
Multiple DICOM parts should be included as a Multipart/related
entity . Receiving agents shall also support multiple parts
as a Multipart/mixed entity. When multiple DICOM parts are