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.

70<br />

We all are brothers <strong>and</strong> sisters<br />

Chapter 5 Parlez-Vous <strong>DICOM</strong>?<br />

As already mentioned, all patients with the same Patient ID are expected<br />

to be the same person <strong>in</strong> <strong>DICOM</strong>. I recently ran <strong>in</strong>to the most <strong>in</strong>terest<strong>in</strong>g<br />

case of patient ID misuse <strong>in</strong> one well-respected hospital. All patients<br />

arriv<strong>in</strong>g without ID entries were labeled with “W/I” patient ID, st<strong>and</strong><strong>in</strong>g<br />

for “without ID”. This was done daily for a large number of exams, essentially<br />

merg<strong>in</strong>g all these patients <strong>in</strong>to one as far as <strong>DICOM</strong> was concerned.<br />

Consequently, PACS software was not able to dist<strong>in</strong>guish between these<br />

patients.<br />

If no ID is available, even us<strong>in</strong>g patient <strong>in</strong>itials with birth date (for example,<br />

JS19670102) would work much better than “W/I”.<br />

You can f<strong>in</strong>d <strong>in</strong> the <strong>DICOM</strong> Data Dictionary another attribute called “Other<br />

Patient IDs” (0010,1001). It was provided to mitigate the problem of multiple<br />

IDs for the same patient, but it is rarely used <strong>in</strong> <strong>DICOM</strong> software. The reason is<br />

obvious: it is much better to enforce a consistent s<strong>in</strong>gle-ID policy than to deal<br />

with a list of different IDs for the same patient (possibly overlapp<strong>in</strong>g with other<br />

patients).<br />

Is there any way to deal with Patient ID <strong>in</strong>consistencies? Practically, yes.<br />

Good <strong>DICOM</strong> software never relies on the Patient ID attribute alone, <strong>and</strong> always<br />

implements some additional logic to verify patient identity. This logic is<br />

based on other data available <strong>in</strong> <strong>DICOM</strong> data elements. Patient name, date of<br />

birth, sex, last study date, weight, size, <strong>and</strong> a few other tags can be used to make<br />

<strong>in</strong>telligent conclusions about patient similarity <strong>and</strong> identity. For example, if all<br />

of these parameters co<strong>in</strong>cided for two patients with different patient IDs, there<br />

is strong reason to believe that the patients are <strong>in</strong>deed the same person <strong>and</strong> that<br />

the IDs need to be reset to the same ID (the one used first). The same approach<br />

is used to merge patients with misspelled names <strong>and</strong> other data errors. Different<br />

patient merge functions are often implemented <strong>in</strong> PACS software.<br />

The same method is also used to split patients if they were erroneously<br />

merged (for example, if the same Patient ID was mistakenly assigned to two different<br />

people). I remember an imag<strong>in</strong>g center where all Patient IDs were threedigit<br />

numbers; but all you can do with the 000–999 numbers is to ID a thous<strong>and</strong><br />

patients. When you run out of these thous<strong>and</strong> options, you will have to start<br />

recycl<strong>in</strong>g the same IDs for the other patients, thereby erroneously merg<strong>in</strong>g different<br />

people. Us<strong>in</strong>g short, easy IDs can hardly make your work easier.<br />

Patient splitt<strong>in</strong>g <strong>and</strong> merg<strong>in</strong>g should not be done automatically. When a<br />

<strong>DICOM</strong> program detects that splitt<strong>in</strong>g or merg<strong>in</strong>g needs to be done, it should<br />

somehow flag the suspected records <strong>and</strong> notify its human adm<strong>in</strong>istrator. No<br />

matter how complex the program logic might be, it could result <strong>in</strong> false merges<br />

<strong>and</strong> splits, <strong>and</strong> human assistance to avoid these problems is important.<br />

As the role of decentralized PACS <strong>in</strong>creases <strong>and</strong> regional or national systems<br />

come to replace the local ones, the dem<strong>and</strong> for correct <strong>and</strong> consistent

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

Saved successfully!

Ooh no, something went wrong!