EU MDR and IVDR require that a device's instructions for use (IFU) and labels be provided in the official language(s) of each member state where the device is marketed, and many states allow English only for professional-use devices. For manufacturers selling across the EU, that means producing and maintaining the same technical document in up to 24 languages while keeping every table, symbol, warning, and layout identical to the approved source. Bluente translates IFUs, labels, and technical files across 120+ languages while preserving the exact formatting, typically in under two minutes per document.
Bluente is an AI-powered document translation platform used by 30,000+ professionals, including regulatory affairs and quality teams, to translate files while keeping the original structure intact. This guide explains the EU language rules as they stand in 2026 and how to translate medical device documentation without breaking format or compliance.
What Do EU MDR and IVDR Require for Translation?
Under Article 10(11) of the MDR and Article 10(10) of the IVDR, every device must be accompanied by its information, including labels and instructions for use, in the official language(s) of the member state where it is made available. Each member state sets its own specific requirements, so the obligation is national, not uniform.
There is a meaningful split between professional and lay users. Several countries, including Germany, Austria, Belgium, the Netherlands, Poland, Ireland, Malta, Cyprus, and Estonia, accept English for devices intended for healthcare professionals. For devices intended for laypersons, almost all member states require the national language, with only Malta and Ireland accepting English. The European Commission maintains official MDR and IVDR language requirement tables (MDR table at Revision 3, August 2025) that map the rule per country, and manufacturers should treat those tables as the source of truth.
Why Is Medical Device Documentation Hard to Translate?
It is hard because the documents are dense, highly structured, and unforgiving of formatting drift. An IFU combines regulated warning text, standardized safety symbols, tables of specifications, diagrams with embedded labels, and precise layout that has often been reviewed and approved as a whole. A translation that reflows the page, breaks a table, or strips a symbol can create a compliance problem, not just a cosmetic one.
Three failure modes are common with general tools. Text embedded in diagrams and images stays in the source language because text-first translators skip it. Tables of technical specifications shift or collapse when only the text layer is touched. And language expansion overflows the tight callouts and label boxes that medical diagrams depend on. Each of these turns a clean approved document into one that needs manual rebuilding before it can ship to a notified body or a market.
How Does Format-Preserving Translation Help Compliance?
It helps because regulators expect the translated document to carry the same content and context as the approved original, and format is part of that context. When a warning, a symbol, or a specification table moves or breaks, the translated IFU no longer matches the version that was assessed, which is exactly the inconsistency reviewers flag.
Bluente uses a layout-aware engine that maps the full structure of the IFU before translating, then rebuilds it in place, so tables, symbols, headers, and diagram labels stay where the approved source put them. Embedded text in images is translated through OCR rather than skipped. The output is a document that reads and looks like the original in the new language, which is what makes it usable for submission and market release without a reformatting pass.
How Do You Keep Terminology Consistent Across 24 Languages?
You keep terminology consistent by locking it with a custom glossary so regulated terms, device names, and standardized phrasing translate the same way every time, in every language, across every document. Inconsistent terminology is one of the most common and avoidable issues in multi-market device documentation.
Bluente lets regulatory and quality teams build a custom glossary of approved terminology, including terms that must never be translated and terms that must always translate a specific way. The platform is trained on large volumes of technical and regulated content and applies the glossary across the whole document set, so "intended purpose," a device trade name, or a standardized warning reads identically whether the file is going to Germany, France, or Poland. For high-stakes deployments, teams can iterate the glossary over a few weeks to reach regulatory-grade contextual accuracy.
Is It Secure Enough for Regulated Medical Content?
Yes, provided the platform meets the security bar regulated manufacturers require, which general consumer tools typically do not. Device documentation, clinical context, and pre-market files are sensitive, and many quality systems prohibit routing them through tools that retain data or train models on uploads.
Bluente is SOC 2 Type II, GDPR, and ISO 27001 compliant, with end-to-end encryption, zero data retention, and automatic deletion of documents within 24 hours, and documents are never used to train any AI model. For teams that cannot share live files during evaluation, the platform supports trials on synthetic or public data so the security review can proceed without exposing regulated content.
What Does a Practical Workflow Look Like in 2026?
A practical workflow is: confirm the per-country language requirement from the Commission's MDR or IVDR table, lock your approved terminology in a glossary, translate the source IFU into each required language with format preserved, and review against the source. The reformatting step that used to dominate this process largely disappears when the file comes back already rebuilt.
For manufacturers entering multiple markets at once, this turns a multi-week, vendor-dependent process into a same-day one. Upload the approved IFU, select the target languages from 120+ options, apply the glossary, and receive market-ready files that match the original layout, each typically in under two minutes. That speed matters most during launches and regulatory windows, where the document pile grows faster than a bilingual team can clear it.
Frequently Asked Questions
Q: What languages do EU MDR and IVDR require for an IFU? MDR Article 10(11) and IVDR Article 10(10) require the IFU and labels in the official language(s) of each member state where the device is sold. Requirements are set nationally; many countries accept English for professional-use devices, while lay-user devices generally require the national language. The European Commission's MDR and IVDR language tables list the rule per country.
Q: Can I use English for a CE-marked device across the whole EU? Only in limited cases. English is accepted for professional-use devices in several states (such as Germany, the Netherlands, and Poland) and for lay users only in Malta and Ireland. Most member states require the national language for patient-facing devices, so a multi-language strategy is usually unavoidable.
Q: Does AI translation preserve medical device symbols and tables? A document-first platform does. Bluente's layout-aware engine keeps standardized symbols, specification tables, and diagram labels in place and translates text embedded in images via OCR, so the translated IFU matches the approved source rather than reflowing.
Q: How do I keep regulated terminology consistent across markets? Use a custom glossary that locks approved terms, device names, and standardized warnings. Bluente applies the glossary across the entire document set in every language, which prevents the terminology drift that reviewers commonly flag.
Q: Is AI document translation secure enough for regulated life sciences files? With the right platform, yes. Bluente is SOC 2, GDPR, and ISO 27001 compliant, with zero data retention, end-to-end encryption, and automatic deletion within 24 hours, and supports trials on synthetic data so security review can happen before any live file is shared.
Start translating documents for free. Bluente preserves your formatting across 120+ languages in under 2 minutes. Try BluTranslate free — no credit card required.