The first four EUDAMED modules become mandatory on 28 May 2026.
That means actor registration, UDI and device registration, notified body and certificate data, and market-surveillance data need to line up cleanly with the way the device is described in the wider EU MDR documentation set.
The European Commission now says that, from 28 May 2026, the first four EUDAMED modules are mandatory to use. Even if your day-to-day work is more technical-file focused than database focused, this matters because registration data and documentation can no longer drift apart without creating downstream friction.
What Becomes Mandatory on 28 May 2026
According to the Commission's EUDAMED overview, the first four modules moving into mandatory use are:
- Actor registration
- UDI and device registration
- Notified Bodies and Certificates
- Market Surveillance
What Is Not Mandatory Yet
The Commission also states that the remaining two modules are still under development:
- Post-market surveillance and vigilance
- Clinical investigations and performance studies
That distinction matters. Teams should not assume that the entire EUDAMED rollout arrives at once. But they should assume that the mandatory modules will start exposing inconsistencies in device, certificate, and actor data much more quickly.
Why EU MDR Documentation Teams Should Care
- Device description consistency: the name, model structure, and registration logic need to match what appears in technical documentation and supporting summaries.
- Certificate alignment: notified body and certificate references should not conflict with what the dossier says about scope, family structure, or status.
- UDI discipline: device registration quality becomes an operational issue, not a background one.
- Internal ownership: regulatory, RA/QA, labeling, and documentation teams need to know who owns each data element and when changes cascade.
- Future PMS readiness: even though the PMS and vigilance module is not yet mandatory, weak document control now will make later rollout harder.
What to Recheck Now
- Legal manufacturer and actor-registration details across templates and internal trackers
- UDI and device-family naming logic used in dossiers, labels, and device lists
- Certificate scope language versus how the product is described in the wider file
- Change-control procedures for product variants, packaging updates, and certificate changes
- Who actually owns the handoff between dossier updates and database updates
EUDAMED readiness is not just an IT task. It is a documentation-governance task. If the device story is inconsistent across systems, certificates, and technical documents, the extra visibility will expose it.
Where This Intersects Biocompatibility Work
The Commission's EUDAMED pages do not frame this as a biocompatibility update. That connection is an operational inference. But it is a reasonable one: when device identity, configuration scope, and certificate framing are under tighter control, the supporting biological evaluation story also needs to stay synchronized. Teams already struggling with variant logic, material differences, or technical-file consistency should treat this milestone as a readiness trigger.
Official References
Why this perspective is practical
MedDev Advisory focuses on ISO 10993 biological evaluation, FDA reviewer-facing files, EU MDR technical documentation, and selected CDSCO strategy work. Arvind Rathore's background includes implantable biosensor research at IIT Kanpur and as a Marie Skłodowska-Curie Fellow at INSERM, including hands-on ISO 10993-aligned biocompatibility testing, cytotoxicity, sterilization effects, oxidative stress, and biomaterial-cell interaction work. Read more about Arvind Rathore.
If data ownership is split across teams, consistency gaps usually appear at the document edges first.
A structured review can show whether the device, certificate, and supporting biological documentation still line up cleanly before the EUDAMED milestone adds extra operational pressure.