How to Verify a Medical Device UDI: A GUDID Lookup Workflow for Hospital Purchasing

Before a hospital, GPO, or distributor adds a device to a contract, someone usually asks a simple question: is this the device we think it is, and who actually made it? The fastest authoritative answer is not the vendor's sell sheet — it is the device's Unique Device Identifier (UDI) looked up in the FDA's public GUDID database. This article is a practical lookup workflow: how to find a UDI on a label, search it in AccessGUDID, interpret what comes back, and spot the data-quality gaps that can quietly break a verification.

Why UDI Verification Matters Before Purchasing

A UDI is the globally unique code that identifies a specific version or model of a medical device distributed in the United States. Verifying it in GUDID lets a value-analysis team independently confirm the manufacturer of record, the brand and model, whether the device is single-use, the product code, and — when populated — the linked premarket submission number. That last point matters: a GUDID record can show whether a device is backed by a cleared 510(k) or approved PMA, which is a different question than whether the sales representative says it is.

UDI verification is also the foundation for downstream safety work. If a device is later recalled, recall notices and adverse-event tracking are far easier to act on when the implant or consumable was captured by its UDI at the point of use. Buying teams that verify the UDI up front are buying into that traceability.

What GUDID Actually Contains (and What It Does Not)

GUDID — the Global Unique Device Identification Database, pronounced "Good ID" — is administered by the FDA and made public through AccessGUDID, a free portal run jointly with the National Library of Medicine at accessgudid.nlm.nih.gov. No account is required, and the FDA updates the data daily.

One distinction trips up first-time users: GUDID stores only the Device Identifier (DI), not the full UDI. A complete UDI on a label has two parts:

• Device Identifier (DI) — the static code for a specific device version or model. This is the database key GUDID holds.
• Production Identifier(s) (PI) — lot or batch number, serial number, expiration date, manufacture date, and, for certain tissue products, a distinct donation identification code. GUDID does not store these, but it flags which PI attributes appear on the label.

In practice this means you can confirm what the device is in GUDID, but you cannot confirm which lot you hold. Lot-level questions belong on the label itself, not in the database.

UDIs are issued under standards maintained by FDA-accredited issuing agencies — GS1, HIBCC, and ICCBBA are the three used for medical devices. A GS1-format UDI in plain text looks like 12345678901234(17)140102(11)100102(10)A1234(21)1234, where the parenthesized application identifiers mark the DI and each PI element.

The GUDID Lookup Workflow, Step by Step

1. Capture the DI. Scan the barcode on the label or packaging with any UDI-aware scanner, or copy the numeric DI directly from the plain-text UDI printed below the barcode. If only the brand and model are available, AccessGUDID also accepts those as search terms.
2. Open AccessGUDID and search. Go to the AccessGUDID "Search For A Device" page. You can search by DI, brand/device name, company name, product code, premarket submission number (for example a K or P number), or MR safety status.
3. Read the device record. Confirm the brand name, company (labeler), version/model number, product code, and whether single-use and sterile flags apply. Note the premarket submission number if present, and the GMDN (Global Medical Device Nomenclature) term.
4. Cross-check the premarket status. If the record lists a 510(k) or PMA number, treat that as a lead to verify in the FDA's 510(k) or PMA databases — the GUDID entry reflects what the labeler submitted and may lag a withdrawal or supplement.
5. Capture the PI separately. Record lot, serial, and expiration from the physical label or your inventory system. GUDID will never give you these.
6. Document what you verified. For regulated purchasing files, save the DI, labeler, model, product code, premarket number, and the verification date. This is the evidence trail that survives a later audit or recall.

What the Database Actually Looks Like: A Data-Quality View

A lookup workflow is only as trustworthy as the data behind it, so it helps to know how complete GUDID is field by field. The figures below are MedDeviceGuide's own analysis of the public FDA GUDID extract (5,083,948 device identifier records, run date 2026-06-10).

The good news for a purchasing team is that the fields you need to identify a device — brand and model — are essentially universal. The warning sign is the description gap: roughly one in five records (20.3%) has no device description at all, so a "describe it in plain language" verification will silently fail for over a million identifiers. Another 31,308 records carry no product code, meaning they cannot be traced back to an FDA product code and its classification.

A subtler issue is identifier uniqueness. The DI is supposed to be unique per device version, yet the public extract contains 22,038 rows that reuse a DI already present on another record — about 0.43% of the database (5,061,910 distinct DIs across 5,083,948 rows). Most are legitimate variants (a reissued or consolidated record), but a small number are duplicates a buyer would want to resolve before relying on a single hit.

Finally, the database is clearly alive: records carry publish_date values across recent years, with hundreds of thousands of records added or updated each year. A stale-looking record may simply be a stable product, but it is worth checking the publish date when the device is new or recently modified.

Common Lookup Pitfalls and How to Handle Them

• You scanned the PI, not the DI. If a search returns nothing, confirm you entered the DI segment (the static identifier), not a lot or serial number. GUDID does not index production identifiers.
• The brand name is generic. Large distributors like Cardinal Health and Medline list enormous catalogs, and common brand names can return many near-identical model variants. Narrow by model number, not brand alone.
• No description to disambiguate. For the ~20% of records without a description, rely on model number and product code rather than a text match, and request a sample or label image from the supplier if the match is ambiguous.
• The record points to a withdrawn or superseded submission. A linked K or P number is a starting point, not proof of current clearance. Verify the submission's status in the relevant FDA database, especially for predicates you intend to rely on.
• MR safety status is blank or "MR Unsafe." If the device will enter an MRI environment, treat an empty MR safety field as "unknown" and obtain the manufacturer's MR safety statement rather than assuming safety.

For teams verifying many devices at once — for example, loading a contract catalog — AccessGUDID also offers bulk downloads and an openFDA API endpoint, which let you automate DI lookups rather than typing them one at a time.

A Pre-Purchase UDI Verification Checklist

• DI captured from the label (not a lot or serial number).
• AccessGUDID record matches the supplier's stated brand, model, and labeler.
• Product code present and consistent with the device family.
• Premarket submission number recorded for follow-up verification.
• Single-use and sterile flags reconciled with reprocessing or sterilization plans.
• Lot, serial, and expiration captured separately from the label (GUDID will not supply them).
• Publish date noted, and record re-checked if the device is new or recently changed.

Key Takeaways

• GUDID is a free, daily-updated FDA database of device identifiers — it holds the DI, not the lot-level production identifiers.
• Brand and model coverage is effectively complete, but about 20% of records lack a description and a small fraction reuse a DI, so verify by model and product code rather than by text alone.
• A linked 510(k) or PMA number in GUDID is a lead to verify elsewhere, not a guarantee of current clearance status.

Sources

• FDA, "Global Unique Device Identification Database (GUDID)."
• FDA / National Library of Medicine, AccessGUDID (accessgudid.nlm.nih.gov), including the "About" and "Search For A Device" pages.
• FDA, "AccessGUDID (for the public)."
• MedDeviceGuide analysis of the public FDA GUDID device-identifier extract (5,083,948 records, run date 2026-06-10). Data source: FDA GUDID public database.