# i am trying to open DCE-MRI data with DICOM module but it is showing me 0 patient added massages, i have uploaded the data set type and the massages it was showing, 

**URL:** <https://discourse.slicer.org/t/i-am-trying-to-open-dce-mri-data-with-dicom-module-but-it-is-showing-me-0-patient-added-massages-i-have-uploaded-the-data-set-type-and-the-massages-it-was-showing/8425>\
**Category:** Support\
**Tags:** dicom\
**Created:** [September 14, 2019, 11:31am UTC](https://discourse.slicer.org/t/i-am-trying-to-open-dce-mri-data-with-dicom-module-but-it-is-showing-me-0-patient-added-massages-i-have-uploaded-the-data-set-type-and-the-massages-it-was-showing/8425 "2019-09-14T11:31:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rahulba](https://avatars.discourse-cdn.com/v4/letter/r/7ba0ec/32.png) [@rahulba](https://discourse.slicer.org/u/rahulba)\
**Post date:** [September 14, 2019, 11:31am UTC](https://discourse.slicer.org/t/i-am-trying-to-open-dce-mri-data-with-dicom-module-but-it-is-showing-me-0-patient-added-massages-i-have-uploaded-the-data-set-type-and-the-massages-it-was-showing/8425/1 "2019-09-14T11:31:43Z")

</div>

Operating system: Windows 10  
Slicer version:4.10  
Expected behavior:  
Actual behavior:

 ![Screenshot%20(18)](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/6/e/6e83ba27fe224e412dc3ca90c89e99e512ae681f.png)

---

<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:** [September 14, 2019, 11:51am UTC](https://discourse.slicer.org/t/i-am-trying-to-open-dce-mri-data-with-dicom-module-but-it-is-showing-me-0-patient-added-massages-i-have-uploaded-the-data-set-type-and-the-massages-it-was-showing/8425/2 "2019-09-14T11:51:03Z")

</div>

Check out the [DICOM FAQ page](https://www.slicer.org/wiki/Documentation/Nightly/FAQ/DICOM#I_try_to_import_a_directory_of_DICOM_files.2C_but_nothing_shows_up_in_the_browser) and let us know if you could fix the problem.