EUDAMED Goes Live: What Mandatory Use Means for Your MDR Strategy

After years of delays, pilot phases, and cautious optimism, EUDAMED has crossed a threshold that many regulatory teams had started to treat as theoretical. As of 28 May 2026, the first four modules of the European Database on Medical Devices are no longer optional. They're mandatory. This isn't just another regulatory milestone to tick off—it fundamentally changes how manufacturers interact with EU competent authorities, how transparency operates across the supply chain, and how prepared your organisation needs to be for what comes next. And it's happening at precisely the moment when the European Commission is actively revising the MDR and IVDR frameworks, with MedTech Europe pushing for changes that could reshape compliance burdens industry-wide.

What Just Became Mandatory—and Why It Matters

The four modules now in mandatory use are the Actor Registration module, the UDI/Device Registration module, the Notified Bodies and Certificates module, and the Clinical Investigations and Performance Studies module. On paper, these might sound like administrative housekeeping. In practice, they represent the operational backbone of post-market surveillance, supply chain traceability, and regulatory oversight across the EU's 27 member states.

For manufacturers, this means several concrete changes. First, all economic operators—manufacturers, authorised representatives, importers, and distributors—must now be registered in EUDAMED with validated data. Second, every device placed on the EU market must have its UDI and registration details submitted and maintained in real-time. Third, all certificates issued by Notified Bodies must be uploaded and kept current, creating a publicly accessible record of conformity assessment status. Fourth, clinical investigation and performance study data must be registered before studies commence, increasing transparency and regulatory scrutiny from the outset.

The shift from voluntary to mandatory isn't merely symbolic. It means competent authorities can—and will—enforce compliance. It means gaps in your EUDAMED submissions are no longer planning issues; they're non-conformities. And it means the database is now a live compliance tool, not a future-state aspiration. If your technical documentation references devices, UDIs, or certificates that don't match what's in EUDAMED, expect questions. If your authorised representative isn't properly registered, expect market access issues.

The Revision Backdrop: MedTech Europe's Qualified Support

Simultaneously, MedTech Europe has published its position on the European Commission's proposed MDR and IVDR revisions—a carefully calibrated response that supports the direction of reform while pressing for more substantial changes. The industry body's stance is revealing: there's cautious optimism that Brussels recognises the implementation burden, but also clear frustration that proposed revisions don't go far enough to address bottlenecks in Notified Body capacity, disproportionate requirements for legacy devices, and the cascading delays affecting device availability.

The timing is critical. EUDAMED going mandatory increases visibility into these exact pain points. When certificates, clinical investigations, and device registrations are publicly trackable, the scale of the Notified Body backlog becomes undeniable. When competent authorities can cross-reference UDI data with market surveillance findings in real-time, post-market obligations intensify. The revision discussions aren't happening in a vacuum—they're happening against the backdrop of a newly operational regulatory infrastructure that makes compliance gaps harder to hide and easier to enforce.

For regulatory teams, this creates a dual planning challenge. You're managing compliance with the MDR as it exists today—now with EUDAMED enforcement in full effect—while also preparing for potential regulatory changes that could alter timelines, technical documentation requirements, or post-market surveillance expectations. MedTech Europe's call for more ambitious revisions suggests the current proposals may not provide the relief manufacturers are hoping for, meaning teams need to plan for continued stringency, not regulatory rollback.

The CER and Software Documentation Squeeze

Two Greenlight Guru articles this month underscore how documentation expectations are tightening in parallel. The first revisits the tension between MEDDEV 2.7/1 Rev. 4 guidance and MDR Annex XIV requirements for Clinical Evaluation Reports. The second explores how FDA's Quality Management System Regulation (QMSR), effective 2 February 2026, is changing what auditors expect from software device documentation—particularly around cybersecurity, software validation, and risk management integration.

Both pieces point to the same underlying reality: regulatory expectations are converging toward higher scrutiny of clinical evidence and software lifecycle documentation, whether you're facing a Notified Body audit in the EU or an FDA inspection in the US. And now, with EUDAMED mandatory, clinical investigation data isn't just reviewed during certification—it's publicly registered and cross-referenced. Software as a Medical Device (SaMD) manufacturers need to recognise that their DHF (Design History File) is no longer just an internal artefact. It's the evidentiary foundation that must align with EUDAMED entries, UDI submissions, and post-market performance data.

This convergence matters because it eliminates the traditional separation between 'regulatory documentation' and 'operational systems.' Your EUDAMED submissions, your CER, your software validation records, and your post-market surveillance reports now form an interconnected evidence web. Inconsistencies between them aren't just quality system issues—they're red flags that competent authorities and Notified Bodies can spot and interrogate with increasing ease.

What This Means for Your Team

If your organisation hasn't yet treated EUDAMED as a live compliance requirement, that grace period is over. Immediate priorities should include auditing your Actor Registration status across all EU markets, verifying that UDI and device registration data is complete and accurate, and ensuring all Notified Body certificates are uploaded and current. For devices under clinical investigation, confirm that study registrations in EUDAMED align with your CER evidence base and that any protocol amendments are reflected.

Longer-term, regulatory affairs and quality teams need to embed EUDAMED submissions into their core compliance workflows. This isn't a one-time data upload—it's an ongoing obligation to maintain accurate, real-time information as devices are modified, certificates are renewed, or post-market findings emerge. That requires process integration, not just database access. It means your change control procedures need to trigger EUDAMED updates. It means your post-market surveillance system needs to flag discrepancies between real-world performance and registered claims.

For SaMD manufacturers, the intersection of EUDAMED, tightening CER expectations, and post-QMSR audit scrutiny creates a triple compliance pressure point. Software updates that alter intended use or performance claims must be reflected in EUDAMED, supported by clinical evaluation updates, and documented in your DHF with full traceability. The old practice of treating software versioning as a purely technical exercise no longer holds. Every material change is now a regulatory event with database, clinical evidence, and documentation implications.

On the strategic front, watch the MDR/IVDR revision process closely. MedTech Europe's position signals that industry is pushing for substantive change, not cosmetic tweaks—but also that the Commission's current proposals may fall short. If revisions don't meaningfully address Notified Body capacity or streamline requirements for established devices, the compliance burden will remain high, and EUDAMED's mandatory use will make that burden more visible and enforceable. Plan for the regulations you have, not the ones you hope are coming.

Key Takeaways

• EUDAMED's first four modules are now mandatory as of 28 May 2026—Actor Registration, UDI/Device Registration, Notified Bodies/Certificates, and Clinical Investigations must be complete and current, not aspirational.
• Mandatory EUDAMED use increases regulatory visibility and enforcement capability, turning database gaps into compliance non-conformities and making inconsistencies between submissions, technical files, and post-market data immediately detectable.
• MedTech Europe supports MDR/IVDR revisions but wants more ambitious changes—current proposals may not provide the relief manufacturers hope for, so plan for continued stringency and integrate EUDAMED into core workflows now.
• For SaMD manufacturers, the convergence of EUDAMED obligations, heightened CER scrutiny, and post-QMSR audit expectations creates a triple compliance pressure point requiring integrated documentation, clinical evidence, and database update processes.
• Strategic regulatory planning must account for both today's enforcement reality and tomorrow's potential revisions—embed EUDAMED compliance into change control, post-market surveillance, and clinical evaluation processes as a permanent operational requirement.

The shift to mandatory EUDAMED use isn't the end of MDR implementation—it's the beginning of a new enforcement era where regulatory oversight operates in real-time, transparency is structural, and compliance gaps are immediately visible. For regulatory affairs teams, this demands a step change from reactive database updates to proactive, integrated compliance management. The organisations that treat EUDAMED as a strategic compliance tool, rather than an administrative burden, will be best positioned not only for today's enforcement environment but for whatever revisions emerge from Brussels in the months ahead. If you're navigating this transition and need support aligning your EUDAMED strategy with broader MDR compliance, SMEDTEC's regulatory consultancy team works daily with manufacturers managing exactly these intersecting pressures.