15.12.2012 Views

Digital Imaging and Communications in Medicine (DICOM)

Digital Imaging and Communications in Medicine (DICOM)

Digital Imaging and Communications in Medicine (DICOM)

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

10.1 <strong>DICOM</strong> File Format 223<br />

10.1.2<br />

Group 0002: <strong>DICOM</strong> File Meta Information<br />

Right after the DICM prefix, beg<strong>in</strong>n<strong>in</strong>g at byte 133, we f<strong>in</strong>d the <strong>DICOM</strong> File<br />

Meta Information. Unlike the preamble <strong>and</strong> the DICM prefix, meta <strong>in</strong>formation<br />

is encoded as a set of <strong>DICOM</strong> attributes with explicit VRs. All attributes <strong>in</strong> File<br />

Meta Information belong to <strong>DICOM</strong> group 0002, <strong>and</strong> are shown <strong>in</strong> Table 49.<br />

The last four elements <strong>in</strong> our table are optional, <strong>and</strong> can therefore be omitted.<br />

The required elements, as you can see, are either derived from the <strong>DICOM</strong> data<br />

object properties (SOP, Transfer Syntax), or record the properties of the application<br />

that created the file. The most important element <strong>in</strong> the entire 0002 group<br />

is probably the “Transfer Syntax UID” (0002,0010), which def<strong>in</strong>es how the subsequent<br />

<strong>DICOM</strong> data object is encoded. If you remember (see 9.4), <strong>in</strong> <strong>DICOM</strong><br />

network<strong>in</strong>g the Transfer Syntaxes are communicated at <strong>DICOM</strong> association establishment<br />

time; now they are written <strong>in</strong>to the <strong>DICOM</strong> file headers.<br />

You will f<strong>in</strong>d another example of group 0002 use a little bit later (<strong>in</strong> 10.2.1)<br />

when the structure of the <strong>DICOM</strong>DIR file is discussed. It will also give you an<br />

example of group 0004 application, which we did not discuss here for brevity,<br />

but which is used quite similarly to group 0002.<br />

Table 49 File Meta Information<br />

Attribute name Tag VR Attribute description<br />

Group Length (0002,0000) UL Number of bytes follow<strong>in</strong>g this File Meta<br />

Element (end of the value field) up to <strong>and</strong><br />

<strong>in</strong>clud<strong>in</strong>g the last File Meta Element of the<br />

Group 0002<br />

File Meta<br />

Information<br />

Version<br />

Media Storage<br />

SOP Class UID<br />

Media Storage<br />

SOP Instance<br />

UID<br />

(0002,0001) OB This is a 2-byte field where each bit identifies<br />

a version of this File Meta Information header.<br />

In current <strong>DICOM</strong> version, the first byte<br />

value is 00H <strong>and</strong> the second byte value is 01H<br />

(0002,0002) UI Uniquely identifies the SOP Class associated<br />

with the <strong>DICOM</strong> data object. The value of<br />

this element is based on the image modality<br />

type; <strong>in</strong> other words, it should conta<strong>in</strong> the C-<br />

Store SOP for image modality (see 7.3)<br />

Example: 1.2.840.10008.5.1.4.1.1.1<br />

(CT image storage)<br />

(0002,0003) UI Uniquely identifies the SOP Instance associated<br />

with the <strong>DICOM</strong> data object placed <strong>in</strong><br />

the file <strong>and</strong> follow<strong>in</strong>g the File Meta Information.<br />

This value comes from the Image SOP<br />

Instance UID attribute (0008,0018)<br />

Example: 1.2.840.10008.2008.03.25.12.33.55.7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!