Vetted consultants
How we vet consultants
Only firms that pass our review are listed here.
- We assess regulatory experience, service scope, and professional credentials.
- Approved status may be revoked if standards are not maintained.
July 18, 2026
Approximately 5 minutes
Reviewed by Nate Lam, Founder & Director, ElendiLabs
EUDAMED UDI Device Registration Requirements: MDR/IVDR Data and May 2026 Mandatory Timeline
Quick answer
Is EUDAMED device registration mandatory? Yes. From 28 May 2026, manufacturers must submit UDI and device information in the EUDAMED UDI/Devices module for medical devices and in vitro diagnostic devices placed on the EU market under Regulation (EU) 2017/745 (MDR) and Regulation (EU) 2017/746 (IVDR). Commission Decision (EU) 2025/2371 and Regulation (EU) 2024/1860 set this deadline alongside three other mandatory modules. Registration is informational—competent authorities do not assess device records—but it is a legal obligation distinct from Actor module registration. Each device needs a unique Basic UDI-DI and UDI-DI; UDI-PI is not registered in EUDAMED. Only users with Proposer or Confirmer profiles can submit device data. Authorised representatives and importers cannot register devices, even though they must register as actors. Voluntary UDI/Device entry has been possible since October 2021 at https://webgate.ec.europa.eu/eudamed.
Who this applies to
This guide applies to economic operators who place devices on the EU market and must fulfil UDI obligations under MDR Articles 27–29 or IVDR Articles 24–26.
Primary users of the UDI/Devices module:
- Manufacturers — EU and non-EU manufacturers who assign UDI-DIs and are responsible for device registration data
- System and procedure pack (SPP) producers — entities that register systems or procedure packs under MDR Article 22 / IVDR Article 22
Roles that register in the Actor module but cannot register devices:
- Authorised representatives (AR) — mandatory for non-EU manufacturers under MDR Article 11 / IVDR Article 11, but ARs do not submit UDI/Device records
- Importers — must hold an SRN as actors under MDR Article 13 / IVDR Article 13, but cannot enter device registration data
Product scope covers MDR medical devices, IVDR in vitro diagnostic devices, legacy devices still marketed under transitional timelines, and old devices subject to separate data rules under Regulation (EU) 2024/1860. Device registration uses EMDN (European Medical Device Nomenclature) codes to classify products in EUDAMED.
Actor module vs UDI/Devices module: two separate obligations
EUDAMED splits economic operator identity from product data. Both modules become mandatory on 28 May 2026, but they serve different purposes and follow different workflows.
| Aspect | Actor module | UDI/Devices module |
|---|---|---|
| Legal basis | MDR Article 30 / IVDR Article 27 | MDR Articles 28–29 / IVDR Articles 25–26 |
| What is registered | Economic operator identity (manufacturer, AR, importer, SPP producer) | Device identifiers and characteristics |
| Key output | Single Registration Number (SRN) | Basic UDI-DI + UDI-DI device record |
| Who submits | Each economic operator for their role | Manufacturer or SPP producer (not AR or importer) |
| NCA role | Validates actor registration; issues SRN | No assessment of device registration data |
| Public visibility | Actor data searchable on public EUDAMED site | Partial device data publicly searchable |
| Prerequisite | EU Login + actor registration request | Active manufacturer/SPP producer SRN + user access |
Practical rule: complete Actor registration and obtain SRN first, then register devices in the UDI/Devices module referencing that SRN. Device records link to the manufacturer's or SPP producer's actor identifier. Attempting device registration without an approved actor profile and appropriate user permissions will fail in the restricted EUDAMED portal.
Mandatory date: 28 May 2026 and the transition from voluntary use
The European Commission confirmed on 27 November 2025 that four EUDAMED electronic systems are functional under Commission Decision (EU) 2025/2371. Regulation (EU) 2024/1860 provides a six-month transition from Official Journal publication, making 28 May 2026 the date mandatory use begins for:
- Actor registration
- UDI database and device registration
- Notified bodies and certificates
- Market surveillance
The UDI/Devices module has accepted voluntary entries since October 2021. Manufacturers who already registered devices voluntarily should review records against current field requirements before the mandatory deadline. From 28 May 2026, placing devices on the EU market without required UDI/Device data in EUDAMED violates MDR/IVDR registration obligations.
Two remaining modules—Clinical Investigations and performance studies and Vigilance and post-market surveillance—are still under development with separate timelines. Do not conflate their availability with the May 2026 UDI/Device deadline.
Proposer and Confirmer roles: who can enter device data
Device registration in EUDAMED requires more than a valid EU Login. Users linked to a manufacturer or SPP producer actor must hold a Proposer or Confirmer profile—not Viewer alone.
| EUDAMED user profile | Can view device data | Can create/edit device records | Typical assignee |
|---|---|---|---|
| Viewer | Yes | No | Quality, regulatory affairs (read-only) |
| Proposer | Yes | Yes — creates and submits draft records | Regulatory affairs specialist |
| Confirmer | Yes | Yes — confirms and finalises records | Authorised signatory, RA manager |
Workflow for user access:
- Economic operator obtains SRN through Actor module approval
- Individual users submit access requests linked to the actor SRN
- The actor's Local Actor Administrator (LAA) approves user access
- LAA assigns Proposer or Confirmer profile for staff who will manage UDI/Device data
- Approved users open the UDI/Device registration module and enter device records
Organisations should identify Proposers (data entry) and Confirmers (final approval) before the mandatory deadline. Viewer-only access is insufficient for compliance teams responsible for submission.
Basic UDI-DI and UDI-DI: identifier rules in EUDAMED
Each device placed on the EU market under MDR or IVDR requires two distinct identifiers in the UDI/Devices module:
Basic UDI-DI
The Basic UDI-DI is the primary identifier for a device model or group of devices sharing the same intended purpose, risk class, and essential design characteristics. It:
- Groups UDI-DIs under one regulatory device record in EUDAMED
- Appears on the EU declaration of conformity and in technical documentation
- Is not printed on individual device labels or packaging
- Must be unique per device under each regulation (MDR or IVDR)
UDI-DI (Device Identifier)
The UDI-DI is the identifier assigned to a specific device version or model variant. It:
- Is assigned by a UDI issuing entity (e.g. GS1, HIBCC, ICCBBA, IFA)
- Appears on device labels and packaging
- For GS1 issuing entity codes, EUDAMED validates a 14-digit UDI-DI format
- Must be unique for each device variant under the applicable regulation
| Identifier | On label? | On EU DoC? | Registered in EUDAMED? | Assigned by |
|---|---|---|---|---|
| Basic UDI-DI | No | Yes | Yes | Manufacturer |
| UDI-DI | Yes | Referenced in technical documentation | Yes | UDI issuing entity (via manufacturer) |
| UDI-PI | Yes (where applicable) | No | No — not registered in UDI/Devices module | Manufacturer (production-level) |
UDI-PI is not registered in EUDAMED
The Production Identifier (UDI-PI)—batch number, serial number, expiry date, or manufacturing date—is part of the UDI carrier on labels but is explicitly excluded from the UDI/Devices module scope. EUDAMED stores device-level identifiers and characteristics, not unit-level production data. Manufacturers must still apply UDI-PI on labels per MDR Annex VI Part C / IVDR Annex VI Part C, but they do not enter UDI-PI values when registering devices in EUDAMED.
Device data fields and mandatory entries
The UDI/Devices module captures device characteristics beyond identifiers. Fields marked with a red asterisk in the EUDAMED user interface are mandatory.
Core data categories include:
- Regulation — MDR or IVDR
- Device type — MDR device, IVDR device, legacy device, or old device (each category triggers different field sets)
- Basic UDI-DI and UDI-DI — unique per regulation
- EMDN code — European Medical Device Nomenclature classification
- Risk class — per MDR Annex VIII or IVDR Annex VIII rules
- Device name and description — trade name and intended purpose summary
- Manufacturer SRN — links to Actor module registration
- Notified body and certificate data — when conformity assessment requires NB involvement (see below)
- Clinical size and characteristics — where applicable to device type
- Status fields — on market, no longer placed on market, etc.
Device registration is informational. The national competent authority does not assess device registration submissions—the data is stored for transparency, market surveillance coordination, and public searchability. This does not reduce manufacturer responsibility for conformity assessment, technical documentation, or labelling compliance.
Partial device data is publicly searchable on the EUDAMED public website. Restricted-area users see additional fields not displayed publicly.
Certificate and notified body linkage
When device conformity assessment requires notified body (NB) confirmation under MDR Article 29(3) or IVDR Article 26(2), the UDI/Devices module requires certificate information linked to the device record.
| Scenario | Certificate data in UDI/Devices module |
|---|---|
| Class I self-declared (MDR) / Class A self-declared (IVDR) | Certificate fields may not apply; manufacturer SRN and DoC reference suffice |
| Class IIa, IIb, III (MDR) or Class B, C, D (IVDR) with NB involvement | NB name, certificate number, validity dates, and scope linkage required |
| Legacy devices under transitional rules | Certificate or declaration data per legacy device category |
Certificate data interconnects with the Notified Bodies and Certificates module, also mandatory from 28 May 2026. Ensure NB certificate records exist or are consistent before linking them to UDI/Device entries.
Legacy devices and old devices: separate data rules
Regulation (EU) 2024/1860 establishes specific rules for devices that were lawfully placed on the market before full MDR/IVDR application or under transitional provisions. EUDAMED distinguishes:
| Device category | Typical scope | Registration notes |
|---|---|---|
| MDR device | Devices certified or declared under MDR | Full MDR field set; Basic UDI-DI + UDI-DI required |
| IVDR device | IVDs certified or declared under IVDR | Full IVDR field set; Basic UDI-DI + UDI-DI required |
| Legacy device | Devices on market under MDR/IVDR transitional timelines (e.g. MDR Article 120, IVDR Article 110) | Reduced or adapted field set per Reg (EU) 2024/1860 legacy rules |
| Old device | Devices placed before MDR/IVDR fully applied, under specific old-device provisions | Separate data requirements; consult EC UDI/Device registration page for applicable fields |
Manufacturers with mixed portfolios must register each device under the correct category. Selecting the wrong device type triggers incorrect mandatory fields and may produce incomplete public records.
Legacy device registration timelines align with the 28 May 2026 mandatory date for the UDI/Devices module, but transitional MDR/IVDR market-access deadlines for specific legacy categories remain separate—check your device's transitional certificate or declaration status independently.
Role restrictions: AR and importers cannot register devices
A common compliance misunderstanding is assuming the authorised representative who verifies non-EU manufacturer actor registration can also submit UDI/Device data. EUDAMED explicitly restricts device registration:
| Role | Actor module registration | UDI/Devices module registration |
|---|---|---|
| Manufacturer | Yes — obtains SRN | Yes — submits device records |
| SPP producer | Yes — obtains SRN | Yes — submits SPP records |
| Authorised representative | Yes — obtains SRN | No — cannot register devices |
| Importer | Yes — obtains SRN | No — cannot register devices |
Non-EU manufacturers must ensure their organisation—not the AR—holds Proposer/Confirmer user access linked to the manufacturer SRN obtained through the AR-verified actor workflow. Importers remain responsible for verifying that devices they place on the market are registered, but they do not enter the data themselves.
Step-by-step: register a device in EUDAMED
Phase 1 — Prerequisites
- Complete Actor module registration and obtain manufacturer or SPP producer SRN
- Register EUDAMED users and obtain LAA approval for access linked to the SRN
- Assign Proposer or Confirmer profiles to staff responsible for UDI data
- Assign Basic UDI-DI and UDI-DI per MDR Annex VI / IVDR Annex VI UDI rules
- Identify correct EMDN code for the device
- Determine device type — MDR, IVDR, legacy, or old device
- Gather certificate data if NB confirmation applies under Art 29(3) MDR / Art 26(2) IVDR
Phase 2 — Create the device record
- Log in to https://webgate.ec.europa.eu/eudamed (restricted area)
- Open the UDI/Device registration module
- Create a new device record and select the applicable regulation and device type
- Enter Basic UDI-DI — verify uniqueness within your portfolio
- Enter UDI-DI — confirm format validation (14-digit for GS1 issuing entity)
- Complete all red asterisk mandatory fields — device name, EMDN, risk class, intended purpose, manufacturer SRN
- Link notified body certificate information where required
- Review data against label, declaration of conformity, and technical documentation
Phase 3 — Submit and maintain
- Proposer saves and submits the draft record
- Confirmer confirms and finalises the registration (where dual-role workflow applies)
- Verify the record appears correctly on the public EUDAMED search
- Update the record when UDI-DI changes, device status changes (e.g. no longer placed on market), or certificate data renews
- Maintain internal QMS traceability between EUDAMED records, UDI carrier labels, and technical documentation
Checklist: UDI/Device registration readiness
- Manufacturer or SPP producer SRN active in Actor module
- EUDAMED users approved with Proposer or Confirmer profile (not Viewer alone)
- Basic UDI-DI assigned and documented on EU declaration of conformity
- UDI-DI assigned by recognised issuing entity; label artwork verified
- UDI-PI strategy defined for labels (not entered in EUDAMED)
- EMDN code selected for each device
- Correct device type selected — MDR, IVDR, legacy, or old device
- Certificate/NB data prepared for Class IIa+ MDR or Class B+ IVDR devices
- Device data matches labels, DoC, and technical documentation
- Legacy/old devices mapped to Reg (EU) 2024/1860 category rules
- AR and importer roles informed they cannot submit device records
- Internal deadline set before 28 May 2026 mandatory date
- Post-registration plan for updates when device variants or certificates change
Common pitfalls
- Confusing Actor and UDI registration — SRN alone does not satisfy UDI/Device obligations; both modules require separate submissions before market placement from May 2026.
- Viewer-only user access — staff with Viewer profiles cannot create or edit device records; request Proposer/Confirmer from the LAA.
- AR attempting device registration — authorised representatives register as actors but cannot enter UDI/Device data; non-EU manufacturers must manage this internally.
- Registering UDI-PI in EUDAMED — production identifiers belong on labels only; the UDI/Devices module excludes UDI-PI by design.
- Wrong device type for legacy products — selecting MDR device instead of legacy device produces incorrect mandatory fields and incomplete records.
- GS1 UDI-DI format errors — EUDAMED validates 14-digit format for GS1 issuing entity codes; truncated or padded codes fail validation.
- Missing certificate linkage — Class IIa/IIb/III and Class B/C/D devices need NB certificate data when Art 29(3) MDR / Art 26(2) IVDR applies.
- Assuming NCA approval of device data — device registration is informational; lack of NCA feedback does not mean data is accurate—manufacturers remain responsible for correctness.
FAQ
Is EUDAMED device registration mandatory?
Yes. From 28 May 2026, the UDI/Devices module is mandatory under Commission Decision (EU) 2025/2371 and Regulation (EU) 2024/1860. Manufacturers must submit UDI and device information for devices placed on the EU market. Voluntary registration has been available since October 2021.
What is the difference between actor and device registration in EUDAMED?
Actor registration assigns an SRN to economic operators (manufacturers, ARs, importers, SPP producers). Device registration stores Basic UDI-DI, UDI-DI, and device characteristics linked to a manufacturer SRN. Both are mandatory from 28 May 2026 but serve different legal bases—MDR Art 30 vs Art 28–29.
What data is required for UDI registration in EUDAMED?
Each device needs a unique Basic UDI-DI and UDI-DI, EMDN code, risk class, device name, intended purpose, manufacturer SRN, and all red asterisk mandatory fields in the EUDAMED UI. UDI-PI is not registered. Certificate data is required when NB confirmation applies under MDR Article 29(3) or IVDR Article 26(2).
Can importers or authorised representatives register devices in EUDAMED?
No. Importers and authorised representatives must register in the Actor module and hold an SRN, but EUDAMED restricts UDI/Device registration to manufacturers and system/procedure pack producers with Proposer or Confirmer user profiles.
When does EUDAMED become mandatory for device registration?
28 May 2026 — six months after Commission Decision (EU) 2025/2371 was published on 27 November 2025. Four modules become mandatory on that date: Actor registration, UDI/Devices, Notified Bodies and Certificates, and Market Surveillance.
What is the difference between Basic UDI-DI and UDI-DI?
Basic UDI-DI identifies a device model group and appears on the EU declaration of conformity—not on labels. UDI-DI identifies a specific device variant, appears on labels, and is assigned by a UDI issuing entity. Both must be registered in EUDAMED; UDI-PI is excluded.
How do legacy devices register in EUDAMED?
Legacy devices under Regulation (EU) 2024/1860 use a dedicated legacy device type in the UDI/Devices module with adapted field requirements. Manufacturers must select the correct device category (MDR, IVDR, legacy, or old device) to trigger the appropriate data set.
Does the competent authority approve device registration in EUDAMED?
No. Device registration is informational—the competent authority does not assess UDI/Device submissions. Manufacturers remain fully responsible for data accuracy and for conformity with MDR/IVDR labelling, technical documentation, and certification requirements.
Official sources
- European Commission — UDI/Device registration: https://health.ec.europa.eu/medical-devices-eudamed/udidevice-registration_en
- European Commission — The EUDAMED four first modules will be mandatory to use as from 28 May 2026: https://health.ec.europa.eu/latest-updates/eudamed-four-first-modules-will-be-mandatory-use-28-may-2026-2025-11-27_en
- European Commission — EUDAMED UDI Devices User Guide (PDF): https://health.ec.europa.eu/system/files/2022-04/md_eudamed_udi-devices-user-guide_en.pdf
- European Commission — EUDAMED help: UDI/Device module introduction: https://webgate.ec.europa.eu/eudamed-help/en/actor/topics-by-actor/all-actors/introduction.html
- European Commission — EUDAMED overview: https://health.ec.europa.eu/medical-devices-eudamed_en
Need Regulatory Help? Try Our Platform
Post your regulatory questions or request quotations from verified pharmaceutical consultants worldwide. Get matched with experts who specialize in your market.
Registered Pharmacist · AI Engineer · Director, ElendiLabs
Registered pharmacist, AI engineer, HKHAIS founder, and pharmaceutical & medical device SEO/GEO specialist.
Ask Anything
We'll follow up with you personally.
100% response rate • Reply within 7 business days
Related Articles
Approximately 5 minutes
EUDAMED Actor Registration Mandatory from 28 May 2026: Step-by-Step Guide
Register economic operators in EUDAMED before 28 May 2026—Actor module, SRN, non-EU manufacturer AR workflow, and mandatory UDI linkage.
Approximately 5 minutes
EU MDR PMS Plan, PMSR and PSUR: Class-by-Class Requirements (Articles 83–86)
Compare EU MDR post-market surveillance obligations by class: PMS system, Annex III PMS plan, Class I PMSR, and Class IIa/IIb/III PSUR update frequencies under Article 86.
Approximately 5 minutes
Master Technical Documentation under MDR 2017/745
Technical Documentation (TD) is more than just paperwork; it is the foundation of your device's identity and proof of conformity with MDR 2017/745. This article explores the 'Iceberg' of TD, breaking down the 7 essential pillars from GSPR to Post-Market Surveillance. Learn how to apply the 3Cs—Clarity, Consistency, and Connectivity—to ensure faster Notified Body reviews and a safer time to market.
Approximately 5 minutes
MDCG Guidance: Navigating the 'Best Practice' Landscape of EU MDR
The Medical Device Coordination Group (MDCG) has published over 70 guidance documents since the MDR came into force. While not legally binding legislation, these papers represent the EU Commission's 'best practice' and are used by Notified Bodies to justify audit findings. This article explores the significance of MDCG documents, their role in conformity assessments, and why manufacturers must integrate them into their compliance strategy.
Approximately 5 minutes
Medical Device Vigilance Reporting: Mandatory Timelines and Critical Incident Scenarios
Medical device vigilance reporting is essential for patient protection, compliance, and risk mitigation. Manufacturers must immediately report critical incidents like **Death**, **Serious Injury**, **FSCA**, or **Public Health Threats**. Reporting deadlines are jurisdiction-specific (**EU/UK** are stricter than the **USA**), emphasizing the need for robust internal Quality Management Systems (QMS).