CE·8 min read·By Angel Translation Corp.·Updated Jul 2026

CE Certification Under MDR and IVDR: Language Compliance Checklist

EU Medical Device Regulation and IVDR requirements for translated technical files, IFU instructions, and Declaration of Conformity. Language requirements for EU27.

Key points
  • Language is set per member state
  • When the language set gets fixed decides how hard the rest will be
  • Revisions are the real test
Who this is forRegulatory and market access teams planning EU launches across multiple member states.

Language is set per member state

Under MDR 2017/745 and IVDR 2017/746, instructions for use and labelling must be provided in the language or languages accepted by each member state where the device is placed on the market — and each member state determines that for its own territory.

The practical consequence is that there is no single "EU version". Your language set is defined by your target markets, and it grows as those markets do. Confirm the current requirement per market with your notified body.

When the language set gets fixed decides how hard the rest will be

Teams frequently finalise the English source, then discover the required language count late and compress translation into the last weeks before launch. That is where quality and consistency problems concentrate — not because the translators are weak, but because the same terminology question is being decided independently, in a dozen languages, at the same time.

So if you want to know whether a manufacturer has its language work under control, you learn more from when the market list was fixed than from a translation sample. The later that list lands, the more every downstream revision costs — and those costs rarely appear in the translation budget.

Revisions are the real test

Devices change, and labelling changes with them. The common failure is not a mistranslation — it is updating some language versions and not others, leaving markets holding different revisions of the same document with no one able to say what differs.

None of this shows during the first certification. It surfaces on the second or third revision. The test of whether a language asset is genuinely maintainable is simple: when one source passage changes, can you say which languages and which paragraphs it affects? If not, every revision is being done from scratch.

Questions

It depends entirely on your market list, and requirements change. Build the list from your commercial plan and verify each market with your notified body rather than working from a general EU figure.
Requirements differ between the technical documentation and the user-facing IFU and labelling. Confirm scope with your notified body — over-translating is expensive and under-translating is a market access risk.
Angel Translation covers 230+ languages, which comfortably includes EU requirements. Tell us the market list and we will scope the set.

Related reading

FDAFDA 510(k) Submission Language Requirements: What Reviewers Actually CheckIFUIFU Instructions for Use: Why Mistranslation Creates Product Liability ExposureOperationsSimultaneous Multi-Language Release: How to Ship 20 Languages at Once

Have a project that touches this?

Tell us what you are shipping and where. We will tell you which service level it needs — including when it does not need our most expensive one.