For many medical device manufacturers, EUDAMED used to sit somewhere near the end of the regulatory checklist. Important, but not always urgent. Now, that has changed.
As of 28 May 2026, the first four EUDAMED modules became mandatory: Actor Registration, UDI/Device Registration, Notified Bodies & Certificates, and Market Surveillance. The European Commission confirmed this following Commission Decision (EU) 2025/2371, which declared the first four modules functional and triggered the six-month transition period.
For manufacturers, this makes EUDAMED registration more than a database task. It is now a regulatory data exercise that touches product identity, UDI structure, technical documentation, certificates, economic operator information, and post-market discipline.
The companies that manage this well will not be the ones that upload the fastest. They will be the ones whose data already tells a clear, consistent story.
What EUDAMED registration now includes
EUDAMED, the European Database on Medical Devices, was established under the MDR and IVDR to improve transparency, traceability, and coordination across the European medical device system. The European Commission describes EUDAMED as a system that provides a “living picture” of the lifecycle of medical devices available in the European Union.
At a practical level, EUDAMED registration now starts with four priority areas.
First, manufacturers and other economic operators need to manage Actor Registration, including providing accurate company details and the Single Registration Number, where applicable.
Second, manufacturers need to prepare UDI/Device Registration. This is where the device data itself becomes visible: Basic UDI-DI, UDI-DI, device identification, risk class, nomenclature, product variants, and other structured device attributes. Under the MDR and IVDR, manufacturers are required to submit UDI/Device information in EUDAMED for devices they place on the EU market.
Third, Notified Bodies & Certificates data must be aligned with the product portfolio. New MDR/IVDR certificates issued from the mandatory date should be registered in EUDAMED, and certificates issued before the mandatory date have a later transition deadline.
Fourth, the Market Surveillance module is now part of the mandatory framework for competent authorities and the European Commission. For manufacturers, this reinforces the broader direction of travel: regulatory data must be complete, structured, and inspection-ready.
EUDAMED registration is not just an upload
Too often, EUDAMED registration is treated as an administrative step. That approach creates problems, and the real work starts before anyone logs into the system.
Manufacturers need to make sure that the product portfolio, technical file, Declaration of Conformity, labelling, IFU, certificate scope, UDI records, and internal quality system all match. If the device name differs between documents, if the certificate scope does not reflect the registration logic, or if product variants are not clearly mapped, EUDAMED will expose those inconsistencies.
This is why EUDAMED registration should be handled as part of regulatory operations, not as a last-minute submission task.
The data behind EUDAMED registration
Good device data is not created at the point of submission. It is built through disciplined documentation.
Before EUDAMED registration, manufacturers should review the core data points that define each device:
- manufacturer and economic operator details
- SRN and actor data
- Basic UDI-DI and UDI-DI structure
- device name, model, version, and variant logic
- device risk class
- EMDN code
- intended purpose
- certificate scope
- Declaration of Conformity
- labelling and instructions for use
- technical documentation
- post-market surveillance documentation
The EMDN is the nomenclature manufacturers use when registering medical devices in EUDAMED, which makes correct classification and coding an important part of submission quality.
When EUDAMED registration data is clean, it supports smoother internal review, clearer notified body interactions, and stronger regulatory maintenance after launch. When it is incomplete or inconsistent, it can create delays that have little to do with the product itself and everything to do with the quality of the regulatory record.
Key deadlines manufacturers should keep in view
The main mandatory-use date is 28 May 2026 for the first four modules. For legacy or Regulation devices placed on the market before mandatory use, the European Commission’s transition timeline shows 28 November 2026 as the deadline to register the device in the UDI/Device module.
For MDR/IVDR certificates issued before the mandatory use of the Notified Bodies & Certificates module, the transition timeline shows 28 May 2027 as the deadline to register those certificates.
These dates matter, but they should not be treated as the starting point. A reliable EUDAMED registration process needs time for portfolio review, data clean-up, cross-functional checks, and quality approval.
Where manufacturers usually get stuck
A device portfolio may have evolved over several years, but the naming logic was never cleaned up. A certificate may cover a group of products, but the internal product list uses different terminology. A Basic UDI-DI structure may have been defined, but not fully reconciled with product variants. A technical file may describe the intended purpose one way, while labelling uses another formulation.
These are the points where EUDAMED registration becomes more than data entry.
The most common gaps include unclear product grouping, inconsistent naming conventions, incomplete UDI records, outdated certificate references, missing EMDN alignment, and poor ownership between Regulatory Affairs, Quality Assurance, Operations, and commercial teams.
Solving these gaps early reduces submission risk and makes future updates easier to manage.
How to prepare for EUDAMED registration
Manufacturers should start with a focused portfolio audit. Every device, accessory, variant, and certificate should be mapped before submission. This gives the regulatory team a clear view of what needs to be registered, what needs to be updated, and what needs further clarification.
Next, the UDI structure should be reviewed against technical documentation, labelling, certificate scope, and internal product records. This step is central to EUDAMED registration because UDI/Device data is where many inconsistencies become visible.
Then, manufacturers should define ownership. Regulatory Affairs may lead the process, but Quality Assurance, supply chain, authorised representatives, importers, and commercial teams often hold parts of the data. Without clear ownership, updates become reactive.
Finally, EUDAMED registration should be built into the quality management system. Changes to the device, intended purpose, labelling, certificate status, market availability, or economic operator details may all trigger a need to review EUDAMED records.
How Aura Health supports EUDAMED registration
For SaMD and AIaMD medical device companies, EUDAMED registration rarely starts with the EUDAMED form itself. It starts much earlier, with the structure behind the device.
That means knowing exactly how the intended purpose is written, how software versions are controlled, how the Basic UDI-DI is assigned, how product variants are grouped, how certificate scope is mapped, and how regulatory changes are managed after launch.
Aura Health helps manufacturers bring that structure into order before submission. We work across regulatory, quality, clinical, technical, and market access workstreams to make sure the device record is not only complete but consistent.
For companies preparing for EUDAMED registration, this includes reviewing how the EUDAMED data connects to the technical documentation, Declaration of Conformity, labelling, instructions for use, clinical evaluation, PMS documentation, certificate scope, and QMS change-control process.
For software-based medical devices, this alignment is especially important. A new release, modified claim, cybersecurity update, market expansion, certificate change, or product variant can all affect the regulatory record. If those changes are not reflected properly, EUDAMED can quickly become disconnected from the actual product lifecycle.
Aura Health supports SaMD and AIaMD manufacturers with the work that sits behind a smooth submission:
- structuring UDI and Basic UDI-DI logic
- mapping software versions, variants, and device families
- aligning EUDAMED data with MDR and IVDR documentation
- reviewing intended purpose, claims, and certificate scope
- connecting regulatory data with QMS change control
- preparing device records for post-market maintenance
- supporting lifecycle planning beyond the initial registration
The goal is to make sure the device record is accurate, traceable, and ready to stand up to regulatory review, not just at submission, but throughout the product lifecycle.
EUDAMED registration done properly
Done well, EUDAMED registration gives manufacturers more than a completed submission. It creates a cleaner view of the product portfolio, clearer ownership of regulatory data, and stronger alignment between documentation and market reality.
That matters because EUDAMED is not a one-time milestone. It is part of the regulatory infrastructure that will shape how medical device information is submitted, maintained, and reviewed in Europe.