EUDAMED identifier mapping: Basic UDI-DI, UDI-DI and issuing entity
The acquired dictionary identifies a Basic UDI-DI code together with its issuing entity, and a UDI-DI reference back to its Basic UDI-DI. Map these relationships explicitly rather than placing all identifiers in one interchangeable column.
Evidence retrieved 2026-10-07. Source versions and topic-specific limits are listed below.
Description: Assigned Issuing Entities that will generate the DI Codes allocated for all DI`s inside Eudamed (Basic UDI DI, UDI-DI, Unit of Use DI, Secondary Di , Package level DI).
The Commission shall designate one or several entities to operate a system for assignment of UDIs ('issuing entity') | Occurrence: 1 | Updateability: not stated | Referenced rules: not stated | XML mapping: issuingEntityCode [1]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
DD BASIC UDI / FLD-UDID-14 / Basic UDI- DI code
Description: Device Identifier code/value (DI Code). Together with the Issuing Entity creates the uniqness of the element to which they are assigned (Basic UDI-DI , UDI-DI, etc.)
The Basic UDI-DI is the primary identifier of a device model.It is the main key for records in the UDI database and is referenced in relevant certificates and EU declarations of conformity | Occurrence: 1 | Updateability: not stated | Referenced rules: BR-UDID-003 | XML mapping: DICode [2]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
Description: Reference to the Basic UDI-DI to which the Device is associated. | Occurrence: 1 | Updateability: not stated | Referenced rules: not stated | XML mapping: basicUDIIdentifier [3]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
Description: Assigned Issuing Entities that will generate the DI Codes allocated for all DI`s inside Eudamed (Basic UDI DI, UDI-DI, Unit of Use DI, Secondary Di , Package level DI).
The Commission shall designate one or several entities to operate a system for assignment of UDIs ('issuing entity') | Occurrence: 1 | Updateability: not stated | Referenced rules: not stated | XML mapping: issuingEntityCode [4]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
Dated technical/help evidence, not a complete legal duty set or live EUDAMED response. Current target-environment release, business rules, permissions and actual buyer records remain unresolved. Blank dictionary flags are unknown; occurrence and update notes keep their stated conditions. No credentials, registration deadline or completed production exchange is inferred.
Prepare the EUDAMED identifier mapping work package
Use this checklist to gather your business or product details before speaking with a specialist. The items below explain what to record and suggest useful supporting documents. You can add your own answers in the editable project brief.
Separate identifier levels
Inventory Basic UDI-DI and device UDI-DI values and issuing entities in distinct source columns.
Useful evidence: An identifier/issuing-entity inventory reconciled to labels and declarations.
Map the parent relationship
Link each device identifier to the correct Basic UDI-DI; investigate missing or ambiguous parent assignments.
Useful evidence: A device-to-Basic-UDI mapping and exception list.
Agree registration versus correction scope
Have the provider identify which records are new and which existing relationships need a supported correction.
Useful evidence: A versioned record plan with ownership and acceptance checks.
Work packages and dependencies
Conditional: EUDAMED identifier mapping: Basic UDI-DI, UDI-DI and issuing entity — Review the actual current records and target-environment requirements; complete the specific mapping/onboarding or maintenance task with source/version and acceptance evidence.
Optional: Related preparation or maintenance support — Use only where the mapped records require that additional phase; confirm ownership and deliverables before adding this service.
Questions for providers
How will you resolve the specific field/identity or state dependencies shown here for our actual records?
Which current environment release, permissions and business rules support the proposed operation?
What mapping, unresolved-error and acceptance evidence will you hand over, and who owns each correction?
Sources and data dates
Read the official document in context. The audit details identify the precise locators and preserved versions used for this page.
