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.

5.6 <strong>DICOM</strong> Information Hierarchy 67<br />

file nam<strong>in</strong>g is justified: each <strong>DICOM</strong> image object <strong>in</strong>cludes the “Image SOP<br />

Instance UID” attribute (0008,0018). This makes it a good name for a <strong>DICOM</strong><br />

image file. When you see file names such as:<br />

1.2.804.114118.2.20040909.125423.3692976692.1.1.1<br />

you are likely deal<strong>in</strong>g with <strong>DICOM</strong> files. In essence, <strong>DICOM</strong> files are noth<strong>in</strong>g<br />

more than <strong>DICOM</strong> objects stored on your hard drive – <strong>DICOM</strong> object<br />

memory dumps, if you wish.<br />

UID pars<strong>in</strong>g?<br />

Even though UID names are always built with certa<strong>in</strong> logic <strong>in</strong> m<strong>in</strong>d, do not<br />

try to parse them or use their names to convey additional <strong>in</strong>formation. For<br />

example, even if you know that a UID name might <strong>in</strong>clude patient ID or<br />

study date, do not try to extract this data. <strong>DICOM</strong> explicitly warns aga<strong>in</strong>st<br />

this.<br />

UID names are not meant for any data exchange, <strong>and</strong> their sole purpose is<br />

to dist<strong>in</strong>guish between multiple object <strong>in</strong>stances. As long as this is guaranteed,<br />

the <strong>DICOM</strong> application is free to change or update UID names<br />

as it f<strong>in</strong>ds appropriate with whatever additional nam<strong>in</strong>g logic it might be<br />

us<strong>in</strong>g. In addition to what <strong>DICOM</strong> prescribes, correct UID-issu<strong>in</strong>g policy<br />

always rema<strong>in</strong>s on your <strong>DICOM</strong> manufacturer’s m<strong>in</strong>d. They, through their<br />

<strong>DICOM</strong>-compliant software, must track image changes <strong>and</strong> create a new<br />

UID for each cl<strong>in</strong>ically different <strong>in</strong>stance of the same image.<br />

5.6<br />

<strong>DICOM</strong> Information Hierarchy<br />

Before we cont<strong>in</strong>ue with our review of <strong>DICOM</strong> data, it is worth hav<strong>in</strong>g a quick<br />

look at how <strong>DICOM</strong> structures its <strong>in</strong>formation. Certa<strong>in</strong>ly, <strong>DICOM</strong> Data Dictionary<br />

attributes play very important roles <strong>in</strong> mapp<strong>in</strong>g real-world data <strong>in</strong>to<br />

the <strong>DICOM</strong> st<strong>and</strong>ard. But still, these attributes are many. Don’t we need to put<br />

them <strong>in</strong> some order?<br />

This order is achieved <strong>in</strong> <strong>DICOM</strong> with the Patient-Study-Series-Image<br />

hierarchy (Fig. 15):<br />

1. One patient may have multiple studies.<br />

2. Each study may <strong>in</strong>clude one or more image series.<br />

3. Each series has one or more images.<br />

This hierarchy naturally reflects what happens <strong>in</strong> the real world when a patient<br />

needs to have some medical imag<strong>in</strong>g done. John Smith comes to a hospital<br />

where several studies may be scheduled (for example, MR, CT, <strong>and</strong> ultrasound<br />

exams). Several follow-up studies could be needed later <strong>in</strong> time. Each study

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

Saved successfully!

Ooh no, something went wrong!