Unique Device Identification (UDI)

Unique Device Identification (UDI) is a system that assigns each medical device a globally unique code, letting regulators, hospitals, and manufacturers trace a specific device from production to patient use. A UDI combines a fixed device identifier (DI) with a variable production identifier (PI) and appears in both barcode and plain-text form.


What is Unique Device Identification (UDI)?

Unique Device Identification (UDI) is the regulatory framework for putting a standardized, machine-readable identity on medical devices. It sits at the intersection of labeling, quality records, and regulatory data submission. Every UDI has two parts. The device identifier (DI) is a fixed code tied to a specific model and packaging level. The production identifier (PI) is variable and carries the lot or batch number, serial number, expiration date, or manufacturing date when those appear on the label.

The identifier is issued under a system run by an accredited issuing agency, such as GS1, HIBCC, or ICCBBA. When GS1 is used, the DI commonly maps to a GTIN. The code prints on labels and packages in two forms: an automatic identification and data capture (AIDC) barcode and human-readable interpretation (HRI) text.


Why Unique Device Identification (UDI) matters in medical device development

A device without a reliable identity is hard to recall, hard to track, and hard to defend in an audit. UDI fixes that by giving every version and model a single, verifiable code that follows it through distribution to the point of care.

The stakes are concrete. During a field safety corrective action, UDI lets a manufacturer pinpoint exactly which lots or serial numbers are affected, which narrows the recall and reduces the removal of unaffected stock. For post-market surveillance, coded device identity links adverse event reports and complaints back to a specific product, so signal detection is cleaner. For regulators, UDI feeds public databases that clinicians and supply-chain teams query directly.

Missing or inconsistent UDI data is also an audit finding waiting to happen. Under both FDA and EU rules, the identifier on the label must match the master data submitted to the regulator’s database. A mismatch is treated as a documentation deficiency and can hold up market access.


How Unique Device Identification (UDI) works

UDI runs on a few coordinated steps that a quality and regulatory team owns together:

  • Assign the identifier. The labeler, usually the manufacturer, obtains DIs from an accredited issuing agency for each model and packaging level.
  • Build the carrier. The UDI is encoded as a barcode (often GS1 DataMatrix or GS1-128) and printed with matching HRI text. Reusable devices that are reprocessed between uses also carry the UDI as direct part marking.
  • Submit device data. In the U.S., the labeler submits DI-keyed attributes to the FDA Global Unique Device Identification Database (GUDID). GUDID holds the DI, not the PI.
  • Register in the EU. Under EU MDR 2017/745 and IVDR 2017/746, manufacturers assign a Basic UDI-DI (the group-level primary key), a UDI-DI (the specific product on the label), and a UDI-PI, then register the data in EUDAMED.
  • Control changes. UDI assignment rules, label artwork, and database entries stay under document control, and any change to core data is updated within the required window.

The governing rules are specific. FDA UDI requirements sit in 21 CFR Part 830 and the labeling provisions of 21 CFR Part 801 Subpart B, alongside the quality system requirements now framed by the QMSR in 21 CFR Part 820. The EU system is built on Article 27 and Annex VI of the EU MDR 2017/745.


Common challenges and best practices

The most common failure is treating UDI as a labeling task instead of a data-governance one. The identifier is easy. Keeping the label, the technical documentation, and the regulator’s database aligned across every packaging level and variant is the hard part.

Teams also underestimate the EU timeline. Commission Decision (EU) 2025/2371 made four EUDAMED modules mandatory from May 28, 2026, so new devices must be registered before they reach the market, and devices already on the market must be registered by late November 2026. Portfolios with hundreds of records need machine-to-machine upload rather than manual entry.

Good practice looks like this. Establish one source of truth for device master data, map DI and PI rules to each model early, verify barcode print quality against the issuing agency standard, and route every UDI change through formal change control. Keep GUDID and EUDAMED entries synchronized with the physical label at all times.


How SJML helps with Unique Device Identification (UDI)

SJML supports UDI as part of its regulatory sustenance and Compliance-as-a-Service work. The team helps manufacturers align labeling and packaging with UDI requirements, structure device master data, and prepare submissions for FDA GUDID and EU EUDAMED, including Basic UDI-DI and UDI-DI hierarchies. Because SJML also handles labeling, technical documentation, and QMS work in-house, UDI data can stay consistent with the design history file, technical file, and physical labels through change control. This reduces the mismatches that trigger audit findings and slow market access.

Talk to SJML’s QARA team →


Frequently asked questions

What is the difference between a UDI-DI and a UDI-PI?

The UDI-DI (device identifier) is the fixed part of a UDI that identifies a specific device model and packaging level. The UDI-PI (production identifier) is the variable part that carries data such as lot or batch number, serial number, manufacturing date, or expiration date. Together, they give each individual unit a traceable identity.

Is a UDI required for every medical device?

Not every device, and not all at once. FDA phased UDI in by risk class, with certain low-risk and exempt devices excepted. In the EU, UDI applies broadly under MDR and IVDR, though timelines vary by class. Class III and implantable devices generally face the earliest and strictest requirements in both systems.

What is GUDID and how does it relate to UDI?

GUDID is the FDA Global Unique Device Identification Database, the U.S. repository where labelers submit device information keyed to the UDI. It stores the device identifier (DI) and its associated attributes, not the production identifier. Regulators, clinicians, and the public can query GUDID to confirm a device’s identity and basic characteristics.

What is a Basic UDI-DI in the EU?

The Basic UDI-DI is the main access key in the EU system. It identifies a group of devices that share the same intended purpose, risk class, and essential design characteristics. It appears on technical documentation and certificates rather than the label, and manufacturers must register it in EUDAMED before a notified body can link related certificates.


Related terms

  • Traceability
  • Device History Record (DHR)
  • Medical Device Labeling
  • EUDAMED
  • GS1 GTIN

Table of Contents

Free EU MDR Technical Documentation Compliance Checklist

Understand documentation gaps and use our single-window worksheet to prepare for Notified Body review.

Related Glossaries

```html ```