# PatientName and rus language - trouble

**URL:** <https://discourse.slicer.org/t/patientname-and-rus-language-trouble/28870>\
**Category:** Support\
**Created:** [April 12, 2023, 6:02pm UTC](https://discourse.slicer.org/t/patientname-and-rus-language-trouble/28870 "2023-04-12T18:02:11Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [April 12, 2023, 9:28pm UTC](https://discourse.slicer.org/t/patientname-and-rus-language-trouble/28870/4 "2023-04-12T21:28:48Z")

</div>

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 errors.

That said, [I’ve added two rules to the DICOM patcher that can fix the two serious issues](https://github.com/Slicer/Slicer/pull/6940). It will be available in Slicer Preview Release that you download tomorrow or later. Enable `Fix invalid exposure tags` and `Specify character set` with `cp1251` parameter.

---

_[View the full topic](https://discourse.slicer.org/t/patientname-and-rus-language-trouble/28870)._