Medical Translation Services: ISO Compliance & Regulatory Requirements by Region

Introduction: Why Medical Translation Is a Compliance Discipline, Not a Language Service

In most industries, a translation error is an inconvenience. In medical translation, a translation error can be a patient safety incident, a regulatory rejection, or grounds for product liability. This single distinction explains why medical translation operates under a layer of formal standards and regulatory obligation that does not exist anywhere else in the language services industry.

Medical device and pharmaceutical manufacturers expanding into new markets face two parallel sets of requirements that must both be satisfied. The first is the quality management framework — the ISO standards that define how a translation provider must be organised, staffed, and audited to be considered fit to handle medical content. The second is the regional regulatory framework — the specific language, certification, and documentation rules imposed by each market’s regulatory authority, from the FDA in the United States to the NMPA in China.

This guide explains both layers in detail: the ISO standards that govern medical translation quality (ISO 17100, ISO 13485, ISO 9001), and the region-by-region regulatory requirements that determine what must be translated, into which language, and under what certification, for the US, EU, China, Japan, and other major markets.

A note on scope: This guide provides a comprehensive overview based on current published regulatory guidance. Regulatory requirements change — the EU MDR/IVDR language tables themselves have been revised multiple times since 2021. Always verify current requirements with your regulatory affairs team or notified body before finalising a submission strategy.

The ISO Standards That Govern Medical Translation Quality

Three ISO standards form the foundation of quality medical translation. Understanding what each one actually certifies — and what it does not — is essential for evaluating a translation partner.

ISO 17100:2015 — Translation Services Standard

ISO 17100 is the global standard for translation service quality, applicable across all industries but foundational to medical translation work. It defines the minimum requirements a language service provider must meet across the full translation lifecycle.

Key requirements under ISO 17100 include:

• Translators must hold recognised translation qualifications, or a minimum of two years of documented professional translation experience, or equivalent combined education and experience
• Every translation must undergo independent revision by a second qualified linguist — self-review by the original translator is not sufficient
• Projects must follow a documented workflow from initial brief through translation, revision, and final delivery, with full traceability at each stage
• Terminology must be managed systematically, typically through translation memory (TM) and glossary tools, to ensure consistency across documents and over time
• Client feedback and complaint-handling procedures must be documented and acted upon

ISO 17100 certification confirms that a provider has the systems and qualified personnel to produce a consistent, quality-controlled translation. It does not, by itself, confirm domain expertise in medical or regulatory content — that requirement is addressed by ISO 13485.

ISO 13485:2016 — Medical Devices Quality Management System

ISO 13485 is the internationally recognised standard for quality management systems specific to the medical device industry, covering the entire device lifecycle from design through manufacturing, distribution, and post-market surveillance. Critically, this standard applies not only to device manufacturers but also to organisations providing services related to medical devices — which explicitly includes translation providers.

When a translation agency holds ISO 13485 certification, it means the agency has implemented a quality management system specifically aligned with medical-sector regulatory demands. In practice, this requires:

• Document control procedures that meet medical-sector record-keeping standards, including version control and change tracking
• Risk management processes applied to the translation workflow itself — identifying where translation errors could compromise patient safety and building controls against them
• Validated processes for handling Instructions for Use (IFUs), labelling, clinical evaluation reports, and other device-related content
• Full traceability from source document to final translated deliverable, supporting audit requirements from notified bodies and regulatory authorities
• Defined competency requirements for linguists working on medical device content, beyond the general ISO 17100 qualification bar

Why this matters in practice: Choosing an ISO 13485-certified translation partner is not only a quality preference — for many manufacturers, it is close to a practical necessity. Notified bodies and regulatory reviewers increasingly expect to see evidence of a controlled, audit-ready translation process as part of technical file review, and a research survey found that 

68% of international medical device manufacturers experienced regulatory delays attributable to translation issues — a figure that rose to 84% for Class III (highest-risk) device manufacturers specifically. Terminology inconsistency and regulatory terminology mismatches were the leading causes.

ISO 9001:2015 — General Quality Management

ISO 9001 is the broad, industry-agnostic quality management standard. While not medical-specific, it is frequently held alongside ISO 17100 and ISO 13485 by serious medical translation providers, demonstrating an organisation-wide commitment to documented process, continuous improvement, and customer satisfaction tracking that underpins the more specialised standards above it.

Regulatory Translation Requirements by Region

Holding the right ISO certifications addresses the quality dimension of medical translation. But each regulatory market imposes its own specific rules about what must be translated, into which language, under what certification, and through what process. The sections below cover the major global markets.

United States: FDA Requirements

The US Food and Drug Administration (FDA) regulates medical device labelling under Title 21 of the Code of Federal Regulations, primarily 21 CFR Part 801 for medical devices and Part 809 for in vitro diagnostics, with quality system controls addressed under 21 CFR Part 820.120.

English-Only Labelling Requirement

Under 21 CFR 801.15, all medical device labelling distributed in the United States must be in English, with one narrow exception: products distributed solely within Puerto Rico or US territories where the predominant language is not English. For prescription-only devices sold exclusively in Puerto Rico, Spanish-only labelling is permitted.

The Foreign Language Addition Rule

A frequently overlooked provision states that if any representation on a device’s label or labelling appears in a foreign language, then all required labelling information must also appear in that same foreign language. In other words, a manufacturer cannot add a partial foreign-language translation — if you translate any part, the full required labelling must follow in that language too.

Certified Translation for Submissions

English is the required language for FDA regulatory submissions. For international manufacturers with source documents in another language — for example, a German manufacturer with German-language test reports — certified English translations are required for any non-English components of a submission, including clinical study reports, patent documentation, and supporting data. A certified translation includes a signed statement attesting to the translation’s accuracy and the authenticity of the source material. Submissions without proper certification are subject to rejection.

Symbols as a Compliance Tool

FDA addresses the use of standardised symbols under 21 CFR 801.15. Internationally recognised symbols (often aligned with ISO 15223-1, the standard also used for EU MDR compliance) can reduce the labelling space needed and bypass some translation requirements — though a symbols glossary must still be included in the IFU or accompanying documentation.

Beyond Labelling: Language Access Obligations

While device labelling itself must be in English, healthcare systems and providers receiving federal funding have separate language access obligations under Title VI of the Civil Rights Act for patient-facing communication with limited-English-proficiency populations. This is a distinct compliance track from device labelling but relevant for manufacturers whose devices are deployed in US healthcare settings serving diverse patient populations.

European Union: MDR & IVDR Requirements

The European Union operates the most linguistically demanding regulatory framework in the world for medical devices, governed by the Medical Device Regulation (MDR, Regulation (EU) 2017/745) and the In Vitro Diagnostic Regulation (IVDR, Regulation (EU) 2017/746).

The Legal Basis: Article 41

MDR Article 10(11) requires manufacturers to ensure that devices are accompanied by required information in an official Union language determined by each Member State where the device is made available. Article 41, under the heading ‘Language requirements’, states that all required documents ‘shall be drawn up’ in the language or languages determined by the Member State concerned. This is a deliberately strengthened formulation compared to the previous Medical Devices Directive, which only said Member States ‘may require’ translation — the shift from ‘may’ to ‘shall’ reflects a tightening of enforcement expectations since MDR became fully applicable in May 2021 (IVDR followed in May 2022).

Scope: Which Documents Require Translation

EU language requirements apply to a defined set of documentation, which can vary by Member State and by whether the device is intended for professional use, lay/patient use, or both:

• Labels and packaging information
• Instructions for Use (IFUs)
• Implant cards (Article 18 MDR), required for implantable devices
• Summary of Safety and Clinical Performance (SSCP) for implantable devices and Class III devices
• Any mandatory information intended for users or patients, including warnings, precautions, and conditions of use
• Post-market documentation intended for patients or end-users

Up to 24 Official Languages

Because each of the 27 EU Member States (plus Iceland, Liechtenstein, Norway, and Turkey under the same framework) can independently set its own language requirement, full pan-European distribution can require IFU and labelling translation into as many as 24 official languages. The European Commission publishes and periodically updates official Language Requirements Tables for both MDR and IVDR — Revision 3 of the MDR table was published in August 2025 — to help manufacturers, particularly SMEs, navigate which languages are accepted in each market and under what conditions.

The English Exception — and Its Limits

Member States are encouraged, though not obliged, to consider accepting information in another language (commonly English) where safe device use is not compromised — this flexibility is most often extended for devices intended solely for professional use rather than lay/patient use. However, this remains a national-level decision, and manufacturers cannot assume English will be accepted without verifying the specific Member State’s position in the official tables.

Software and Digital Interfaces

Whether software interfaces — such as companion apps or onboard device displays — require translation is a frequent point of manufacturer confusion. The Commission’s language tables do include a column addressing this, but as of the most recent revisions, this field is only populated for roughly half of the covered countries, meaning manufacturers often need direct confirmation from the relevant national authority.

A Live Regulatory Area: 2025–2026 Reform Proposal

In December 2025, the European Commission published a proposed MDR/IVDR revision that includes potential language flexibility for certain professional-use devices. The proposal remained open for feedback through March 2026 and had not yet been adopted at time of writing. Manufacturers should monitor this proposal closely, since any softening of language requirements would apply selectively by device risk class and intended user — and core safety and transparency obligations are expected to remain unchanged regardless of the outcome.

China: NMPA Requirements

China’s National Medical Products Administration (NMPA) — formerly the CFDA — regulates medical devices, in vitro diagnostics, and pharmaceuticals, and applies one of the strictest single-language mandates of any major regulatory market.

Simplified Chinese, Without Exception

All labelling, Instructions for Use, technical files, registration dossiers, and clinical data submitted to NMPA must be in Simplified Chinese. The NMPA does not accept Traditional Chinese as a substitute — this is a meaningful distinction for manufacturers also targeting Hong Kong, Taiwan, or other Traditional Chinese-reading markets, since separate translation work is required for each script variant.

Registration Pathway and Local Representation

Imported devices must be registered directly with the central NMPA in Beijing, and foreign manufacturers must appoint a local Authorized Agent in China to manage submission and post-market communication. Class II and Class III devices require full technical review and product testing, and may require local clinical trial data in addition to (or instead of) overseas Clinical Evaluation Reports, depending on the device’s risk profile and predicate history.

Terminology Standardisation

NMPA reviewers evaluate submissions for clarity, accuracy, and consistency — not literal translation correctness alone. Translations must use standardised regulatory terminology aligned with NMPA’s published nomenclature and Chinese Pharmacopoeia standards where applicable. Incorrect or inconsistent terminology is one of the most common causes of review delays and requests for clarification.

Quality Management System Evidence

As part of the registration dossier, manufacturers must submit proof of an active quality management system — an ISO 13485 certificate is the standard form of evidence accepted by NMPA, linking back directly to the ISO compliance discussion above.

Japan: PMDA Requirements

Japan’s Pharmaceuticals and Medical Devices Agency (PMDA) regulates devices and pharmaceuticals under the Pharmaceuticals and Medical Devices (PMD) Act, with requirements that combine strict language mandates with sector-specific technical standards.

Japanese-Language Documentation Is Mandatory

PMDA requires Japanese-language documentation for device registration, covering clinical data summaries, device descriptions, and risk analysis files. Japanese medical and regulatory terminology carries significant complexity and nuance, and PMDA reviewers expect translations that align not just linguistically but with established Japanese regulatory and scientific expression conventions — generic translation without local regulatory expertise is a common source of review friction.

The e-Package Insert (e-PI) System

Since August 2021, Japan has used an electronic package insert system for prescription drugs and certain medical devices. Under this system, the Japanese-language version posted on PMDA’s official website is the legally official labelling document — any English version that may exist serves only as a reference and has no regulatory standing. Users and healthcare professionals access the official Japanese insert via barcode, 2D code, or PMDA’s website directly.

Compliance with Japanese Industrial Standards

Beyond PMDA submission requirements, manufacturers must ensure alignment with Japanese Industrial Standards (JIS) relevant to medical devices, and translations should reflect this technical standards framework in addition to general regulatory language.

In-Country Review Recommended

Given the complexity and specificity of Japanese regulatory and medical terminology, in-country review by linguists with both Japanese fluency and life sciences regulatory experience is strongly recommended — not merely as a quality enhancement, but as a practical risk reduction measure against the kind of submission delays that generic translation approaches frequently trigger in this market.

Other Major Markets: Quick Reference

Beyond the four markets covered in detail above, manufacturers expanding globally should be aware of language requirements in the following regulatory jurisdictions.

What ISO-Compliant Medical Translation Actually Looks Like in Practice

Combining the ISO quality framework with the regional regulatory requirements above produces a specific, repeatable workflow that distinguishes professional medical translation from general translation services.

1. Linguist Qualification and Domain Assignment

Translators are not assigned by language pair alone — they are matched by language pair plus subject-matter domain (medical devices, pharmaceuticals, clinical research, IVD) and, where relevant, by specific regulatory market experience (EU MDR vs. FDA vs. NMPA documentation conventions differ meaningfully even for the same source content).

2. Independent Second-Linguist Review

Every translation undergoes review by a second qualified linguist who did not produce the original translation — a non-negotiable requirement under ISO 17100 and reinforced under ISO 13485 for medical content specifically.

3. Back-Translation for High-Risk Content

For high-risk content — informed consent forms, clinical trial protocols, critical warnings — many providers and sponsors require back-translation: translating the target-language version back into the source language by an independent translator, then comparing it against the original to catch meaning drift introduced during translation. This is standard practice for clinical and pharmacovigilance content even where not strictly mandated by regulation.

4. Terminology Management

A controlled, market-specific glossary and translation memory is built and maintained for each client and product line, ensuring that device names, technical terms, and regulatory phrases remain consistent not only within a single document but across the full lifecycle of labelling updates, IFU revisions, and post-market communications.

5. In-Country Regulatory Review

Beyond linguistic QA, content is validated against local regulatory and cultural expectations by in-country reviewers — confirming that translated labelling will be accepted by the relevant notified body, NMPA reviewer, or PMDA examiner, not just that it is linguistically correct.

6. Full Traceability and Certification

Every project maintains a complete audit trail — source document, translation, review history, version changes — supporting both notified body audits in the EU and FDA inspection readiness in the US. Where required, a signed certificate of translation accuracy accompanies the final deliverable.

The Cost of Non-Compliant Medical Translation

The consequences of inadequate medical translation are more severe and more concrete than in most other content categories.

Beyond delay, the practical risks of non-compliant medical translation include: outright rejection of regulatory submissions; product recalls triggered by mistranslated warnings or dosing instructions; product misbranding violations and associated FDA warning letters; and, in the most serious cases, patient harm and consequent product liability exposure. These risks sit on top of the straightforward commercial cost of delayed market entry — every month spent resolving a translation-driven query from a notified body or regulator is a month of lost revenue in that market.

What to Look for in a Medical Translation Partner

Given the stakes outlined above, selecting a medical translation provider should be treated as a regulatory due-diligence exercise, not a procurement decision based on price per word alone.

• Current ISO 17100, ISO 13485, and ideally ISO 9001 certification, verifiable and renewed within the standard audit cycle
• Demonstrated experience with your specific target regulatory frameworks — EU MDR/IVDR, FDA 21 CFR, NMPA, PMDA — not just general medical translation experience
• Native-speaking linguists with documented subject-matter expertise in your device category or therapeutic area
• A documented, auditable QA workflow including independent second-linguist review and, where appropriate, back-translation capability
• Robust terminology management and translation memory systems to maintain consistency across labelling updates and product line extensions
• In-country review capability for your target markets, validating cultural and regulatory fit beyond linguistic accuracy
• Data security practices appropriate for clinical and patient data — ISO 27001 certification is a strong additional signal where clinical trial data is involved
• Willingness to provide signed certificates of translation accuracy where required for submission

How Ekitai Solutions Supports Regulated Medical Translation

Ekitai Solutions provides medical and life sciences translation built around the ISO compliance framework and regional regulatory requirements covered in this guide.

Conclusion: Compliance Is the Product, Not a Feature of It

Medical translation sits at the intersection of two demanding requirements: a quality management framework defined by ISO 17100, ISO 13485, and ISO 9001, and a patchwork of regional regulatory mandates that differ meaningfully across the US, EU, China, Japan, and every other market a manufacturer enters.

Treating these requirements as a checklist to satisfy after the fact is the most common — and most costly — mistake manufacturers make. The data is consistent: translation-related issues are a leading cause of regulatory delay, and the highest-risk device categories are the most exposed. Building ISO-compliant, regionally informed translation into your regulatory strategy from the start is not an added cost. It is the difference between a smooth market entry and a submission stuck in query cycles.

Frequently Asked Questions

Q: Is ISO 13485 certification mandatory for medical translation providers?

A: No regulation explicitly mandates that a translation provider itself hold ISO 13485 certification. However, because ISO 13485 covers organisations providing services related to medical devices, and because notified bodies and regulatory reviewers increasingly expect evidence of a controlled, audit-ready translation process, working with an ISO 13485-certified provider is considered close to a practical necessity for manufacturers seeking smooth regulatory review, particularly for higher-risk device classes.

Q: What is the difference between ISO 17100 and ISO 13485 for translation?

A: ISO 17100 is a general translation quality standard applicable across all industries, defining requirements like qualified translators, independent revision, and traceable workflows. ISO 13485 is medical-device-specific and applies the broader quality management system principles of the medical device industry to the translation process itself, including document control, risk management, and audit-readiness aligned with medical sector regulatory expectations. Most serious medical translation providers hold both.

Q: Does the EU require translation into all 24 languages for every medical device?

A: Not necessarily — but it can. Each EU Member State independently determines its own language requirement under MDR Article 41, and full pan-European distribution can require translation into as many as 24 official languages depending on which countries a manufacturer targets. The European Commission’s official MDR and IVDR Language Requirements Tables specify the exact requirement per Member State, and some flexibility exists for professional-use devices in certain markets.

Q: Can FDA-regulated medical device labelling include languages other than English?

A: Yes, but with conditions. Under 21 CFR 801.15, all required labelling must appear in English. Foreign-language information can be added, but if any foreign-language text appears, the full set of required labelling information must also appear in that same foreign language — partial foreign-language labelling is not permitted. The narrow exception is for products distributed solely in Puerto Rico or US territories with non-English-speaking majorities.

Q: Does China’s NMPA accept Traditional Chinese translations?

A: No. The NMPA requires Simplified Chinese for all labelling, Instructions for Use, technical files, and registration documentation submitted for the Chinese mainland market. Traditional Chinese is a separate script used in markets such as Hong Kong and Taiwan and is not an accepted substitute for NMPA submissions.

Q: What is back-translation, and is it required for medical translation?

A: Back-translation is the process of translating a target-language document back into the original source language by an independent translator, then comparing the result against the original to identify any meaning drift introduced during the initial translation. It is not universally mandated by regulation, but it is widely considered best practice — and is required by many clinical trial sponsors and ethics committees — for high-risk content such as informed consent forms, patient-reported outcome instruments, and clinical trial protocols.

Q: How long does ISO-compliant medical translation typically take?

A: Timelines vary significantly based on document volume, language pair, and the number of QA stages required. A straightforward IFU translation with standard ISO 17100 workflow (translation plus independent review) might take one to two weeks per language. Projects requiring back-translation, in-country regulatory review, and certification for multiple target markets can take four to eight weeks or longer. Building translation timelines into your overall regulatory submission schedule — rather than treating translation as a final step — is the most effective way to avoid delays.

Q: Do software interfaces and apps on medical devices need to be translated under EU MDR?

A: This depends on the Member State and is one of the more ambiguous areas of EU MDR language compliance. The European Commission’s official language requirements tables include a column addressing software interface translation, but as of the most recent revisions, this field is populated for roughly half of the covered countries. Manufacturers with software-driven devices or companion apps should confirm directly with the relevant national authority or notified body for markets where the table does not provide a clear answer.