Should a DICOM StudyInstanceUID be unique to the patient?
Asked Answered
P

3

2

While working with the DICOM study, series and media concepts, I wondered if these values are to be unique over all data, or only to the patient they belong to.

Phrased otherwise; can I have 2 patients having a study/series/sop instance uid that is the same value for both patients?

Or does the DICOM standard simply doesn't care about that and is that open to the implementor to decide?

Pieplant answered 13/12, 2018 at 17:52 Comment(0)
S
5

In DICOM, a Study (identified by its Study Instance UID) is always associated with a single Patient. See DICOM standard part 3 for details.

To answer your initial question/thought: a Unique Identifier (UID) has to be globally unique, i.e. world-wide over all patients, devices, hospitals, etc.

Sundowner answered 13/12, 2018 at 20:22 Comment(0)
T
3

UID in DICOM (no matter what UID) is always globally unique. So, as you asked in question, uniqueness is not limited to Patient level or something.

Following is from specifications:

2017a Part 5 - Data Structures and Encoding (9 Unique Identifiers (UIDs))

Unique Identifiers (UIDs) provide the capability to uniquely identify a wide variety of items. They guarantee uniqueness across multiple countries, sites, vendors and equipment. Different classes of objects, instance of objects and information entities can be distinguished from one another across the DICOM universe of discourse irrespective of any semantic context.

More details about DICOM UID can be found in this answer.

Your comment on question as below:

My question was more about what to do in case I choose to clone a patient in my system and attach the same dicom(s) to it. Should I regenerate the dicom-uid's or could I keep them as-is.

I am not sure what you mean by "clone". While cloning, if there is change in dataset, you should regenerate the SOPInstance UID. Even if you simply apply lossy transfer syntax to your dataset, you should regenerate the SOPInstance UID. Any action that differentiates/separates the the datasets from original require new SOPInstance UID. So, while cloning, if you are changing patient demographics, new UID should be generated. Whether new StudyInstance UID should be generated or not depends upon what is changed.

OTOH, if you are just copying your dataset at different location, it is still same dataset. You do not need to regenerate UIDs in this case.

Thoroughbred answered 14/12, 2018 at 7:24 Comment(0)
T
1

Unfortunately although the standard states the UID should be globally unique you can not guarantee it at the series level in my experience. I have come across series with duplicate ids across studies. To protect yourself assume you have to use StudyUID +SeriesUID to ensure a unique series key.

Threlkeld answered 20/11, 2019 at 20:11 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.