Chinese Patient Names Break on Export: Trace Ultrasound DICOM Character Sets

The Symptom at the Console: Why Do Chinese Names Fail Downstream?

Consider a fictional acceptance test at a bilingual ultrasound facility. The scanner displays the test name 张小东 correctly, and a subsequent send reports success. On the PACS workstation, however, the name appears as question marks or garbled text. That discrepancy is enough to investigate demographic delivery even when the image is visible; it is not a diagnosis of the scanner or archive.

Three superficially similar outcomes need different evidence: a replacement glyph on screen, literal question-mark bytes in an object, and a study rejected by the receiver. Only the first describes presentation; the second identifies a damaged representation at the inspected hop; the third needs a status code and receiver log before its cause is known. Preserve the original artifacts and compare adjacent stages rather than inferring a cause from a screenshot.

For healthcare technology management (HTM) teams, independent service organizations and distributors accepting used or repaired systems, the immediate decision is who should investigate. If association and image delivery work while only name text fails, check application encoding, mapping and rendering first. This does not certify every board as healthy. Separate connectivity symptoms belong in our guide to ultrasound DICOM and PACS output failures; collect hardware evidence before requesting component repair.

DICOM text attributes contain encoded character data, and a console display need not use the same representation as the exported object. The Modality Worklist (MWL) response, scanner-created instance, archive database and viewer can therefore disagree. The useful trace pairs a declaration with the bytes and decoded value at each boundary, keeping authorized demographic updates separate from encoding faults. ^{1 3}

DICOM Specific Character Set (0008,0005): Which Chinese Encodings Are Legal?

Specific Character Set (0008,0005) controls the extended repertoire for affected text Value Representations (VRs), including SH, LO, ST, LT, PN, UC and UT. It does not redefine every attribute: constrained fields such as unique identifiers (UIDs) and dates retain their own rules. Check Patient’s Name (0010,0010) specifically rather than treating a readable pixel annotation as proof of a correct PN value. ^{1 2}

When the declaration is absent: PS3.5 specifies the default ISO-IR 6 repertoire and prohibits code extension for those text fields. Chinese bytes supplied without a valid declaration do not conform to that encoding. The standard does not prescribe a universal rejection or stripping outcome: a particular receiver may store opaque bytes, substitute characters or reject the instance. Record the observed behavior and the product’s documented policy. ^{1 11}

For the Chinese paths considered here, distinguish ISO 2022 code extension from a single multi-byte encoding. A valid term still needs support at every relevant endpoint:

1. Code extension: ISO 2022 IR 58 identifies the GB2312 repertoire. In the standard’s Chinese example, \ISO 2022 IR 58 has an empty first value, meaning the default repertoire, followed by the Chinese set. ISO_IR 58 is not a defined term. The supported combination and escape handling must be checked in the implementation. ^{2 4 5}
2. One multi-byte set: ISO_IR 192 (UTF-8), GB18030 and GBK each require a single value in (0008,0005), without ISO 2022 code extension. An object declaring ISO_IR 192\ISO 2022 IR 58 violates that rule. UTF-8 requires minimal-length encoding; changing the declaration alone does not transcode existing bytes. ^{1 2}

Person Name (PN) Component Groups: Why Do Hanzi Belong in the Ideographic Group?

A valid character-set declaration does not by itself establish a correct Person Name (PN) layout. DICOM PS3.5 Section 6.2.1.2 separates the parts of a name, such as family and given names, into components. It separates alphabetic, ideographic and phonetic representations into component groups. Check both the encoding and this structure when comparing the source name with the receiver’s display. ³

Within any single representation, a name may contain up to five components separated by caret (^) characters: FamilyName^GivenName^MiddleName^Prefix^Suffix. To support multilingual healthcare workflows where individuals possess both Romanized transliterations (such as Pinyin) and native ideographic or phonetic scripts, DICOM establishes up to three component groups, separated by equal sign (=) delimiters: Alphabetic Group = Ideographic Group = Phonetic Group.

Placement under UTF-8: PS3.5 6.2.1.2 restricts the alphabetic group to U+0020–U+1FFF plus specified punctuation and kana when UTF-8, GB18030 or GBK is used. Hanzi such as 张 lie outside that range and belong in the ideographic group. An ideographic-only name may therefore start with =, for example =张^小东. Keep group placement and byte decoding as separate checks. ³

The standard’s informative example: Annex K.2 illustrates Zhang^XiaoDong=张^小东= with \ISO 2022 IR 58. It is an encoding example, not evidence that a particular scanner supports this path. ⁵

• Alphabetic group: Zhang^XiaoDong uses the default repertoire in this example, with no escape sequence in the first group.
• Ideographic group: after =, the example designates ISO-IR 58 to G1 with 1B 24 29 41 before 张; its GB2312 bytes are D5 C5.
• Next name component: after ^, the example repeats 1B 24 29 41 before 小东. ASCII remains in G0, so there is no additional escape back to ASCII before the delimiter in this particular G1 example.
• Optional trailing group: the final = marks an empty phonetic group; a trailing empty group and delimiter may be omitted. Chinese-language names can have phonetic representations too. ^{3 5}

Layout versus corruption: if a received value contains 张^小东 in the first group, record that layout separately from a decode failure. A viewer may display it, while another may impose the standard’s component-group restriction. Do not label a readable name as irrecoverably corrupt, infer how common this layout is, or rewrite historical clinical records to make a test pass. Resolve the expected representation with the modality and archive owners. ³

Triage: What Evidence Localizes the First Changed Hop?

Table 2 lists hypotheses, not one-to-one diagnoses. Compare unmodified source and receiver artifacts for the same fictional instance. If a display shows question marks but the stored PN still contains valid Hanzi, the characters have not been lost from that object. If a later copy contains 3F bytes while the preceding copy does not, investigate the intervening conversion. A byte inspection must use a tool that exposes the original value, not merely its decoded text output. ^{11 13 14}

Reading the Conformance Statement: What Do the Scanner and Archive Actually Support?

Use the exact model, software release and application entity’s conformance statement on both sides. PS3.2 provides a standard disclosure template; it is not, by itself, a legal obligation or proof that two products interoperate. Older statements can use different section numbers. Match the content below rather than requiring an old device’s PDF to contain today’s table labels. ^{6 7}

Look for four disclosures, keeping input, output and display support separate:

• Supported sets: current template Table N.1-15 lists the DICOM terms and IANA names. A product’s actual list, not the template’s example rows, determines its claimed support. ⁷
• Attribute presentation and editing: Table N.5-164a asks which fields support extended characters and how fonts or substitutions are handled. Patient’s Name support does not establish equivalent support for every descriptive field. ⁶
• Received-to-created-instance mapping: Table N.5-165 describes conversions, including MWL values used in created instances. Its Japanese-to-UTF-8 example demonstrates how to document a mapping; it is not a default rule for Chinese data. ⁶
• Unsupported-set behavior: find the product’s documented response and any configuration limitations. Distinguish storing, displaying, querying and exporting; success in one operation does not establish the others. ⁶

Two product-specific examples: these documents illustrate why appearance and brand are poor substitutes for a release-specific capability check. They do not establish support for the reader’s installed system.

• TOMTEC-ARENA TTA2: the Philips-hosted statement D.32.0131-16 is dated 17 November 2021. Sections 7/7.1, printed pages 29–30, list ISO_IR 192 and GB18030 for decoding/display support. Section 5.2.2, printed page 27, says its media export encoding is UTF-8. That media-specific statement must not be generalized to every network export path. ⁸
• Philips Lumify R5.0: HSDP-1299212, version 01 dated 17 August 2023, Table 37 on page 35 lists ISO_IR 100 as its supported extended set; created-instance tables also declare that term. The statement lists no Chinese-capable set. It does not establish whether the mobile app accepts Chinese entry or how an unsupported name is handled. Confirm those questions with the applicable OEM documentation and a synthetic test. ⁹

The takeaway for biomedical specialists is clear: never assume DICOM character-set capabilities based on equipment appearance, cart price, or manufacturer reputation. Every system's exact model and software revision must be cross-checked against its conformance statement before designing an integration workflow.

Downstream Reality: PACS Archiving, Coercion, and Viewer Rendering

Once a Service-Object Pair (SOP) instance leaves the ultrasound cart, check archive storage, demographic updates and viewer rendering separately. A stored object and a readable name on one client do not establish correct presentation on every required viewer. The examples below show why each operation needs its own evidence.

Archive versus Health Level Seven (HL7): dcm4che Archive 5 documentation lists ISO 2022 IR 58, ISO_IR 192, GB18030 and GBK for DICOM decoding/display. It separately states that multi-character-set escape sequences in HL7 v2 messages are unsupported. This is one product’s boundary, not a rule that all hospital interfaces require a UTF-8 gateway. Keep any HL7 interface verification with the facility’s integration team. ¹⁰

Authorized updates versus decoding faults: the Sectra PACS 28.1 statement, March 2026, section 8.1.4 and Table 8.3, lists Patient’s Name among fields that may be modified during export. It attributes coercion to updated hospital information system/HL7 information, import grouping or configuration. Compare the audit history and source of an update before calling every changed name an encoding error. A supported product capability does not authorize an engineer to edit a clinical record. ¹⁶

Toolkit limits: J. Riesmeier’s November 2011 DCMTK description explains that string bytes could be stored without checking the accuracy of the Specific Character Set declaration. This historical example explains why a successful file operation need not validate the text. It does not establish the behavior of every current toolkit or appliance. A decoded dump can conceal substitutions or transcoding; retain the original instance and use an appropriate raw-value inspection method. ¹¹

Dated implementation cases: Conquest thread 50545 (July 2023) records different Traditional Chinese presentation across server/database/viewer paths; the maintainer describes a converter assuming ISO_IR 100. In fo-dicom 4.03 issue 938 (2019), an explicit UTF-8 parameter removed an umlaut’s question-mark substitution, but the query still failed; the reporter later used a different encoding. Slicer issue 4778 (March 2020) records a display regression and discussion of preview builds and Windows code pages, with a remaining discrepancy. These cases support checking each layer; they do not prove a universal fix, irrecoverable source loss or present-day product failure. ^{12 13 14}

Synthetic Round-Trip Verification Protocol

The following is a proposed acceptance workflow for the facility’s modality and PACS/IT owners. Adapt it to the documented capabilities and required name representations of the installed releases. Passing it demonstrates the tested text path; it does not replace electrical safety, image-quality or other return-to-service checks.

Use facility-approved fictional demographics and an isolated test destination with controlled access. Keep test objects clearly identified and out of clinical matching/reporting workflows. Handle any existing clinical discrepancy under the facility’s privacy and record-correction process. For a repair shipment, follow the separate patient-data export and erasure handoff. Preserve originals and audit records; retyping a displayed name is not evidence that the producing fault is fixed.

1. Define the test contract: record scanner, worklist, archive and viewer releases; expected name groups; the sets each operation supports; and any approved conversion. Create a fictional worklist order. Use Zhang^XiaoDong=张^小东= as one test value, plus a facility-chosen fictional value representing any additional scripts required. Do not assume GB2312 covers every character.
2. Compare the MWL response and console: the authorized worklist/modality team records (0008,0005), PN bytes and decoded groups in the response. Compare the console with the representations it documents, rather than requiring every device to show three groups simultaneously. Retain any substitution or truncation evidence.
3. Inspect the scanner-created instance: produce an OEM-supported nonpatient test object and send it to the approved test receiver. Inspect the stored instance with a DICOM-aware tool, retaining the original bytes separately from a decoded dump. Pair (0008,0005) with (0010,0010). For the ISO 2022 IR 58 example check component escapes; for UTF-8 verify its own bytes without ISO 2022 escapes. Document any deliberate conversion from the worklist response.
4. Compare the retrieved archive object: retrieve the same fictional instance through an approved workflow and compare its declaration, decoded PN groups and raw value with the scanner output. Explain any encoding conversion or authorized demographic update from the archive’s documentation and audit record. If bytes were replaced, locate the earliest artifact still containing the intended characters. Archive responsibility and deletion are a separate decision covered in the storage-commitment guide; commitment does not prove a name is readable.
5. Verify the required viewers and sign off: check each viewer used in the acceptance scope, its software version and required name representation. Record the first divergence, responsible owner and retest result. A screenshot proves presentation only. Keep unresolved demographic discrepancies out of the accepted workflow pending the facility’s disposition, and coordinate other checks through the maintenance and acceptance checklist.

If one hop cannot support the required characters: stop treating UTF-8 as a universal switch. Ask the responsible vendors and facility owner whether a supported update or a validated conversion can preserve all required characters and name groups. ASCII transliteration does not preserve Hanzi, and a narrower repertoire may not represent a rare character. Document any approved reduced workflow as a limitation rather than claiming complete multilingual acceptance; retain clinical corrections under the facility’s governance process.

Recheck triggers: repeat the agreed synthetic test after a worklist/PACS migration, modality software change, viewer update or relevant conformance-statement revision. The standard links are the current online edition reviewed on 11 October 2026; named product documents and issue reports are dated examples, not claims about all current releases.

Where Rongtao Medical Fits — And Where It Does Not

Clarifying operational boundaries between clinical software engineering and medical hardware servicing protects healthcare facilities from costly misdirected repairs and extended equipment downtime.

Rongtao Medical provides component-level ultrasound board repair, probe service and tested parts. Its published service facts specify 48-hour real-machine testing for every repaired board, standard 5–8 business-day board-repair turnaround and a typically 90-day warranty. Confirm item-specific scope, availability, turnaround and warranty in the quotation; the testing claim does not establish full clinical workload or validation of a hospital’s multilingual integration. ¹⁵

Escalate to hardware service when qualified investigation identifies a physical fault or separate connectivity/boot symptoms. A corrupted name alone does not identify a failed board, connector or transceiver. Retain symptom logs and model/revision evidence so a service provider can assess the actual hardware question.

PACS and radiology information system (RIS) configuration, interface mapping and clinical-record reconciliation belong with the facility’s IT, archive and OEM teams. Rongtao’s documented board/parts services do not establish a PACS integration or database-consulting offering. If application evidence identifies a charset mismatch, address that supported software path before buying hardware; continue to assess any independent hardware symptoms on their own evidence.

Name readability is one acceptance criterion. Numeric measurement delivery is a different task: the DICOM SR measurement-delivery guide explains that path. Image-based reporting can remain valid where it meets the facility’s requirements; it is not automatically defective because it lacks structured fields.

Quote-ready hardware handoff: if a hardware issue remains, send the evidence below through the approved contact channel. Keep patient demographics and clinical images out of a commercial enquiry; fictional logs or redacted evidence are sufficient for initial scope discussion.

• Equipment: OEM, exact model, software release and relevant hardware revision.
• Component: manufacturer part number and revision from the label, plus clear label photos. Only qualified staff should remove a board; request both sides when it is already safely removed.
• Symptoms: observed fault/error, when it occurs, separate connectivity or boot symptoms, and prior service history. Provide approved redacted or fictional diagnostic evidence.
• Supply request: quantity, repair or replacement preference and destination country. Confirm compatibility, current availability and terms against the actual item.

For verified hardware diagnostics, circuit board exchanges, or ultrasound transducer repairs, explore our capabilities at Rongtao Medical Repair Services or submit your technical repair inquiry directly through Rongtao Medical Contact.