Medical devices: what are the language requirements for regulatory documentation?

If you are bringing a medical device into the European market, your regulatory documentation has to exist in the language of every country where the device will be sold. That is the simple version. The full version is more complicated, has changed substantially since 2021, and is often the difference between a smooth CE marking process and a delayed launch.

This article covers what the current EU framework requires linguistically, which languages apply to which markets, where the country-specific traps are, and how to plan a multilingual rollout without disturbing the rest of the regulatory work.

The current regulatory framework

Two regulations now govern medical devices in the EU. The Medical Device Regulation (MDR, Regulation 2017/745) became fully applicable in May 2021. The In Vitro Diagnostic Regulation (IVDR, Regulation 2017/746) became applicable in May 2022 and is in a phased transition that runs through 2027 for the highest-risk classes.

These two regulations replaced the older directives (90/385/EEC, 93/42/EEC, 98/79/EEC). If you still see references to those directive numbers in current vendor materials, you are looking at outdated guidance.

Both regulations are stricter than what they replaced. They expand the scope of what counts as a medical device, raise the bar for clinical evidence, introduce stronger post-market surveillance obligations, and tighten linguistic requirements at every stage of the product lifecycle.

Alongside the regulations sits EUDAMED, the European database on medical devices. Several modules are already operational, others are coming into force in stages, and the database centralizes information previously held by national competent authorities. EUDAMED entries follow specific language conventions that we return to later in this article.

What MDR and IVDR require linguistically

The core obligation sits in MDR Article 10. Labels, instructions for use, and the information supplied with the device (detailed in Annex I, Chapter III) must appear in a language accepted by the member state where the device is made available. This applies to the device itself, its packaging, and the manufacturer's website where one exists.

The same article requires the information to be indelible, easily legible, and clearly comprehensible to the intended user. The phrase "intended user" matters. For devices used by patients or lay users, the language must be the country's official language for public-facing communication. For devices used only by healthcare professionals, some member states accept English, but the default is still the national language.

A few specific document types carry their own obligations:

• EU Declaration of Conformity (Article 19, Annex IV) — in versions for each member state, in the languages those states require.
• Implant card and patient information for implantable devices (Article 18) — in the language determined by each member state, written in plain language for lay users.
• Summary of Safety and Clinical Performance (SSCP) for class III and implantable devices (Article 32) — uploaded to EUDAMED in English and translated into all required languages of the markets where the device is sold.

IVDR mirrors most of these obligations for in vitro diagnostic devices. The IVDR equivalent of the SSCP is the Summary of Safety and Performance (SSP), required for class C and class D devices, with the same multilingual upload obligation.

Post-market obligations carry their own language requirements. Field Safety Notices (FSN), issued when a Field Safety Corrective Action is taken, must reach affected users in the language of each country involved. Periodic Safety Update Reports (PSUR) are typically submitted to the competent authority in English, though some authorities require translated summaries. Vigilance reporting follows the language conventions of each national authority.

Which languages for which markets

The European Union has 24 official languages. The European Economic Area adds three more (Icelandic, Norwegian, and the German variant used in Liechtenstein). Switzerland and the United Kingdom sit outside the EU but operate adjacent regulatory systems with their own language obligations.

For medical device documentation, the rule is straightforward in principle. Each member state specifies which language or languages must appear on the labels, the IFU, and the patient-facing materials sold within its borders. In practice, a single device sold across the EEA can require up to 24 EU language versions, plus local versions for non-EU markets.

The table below summarizes the baseline requirement for each EEA market and flags where English is sometimes accepted for professional-use-only devices. The detail varies by device class, by intended user, and by enforcement practice. Use this table as a planning starting point, not as a substitute for confirmation with the competent authority of each market.

Market	Required language(s)	Notes
Austria	German
Belgium	Dutch, French, German	Regional minimum is the local language; all three needed for nationwide distribution
Bulgaria	Bulgarian
Croatia	Croatian
Cyprus	Greek	English sometimes accepted for professional-use devices
Czech Republic	Czech
Denmark	Danish	English sometimes accepted for professional-use devices
Estonia	Estonian	English sometimes accepted for professional-use devices
Finland	Finnish, Swedish	Both required for nationwide distribution
France	French	Strict enforcement under the Toubon Law
Germany	German
Greece	Greek
Hungary	Hungarian
Ireland	English	Irish is also official but rarely required in practice
Italy	Italian
Latvia	Latvian
Lithuania	Lithuanian
Luxembourg	French, German	Luxembourgish is also official; French and German are typically accepted
Malta	Maltese, English
Netherlands	Dutch	English often accepted for professional-use devices
Poland	Polish
Portugal	Portuguese
Romania	Romanian
Slovakia	Slovak
Slovenia	Slovenian
Spain	Spanish	Regional languages may apply for regional distribution
Sweden	Swedish	English sometimes accepted for professional-use devices
Iceland (EEA)	Icelandic
Liechtenstein (EEA)	German
Norway (EEA)	Norwegian
Switzerland	German, French, Italian	Separate Swiss MedDO regulation
United Kingdom	English	UKCA marking, separate process from CE

Two patterns are worth highlighting before moving on.

First, multilingual countries require multiple language versions even within a single market. Belgium, Finland, Luxembourg, and Malta each have more than one official language, and all of them may be required depending on where and how the device is sold.

Second, the "English accepted for professional use" exception is a moving target. It depends on the device class, the specific document type (label, IFU, patient information), the device's intended user, and the discretion of the national authority. We have seen the same exception treated differently by the same authority in different audits. If your launch plan relies on this exception, verify it in writing with the relevant authority for the specific device.

Country-specific complications worth knowing

A few markets carry rules that catch first-time launchers off guard. These are the ones we see cause the most rework.

France: the Toubon Law

France enforces native-language requirements more strictly than any other EU country, under the Toubon Law (Law 94-665, 1994). Any document directed at a consumer or end user must be in French. This applies to medical device labels, IFU, packaging, advertising, and patient information. There is no exception for professional-use devices when the document reaches a patient or an untrained user. Authorities have blocked products from the French market for non-compliant translations.

Belgium: three languages, three regions

Belgium is officially trilingual, and the language requirement depends on where the device is sold. Flanders requires Dutch. Wallonia requires French. The German-speaking community in the east requires German. Brussels-Capital is officially bilingual French and Dutch. For a device distributed nationally, all three official languages may be needed. Assuming that French alone covers Belgium is a common and expensive mistake.

Spain: national language plus regional questions

Castilian Spanish is the language for national distribution. The autonomous regions of Catalonia, the Basque Country, Galicia, Valencia, and the Balearic Islands have co-official languages that may be required for materials distributed within those regions only. For a national launch, Spanish is the baseline. For regional procurement or regional distribution channels, verify whether the regional language is also required.

Switzerland: not EU, but adjacent

Switzerland sits outside the EU. The Mutual Recognition Agreement that previously aligned Swiss and EU medical device regulation expired in May 2021. Swiss regulation now operates under the national MedDO (Medical Devices Ordinance), which mirrors much of MDR but adds national requirements. MedDO requires labels and IFU in German, French, and Italian for the three main language regions. Romansh is officially a fourth language but is not typically required for device documentation.

The Nordics: flexible, but not unlimited

Sweden, Denmark, Finland, Norway, and Iceland are sometimes grouped as having a flexible attitude toward English in professional-use device documentation. The flexibility is real but limited. For patient-facing materials, the national language is always required. For professional-use devices, English may be accepted, but the decision sits with the national authority. Finland additionally requires both Finnish and Swedish for nationwide distribution because both are official.

The United Kingdom: a separate system since Brexit

The UK no longer participates in CE marking for new approvals; transitional arrangements have been extended and revised multiple times. The UKCA marking is the UK's domestic alternative, with English as the regulatory language. Northern Ireland operates under arrangements that align it more closely with EU rules under the Windsor Framework.

Planning the multilingual rollout

The biggest mistake we see in multilingual CE marking projects is not a translation mistake. It is a timing mistake. Translation is treated as the last step before launch, ordered when the technical file is "final," and the team discovers too late that the file is never final. Late changes come back from notified body review, from clinical evidence updates, from labeling amendments. Each change ripples through every language version already completed.

A few principles to plan around.

Start translation when the source is stable, not when it is final

Wait for the source content to be approved by your regulatory and quality teams before sending to translation. Do not wait for the absolute last sign-off. Late minor changes can be handled efficiently if translated versions already exist and are managed in a translation memory. Rebuilding 24 language versions from scratch for a final-stage edit is far more expensive than updating existing ones.

Use a translation memory and a termbase from day one

A translation memory captures every sentence translated for your product. When the IFU is updated, only the changed sentences need re-translation; unchanged content is reused. A termbase enforces consistent terminology across linguists, document types, and product updates. For a multilingual device with regular updates, the savings over the product lifecycle are substantial. We have seen cost reductions of 40 to 60 percent on follow-on versions for clients who established TM and termbase from the first project.

Plan for source change management

When the source document changes after translation has started, the change management process matters. Each change should be marked, tracked, and applied consistently across all language versions. A single change applied inconsistently across 12 languages is a regulatory finding waiting to happen.

Budget for the full lifecycle, not just the first launch

The first translation is usually the largest single cost, but it is not the total cost. Updates, post-market communications (FSN, FSCA), labeling amendments, and product line extensions all generate translation work. A realistic multilingual budget plans for the first three years of the device on market, not the first launch.

Use an ISO 17100 certified provider

ISO 17100 is the international standard for translation services. It specifies requirements for translator and reviser qualifications, the workflow (translation, revision by a second qualified linguist, final QA), and the quality systems behind them. For regulated content, the standard is not optional in practice. Notified bodies and competent authorities increasingly expect translation work to be performed under a recognized quality framework.

AI is a productivity tool, not a delivery channel for regulated content

Machine translation has a place inside a regulated workflow, particularly for repetitive content with stable terminology. It does not replace the human accountability that MDR and IVDR ultimately require. Fluent does not mean accurate, and AI providers do not sign the quality file. Use AI to accelerate; keep qualified linguists and ISO 17100 workflow in place to deliver. (We cover this in more depth in a dedicated article on AI in regulated medical translation.)

Bringing it together

Multilingual regulatory documentation for medical devices is not a translation problem layered on top of a regulatory problem. The two are the same problem, governed by the same regulations, audited by the same authorities, and delivered to the same patients. A document that is regulatorily correct in one language and inconsistent in another is not compliant. A device that ships with a fluent but incorrect translation is not safe.

The work is harder than it looks because the inputs change, the regulations evolve, the languages multiply, and the timelines compress. The work is also tractable when it is planned early, supported by translation memory and terminology systems, and delivered under a quality framework that takes accountability seriously.

If you are planning a CE marking project across multiple EU and EEA markets, or you are reviewing how your current translation workflow is positioned for the regulatory expectations of 2026 and beyond, we would be glad to help. We translate medical device documentation under ISO 17100, in over 30 European and global languages, with linguists who specialize in life sciences and project managers who have delivered multilingual CE marking projects from start to launch.