You do not need to regenerate UIDs in this case. OTOH, if you are just copying your dataset at different location, it is still same dataset. Whether new StudyInstance UID should be generated or not depends upon what is changed. So, while cloning, if you are changing patient demographics, new UID should be generated. ![]() The relationship between the Study/Series/Instace is: a STUDY HAS Multiple SERIES which HAVE Multiple SOP. Any action that differentiates/separates the the datasets from original require new SOPInstance UID. Each Image (dicom IOD) will contain all three UIDs. Even if you simply apply lossy transfer syntax to your dataset, you should regenerate the SOPInstance UID. While cloning, if there is change in dataset, you should regenerate the SOPInstance UID. Should I regenerate the dicom-uid's or could I keep them as-is. 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. More details about DICOM UID can be found in this answer. 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. ![]() They guarantee uniqueness across multiple countries, sites, vendors and equipment. Unique Identifiers (UIDs) provide the capability to uniquely identify a wide variety of items. So, as you asked in question, uniqueness is not limited to Patient level or something.ΔΆ017a Part 5 - Data Structures and Encoding ( 9 Unique Identifiers (UIDs)) UID in DICOM (no matter what UID) is always globally unique.
0 Comments
Leave a Reply. |