The Clock Is Ticking: What Medical Device Manufacturers Need to Know About EUDAMED’s Mandatory Transition

The voluntary period for EUDAMED is over. Commission Decision (EU) 2025/2371, published November 27, 2025, formally confirmed that the first four EUDAMED modules are fully functional; triggering a six-month transition period that ends on May 28, 2026, when mandatory use begins. For medical device manufacturers, authorized representatives, importers, and notified bodies, this is no longer a preparation window. It is the compliance deadline.

From May 28, 2026, EUDAMED is no longer optional. If an obligation is linked to one of the four mandatory modules, it must be fulfilled through EUDAMED. Parallel national systems or alternative processes are no longer sufficient.

What Is EUDAMED and Why Does the Transition Matter?

EUDAMED (European Database on Medical Devices) is the European Union’s centralized database designed to strengthen transparency, improve traceability, and support coordinated market surveillance across EU Member States.

EUDAMED (European Database on Medical Devices) is the EU’s centralized database designed to strengthen transparency, traceability, and market surveillance across all Member States. The four modules now mandatory from May 28, 2026 are: Actor Registration (for registering economic operators), UDI/Device Registration (for registering devices and their unique device identifiers), Notified Bodies and Certificates (for certificate information), and Market Surveillance (for coordinating enforcement actions between competent authorities). The Vigilance and Post-Market Surveillance and Clinical Investigations modules will become mandatory at a later date.

For manufacturers, the challenge is not just understanding what needs to be submitted. It is ensuring the right data is accessible, accurate, and ready to maintain over time and that the upstream processes feeding EUDAMED (regulatory interpretation, product master data, labelling, and quality systems) are strong enough to support compliant, scalable submissions.

The “Voluntary Period” Is a Strategic Opportunity

The voluntary period this webinar discussed is now closed for the four mandatory modules. Until May 28, 2026, use of the modules remained voluntary: after that date, their use became a legal requirement for any responsible economic operator under MDR/IVDR. If your organization used the voluntary period strategically to build readiness, you are in a strong position. If not, the priority now is accelerated action on the steps below.

The core lessons from the voluntary period remain fully relevant: manufacturers who rushed at the last minute faced data quality issues, missed dependencies between modules, and submission failures that blocked market access. Early EUDAMED testing has revealed an uncomfortable reality; most manufacturers were far less prepared than they assumed, with poor data quality remaining the single greatest obstacle to achieving full compliance.

EUDAMED Readiness Starts with Data

A major insight Yuan and I shared was that EUDAMED implementation challenges often come down to one issue: data fragmentation.

The data readiness challenge is real and well-documented. Industry data shows that nearly 60% of required device data is missing from internal systems at the outset, not a simple gap that can be resolved quickly, but a reflection of deeper issues in documentation practices, data ownership, and cross-system consistency.

EUDAMED requires consolidating over 120 fields per device entry, from risk class to critical components, a level of data cleansing that most internal IT departments are not prepared to execute alone. Common problems include: siloed data, inconsistent definitions, incomplete product hierarchies, unclear regulatory ownership, and over reliance on manual entry.

The key question every regulatory team must answer today: Do we have a validated, single source of truth for device and regulatory attributes and is that source aligned with what EUDAMED’s validation pipeline expects?

EUDAMED Modules Are Connected, So Your Strategy Must Be Too

EUDAMED is not a series of isolated tasks: it is an interconnected ecosystem where gaps in one module create downstream failures in others. All EUDAMED data must match across technical documentation, labelling, instructions for use, and certificates issued by the notified body. Inconsistencies can delay certification, surveillance actions, or authority communications.

A concrete example of module dependency: manufacturers must register basic UDI-DI and all relevant UDI-DIs and device attributes before a notified body can link certificates to those devices in the NB/Certificates module. If the device is not in EUDAMED, it cannot be placed on the market. Similarly, refused notified body applications will be visible to all other notified bodies; requiring manufacturers to disclose prior failures, making accurate first-time submissions more important than ever.

For teams supporting multiple product lines, regions, and device classifications, understanding these dependencies before submission, not during, is essential.

Use the EUDAMED Practice Portal to Build Readiness Faster

The EUDAMED practice environment (playground) remains one of the most valuable preparation tools available, even now that mandatory use has begun. Teams that have not yet used it should prioritize it immediately to identify data gaps before attempting live submissions.

Manufacturers should also evaluate their device registration method based on portfolio size: manual registration is suitable for small volumes; XML file upload is semi-automated and more complex; and full machine-to-machine (M2M) integration is highly recommended for large portfolios. For manufacturers with large product catalogs, M2M integration with ERP or PLM systems via XML-based protocols is the most scalable approach.

Companies that begin preparing device registrations and UDI uploads at this stage commonly discover that product names differ between systems, device hierarchies are incomplete, and documentation references no longer match operational data — regulatory teams find they cannot submit information until these discrepancies are resolved. Testing in the practice environment first surfaces these issues in a low-risk setting.

Legacy Products Require Special Attention

Legacy products: devices placed on the market under older MDD/IVDD frameworks or MDR/IVDR devices already on the market before May 28, 2026 have a separate, firm deadline. Legacy devices already placed on the market before May 28, 2026 but continuing to be sold after that date must be registered in EUDAMED’s UDI/Device module by November 27, 2026. Notified bodies must complete the upload of relevant legacy certificate information by May 28, 2027.

A common misconception is that the registration process is automatic, or that a notified body or authorized representative will handle it. In most cases, the responsibility for submitting device data in EUDAMED falls on the manufacturer. For large portfolios where prioritization is essential, regulatory teams should triage by product line, revenue impact, and certificate expiry date to avoid bottlenecks approaching the November 2026 deadline.

Learn how to build an EUDAMED readiness strategy that reduces risk, improves efficiency, and supports long term compliance. To get the full context, timelines, and step by step guidance shared by RegDesk and DQS, watch the complete webinar recording for practical insights you can apply immediately.

Q&A:

1. Is EUDAMED registration mandatory now in May 2026? Yes. Commission Decision (EU) 2025/2371, published November 27, 2025, confirmed the functionality of the first four modules and triggered a six-month transition. From May 28, 2026, the Actor Registration, UDI/Device, Notified Bodies and Certificates, and Market Surveillance modules are mandatory to use. Voluntary use of the four modules ended on May 27, 2026.
2. What are the four mandatory EUDAMED modules? The four mandatory modules from May 28, 2026 are: Actor Registration (economic operators), UDI/Device Registration (devices and their UDIs), Notified Bodies and Certificates (certificate information), and Market Surveillance (competent authority coordination). The Vigilance and Clinical Investigations modules will become mandatory at a later date.
3. What happens if my company misses the EUDAMED deadline? Missing the deadline can prevent new devices from entering the EU market and may trigger regulatory scrutiny for existing products. Additionally, failure to notify authorities of an unavailable device registered as “on the market” in EUDAMED may lead to double liability for the manufacturer. Non-compliance is not a minor procedural issue; it directly affects market access.
4. Does my authorized representative or notified body handle EUDAMED registration for me? No, this is a common misconception. In most cases, the responsibility for submitting device data in EUDAMED falls on the manufacturer. Authorized representatives and notified bodies have their own EUDAMED obligations but do not automatically submit device registration data on a manufacturer’s behalf.
5. What is the deadline for legacy devices already on the EU market? Devices already placed on the market before May 28, 2026 but continuing to be sold after that date must be registered in EUDAMED’s UDI/Device module by November 27, 2026. Certificates issued before May 28, 2026 must be uploaded by notified bodies by May 28, 2027.
6. What is a Basic UDI-DI (BUDI-DI) and why does it matter for EUDAMED? The Basic UDI-DI (BUDI-DI) is the primary key grouping devices in EUDAMED that share the same intended purpose, risk class, and essential design characteristics. It is also the link between certificates and vigilance records; meaning incorrect BUDI-DI grouping creates cascading errors across multiple modules. Existing product families must be uploaded with their correct BUDI-DI by November 27, 2026.
7. What is the EUDAMED practice portal and should we still use it? The EUDAMED practice environment (playground) allows teams to test data submissions in a low-risk setting before making live submissions. Yes, even now that mandatory use has begun, the practice portal is valuable for teams working through their first submissions, testing XML or M2M integration, or identifying data gaps before submitting to the live system.
8. What are the biggest data readiness mistakes manufacturers make? The most common problems include siloed data, inconsistent definitions, incomplete product hierarchies, unclear regulatory ownership, and overreliance on manual entry. Manufacturers frequently discover that product names differ between systems, device hierarchies are incomplete, and documentation references no longer match operational data; only when they begin actual registration work. Starting the data audit process immediately, before attempting live EUDAMED submissions, is the single most impactful step any team can take.
9. What does EUDAMED mean for manufacturers with large portfolios? Large portfolios face a significant data consolidation challenge, each EUDAMED device entry requires over 120 fields of structured data. For high-volume portfolios, machine-to-machine (M2M) integration with ERP and PLM systems via XML protocols is the recommended registration method, and manufacturers should begin implementation immediately if they have not already done so.