Which MDR Documents Require Translation Into All EU Languages
No MDR document has to appear in all 24 EU languages by default. Regulation (EU) 2017/745 ties the language of your labelling and instructions for use to the official language of each member state where the device reaches the user, not to the Union as a whole. Sell an implantable device into every EU country plus Norway, Iceland and Liechtenstein and you do land at 24 languages plus Icelandic and Norwegian. Sell into Germany and France only, and two languages clear the obligation.
The rule that sets this is Article 10(11), and it points to Section 23 of Annex I for what the label and instructions for use must contain. Each member state decides which of its official languages it wants. Belgium can ask for Dutch, French and German. Finland expects Finnish and Swedish. So “all EU languages” is the wrong question, and “which markets are you entering” is the right one.
Five MDR document types carry a hard language obligation. Each maps to the market where the device is made available, and a gap in any one of them can stop the device at the border or at the notified body.
1. Instructions for use
The instructions for use are the manual that tells the user how to run the device safely, from intended purpose to warnings and residual risks. Under Article 10(11) and Section 23 of Annex I, they have to reach the user in the official language of the member state where the device is made available. For low-risk Class I and Class IIa devices that can be used safely without a manual, Annex I lets you drop the printed instructions, but then the label carries the whole burden. Skip a required language and the device is non-compliant in that one market, even where the CE certificate is valid everywhere else.
2. Label
The label is the information on the device or its packaging that identifies it and states the essential safety particulars set out in Section 23.2 of Annex I. Article 10(11) applies the same rule: the particulars must be indelible, legible and clearly comprehensible to the intended user in the language the member state requires. Harmonised symbols from EN ISO 15223-1 carry part of the meaning, which trims the translated text but never removes it. A label a patient in Warsaw cannot read in Polish is a market-access problem, not a formatting one.
3. EU declaration of conformity
The EU declaration of conformity is the manufacturer’s signed statement that the device meets the MDR, with its content fixed by Annex IV. Article 19(1) requires it to be translated into the official Union language or languages that each member state of availability demands. This one catches people out, because it reads like an internal file. It isn’t. A distributor or a competent authority can ask for it in the national language, and if you cannot produce that version the device’s route to market is exposed.
4. Implant card and patient information
For implantable devices, Article 18 requires an implant card plus information the patient keeps and can understand. That patient-facing material has to be in the official language the member state decides, because the reader is the patient, not a clinician. Certain implants such as sutures, staples and dental fillings are exempt from the card itself, yet the underlying duty to inform the patient still tracks the market. Get the language wrong and you have handed a cardiac or orthopaedic patient safety information they cannot act on.
5. Field safety notices
A field safety notice is the letter you send when a device already on the market needs a correction, whether a recall, a software fix or an updated warning. Article 89(8) requires it in the official Union language of the member state where the field safety corrective action is taken, and it expects the wording to stay consistent across every affected country. This is the hardest of the five, because it is written under time pressure during a live safety event. A notice that reaches French hospitals in English, or says something subtly different in the Dutch version, is a documented failure at the exact moment a regulator is watching.
Where EUDAMED tightens label-data consistency
From 28 May 2026, EUDAMED’s four core modules become mandatory under Commission Decision (EU) 2025/2371, and the UDI and device-registration data you enter has to line up with what is printed on the label and in the instructions for use. New devices register before they go on the market; devices already sold register by 28 November 2026. The catch is keeping device data consistent across language versions: if your Basic UDI-DI record says one thing and the national label says another, the mismatch is visible to every competent authority at once. Work that used to sit in separate country files now reconciles against a single structured record.
How AD VERBUM keeps every language version consistent
This is where the document count stops being the problem and version control starts. AD VERBUM runs MDR document sets through one terminology-controlled pipeline, so the Polish instructions, the German label and the EUDAMED record use the same approved term for the same part. Our ISO 13485 quality management system matches the manufacturer’s own QMS obligations, our ISO 17100 process puts a second qualified linguist on every translation, and our ISO 27001, EU-hosted infrastructure keeps technical files inside the EU. If you are weighing translation companies that handle MDR and IVDR device documentation, ask how translation memory and term bases travel with the product across markets and variation cycles, because that is what stops the twelfth language from drifting away from the first. When a safety notice has to ship in nine languages in a day, that groundwork is the difference between a coordinated release and nine separate scrambles.
Our medical device translation services
Our translation services for regulated sectors run on ISO 27001 and ISO 42001 certified, EU-hosted infrastructure, with no reliance on public cloud tooling for core processing. Every project runs through our AI+HUMAN hybrid workflow: we ingest client Translation Memories and Term Bases first, our proprietary LLM-based LangOps System generates output constrained by client terminology on client-tuned open-weight models, and our certified subject-matter experts review for technical accuracy and regulatory compliance. Our QA is aligned to ISO 17100 and ISO 18587, with sector-specific requirements such as MDR Article 10(11) language obligations and ISO 13485 medical device quality management applied where relevant. We serve Life Sciences, Legal, Finance, Defense, and Manufacturing clients across 150+ languages with 3,500+ subject-matter linguists. For teams managing audit-sensitive content, contact us to discuss your security and compliance requirements directly.
FAQ
Does MDR require all medical device documents in all 24 EU languages?
No. Article 10(11) of Regulation (EU) 2017/745 ties the language of the label and instructions for use to each member state where the device is made available. You only reach 24 EU languages plus Icelandic and Norwegian if you sell across the whole EU and EEA. A two-country launch needs two languages.
Which MDR article sets the language of the label and IFU?
Article 10(11), which points to Section 23 of Annex I for the required content. It says the information must be in an official Union language determined by the member state where the device reaches the user or patient, and the label particulars must be legible and clearly comprehensible.
Does the EU declaration of conformity need translation?
Yes. Article 19(1) requires the declaration to be translated into the official Union language or languages that each member state of availability demands, with content fixed by Annex IV. Treating it as an English-only internal record is a common and avoidable gap.
What language must an implant card be in?
Article 18 requires the implant card and the patient information to be in the official language the member state decides, because the reader is the patient. Some implants such as sutures and dental fillings are exempt from the card itself, but the patient-information duty still follows the market.
How does EUDAMED affect multilingual device data?
From 28 May 2026, under Commission Decision (EU) 2025/2371, the four core EUDAMED modules are mandatory, and the registered UDI and device data must stay consistent with the national label and instructions for use. A mismatch between the structured record and the printed label is visible to every competent authority.
Can machine translation be used for MDR documents?
Yes, if it is controlled. ISO 18587 covers full post-editing of machine-translation output, and for safety-critical text such as warnings and intended purpose a qualified reviewer under ISO 17100 has to confirm accuracy. Raw, unreviewed output in an instruction sheet or label is what a notified body flags.
