# Could you please tell me what the reason that Ondemand CT scan files (DCM) are not readable by a slicer?

**URL:** <https://discourse.slicer.org/t/could-you-please-tell-me-what-the-reason-that-ondemand-ct-scan-files-dcm-are-not-readable-by-a-slicer/39787>\
**Category:** Support\
**Created:** [October 21, 2024, 11:36pm UTC](https://discourse.slicer.org/t/could-you-please-tell-me-what-the-reason-that-ondemand-ct-scan-files-dcm-are-not-readable-by-a-slicer/39787 "2024-10-21T23:36:17Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [October 21, 2024, 11:40pm UTC](https://discourse.slicer.org/t/could-you-please-tell-me-what-the-reason-that-ondemand-ct-scan-files-dcm-are-not-readable-by-a-slicer/39787/2 "2024-10-21T23:40:05Z")

</div>

Ondemand scanners generate invalid DICOM files. See details in this topic:

> [@PatientName and rus language - trouble](https://discourse.slicer.org/t/patientname-and-rus-language-trouble/28870/4):
>
> The DICOM files have multiple sever DICOM non-conformities. The most serious are: CharacterSet is not saved in the file. It seems that the file uses Windows-1251 code page, which is not even a valid DICOM character set. XRayTubeCurrent field is stored incorrectly (it must be an integer value, the value is 4.1 - see [David Clunie's Blog: The DICOM Exposure attribute fiasco](http://dclunie.blogspot.com/2008/11/dicom-exposure-attribute-fiasco.html)) There are also some incorrectly generated UIDs. I would recommend to contact your device manufacturer and report these …

Please report the issues to the manufacturer. Until the manufacturer fixes its software you can use the workaround described in that topic.

---

_[View the full topic](https://discourse.slicer.org/t/could-you-please-tell-me-what-the-reason-that-ondemand-ct-scan-files-dcm-are-not-readable-by-a-slicer/39787)._