Professional Language Services for Medical Device Compliance: Beyond Translation

Why Medical Device Translations Fail at Notified Body Review

Last year a client with a Class IIb active implantable device had their technical file rejected by TÜV SÜD. The issue wasn't clinical data. It was the Chinese version of the risk management report, where "harm" and "hazard" were used interchangeably, making it impossible for the reviewer to trace risk control measures.

This isn't an isolated case. If a language service company translates literally without engaging regulatory logic, they're planting landmines.

Three Hard Requirements for LSPs in MDR/IVDR Context

1. Termbases Are Not Excel Files—They're Regulatory Mappings

EU MDR 2017/745 Annex I Section 23 requires labels and IFUs in the official language of the target market. But "official language" implies terminological consistency:

• GSPR 23.4 requires symbols to take precedence over text, but symbols must comply with ISO 15223-1. If a translator renders "STERILE" as "无菌" but omits the sterilization method, the Notified Body issues a non-conformity.
• In Clinical Evaluation Reports (CER), "clinical benefit" must be consistently translated as "临床受益" in the Chinese MDR context—not "临床获益" or "临床好处." Terminological drift makes reviewers question data integrity.

We build a three-tier termbase for every client: regulatory terms (MDR/IVDR), product terms (device names, components), and clinical terms (AE/SAE grading). Synchronized quarterly with IMDRF and MedDRA updates.

2. Engineering Constraints of Multilingual Labels

A device sold in 28 EU member states requires labels in 24 official languages. You don't just hire 24 translators.

• Space constraints: German "Gebrauchsanweisung" is 40% longer than English "Instructions for Use." Packaging layout must be redesigned.
• Symbol compliance: ISO 15223-1 symbols must sit alongside text, but in some languages (e.g., Greek) character height affects readability.
• Version control: Each language version maps to a UDI-DI. Translation changes must trigger UDI updates.

We recommend clients involve an LSP during Design Control for label pre-adaptation. Post-hoc translation costs 5x more in tooling changes.

3. Structured Translation for eCTD and IFUs

FDA 510(k) eCTD format requires PDF bookmarks and hyperlinks to match the source. Many LSPs translate PDF content directly, resulting in corrupted bookmarks and broken cross-references.

The professional approach:

1. Parse source files into XML (e.g., DITA or S1000D).
2. Translate while preserving structural tags.
3. Regenerate bookmarks and links when writing back to PDF.

IFU translation is trickier. MDR requires IFUs to accompany the device, but electronic IFUs must comply with Annex I Section 23.1(f) of 2017/745. We helped an endoscopy manufacturer migrate IFUs from PDF to HTML5 while maintaining version indices for 21 languages.

How to Vet a Language Service Provider

Don't just check for ISO 17100. Ask three questions:

• Who maintains the termbase? If they say "the client provides it," end the conversation.
• Does the review process include regulatory review? Linguistic review alone isn't enough. You need reviewers with RA backgrounds.
• How is change management handled? After a device design change, how are translation versions traced?

We use an internal "translation defect severity table":

Severity	Definition	Action
Critical	Affects safety or regulatory compliance	Immediate recall, RA介入
Major	Terminological inconsistency or omission	Corrected within 24 hours
Minor	Formatting or punctuation issues	Updated in next version

The Cost Trap of Multilingual Service Companies

Per-word pricing fails in medical devices. A single "sterile" could mean "无菌," "灭菌," or "消毒" depending on context. Translators paid per word have no incentive to verify context.

We prefer project-based pricing that includes termbase development, regulatory review, and version management. It looks expensive short-term, but long-term it saves Notified Body review cycles and recall risks.

A Real Timeline

An orthopedic implant client, from kickoff to CE certificate:

• Weeks 1-2: Termbase setup, regulatory mapping
• Weeks 3-6: Technical file translation + RA review
• Weeks 7-8: Notified Body query response translation
• Week 9: Multilingual label and IFU delivery

Three weeks longer than the client expected. But zero Notified Body findings. Those three weeks bought a first-pass approval.

When Does Your LSP Get Involved?

If the answer is "after the documents are written," the risk is already embedded. Professional language services should be embedded in the design control process, like QA.

Need to assess the translation compliance of your current technical file? Contact the Linguist team for a termbase sample and regulatory review checklist.