- Commission page for actor registration, Actor ID/SRN, registration requests, required documents, users, and module status.
"The Actor registration is the first"
A focused guide to how the EU MDR connects UDI assignment, UDI carriers, Basic UDI-DI records, device registration, and actor registration in EUDAMED.
Use it to keep label data, certificates, declarations, technical documentation, EUDAMED entries, and change-control records aligned.
Structured answer sets in this page tree.
Cited legal and guidance references.
Under the EU MDR, identifiers connect the device, manufacturer, actor registration, declaration of conformity, certificates, technical documentation, vigilance records, and public data. Managing the label code or the database filing in isolation leaves those records inconsistent.
Start with the manufacturer and actor record. MDR Article 31 requires manufacturers, authorised representatives, and importers to submit actor information before placing non-custom-made devices on the market, unless already registered. After competent-authority verification, the electronic system issues the Single Registration Number ().
Then map the device identifiers. MDR Article 27 describes the system as a , which is specific to a manufacturer and device, plus a , which identifies the production unit and, where applicable, packaged devices. Article 29 requires the manufacturer to assign a before placing a non-custom-made device on the market and to provide it with core data elements to the UDI database.
Treat the as the regulatory family key, not the label code. MDCG 2022-7 describes it as the main key in the database and relevant documentation, including product certificate, declaration of conformity, technical documentation, and SSCP, for devices with the same intended purpose, risk class, and essential design and manufacturing characteristics.
The carrier must not be managed separately from the technical file. MDR Article 27 requires UDI carriers on the device label and all higher levels of packaging, excluding shipping containers. The same article requires the on the EU declaration of conformity and an up-to-date list of assigned UDIs in the technical documentation.
For software, Annex VI Part C gives separate rules. A new is required when a software modification changes original performance, safety, intended use, or data interpretation; minor revisions require a new rather than a new UDI-DI. The UDI must be available on an accessible screen or through an API where there is no user interface.
For systems and procedure packs, Annex VI Part C assigns responsibility to the person referred to in Article 22, requires the pack UDI carrier outside the packaging as a general rule, and preserves separate UDI requirements for device contents unless an exemption applies.
has six modules: actor registration, /device registration, notified bodies and certificates, clinical investigations and performance studies, vigilance and post-market surveillance, and market surveillance. The Commission EUDAMED portal states that the first four modules are mandatory from 28 May 2026 and identifies Actor, UDI/devices, NBs and Certificates, and Market Surveillance for competent authorities and the European Commission as those modules.
The actor-registration page states that every economic operator in the medical devices sector, including EU and non-EU manufacturers, authorised representatives, system or procedure pack producers, and importers, must register before placing devices or systems/procedure packs on the EU market. The same page states that all actors upload a signed declaration on information-security responsibilities, and non-EU manufacturers need an active authorised representative and mandate summary document.
The /Device registration page states that manufacturers submit UDI/Device information for devices they place on the EU market. Voluntary entry began in October 2021, and the module became mandatory on 28 May 2026 after Commission Decision (EU) 2025/2371 declared it functional and Regulation (EU) 2024/1860 supplied the transition rule. The Vigilance and Post-Market Surveillance module remains in development, and the Clinical Investigations and Performance Studies module remains under analysis.
and records need explicit change governance. MDCG 2022-7 states that a new is required when a change could lead to device misidentification or ambiguity in traceability, including changes to name or trade name, device version or model, single-use status, sterile packaging, need for sterilisation before use, package quantity, critical warnings or contraindications, and certain CMR or endocrine-disruptor information.
The same guidance says a new would be required when a substance-based device has a formulation change or an extension of claims such as an additional medical purpose. For reprocessed single-use devices under MDR Article 17(2), MDCG 2022-7 says the reprocessor is considered the manufacturer and must assign a new and ; reprocessing within a health institution under Article 17(3) does not require a new UDI under that guidance.
Branding agreements do not transfer assignment to a distributor. MDCG 2026-5 says the manufacturer assigns every , including separate UDI-DIs for the same device sold under different trade names, and those identifiers must remain linked to the manufacturer. A third party may perform practical tasks on the manufacturer's behalf, but the manufacturer retains legal responsibility.
MDR Article 10 also makes verification part of the manufacturer's quality management system: procedures must verify UDI assignments and ensure consistency and validity of information provided under Article 29. That makes UDI impact review part of change control, not a clerical update after release.
Use Sorena to compare MDR identifiers, labels, declarations, certificates, technical documentation, and EUDAMED fields before a device record or change package is approved.
"The Actor registration is the first"
"The two remaining modules"
"at least 2 active Local Actor Administrators"
"UDI/Devices Data sets"
"A new UDI-DI assignment is required"
"is the only entity"
"keep up-to-date a list of all UDIs"