Only garbled characters can be seen in DICOM Dump for Visual Studio Code

There are three troubleshooting steps at the bottom of the link, and the first and third of them are as follows. Is that why the original file does not conform to the standard or is corrupted or the character encoding of the data is different?

My DICOM file does not load at all! : Can you open that file with dicom-parser's online demo? If not, probably your DICOM file is not standard-compliant, and there is little I can do. Some DICOM implementations are tolerant enough to open mildly broken files. Just because you can view your file with does not mean the file is not corrupted. If you could open the file with the demo above and are still ggetting an error from this extension, feel free to report as bug.

DICOM file is not loaded at all!: Can I open it in the online demo of dicom-parser?Otherwise, there is little I can do because the DICOM file is probably not compliant with the standard.Some DICOM implementations are resistant enough to open slightly corrupted files.<Insert your favorite viewer here> does not mean that the file is not corrupt.If the above demo allows you to open the file, and this extension still fails, report it as a bug.

Patient/institution names are garbled! : Currently the character encoding support is limited and buggy, and it's partially due to the fact that DICOM uses rare character encodings not supported by iconv-lite. Also note that some DICOM implementations store multibyte strings with a totally wrong encoding (e.g., Japanse SJIS). I'd rather not support all sorts of malformed files "in the wild", but reasonable Suggestions and PRs are welcome.

Patient/Facility Name is garbled!: Support for character encoding is currently limited and bugged.This is partly due to the fact that DICOM uses rare character encoding that is not supported by iconv-lite.Also note that in some DICOM implementations, multi-byte strings are stored with completely incorrect encoding (for example, SJIS in Japan).Rather than supporting all kinds of unauthorized files "in the wilderness", we welcome reasonable suggestions and PR.