EUDAMED secondary identifiers: optional DI and issuing-entity mapping
The acquired dictionary permits at most one secondary DI associated with a UDI-DI and records a separate secondary issuing entity. Keep optional secondary identifiers separate from the primary DI and confirm the actual supported addition workflow.
Evidence retrieved 2026-10-07. Source versions and topic-specific limits are listed below.
Description: Secondary UDI DI Code - reference to the Secondary UDI-DI registered for the current UDI-DI .
Additional DI associated to this UDI-DI.
Only one Secondary UDI-DI (Additional UDI-DI) can be associated to a UDI-DI | Occurrence: 0..1 | Updateability: Y
(Add)
Can be provided later on if initially not provided | Referenced rules: BR-UDID-03
BR-UDID-20 | XML mapping: secondaryIdentifier
(DIIdentififierType->DIcode) [1]
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: 0..1 | Updateability: Y
(Add)
Can be provided later on if initially not provided | Referenced rules: not stated | XML mapping: issuingEntityCode [2]
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 [3]
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 secondary identifiers 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.
Inventory primary and additional identities
Identify the primary DI and any actual secondary DI without creating a secondary value merely to fill a blank.
Useful evidence: A source-backed primary/secondary identifier list.
Reconcile issuing entities
Map the issuer for each identifier and flag ambiguous or multiple-secondary entries.
Useful evidence: A DI/issuer reconciliation and exception list.
Plan the supported addition or correction
Ask the provider to check the exact recorded update notes and current business rules before modifying existing records.
Useful evidence: A scoped addition/correction plan with validation results.
Work packages and dependencies
Conditional: EUDAMED secondary identifiers: optional DI and issuing-entity mapping — 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.
