# Organizational Changes to DICOM Databse

**URL:** <https://discourse.slicer.org/t/organizational-changes-to-dicom-databse/29953>\
**Category:** Feature requests\
**Tags:** dicom\
**Created:** [June 9, 2023, 8:24pm UTC](https://discourse.slicer.org/t/organizational-changes-to-dicom-databse/29953 "2023-06-09T20:24:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![AnishJag](https://avatars.discourse-cdn.com/v4/letter/a/3be4f8/32.png) [@AnishJag](https://discourse.slicer.org/u/AnishJag)\
**Post date:** [June 9, 2023, 8:24pm UTC](https://discourse.slicer.org/t/organizational-changes-to-dicom-databse/29953/1 "2023-06-09T20:24:29Z")

</div>

I’ve been using a custom extension for Slicer3D for bone analysis and realized that I accidentally ran an analysis on incorrect images because when importing the DICOMs from a folder, it appears extremely similar in the DICOM Database. If there was an easier way to distinguish these DICOMs, my analysis would have run smoother. I thought that the following changes may help:

1. Having the File Names in the DICOM Database where the DICOMs were imported from.
2. Anything that pertains to dates, have it in a simpler format such as dd/mm/yyyy. For times, use the local machine’s time and have the option to switch between military and non-military formats.
3. Have arrows on both sides of a column to change its size. I was trying to adjust the column widths and it wasn’t quite intuitive.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [June 16, 2023, 2:41pm UTC](https://discourse.slicer.org/t/organizational-changes-to-dicom-databse/29953/2 "2023-06-16T14:41:57Z")

</div>

Thanks for the suggestions. We are working on a completely new, patient-oriented, visual DICOM browser with thumbnails and more clear separation of patients and studies. We expect to make it available within a few months.

---

<div class="post-metadata">

**Author:** ![AnishJag](https://avatars.discourse-cdn.com/v4/letter/a/3be4f8/32.png) [@AnishJag](https://discourse.slicer.org/u/AnishJag)\
**Post date:** [July 27, 2023, 3:46pm UTC](https://discourse.slicer.org/t/organizational-changes-to-dicom-databse/29953/3 "2023-07-27T15:46:56Z")

</div>

Hello again!

I was just curious to know if there was any new information regarding the release of the new DICOM database. I’ve been tasked to create a tutorial video regarding how to use our custom extension with Slicer, and I’d like to incorporate the new database in the video to help prevent confusion. Thanks!

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [July 29, 2023, 4:39pm UTC](https://discourse.slicer.org/t/organizational-changes-to-dicom-databse/29953/4 "2023-07-29T16:39:29Z")

</div>

We experienced some performance issues that we are addressing in the coming weeks, so probably the feature will be available around the end of August.