# DICOM data import error: patients are read as others

**URL:** <https://discourse.slicer.org/t/dicom-data-import-error-patients-are-read-as-others/12041>\
**Category:** Support\
**Tags:** bug, dicom, file-import\
**Created:** [June 15, 2020, 5:57pm UTC](https://discourse.slicer.org/t/dicom-data-import-error-patients-are-read-as-others/12041 "2020-06-15T17:57:35Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Alexandre\_Huat](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/alexandre_huat/32/7119_2.png) [@Alexandre\_Huat](https://discourse.slicer.org/u/Alexandre_Huat)\
**Post date:** [June 16, 2020, 7:20pm UTC](https://discourse.slicer.org/t/dicom-data-import-error-patients-are-read-as-others/12041/6 "2020-06-16T19:20:47Z")

</div>

1. I have checked the UIDs of the images causing these buggy behaviors (SOP Class, SOP Instance, Study Instance, Series Instance, Frame of Reference): none are the same for the buggy images that I have detected.
2. I reviewed the anonymization process with the data curator: only the SOP Instance UIDs are modified and the assignement process ensures no duplicates.
3. After deletion of Documents/SlicerDICOMDatabase and reinstallation of Slicer Stable Release 4.10.2, my intern wasn’t able to reproduce the bug on some patients but it seems to remain on a few others.

All of this makes me think that the initial problem is due to Slicer. I stay confused by point 3.

For your record: when trying Slicer Preview Release 4.11.0 on macOS 10.14.6, my intern says the software bugs on start and that she doesn’t succeed in installing the SlicerRT extension. I don’t have enough time to dig into this problem though.

---

_[View the full topic](https://discourse.slicer.org/t/dicom-data-import-error-patients-are-read-as-others/12041)._