The U.S. Food and Drug Administration’s Unique Device Identification (UDI) system reached a maturity point as the last tiers of its risk-based phase-in came due. The UDI rule, finalized in 2013, was deliberately staged: the highest-risk devices — implantable, life-supporting, and life-sustaining products — were required to carry identifiers and be submitted to the Global Unique Device Identification Database (GUDID) first, with lower-risk classes following on a multi-year schedule.
How the system works
A UDI has two parts. The device identifier (DI) is a fixed code that names the specific make and model; the production identifier (PI) carries variable data such as lot or batch number, serial number, and expiration date. Together they let a single scanned barcode answer both “what is this device” and “which exact unit is it.” The DI is also the key that links a physical item to its record in GUDID, the FDA’s public reference database.
The phase-in logic
Sequencing by risk class was a pragmatic decision. Implantables and life-sustaining devices carry the gravest consequences when a recall or adverse event occurs, so they came first. The FDA later set enforcement policy for the lowest-risk Class I and unclassified devices, and addressed the retirement of certain legacy identification numbers on a defined timeline.
Why it matters beyond the manufacturer
UDI is often described as a labeling rule, but its real value is realized downstream — in hospitals, registries, and exchange systems. When a device identifier is captured at the point of use and carried into the patient record, recalls become targeted instead of broad, adverse-event reports become precise, and supply data becomes comparable across institutions.
That downstream value is exactly where a health-IT convener has a role. Capturing UDI consistently requires barcode-scanning workflows, documentation fields that can hold the identifiers, and exchange standards that carry them forward. AzHeC’s Standards work area explains UDI in plain language, and our Connected Devices coverage addresses how device identity travels into clinical systems. The labeling phase-in is the foundation; using the data is the ongoing work.