Does EUDAMED Require Consistent Multilingual Device Data From May 2026
- 2 hours ago
- 5 min read
Yes. From 28 May 2026, EUDAMED use is mandatory, and the device records you upload have to match across every national language version you sell into. Commission Decision (EU) 2025/2371, published on 27 November 2025, confirmed the four core modules are functional and started the six-month countdown to that date.
If your UDI-DI data, labels, and instructions for use say one thing in the German registration and another on the Spanish leaflet, that gap is now visible to every competent authority at once. Here is what changed, the deadlines that follow, and why consistency across languages stopped being optional.
What became mandatory on 28 May 2026
EUDAMED is the EU database that ties together device registration, identification, certificates, and market surveillance. Four of its six modules moved from voluntary to mandatory on 28 May 2026. The two remaining modules, Vigilance and Clinical Investigations, stay voluntary until they are separately declared functional.
The four modules now in force are these:
Actor Registration, where every manufacturer, authorised representative, and importer receives a single registration number.
UDI and Device Registration, which holds the unique device identifier and the descriptive data attached to each device.
Notified Bodies and Certificates, listing the certificates issued under MDR and IVDR.
Market Surveillance, where authorities record and share their findings across member states.
Actor registration is the gate. Without a registered actor number you cannot file device or certificate data at all, so it is the first thing to clear.
The deadlines that follow
The mandatory date is a start line, not a finish. Two follow-on deadlines matter for anyone with devices already on the market:
Legacy devices, meaning devices placed on the market before 28 May 2026 and still supplied afterwards, must be registered in the UDI and Device module by 28 November 2026.
Certificates issued by notified bodies must be uploaded by 28 May 2027.
Miss the November window and a device that is still selling has no valid EUDAMED record behind it. That is the kind of gap a market-surveillance authority notices quickly.
Where the language requirement bites
MDR Article 10(11) requires the label and the instructions for use to reach the user in an official language set by each member state where the device is made available. Annex I, Section 23 defines what that covers: the device label, the packaging label, and the full instructions for use.
A common myth says Article 10(11) forces all 24 EU languages at once. It does not. The obligation is market-specific, so a manufacturer selling in six countries produces six language versions, not twenty-four. The catch is that each of those versions feeds data that has to reconcile with what sits in EUDAMED.
Your UDI-DI record carries structured data: the basic UDI-DI, the device name, and its attributes. Your national labels and IFUs carry the human-readable version of the same facts. When a linguist adjusts an intended-purpose sentence in the Italian IFU but the EUDAMED device name never moves, you have created a mismatch that a market-surveillance check can find.
How a mismatch surfaces in audit
Registration and surveillance data now sit in one place that authorities in 27 member states read from. A discrepancy between the German label, the Portuguese IFU, and the central EUDAMED entry does not stay local anymore.
At audit or during a surveillance query, three things get compared: the registered device data, the notified-body certificate scope, and the language versions on the market. When they diverge, the finding lands on you, and the fix, a correction and re-registration, costs more than getting the terminology aligned once.
What keeps language versions consistent
Consistency across languages is a terminology problem before it is a translation problem. The controls that hold it together are these:
A single term base that fixes the approved rendering of each device name, intended purpose, and warning in every target language.
Version-locked source files, so a change to the English master triggers a controlled update everywhere, not an isolated per-country edit.
Translation memory that reuses the exact approved wording from the last registration cycle.
One owner for the terminology, rather than separate distributors correcting their own market copy in isolation.
Isolated fixes are how divergence starts. A country manager who tweaks a warning line locally, without touching the central term base, breaks the reconciliation that EUDAMED now checks.
How AD VERBUM keeps device data aligned
We built our medical device workflow around exactly this reconciliation problem. AD VERBUM runs ISO 13485 certified quality management for the device scope, ISO 17100 certified translation with a second independent linguist on every project, and ISO 27001 information security on EU-hosted infrastructure. The same discipline runs through our work on MDR and IVDR device documentation.
The term base and translation memory travel with your product across registration cycles, the way we handle term-base governance for EMA regulatory submissions. So the German label, the Finnish IFU, and the EUDAMED record all stay derived from the same approved source. For manufacturers registering across several markets before the November 2026 deadline, that shared terminology layer is the difference between one clean submission and a round of corrections. The same certified process backs our work on ISO 13485 medical device documentation.
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) labelling obligations and EUDAMED data consistency 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
When does EUDAMED become mandatory?
The four core modules became mandatory on 28 May 2026, following Commission Decision (EU) 2025/2371 of 26 November 2025, which confirmed their functionality and started a six-month transition. From that date the related EUDAMED obligations under MDR and IVDR apply in full.
Which EUDAMED modules are mandatory from May 2026?
Four: Actor Registration, UDI and Device Registration, Notified Bodies and Certificates, and Market Surveillance. The remaining two, Vigilance and Clinical Investigations, stay voluntary until they are separately declared functional.
What is the deadline to register legacy devices in EUDAMED?
Devices placed on the market before 28 May 2026 and still supplied afterwards must be registered in the UDI and Device module by 28 November 2026. Certificates issued by notified bodies must be uploaded by 28 May 2027.
Does MDR Article 10(11) require all 24 EU languages?
No. Article 10(11) is market-specific: the label and instructions for use must be in the official language set by each member state where the device is made available. Annex I, Section 23 defines the covered material, so you translate only for the markets you supply.
Why does multilingual consistency matter for EUDAMED?
Because UDI-DI and label data have to reconcile with the national IFUs on the market. A mismatch between the central EUDAMED entry and a translated label surfaces in market surveillance or audit under MDR, and the correction and re-registration cost more than aligning terminology once.
How does AD VERBUM keep device translations consistent?
We run ISO 13485 certified quality management, ISO 17100 certified translation with independent revision, and ISO 27001 security on EU-hosted infrastructure. A single term base and translation memory travel with your product across registration cycles, so every language version stays derived from the same approved source.
