# Encoding Error for DICOM File from Chison

**URL:** <https://discourse.slicer.org/t/encoding-error-for-dicom-file-from-chison/28437>\
**Category:** Support\
**Tags:** dicom\
**Created:** [March 18, 2023, 12:31am UTC](https://discourse.slicer.org/t/encoding-error-for-dicom-file-from-chison/28437 "2023-03-18T00:31:26Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![HMAH](https://avatars.discourse-cdn.com/v4/letter/h/5e9695/32.png) [@HMAH](https://discourse.slicer.org/u/HMAH)\
**Post date:** [March 18, 2023, 12:31am UTC](https://discourse.slicer.org/t/encoding-error-for-dicom-file-from-chison/28437/1 "2023-03-18T00:31:26Z")

</div>

Hi everyone,

It’s my first time using 3D Slicer and I hit a big road block at my very first step which is importing the DICOM file to the software. The software show me a number of faults which are:

- DICOM dataset contains some encoding that we never thought we would see (ISO 2022 IR 6). Using ASCII encoding.

- Image spacing may need to be calibrated for accurate size measurements.

The file is from a Chison Sonobook 9 machine.

I’m unable to proceed any further. Any help is much appreciated.

Regards,

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [March 18, 2023, 3:19pm UTC](https://discourse.slicer.org/t/encoding-error-for-dicom-file-from-chison/28437/2 "2023-03-18T15:19:07Z")

</div>

It could help if you paste the exact messages you get in the Slicer console.

Also if you post some sample data of a phantom or something (not patient identifiable data) to replicate the issue then maybe someone can check on their system.

---

<div class="post-metadata">

**Author:** ![HMAH](https://avatars.discourse-cdn.com/v4/letter/h/5e9695/32.png) [@HMAH](https://discourse.slicer.org/u/HMAH)\
**Post date:** [March 18, 2023, 10:50pm UTC](https://discourse.slicer.org/t/encoding-error-for-dicom-file-from-chison/28437/3 "2023-03-18T22:50:09Z")

</div>

Hi Steve,

Thank you for responding.

I’ve taken the following screenshots as requested.  
 ![Screenshot 2023-03-19 at 9.07.43 am](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/9/0/90a27a323ad480742ae265bf3b749e58ad82e3b0.png)

 ![Screenshot 2023-03-19 at 9.11.14 am](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/4/4/448fffb996761c950cbc80c3c85587945759d423.png)  
 ![Screenshot 2023-03-19 at 9.11.06 am](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/9/e/9e43079da2ffb85f0c9d0eac3b0cd0f38ff963ff.png)

I’d like to submit the DICOM file I’m working on to this post but because I’m unable to open it with 3DSlicer, I can’t remove the patient’s data. Is there another software I can use to do this?

Thanks kindly,

---

<div class="post-metadata">

**Author:** ![HMAH](https://avatars.discourse-cdn.com/v4/letter/h/5e9695/32.png) [@HMAH](https://discourse.slicer.org/u/HMAH)\
**Post date:** [March 18, 2023, 10:57pm UTC](https://discourse.slicer.org/t/encoding-error-for-dicom-file-from-chison/28437/4 "2023-03-18T22:57:51Z")

</div>

Hi Steve,

I have been able to delete the patient’s information from the DICOM file using Osirix. The DICOM file is attached.

[DICOM File](https://www.dropbox.com/s/hrrxodm5gqzi6w4/IM-0001-0032-0001.dcm?dl=0)

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [March 19, 2023, 6:49pm UTC](https://discourse.slicer.org/t/encoding-error-for-dicom-file-from-chison/28437/5 "2023-03-19T18:49:01Z")

</div>

Hmm, it seems to work fine for me. This is a rendered screen capture though (the scale on the right is burned into the image and it’s only one frame) so probably nothing meaningful to do with it in slicer.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/b/8/b8a9eb0064457af44c5e20a2ca445e3d6a28016c.jpeg)

Maybe Osirix fixed the format compared to the original?

---

<div class="post-metadata">

**Author:** ![HMAH](https://avatars.discourse-cdn.com/v4/letter/h/5e9695/32.png) [@HMAH](https://discourse.slicer.org/u/HMAH)\
**Post date:** [March 20, 2023, 12:32am UTC](https://discourse.slicer.org/t/encoding-error-for-dicom-file-from-chison/28437/6 "2023-03-20T00:32:49Z")

</div>

Hi Steve,

Yes, it seems Osirix had fixed the format. I can open the new file but not the original.

Now i’m facing with a new problem. I thought I’ve exported a 3D Dicom file but it is in fact only an image. I need to find a way to export the 3D file from a Chison Sonobook 9 and their manual is next to useless.

Your help is much appreciated.

---

<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:** [March 20, 2023, 4:53am UTC](https://discourse.slicer.org/t/encoding-error-for-dicom-file-from-chison/28437/7 "2023-03-20T04:53:47Z")

</div>

Most 3D ultrasound systems do not allow saving of the 3D data in standard file fornat. You can contact sales representatives or technical support people and ask for a 3D data export.

Alternatively, you can try to reverse engineer their proprietary file format. It should be doable if they don’t use compression.