You run regulatory affairs for a device manufacturer. The CE mark is in hand, you have been shipping into three member states, and the board has just approved expansion into eleven more. Somebody in the meeting asks the obvious question: which languages do we need, and for what?
So you search it. And the top results answer confidently, with a citation: Article 41. Several of them say it. It looks settled.
It is wrong. Article 41 of the Medical Device Regulation has nothing to do with the leaflet in your box. If that citation makes it into your scope of work, your quality plan, or the specification you hand a translation vendor, you will be scoping the wrong deliverable against the wrong obligation — and you may not find out until a competent authority asks you to justify it.
Why So Many Guides Land on Article 41
The mistake is easy to reconstruct, and understanding it is how you avoid repeating it. Open the regulation, search for "language," and Article 41 comes back with the heading "Language requirements." It is the only article in the regulation carrying that title. If you stop reading at the heading, you are done.
Read the text and it dissolves immediately. Article 41 says, in full, that all documents required pursuant to Articles 38 and 39 shall be drawn up in a language or languages determined by the member state concerned; that member states should consider accepting a commonly understood language in the medical field; and that the Commission will provide translations as needed for the joint assessment team appointed under Article 39(3).
Articles 38 and 39 are "Application by conformity assessment bodies for designation" and "Assessment of the application." Article 41 governs the paperwork a would-be notified body files with a designating authority, and the language in which an assessment team reads it. No patient, clinician, or hospital biomed tech will ever see a document governed by Article 41.
A miscitation is not a cosmetic error. Procurement writes specifications from these articles. If your RFP invokes Article 41, every bid you receive is scoped to a provision about notified-body designation files — and none of them are priced against the Annex I content that actually has to be translated.
What Article 10(11) Actually Requires
Article 10 sets out the general obligations of manufacturers, and paragraph 11 is the operative language provision. Three consequences follow from its wording, and each one catches somebody out.
The obligation is the manufacturer's. Article 10 places it there. Handing a distributor a PDF and asking them to sort out the local version does not move the duty, and it usually means an untracked, unversioned translation is circulating in a market you remain responsible for.
The trigger is where the device reaches the user or patient. Not where you are headquartered, not where your notified body sits, not where the CE mark was issued. Each market of supply generates its own language requirement, which is why the answer scales with your distribution footprint rather than with your company.
The content is defined by Annex I, Section 23. That section specifies the particulars for the label and for the instructions for use. It is your scope of work — not "the manual," not the marketing collateral. Anything Section 23 lists is in scope; everything else is a separate commercial decision.
Which Languages You Can Actually Be Required to Provide
Here is the constraint most vendor tables quietly skip. Article 10(11) does not say "the official language of the member state." It says an official Union language determined by the member state. Those are not the same set.
| The question | What the regulation establishes |
|---|---|
| Who chooses the language? | Each member state, for its own territory — Article 10(11) |
| Chosen from what set? | The EU's 24 official languages, under Regulation No 1/1958 as amended |
| Can a state demand a language outside that set? | Not on the strength of Article 10(11)'s "official Union language" wording |
| Does one language ever cover the EU? | No — the obligation attaches per market of supply |
| Must the label and the IFU always match? | No — several states treat professional-only IFUs differently from lay-user ones |
Luxembourg is the clean illustration. Its official national languages are French, German, and Luxembourgish — and Luxembourgish is not one of the EU's 24 official languages. It nonetheless appears in published MDR language tables, because the author reached for a list of national languages instead of the set Article 10(11) actually points to. Contrast Belgium, where Dutch, French, and German are all official Union languages and therefore all genuinely available for a member state to require, or Finland, where Finnish and Swedish both are.
The second variable is who uses the device. A number of member states distinguish devices used exclusively by healthcare professionals from devices that reach lay users, and some accept English for professional-only instructions. That relief is real, it is worth money across eleven markets, and it is set nationally rather than by the regulation itself.
Which leads to the only honest instruction anyone can give you about the per-country list: confirm it against each competent authority for your specific device class and intended user. National implementing rules change, and they change without the MDR changing. Treat any published country table as a starting hypothesis — including one on our site — and not as evidence for your technical file.
Label, IFU, and Implant Card Are Three Different Obligations
Teams routinely apply one translation rule to all three and get two of them wrong.
The label carries the particulars in Annex I, Section 23.2, and the regulation requires them to be indelible, easily legible, and clearly comprehensible to the intended user or patient. Space is the binding constraint, which is exactly why symbols matter here and nowhere else.
The instructions for use are narrative: intended purpose, contraindications, warnings, procedure, handling, disposal. There is no compression trick available. This is the bulk of the word count, and it is where a translation error stops being a language problem and becomes a patient-safety one.
The implant card is its own regime under Article 18. Manufacturers of implantable devices supply the card and accompanying patient information, in the language or languages determined by the member state concerned, and — critically — written so as to be readily understood by a lay person. The Commission's MDCG 2019-8 guidance covers the practicalities. Note what that lay-person standard demands: a translation can be technically faultless and still fail it, because faithfully rendering clinical register into another language preserves the register. Meeting Article 18 means the target text has to be readable by the person carrying the card in their wallet.
Expanding into new EU markets? Our life-sciences team builds the language matrix market by market — label, IFU, and implant card scoped separately — before any translation starts.
Where Symbols Remove the Translation Problem — and Where They Don't
Annex I, Chapter III, Section 23.1(h) provides that where appropriate the information supplied by the manufacturer shall take the form of internationally recognised symbols, and that any symbol or identification colour used shall conform to the harmonised standards. EN ISO 15223-1:2021 is the harmonised standard supplying those symbols for medical devices.
Because that standard is harmonised to the MDR, symbols it defines generally do not need to be explained in the information supplied with the device — subject to the qualification that omitting the explanation must not introduce higher risk from the device. For a crowded label carrying a manufacturer, a batch code, a use-by date, a sterilisation method, and a "consult instructions for use" pointer, that is a real reduction in translated text across every market.
It buys you nothing on the IFU. There is no symbol for a contraindication, a warning about concomitant use, or a nine-step reprocessing procedure. Manufacturers who discover the symbol relief sometimes assume it scales. It does not scale past the label.
How These Projects Actually Fail
In our experience the failures are boringly consistent, and none of them are about a linguist picking the wrong word.
- Machine output with a friendly reviewer. The IFU goes through an engine, then to a distributor's sales contact who is a native speaker but is neither a translator nor a clinician. They will fix what reads oddly. They will not catch an inverted contraindication, because they do not know what it was supposed to say.
- Lowest-price procurement, one language at a time. Eleven markets awarded to whoever was cheapest in each means eleven independent glossaries. The same warning ends up phrased eleven different ways, and you cannot demonstrate consistency across your technical file because there is none.
- Nobody owns the layout. Translation comes back and German and Finnish have expanded, while your IFU is a fixed-format folded insert carrying a legibility requirement. Type gets shrunk to fit — which quietly breaks the requirement you were trying to satisfy. Multilingual desktop publishing is the step that decides whether a correct translation is actually usable.
- Version drift. The IFU is revised. Six of eleven languages get updated. The other five stay in market, and nothing in the process flags it.
The regulation's standard is that information be "clearly comprehensible to the intended user or patient." That is an outcome standard, not a word-count standard — and outcome standards are the ones you have to be able to evidence years later.
A Three-Step Plan
- Build the language matrix before you buy any translation. One row per market you actually supply. Columns: label language(s), IFU language(s), whether professional-only relief applies to your device and user, and implant-card language if Article 18 is in scope. Confirm each row against the competent authority rather than a vendor table, and keep the confirmation.
- Lock terminology first, then translate. One approved glossary and one translation memory — and make sure your contract says you own them, not the vendor. This is the single change that makes eleven markets consistent, makes the next revision cheaper, and turns consistency into something you can show rather than assert.
- Treat layout and revision control as deliverables, not afterthoughts. Specify print-ready output against your template, and define one path that pushes a revision through every language at once. If updating an IFU requires eleven separate conversations, drift is not a risk — it is scheduled.
Why Work With Taika
Language Access Hub, powered by Taika Translations, is a veteran-owned (VOSB), SAM-registered, GSA- and NASPO ValuePoint-contracted language services provider working across life sciences and medical device documentation. Our work is delivered by ATA-certified linguists with subject-matter review, under terminology and translation memory you own, and we handle the multilingual desktop publishing so the translated IFU still fits its format and stays legible. One vendor across translation, layout, and accessibility — and one point of accountability when a revision has to reach every market at once.
We also read the regulation before we quote it. Our guarantees attach to the quality of the translation and layout work we deliver, the part we control, and we will tell you plainly when guidance you have been handed cites the wrong article.