Hi guys,
In the DICOM db, I get some ??? instead of the patient name. Is there a way to amend this?
TIA
Dr. Avri Lev
Support for international characters was limited in Slicer-4.10. Slicer-4.11 (Slicer Preview Release) has full unicode support, so special characters should show up correctly.
Well, the only issue, that it doesn’t…
Could you send the content of “Operating system” line in application log (menu: Help / Report a bug)?
It should be something like this:
[DEBUG][Qt] 18.08.2020 00:32:49 [] (unknown:0) - Operating system .........: Windows / Personal / (Build 18363, Code Page 65001) - 64-bit
How the data set was created?
Can you share a sample data set of a phantom (not a patient), with similar characters in the patient name?
I guess this is what you want:
[DEBUG][Qt] 18.08.2020 10:47:37 [] (unknown:0) - Operating system …: Windows / Professional / (Build 19041, Code Page 65001) - 64-bit
Thank you, this looks good.
How the data set was created?
Can you share a sample data set of a phantom (not a patient’s), with similar characters in the patient name?
Hi, I wouldn’t know how to do what you’ve asked from me…
Sorry.
Best,
Dr. Avri Lev
How the data set was created? Acquired on a clinical scanner? Was it anonymized?
Can you acquire a data set of a phantom (e.g., calibration object, but if the scanner can acquire an empty image then that’s fine, too, you don’t need to put anything in the bore), enter patient name that has similar characters that you have problem with displaying, and share that data set, so that we can investigate if the created image is valid and if it is, why Slicer does not display the characters properly?
The data are taken from a CT scan. I have the dicoms in a library on my PC.
Where can I get a phantom data?
Best,
Dr. Avri Lev
A “phantom” is just any object that you out into the scanner. Do you still have access to the scanner so that you can acquire image of any object (or just the empty bore) with the same protocol and similar patient names that are used in your existing images? We could use these test images to investigate why some characters in the name do not appear correctly. Normally we could use anonymized patient images for such investigation but anonymization would remove the patient name, so it is not a good solution in this case.
Note that you don’t have to see the patient name if you import them one by one and save as nrrd image with the appropriate name. You can write a script that automates this, if doing manually would be too tedious.
Hi Andras Lasso,
I did some digging on the subject.
It seams that the metadata associated with each DICOM file is to blame For the phenomena.
The issue resides in the field “Patient Name” and only there, since this is the field where you put the patient name by the receptionist who’s responsible for checking in the patient. The app cannot read other fonts besides Latin ones, hence it’s not adhering to the UTF-8 protocol.
i.e. the examination date is written in a number format, so Windows can read it and format it accordingly in my language. (see photos attached).
Now, the only thing to do here, is to let us, users, the possibility to be able to edit that field (Patient Name), directly in 3D Slicer, because it is impossible to make these changes for every single DICOM file (hundreds of them…) .
I know that 3D Slicer is open source and I think also that the app can be manipulate through coding - hence developers can change the behavior of the app.
Best,
Dr. Avri Lev
Did you try the dicom patcher module?
https://slicer.readthedocs.io/en/latest/user_guide/modules/dicompatcher.html
Extending it with extra name editing fearures would very feasible, and a good project that any python programmer could take on.
Slicer can read patient name with various encodings:
There is a good chance that there is something wrong with the DICOM file encoding, but of course it is possible that the DICOM file is valid and DCMTK toolkit does not interpret it correctly. We need an example file to verify. You can create an example data set by creating a patient in the dental imaging software (with non-Latin characters in the patient name) and acquire an image of anything.
I can’t find that module on 3d slicer…
Can you guide me through, please?
Avri
I really don’t understand what you guys referring to by “. We need an example file to verify. You can create an example data set by creating a patient in the dental imaging software (with non-Latin characters in the patient name) and acquire an image of anything.”
What kind of file? I’m really confused now.
Also I cannot fine the DICOM Patcher module within 3D Slicer ( in the Slicer extension section)…
Thanks,
Dr. Avri Lev
I found the module. Thank you guys, everything back to normal. 
We can only fix those problems that we can reproduce on our own computers. With DICOM images that we have, we don’t have any patient name encoding issues. Therefore, if you want us to investigate this issue then you need to send us a DICOM image file that you have problem with. We don’t want to handle files that have patient health information in it, so send us a DICOM image file that does not belong to a real patient (but it contains a fake patient name with non-latin characters in it).