Digital Imaging and Communications in Medicine (DICOM

Digital Imaging and Communications in Medicine (DICOM)8

Supplement 54: DICOM MIME Type

Prepared by:

DICOM Standards Committee23

1300 N. 17th Street24

Rosslyn, Virginia 22209 USA25

VERSION: Final Text28

March 10, 200229

Supplement 54: DICOM MIME Type

Page i

Table of Contents30

Foreword.................................................................................................................................................................ii31

1 Supplement Scope and Field of Application........................................................................................... 132

Part 11, Body Addendum ...................................................................................................................................... 233

4 Symbols and abbreviations ..................................................................................................................... 234

Annex Y (Normative) - General Purpose MIME Interchange Profile................................................................... 235

Y.1 PROFILE IDENTIFICATION ......................................................................................................... 236

Y.2 CLINICAL CONTEXT .................................................................................................................... 337

Y.2.1 ROLES AND SERVICE CLASS OPTIONS.................................................................................. 338

Y.2.1.1 File Set Creator................................................................................................................ 339

Y.2.1.2 File Set Reader ................................................................................................................ 340

Y.3 STD-GEN-MIME PROFILE........................................................................................................... 341

Y.3.1 SOP Classes and Transfer Syntaxes................................................................................. 342

Y.3.2 Physical Medium and Medium Format ............................................................................... 443

Y.3.3 Directory Information in DICOMDIR ................................................................................... 444

Y.3.3.1 Additional Keys ................................................................................................................ 445

Part 12, Body Addendum ...................................................................................................................................... 546

2 References ............................................................................................................................................... 547

ANNEX X (Normative) DICOM MIME media ....................................................................................................... 548

X.1 DICOM MAPPING TO MIME FORMATS ............................................................................................... 549

X.1.1 DICOM File set............................................................................................................................... 550

X.1.2 DICOM file ...................................................................................................................................... 551

X.1.2.1 DICOMDIR ........................................................................................................................ 652

X.3 LOGICAL FORMAT ................................................................................................................................. 653

RFC 3240 – Digital Imaging and Communications in Medicine (DICOM) – Application/dicom MIME Sub-54

type Registration (Informative).............................................................................................................................. 755

Example 1: Simple DICOM File MIME message (Informative) .....................................................................121456

Example 2: DICOM File Set MIME message (Informative)...........................................................................141657

Supplement 54: DICOM MIME Type

Page ii

Foreword59

The American College of Radiology (ACR) and the National Electrical Manufacturers Association (NEMA)60

formed a joint committee to develop a standard for Digital Imaging and Communications in Medicine61

(DICOM). This DICOM Standard and the corresponding Supplements to the DICOM Standard were62

developed according to the NEMA procedures.63

DICOM is developed in liaison with other standardization organizations including CEN TC251 in Europe64

and JIRA in Japan, with review also by other organizations including IEEE, HL7 and ANSI in the USA.65

This document is a Supplement to the DICOM Standard. It is an extension to PS 3.11 and 3.12 of the66

published DICOM Standard which consists of the following parts:67

PS 3.1 Introduction and Overview68

PS 3.2 Conformance69

PS 3.3 Information Object Definitions70

PS 3.4 Service Class Specifications71

PS 3.5 Data Structures and Encoding72

PS 3.6 Data Dictionary73

PS 3.7 Message Exchange74

PS 3.8 Network Communication Support for Message Exchange75

PS 3.9 Point-to-Point Communication Support for Message Exchange76

PS 3.10 Media Storage and File Format77

PS 3.11 Media Storage Application Profiles78

PS 3.12 Media Format and Physical Media for Media Interchange79

PS 3.13 Print Management Point-to-Point Communication Support80

PS 3.14 Grayscale Standard Display Function81

PS 3.15 Security Profiles82

PS 3.16 Content Mapping Resource83

These parts are related but independent documents.84

This Supplement includes the definition of DICOM MIME Type definition, which enables applications to85

exchange DICOM objects with other applications that support communication by e-mail.86

Supplement 54: DICOM MIME Type

Page 1

1 Supplement Scope and Field of Application87

This Supplement describes the DICOM MIME Type. MIME (Multipurpose Internet Mail Extension)88

describes how to include attached files as “parts” into internet mail, these may be sent by protocols such89

as SMTP (Simple Mail Transfer Protocol).90

DICOM network protocols are widely used for applications that:91

— involve primary diagnosis and review,92

— are used within a tightly integrated imaging department93

— are used when there is controlled distribution of images (and other DICOM objects) to other94

departments which also support DICOM protocols.95

DICOM network protocols are less frequently used for applications in areas less amenable to tight96

integration, such as:97

— hospital-to-doctor DICOM object distribution for reviewing or referral purposes98

— exchange of DICOM objects for testing purposes99

— DICOM object distribution for education, scientific cooperation and contract research100

— interpretation by professionals at home (e.g. teleradiology)101

These applications are characterized by:102

— greater desire to integrate with consumer desktop applications103

— lower expectations of image quality, fidelity, reliability of delivery and conformance104

— less centralized control over system setup and configuration105

There has been an increasing demand for the ability to exchange DICOM objects by e-mail.106

The DICOM MIME Type concept covers two levels:107

— the DICOM File level, using the Application/dicom MIME Type108

— the DICOM File-set level, using the Multipart/mixed MIME Type with some constraints109

(naming, parameters)110

Note: No Image/dicom MIME type is proposed, because DICOM objects may also contain other information,111

not only images.112

Since this document proposes changes to existing Parts of DICOM the reader should have a working113

understanding of the Standard.114

After having introduced the interest of such an extension of DICOM, this document includes a number of115

Addenda to existing Parts of DICOM:116

PS 3.11 Addendum Annex XX: General Purpose MIME Interchange Profile117

PS 3.12 Addendum Annex XX: DICOM MIME Type118

In addition, it contains the official text of the RFC (Request for Comments) to be submitted to the Internet119

Engineering Task Force (IETF) and defining the Application/dicom MIME Type. Once approved this120

RFC text will be included as an appendix to Part 12.121

Finally it presents two examples of e-mail messages that can be generated by using DICOM MIME Type.122

Supplement 54: DICOM MIME Type

Page 2

Part 11, Body Addendum123

Add the following definitions to Section 4. Symbols and abbreviations.124

4 Symbols and abbreviations125

IETF Internet Engineering Task Force126

MIME Multipurpose Internet Mail Extension127

RFC Request for Comments128

SMTP Simple Mail Transfer Protocol129

Add the following Annex at the end of the document.130

Annex Y (Normative) - General Purpose MIME Interchange Profile131

Y.1 PROFILE IDENTIFICATION132

This Annex defines an Application Profile Class including all defined Media Storage SOP Classes. This133

class is intended to be used for the interchange of Composite SOP Instances via e-mail for general134

purpose applications.135

Note: This Media Storage Application Profile Class is not intended to replace the more robust DICOM Storage136

Service Class.137

Objects from multiple modalities may be included on the same e-mail. A detailed list of the Media Storage138

SOP Classes that may be supported is defined in PS 3.4.139

Table Y.1-1140

STD-GEN-MIME Profile141

Application Profile

Identifier

Description

General Purpose MIME

Interchange

STD-GEN-MIME

Handles interchange of Composite SOP Instances by

e-mail.

142

The identifier for this General Purpose MIME Interchange profile shall be STD-GEN-MIME.143

Equipment claiming conformance to this Application Profile shall list the subset of Media Storage SOP144

Classes that it supports in its Conformance Statement.145

Supplement 54: DICOM MIME Type

Page 3

Note: Since it is not required to support all Media Storage Classes the user should carefully consider the146

subset of supported Media Storage SOP Classes in the Conformance Statements of such equipment to147

establish effective object interchange.148

Y.2 CLINICAL CONTEXT149

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

This profile is intended only for general purpose applications. It is not intended as a replacement for151

specific Application Profiles that may be defined for a particular clinical context.152

Note: The present Application Profile does not include any specific mechanism regarding privacy. However it is153

highly recommended to use secure mechanisms (e.g. S/MIME) when using STD-GEN-MIME Application154

Profile over networks that are not otherwise secured.155

156

Y.2.1 ROLES AND SERVICE CLASS OPTIONS157

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

Option.159

The Application Entity shall support one or two of the roles of File Set Creator (FSC) and File Set Reader160

(FSR), defined in PS 3.10. Because the exchange of e-mail does not involve storage, the role of File Set161

Updater (FSU) is not specified.162

Y.2.1.1 File Set Creator163

The role of File Set Creator may be used by Application Entities which generate a File Set under this164

Interchange Class of Application Profiles.165

File Set Creators may be able to generate the Basic Directory SOP Class in the DICOMDIR file with all the166

subsidiary Directory Records related to the Image SOP Classes included in the File Set.167

The Application Entity acting as a File Set Creator generates a File Set under the STD-GEN-MIME168

Application Profile.169

Note: A multiple volume (i.e. a logical volume that can cross multiple media) is not supported by this class of170

Application profile. Because MIME is a virtual medium and since e-mail mechanisms include some way171

of fragmenting MIME parts to be sent through limited size e-mail, there are no needs for multiple volume.172

Y.2.1.2 File Set Reader173

The role of File Set Reader shall be used by Application Entities which receive an exchanged File Set174

under the Image Interchange Class of Application Profiles.175

File Set Readers may be able to read the DICOMDIR directory file and shall be able to read all the SOP176

Instance files defined for this Application Profile, using the Transfer Syntaxes specified in the Conformance177

Statement.178

Y.3 STD-GEN-MIME PROFILE179

Y.3.1 SOP Classes and Transfer Syntaxes180

This Application Profile is based on the Media Storage Service Class with the Interchange Option (see PS181

3.4).182

Supplement 54: DICOM MIME Type

Page 4

Table Y.3-1183

STD-GEN-MIME SOP Classes and Transfer Syntaxes184

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

Optional

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

185

The SOP Classes and corresponding Transfer Syntax supported by this Application Profile are specified in186

the Table Y.3-1. The supported Storage SOP Class(es) and Transfers Syntax(es) shall be listed in the187

Conformance Statement using a table of the same form.188

Y.3.2 Physical Medium and Medium Format189

The STD-GEN-MIME application profile requires the DICOM MIME medium as defined in PS3.12.190

Y.3.3 Directory Information in DICOMDIR191

If the DICOMDIR is included, conformant Application Entities shall include in it the Basic Directory IOD192

containing Directory Records at the Patient and the subsidiary Study and Series levels, appropriate to the193

SOP Classes in the File Set.194

All DICOM files in the File Set incorporating SOP Instances defined for the specific Application Profile shall195

be referenced by Directory Records.196

Note: 1. DICOMDIRs with no directory information are not allowed by this Application Profile.197

2. In the DICOMDIR each object may be referenced by a referenced file ID (e.g. 000/000) which198

contains multiple values corresponding to a path for physical system, since the MIME organization is flat.199

There is no requirement that this path will be used by the receiving application to create file hierarchy.200

There may only be one DICOMDIR file per File Set. The Patient ID at the patient level shall be unique for201

each patient directory record in one File Set.202

Y.3.3.1 Additional Keys203

No additional keys are specified.204

Supplement 54: DICOM MIME Type

Page 5

Part 12, Body Addendum205

Add the following definitions to Section 2. Normative References.206

2 Normative References207

RFC 3240, Digital Imaging and Communications in Medicine (DICOM) - Application/dicom MIME208

Sub-type Registration209

210

The concepts “MIME”, “Media Type”, “MIME Entity”, "MIME Part", “Content-Type”, “Multipart/mixed”,211

“Message/partial”, “Content-Transfer-Encoding”, “Content-ID” and “Application/xx” are developed212

in IETF “Multipurpose Internet Mail Extensions”, or “MIME”, described in RFC (Request for Comments)213

number 2045, 2046, 2047, 2048 and 2049 (see http://www.imc.org/rfc2045 and ftp://ftp.isi.edu/in-214

notes/rfc2045.txt).215

Add the following Annex at the end of the document.216

ANNEX X (Normative) DICOM MIME media217

X.1 DICOM MAPPING TO MIME FORMATS218

X.1.1 DICOM File set219

One DICOM File set shall be contained in a MIME Multipart/mixed or Multipart/related Media220

Type, called "DICOM File set" MIME Entity.221

Notes: 1. It may be necessary to fragment a message by using the Message/partial Media Type format.222

2. A "DICOM File set" MIME Entity may contain MIME Parts other than Application/dicom which223

may be ignored by the DICOM application.224

X.1.2 DICOM file225

Each generic DICOM file shall be encoded as a MIME Application/dicom Media Type, called "DICOM226

File" MIME Part, with the following parameters:227

- “id” is constructed from the DICOM File ID. The total length is limited to 71 characters (to avoid that228

the e-mail application splits the id string). Each component is limited to 8 characters. The delimiter is a229

forward slash “/”. There is never a leading delimiter (i.e. this is not a traditional path from a root230

directory).231

For example: “ROOTDIR/SUBDIR1/MRSCAN/A789FD07/19991024/ST00234/S00003/I00023”232

Supplement 54: DICOM MIME Type

Page 6

- "name" is constructed from the last DICOM File ID component (that means the “file name” without233

“path” information) and the extension ".dcm" (except for the DICOMDIR).234

For example: “I00023.dcm”235

Note: 1. Email clients typically use this parameter as the default name with which to save the file. If used for236

only one "DICOM File" Part (versus one DICOM File set), the length of this parameter is not restricted237

(unlike the “id” parameter).238

2. This name can not be the same as the name inside the DICOMDIR where the file extension is239

forbidden.240

241

The other fields of the header of this "DICOM File" MIME Part are respecting the general rules of MIME.242

X.1.2.1 DICOMDIR243

One and only one DICOMDIR File may be present in any "DICOM File set" MIME Entity. It is encoded as244

the generic "DICOM File" MIME Part, with a DICOM File ID set to “DICOMDIR” and the “id” parameter set245

to “DICOMDIR”.246

X.3 LOGICAL FORMAT247

The MIME logical format is used. The Content-Transfer-Encoding shall allow the transfer of binary248

information (e.g. typically base64 if the higher level does not allow transfer of binary information).249

Supplement 54: DICOM MIME Type

Page 7

Add the following Annex at the end of the PS 3.12.250

ANNEX Y (Informative) RFC 3240 – Digital Imaging and Communications in251

Medicine (DICOM) – Application/dicom MIME Sub-type Registration252

Network Working Group D. Clunie253

Request for Comments: 3240 E. Cordonnier254

Category: Informational DICOM Committee255

February 2002256

257

258

Digital Imaging and Communications in Medicine (DICOM) -259

Application/dicom MIME Sub-type Registration260

261

Status of this Memo262

263

This memo provides information for the Internet community. It does264

not specify an Internet standard of any kind. Distribution of this265

memo is unlimited.266

267

269

271

Abstract272

273

This document describes the registration of the MIME sub-type274

application/dicom (Digital Imaging and Communications in Medicine).275

The baseline encoding is defined by the DICOM Standards Committee in276

"Digital Imaging and Communications in Medicine".277

278

1. DICOM Definition279

280

Digital Imaging and Communications in Medicine (DICOM) specifies281

protocols and formats for the exchange of images, time-based282

waveforms, reports, and associated information for medical283

applications.284

285

Individual DICOM objects (such as images) may be encapulsated in286

files and exchanged by e-mail using the Media Type defined herein.287

In addition, a set of DICOM files may be described by an index file,288

DICOMDIR, which may accompany the files that it references.289

290

2. IANA Registration291

292

MIME media type name: Application293

294

MIME subtype name: dicom295

296

Required parameters:297

Supplement 54: DICOM MIME Type

Page 8

298

"id" is constructed from a DICOM File ID (see DICOM PS3.11). The299

total length is limited to 71 characters. Each component is300

limited to 8 characters. The delimiter is a forward slash "/".301

There is never a leading delimiter (i.e., this is not a302

traditional path from a root directory).303

304

If a DICOMDIR (which provides an index of files) is included, then305

it will refer to other DICOM files in the file set by use of this306

File ID. The File ID is not encoded within each DICOM file. If a307

DICOMDIR is not present, then the "id" parameter may be absent.308

Note that the DICOMDIR will also have a Media Type of309

application/dicom and is distinguished from other files by its ID310

of "DICOMDIR".311

312

For example:313

"ROOTDIR/SUBDIR1/MRSCAN/A789FD07/19991024/ST00234/S00003/I00023"314

315

Each component shall be character strings made of characters from316

a subset of the G0 repertoire of ISO 8859. This subset consists317

of uppercase alphabetic characters, numeric characters and318

underscore. The following characters are permissable:319

320

A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V,321

W, X, Y, Z (uppercase)322

1, 2, 3, 4, 5, 6, 7, 8, 9, 0 and _ (underscore)323

324

Optional parameters:325

326

none327

328

Encoding considerations:329

330

The DICOM information is binary, therefore the encoding used shall331

support lossless transfer of binary information. Typically, the332

Content-Transfer-Encoding would be set to "Base64".333

334

Multiple DICOM parts should be included as a Multipart/related335

entity [2387]. Receiving agents shall also support multiple parts336

as a Multipart/mixed entity. When multiple DICOM parts are337

included, one of the parts may be a DICOMDIR, in which case, all338

the files referred to by the DICOMDIR shall also be present. The339

DICOMDIR is not required to be the first Application/dicom part340

encoded in the message, in which case the optional "start"341

parameter should refer to the content-id of the part containing342

the DICOMDIR.343

344

Multiple DICOM Application/dicom parts may be included with other345

types of parts as a Multipart/mixed entity.346

347

Security considerations:348

349

Application/dicom parts contain medical information, including350

individual demographic information. Accordingly, their exchange351

should be restricted to a secure network or within a secure352

Supplement 54: DICOM MIME Type

Page 9

wrapper that protects a patient's right to confidentiality353

according to local and national policy. The specific security354

mechanisms are outside the scope of this proposal. Such355

mechanisms as Secured MIME (S/MIME) [2633] or similar might be356

appropriate.357

358

Interoperability considerations:359

360

Because DICOM information is specific to the medical (imaging)361

domain, generic e-mail applications may not be able to interpret362

the information.363

364

The Media Type has been designed in order to allow for365

366

(i) DICOM aware applications to interoperate,367

(ii) generic applications to save the files in a form368

recognizable as DICOM files, that a DICOM application may369

subsequently use.370

371

Published specification:372

373

The Digital Imaging and Communications in Medicine (DICOM)374

Standard is a standard of the DICOM Standards Committee, published375

by the National Electrical Manufacturers Association (NEMA), 1300376

N. 17th Street, Rosslyn, Virginia 22209 USA,377

(http://medical.nema.org).378

379

Applications which use this media:380

381

Biomedical imaging applications.382

383

Additional information:384

385

1. Magic number(s): "DICM" after 128 byte preamble indicates DICOM386

PS 3.10 file387

388

2. File extension(s): ".dcm" is recommended for files saved to389

disk (other than DICOMDIR)390

391

3. Macintosh file type code: Macintosh File Type "DICM" is392

recommended393

394

4. Object Identifiers: none395

396

Person to contact for further information:397

398

1. Name: Howard Clark399

2. E-mail: [email protected]400

401

Intended usage:402

403

Common404

405

Interchange of biomedical images.406

407

Supplement 54: DICOM MIME Type

Page 10

Author/Change controller:408

409

DICOM Standards Committee410

411

3. References412

413

[DICOM] DICOM Standards Committee, "Digital Imaging and414

Communications in Medicine", 2001.415

416

[2387] Levinson, E., "The MIME Multipart/Related Content-type", RFC417

2387, August 1998.418

419

[2633] Ramsdell, B., "S/MIME Version 3 Message Specification", RFC420

2633, June 1999.421

422

4. Authors' Addresses423

424

David Clunie425

RadPharm426

943 Heiden Road427

Bangor PA 18013428

USA429

430

Phone: +1-570-897-7123431

Fax: +1-425-930-0171432

EMail: [email protected]433

434

435

Emmanuel Cordonnier436

Etiam437

20 rue du Pr J. Pecker438

35000 Rennes439

France440

441

Phone: +33(0)299 14 33 88442

Fax: +33(0)299 14 33 80443

EMail: [email protected]444

445

5. Full Copyright Statement446

447

449

This document and translations of it may be copied and furnished to450

others, and derivative works that comment on or otherwise explain it451

or assist in its implementation may be prepared, copied, published452

and distributed, in whole or in part, without restriction of any453

kind, provided that the above copyright notice and this paragraph are454

included on all such copies and derivative works. However, this455

document itself may not be modified in any way, such as by removing456

the copyright notice or references to the Internet Society or other457

Internet organizations, except as needed for the purpose of458

developing Internet standards in which case the procedures for459

copyrights defined in the Internet Standards process must be460

followed, or as required to translate it into languages other than461

English.462

Supplement 54: DICOM MIME Type

Page 11

463

The limited permissions granted above are perpetual and will not be464

revoked by the Internet Society or its successors or assigns.465

466

This document and the information contained herein is provided on an467

"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING468

TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING469

BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION470

HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF471

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.472

473

Acknowledgement474

475

Funding for the RFC Editor function is currently provided by the476

Internet Society.477

Supplement 54: DICOM MIME Type

Page 12

Example 1: Simple DICOM File MIME message (Informative)478

From: "Dr Smith" <[email protected]>479

To: "Dr Johnson" <[email protected]>480

Subject: test DICOM Mime Type481

Date: Fri, 5 Nov 1999 15:15:35 +0100482

MIME-Version: 1.0483

Content-Type: Multipart/mixed;484

boundary="----=_NextPart_000_0027_01BF27A0.9BE21980"485

486

This is a multi-part message in MIME format.487

488

------=_NextPart_000_0027_01BF27A0.9BE21980489

Content-Type: text/plain;490

charset="iso-8859-1"491

Content-Transfer-Encoding: 7bit492

493

Message text: this is a DICOM MIME Type example for DICOM File.494

495

------=_NextPart_000_0027_01BF27A0.9BE21980496

Content-Type: Application/dicom;497

id="i00023"; name="i00023.dcm"498

Content-Transfer-Encoding: base64499

500

byEAALcAAABbAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA501

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA502

AAAAAAAAAAAAAAAAAABESUNNAgAAAFVMBACgAAAAAgABAE9CAAACAAAAAAECAAIAVUkaADEuMi44503

NDAuMTAwMDguNS4xLjQuMS4xLjcAAgADAFVJFgBFeGFtaW5lZC1ieS1ESUNPTS4xLjEAAgAQAFVJ504

FAAxLjIuODQwLjEwMDA4LjEuMi4xAAIAEgBVSRYAMS4yLjI1MC4xLjU5LjMuMC4zLjMuMQIAEwBT505

SBAARVRJQU1fRENNVEtfMzMxIAgAAABVTAQAdgAAAAgAFgBVSRoAMS4yLjg0MC4xMDAwOC41LjEu506

NC4xLjEuNwAIABgAVUkWAEV4YW1pbmVkLWJ5LURJQ09NLjEuMQAIACAAREEAAAgAMABUTQAACABQ507

AFNIAAAIAGAAQ1MCAE9UCABkAENTBABXU0QgCACQAFBOAAAQAAAAVUwEAEYAAAAQABAAUE4QAERJ508

Q09NIE1JTUVeVHlwZSAQACAATE8MAERJQ09NLVNVUDU0IBAAMABEQQgAMjAwMDAzMTAQAEAAQ1MC509

AE0gIAAAAFVMBABkAAAAIAANAFVJEgBFeGFtaW5lZC1ieS1ESUNPTQAgAA4AVUkUAEV4YW1pbmVk510

LWJ5LURJQ09NLjEAIAAQAFNIEgBFeGFtaW5lZC1ieS1ESUNPTSAgABEASVMCADEgIAATAElTAgAx511

ICgAAABVTAQAZAAAACgAAgBVUwIAAQAoAAQAQ1MMAE1PTk9DSFJPTUUyICgACABJUwIAMSAoABAA512

VVMCAB8AKAARAFVTAgAkACgAAAFVUwIACAAoAAEBVVMCAAgAKAACAVVTAgAHACgAAwFVUwIAAADg513

fwAAVUwEAGgEAADgfxAAT0IAAFwEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJJjosEAIAAAAACSY8514

KAAPLS0tFgAAAB4tLS0AABZTW0QAAAA3YmUjBQAWLRYAAyI9IwAtt7e3t5APAIm3t7cAHqeniadb515

AHq3mKC3PQBbt5AAAKC3WwAtt1sATLdxAACJtwAAkLceABY9JrdxAACgpw9bt7cmRLe3WwAtt1sA516

AJi3AACJtwAAt4kAAAAAW7ctAABbty1bt5BxoIm3WwAtt1sAAJi3AACJtwAAt5gAAAAAW7c1AABj517

ty1btya3pz23WwAtt1sATLdxAACJtwAAgbc9ACZMFreQDxanoABbtwCBWy23WwAtt7e3t5APAIm3518

t7cAD5i3t7dEAD2nt7egHgBbtwAAAC23WwAPLS0tFgAAAB4tLS0AAAAeLQ8AAAAPLS0AAAAWLQAA519

AA8tFgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA520

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA521

AAAAAA8tHgAADy0eAB4tLS0AHi0PAAAeLQ8PLS0tLR4AAAAAAAAAAC23pw8AcbeJAIm3t7cAibdb522

ABa3ty0tt7e3t4kAAAAAAAAAAC23t1sWt7eJAACJtwAAibenD3G3ty0tt1sAAAAAAAAAAAAAAC23523

iaBxkLeJAACJtwAAiZinW7eBty0tt6CJiUQAAAAAAAAAAC23Pae3JreJAACJtwAAiYlbt5Bbty0t524

t4lbWy0AAAAAAAAAAC23LVuBALeJAACJtwAAiYkWiTVbty0tt1sAAAAAAAAAAAAAAC23LQAAALeJ525

AIm3t7cAiYkAAABbty0tt7e3t4kAAAAAAAAAAA8tDwAAAC0eAB4tLS0AHh4AAAAWLQ8PLS0tLR4A526

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA527

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA528

AAAWLS0tLS0mLRYAABYtDy0tLS0AABYtLS0tFgAAAAAAAAAAAABbt7e3t7c9p6cPD6CQALe3t7eg529

Flu3t7e3WwAAAAAAAAAAAAAAAFu3LQAATLdqW7ceALeJAEy3W1u3LQAAAAAAAAAAAAAAAAAAAFu3530

LQAAAJi3p1sAALeJAEy3U1u3mImJHgAAAAAAAAAAAAAAAFu3LQAAAB63oA8AALe3t7eQD1u3cVtb531

FgAAAAAAAAAAAAAAAFu3LQAAAAC3iQAAALeYLR4AAFu3LQAAAAAAAAAAAAAAAAAAAFu3LQAAAAC3532

iQAAALeJAAAAAFu3t7e3WwAAAAAAAAAAAAAAABYtDwAAAAAtHgAAAC0eAAAAABYtLS0tFgAAAAA=533

Supplement 54: DICOM MIME Type

Page 13

534

------=_NextPart_000_0027_01BF27A0.9BE21980--535

Supplement 54: DICOM MIME Type

Page 14

Example 2: DICOM File Set MIME message (Informative)536

From: "Dr Johnson" <[email protected]>537

To: "Dr Smith" <[email protected]>538

Subject: DICOM MIME sub-type file set example539

Date: Sat, 9 Mar 2002 16:24:27 +0100540

MIME-Version: 1.0541

Content-Type: multipart/mixed;542

boundary="----=_NextPart_000_0062_01C1C786.EA262CC0";543

start="<[email protected]>";544

type="text/plain"545

546

This is a multi-part message in MIME format.547

548

------=_NextPart_000_0062_01C1C786.EA262CC0549

Content-Type: text/plain;550

charset="iso-8859-1"551

Content-Transfer-Encoding: 7bit552

Content-ID: "<[email protected]>"553

554

This is an example message containing a DICOM file set encoded following the555

DICOM MIME sub-type (RFC3240).556

557

558

------=_NextPart_000_0062_01C1C786.EA262CC0559

Content-Type: text/plain;560

name="header1.txt"561

Content-Transfer-Encoding: quoted-printable562

Content-Disposition: attachment;563

filename="header1.txt"564

Content-ID: "<[email protected]>"565

Content-Description: Header of the medical message566

567

This is the header part of the message, which contains:568

- a first text document (letter1)569

- a DICOM file set part (dicomfileset1) including an additional =570

complementary note571

This message was sent by Dr Johnson to Dr Smith.572

It relates to the patient: DICOM Nema (M) 01/01/1993573

------=_NextPart_000_0062_01C1C786.EA262CC0574

Content-Type: multipart/related;575

boundary="----=_NextPart_000_0062_01C1C786.EA262CC1_13487";576

start="<[email protected]>";577

type="application/dicom"578

579

------=_NextPart_000_0062_01C1C786.EA262CC1_13487580

Content-Type: text/plain;581

name="dicomfileset1note1.txt"582

Content-Transfer-Encoding: 7bit583

Content-Disposition: attachment;584

filename="dicomfileset1note1.txt"585

Content-ID: "<[email protected]>"586

Content-Description: Note for the images use587

588

This is a simple note, for receivers who can not read images.589

These images are DICOM 3.0 images and the DICOMDIR index related file.590

Please use a DICOM compatible application.591

Supplement 54: DICOM MIME Type

Page 15

DICOM is a Standard Mark of Nema (www.nema.org).592

------=_NextPart_000_0062_01C1C786.EA262CC1_13487593

Content-Type: application/dicom;594

id="DICOMDIR";595

name="Dicomdir"596

Content-Transfer-Encoding: base64597

Content-Disposition: attachment;598

filename="Dicomdir";599

Content-ID: "<[email protected]>"600

Content-Description: Index of the images (DICOMDIR)601

602

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA603

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA604

AAAAAAAAAAAAAAAAAABESUNNAgAAAFVMBACIAAAAAgABAE9CAAACAAAAAQACAAIAVUkUADEuMi44605

NDAuMTAwMDguMS4zLjEwAgADAFVJIAAxLjIuMjUwLjEuNTkuMi40Mi4yMDAyMDMwOTE2NDkyMAIA606

EABVSRQAMS4yLjg0MC4xMDAwOC4xLjIuMQACABIAVUkSADEuMi4yNTAuMS41OS4yLjQ0AAQAAABV607

TAQAdgMAAAQAMBFDUw4ARVRJQU1fREVZRTI0NAAEAAASVUwEAGgBAAAEAAISVUwEAGgBAAAEABIS608

VVMCAAAABAAgElNRAAAyAwAA/v8A4G4AAAAEAAAUVUwEAAAAAAAEABAUVVMCAP//BAAgFFVMBADe609

AQAABAAwFENTCABQQVRJRU5UIBAAEABQTgoARElDT01eTkVNQRAAIABMTwgARElDT00zMAAQADAA610

REEIADE5OTMwMTAxEABAAENTAgBNAP7/AOCmAAAABAAAFFVMBAAAAAAABAAQFFVTAgD//wQAIBRV611

TAQAjAIAAAQAMBRDUwYAU1RVRFkgCAAgAERBCAAyMDAyMDMwOQgAMABUTQYAMTYwMzI1CABQAFNI612

CABESUNPTTMwAAgAMBBMTxgARElDT00gTUlNRSB0eXBlIGV4YW1wbGUAIAANAFVJGAAxLjIuMjUw613

LjEuNTkuMTIzLjQ1Ni43ODkgABAAU0gAAP7/AOCGAAAABAAAFFVMBAAAAAAABAAQFFVTAgD//wQA614

IBRVTAQAGgMAAAQAMBRDUwYAU0VSSUVTCABgAENTAgBPVAgAgABMTwAACACBAFNUAAAIAD4QTE8A615

AAgAUBBQTgAAIAAOAFVJGgAxLjIuMjUwLjEuNTkuMTIzLjQ1Ni43ODkuMSAAEQBJUwIAMQD+/wDg616

uAAAAAQAABRVTAQA2gMAAAQAEBRVUwIA//8EACAUVUwEAAAAAAAEADAUQ1MGAElNQUdFIAQAABVD617

UwwAU0UwMDAxL0kwMDAxBAAQFVVJGgAxLjIuODQwLjEwMDA4LjUuMS40LjEuMS43AAQAERVVSRwA618

MS4yLjI1MC4xLjU5LjEyMy40NTYuNzg5LjEuMQQAEhVVSRQAMS4yLjg0MC4xMDAwOC4xLjIuMQAI619

AAgAQ1MAACAAEwBJUwIAMQD+/wDguAAAAAQAABRVTAQAAAAAAAQAEBRVUwIA//8EACAUVUwEAAAA620

AAAEADAUQ1MGAElNQUdFIAQAABVDUwwAU0UwMDAxL0kwMDAyBAAQFVVJGgAxLjIuODQwLjEwMDA4621

LjUuMS40LjEuMS43AAQAERVVSRwAMS4yLjI1MC4xLjU5LjEyMy40NTYuNzg5LjEuMgQAEhVVSRQA622

MS4yLjg0MC4xMDAwOC4xLjIuMQAIAAgAQ1MAACAAEwBJUwIAMgA=623

624

------=_NextPart_000_0062_01C1C786.EA262CC1_13487625

Content-Type: application/dicom;626

id="SE0001/I0001";627

name="I0001.dcm"628

Content-Transfer-Encoding: base64629

Content-Disposition: attachment;630

filename="I0001.dcm"631

Content-ID: "<[email protected]>"632

Content-Description: Color image633

634

635

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA636

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA637

AAAAAAAAAAAAAAAAAABESUNNAgAAAFVMBACmAAAAAgABAE9CAAACAAAAAQACAAIAVUkaADEuMi44638

NDAuMTAwMDguNS4xLjQuMS4xLjcAAgADAFVJHAAxLjIuMjUwLjEuNTkuMTIzLjQ1Ni43ODkuMS4x639

AgAQAFVJFAAxLjIuODQwLjEwMDA4LjEuMi4xAAIAEgBVSRgAMS4yLjI1MC4xLjU5LjIuNDMuODYu640

MjQzAgATAFNIDgBBQ1EtRVRJQU0tMi40MwgAAABVTAQAxAAAAAgABQBDUwoASVNPX0lSIDEwMAgA641

FgBVSRoAMS4yLjg0MC4xMDAwOC41LjEuNC4xLjEuNwAIABgAVUkcADEuMi4yNTAuMS41OS4xMjMu642

NDU2Ljc4OS4xLjEIACAAREEIADIwMDIwMzA5CAAwAFRNBgAxNjAzMjUIAFAAU0gIAERJQ09NMzAA643

CABgAENTAgBPVAgAZABDUwQAV1NEAAgAkABQTgAACAAwEExPGABESUNPTSBNSU1FIHR5cGUgZXhh644

bXBsZQAQAAAAVUwEADwAAAAQABAAUE4KAERJQ09NXk5lbWEQACAATE8IAERJQ09NMzAAEAAwAERB645

CAAxOTkzMDEwMRAAQABDUwIATQAgAAAAVUwEAF4AAAAgAA0AVUkYADEuMi4yNTAuMS41OS4xMjMu646

NDU2Ljc4OSAADgBVSRoAMS4yLjI1MC4xLjU5LjEyMy40NTYuNzg5LjEgABAAU0gAACAAEQBJUwIA647

MQAgABMASVMCADEAKAAAAFVMBABmAAAAKAACAFVTAgADACgABABDUwQAUkdCICgABgBVUwIAAAAo648

AAgASVMCADEAKAAQAFVTAgAIACgAEQBVUwIAGgAoAAABVVMCAAgAKAABAVVTAgAIACgAAgFVUwIA649

BwAoAAMBVVMCAAAA4H8AAFVMBAB8AgAA4H8QAE9CAABwAgAA////9fXs0NCivLx6zMyZ4uLG7/Hr650

6+/v7vHx/f39+vv77PDw+vv7+/z83+Xl5erq/f399ff33uTk+vv7/v7+9fb2/////v7+7fDw+/z8651

8PHlcYNRXnI5dIVPUm1ISmpYaoJpdY+HtMPDeJKS6O3tb4uL4ujoj6WlzdfXtcTEwc3Nm6+vyNPT652

Supplement 54: DICOM MIME Type

Page 16

cY2N6+/vhJ2d9ff33uTkjqSk9/j4zs6fVWw2coNQY3pUGUU8K1NKdY19i5+P/f79kKamu8nJb4yM653

v8zMiaCg/v7+/P39lKmpxdDQ/v7+j6Wlrb29aYeHpri4oLOzdZCQ////29u4l5k6RGJCnql/TW1b654

v8Wkh5yLg5mM/v7+ma2ty9XVb4yMyNLSdZCQ+fr6+/z8m6+vq7u7/v7+k6iou8jIo7W1YoKCsMDA655

b4yM////+/v4ycmTfoxQurt+r7WF4ODDorKodpGQuMbGs8LC8vT0h5+f5uvrpri4nbCwq7y83eTk656

kaentcTErb6+4efnu8jIq7y86+7uiqGh9ff3+/v4+Pjy5ubR3Ny74+PH8vLm+vr1+fn0+vr3+vr2657

+fn0+/v3+vr1+fn0+fn1+Pjz+vr1+fn0+Pn1+vr2/Pz59/fw+fnz+fn0+fn0/Pz66OjT0tKl1tau658

3Ny619ew2tq21tau1NSq5OTJ2dm03d294uLG2Niz2Nix2dmz19ex2Niz1NSq3t6+39+/5ubP0tKm659

09Oo2dm11tau8fHj////+/v4/v7+/////////v7++/v4/Pz6/f38////////////////////////660

////////////////////////////////////////////661

662

------=_NextPart_000_0062_01C1C786.EA262CC1_13487663

Content-Type: application/dicom;664

id="SE0001/I0002";665

name="I0002.dcm"666

Content-Transfer-Encoding: base64667

Content-Disposition: attachment;668

filename="I0002.dcm"669

Content-ID: "<[email protected]>"670

Content-Description: B&W image671

672

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA673

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA674

AAAAAAAAAAAAAAAAAABESUNNAgAAAFVMBACmAAAAAgABAE9CAAACAAAAAQACAAIAVUkaADEuMi44675

NDAuMTAwMDguNS4xLjQuMS4xLjcAAgADAFVJHAAxLjIuMjUwLjEuNTkuMTIzLjQ1Ni43ODkuMS4y676

AgAQAFVJFAAxLjIuODQwLjEwMDA4LjEuMi4xAAIAEgBVSRgAMS4yLjI1MC4xLjU5LjIuNDMuODYu677

MjQzAgATAFNIDgBBQ1EtRVRJQU0tMi40MwgAAABVTAQAxAAAAAgABQBDUwoASVNPX0lSIDEwMAgA678

FgBVSRoAMS4yLjg0MC4xMDAwOC41LjEuNC4xLjEuNwAIABgAVUkcADEuMi4yNTAuMS41OS4xMjMu679

NDU2Ljc4OS4xLjIIACAAREEIADIwMDIwMzA4CAAwAFRNBgAwNzQ3NDAIAFAAU0gIAERJQ09NMzAA680

CABgAENTAgBPVAgAZABDUwQAV1NEAAgAkABQTgAACAAwEExPGABESUNPTSBNSU1FIHR5cGUgZXhh681

bXBsZQAQAAAAVUwEADwAAAAQABAAUE4KAERJQ09NXk5lbWEQACAATE8IAERJQ09NMzAAEAAwAERB682

CAAxOTkzMDEwMRAAQABDUwIATQAgAAAAVUwEAF4AAAAgAA0AVUkYADEuMi4yNTAuMS41OS4xMjMu683

NDU2Ljc4OSAADgBVSRoAMS4yLjI1MC4xLjU5LjEyMy40NTYuNzg5LjEgABAAU0gAACAAEQBJUwIA684

MQAgABMASVMCADIAKAAAAFVMBABkAAAAKAACAFVTAgABACgABABDUwwATU9OT0NIUk9NRTIAKAAI685

AElTAgAxACgAEABVUwIADwAoABEAVVMCADMAKAAAAVVTAgAIACgAAQFVUwIACAAoAAIBVVMCAAcA686

KAADAVVTAgAAAOB/AABVTAQACgMAAOB/EABPQgAA/gIAAP/////98dPX5O//////////////////687

/////////////////////////////////////////dCcjY2OnqW1yufa2tra6f///+Xa3f///+W5688

uc/2///xwLnn////+d7/////5Nfx///6oX53blKghHl6h5J8N72mT2Lo/+sktv/7fX/Mx3as/6l0689

0rhIgfz/51r////0Wdfn//+2WiM7YZFoJyMjIzt9V///92VX/f8k1P+ZWv3///rF0Tn4///hL6r/690

zSTP//+nJPj///uScylco6MwQCgmI2+hS/v//80j4f8k1P9ImP//////gnH/////aWD/rkJr//lp691

I9z///aOjHVqqZIoJGOSh7GrV/b//+Ujzv8k1P8/mP//////ZXT/////gUr/hLMl27KuPsP///+i692

jZQ4RLSiI5rFy7V+Uv3//9wq9f8k1P9VdP//////j0T9////boD/cvdreXH8WKT////kkI1sP9LH693

T7Xk6HQlRP///YaL//8k0v/AKbv///nQ4yux///wQtj/YP/PJqH/gIH/////5qB1g7O9vcbb291q694

QYmbgJz9/+A+ofb/vlZwf1/V/89adp93yv/dYOz/fvT/m2Pg//////vTppydq8Pa8/////j3////695

///////////59/r/////+Pj/////////////////////////////////////////////////////696

///////////////////////////////////JwdnRz9vQy9Xh3N3VzODx0drez8/k38/czNji0NXd697

2MrX2t/j2NH/u8DbxsfeyNnY//nPzcHRyMvi1cbUwLvXyrnzxs/K4tvd2sjN0sbLzsbayMHH0dLi698

08fz0dHNwsbc0cjg/////+79/////////PD//+79////////////////////////////////////699

////////////////////////////////////////////////////////////////////////////700

/wA=701

702

------=_NextPart_000_0062_01C1C786.EA262CC1_13487--703

------=_NextPart_000_0062_01C1C786.EA262CC0--704

705