U.S. UDI for Medical Devices: 7 Step Checklist to Avoid GUDID Errors
- Qubit Technology
- 5 days ago
- 12 min read
Most medical devices marketed in the United States must carry a UDI, and labelers must submit DI-level data to the FDA’s device database unless a specific exception applies. Enforcement discretion covers certain Class I consumer health products, but professional-use devices and every Class II and III device stay on the hook. Your first move: confirm your device’s classification and intended use before touching label artwork.
TL;DR:
Most medical devices must have a fixed Device Identifier issued by an accredited agency, with production data updated only when relevant.
GUDID submission is mandatory for Class II and most Class III devices, while enforcement discretion allows some leeway for certain Class I consumer health products.
Manufacturers must carefully coordinate label design, including barcode and date format, and test direct marking durability for reusable, implantable, or life-supporting devices.
Data quality requires a single ownership, version control, and regular reconciliation to prevent mismatches and maintain compliance integrity.
UDI improves supply chain visibility and recall response but depends on accurate, consistent data entry across manufacturing, distribution, and healthcare settings.
Table of Contents
What Is UDI in Healthcare? DI, PI, and Labeling Basics
A Unique Device Identifier has two parts. The Device Identifier (DI) is fixed. It identifies the labeler and the specific device model, and it never changes. The Production Identifier (PI) is conditional. It carries lot number, serial number, expiration date, or manufacturing date, so it changes with every batch or unit.
Most U.S. manufacturers use a GS1-issued GTIN as their DI, though the FDA accepts identifiers from any FDA-accredited issuing agency and does not mandate a specific barcode technology.
Labels need both a human-readable form of the UDI and a machine-readable AIDC format, typically a barcode or data matrix. A few technical rules trip up new filers:
Every date on the label, including expiration and manufacturing dates, must follow the YYYY-MM-DD format.
The AIDC symbol must encode the exact same DI and PI shown in human-readable text; mismatches trigger rejected submissions.
Packaging at multiple levels (unit, case, pallet) often needs its own DI if sold or tracked separately.
Get this part wrong and everything downstream, from GUDID submission to recall tracking, inherits the error.
Who Must Comply With UDI Labeling Requirements?
The FDA calls the responsible party the “labeler.” That is generally whoever owns the device listing, not necessarily the contract manufacturer that physically makes the product. If your company name goes on the label, you carry the compliance burden, including GUDID submission.
Nearly every device class falls under UDI rules, but the practical obligations differ:
Class III devices and implantables face the strictest requirements, including direct marking in most cases.
Class II devices need UDI on labels and packaging plus full GUDID submission.
Class I devices generally need UDI, but the FDA applies enforcement discretion for certain Class I consumer health products regarding GUDID data entry.
Class I devices used in professional healthcare settings still must submit to GUDID; the discretion applies specifically to consumer-facing items.
Intended use matters more than most manufacturers expect. A bandage sold over the counter at a pharmacy may fall under enforcement discretion, while the identical product marketed for use in a hospital wound-care unit likely does not. That distinction should shape your regulatory strategy from the start, not get discovered during a submission review.
How to Submit Data to GUDID: Web Entry vs. Bulk Upload
The FDA gives labelers two paths into the Global Unique Device Identification Database. Small manufacturers with a handful of SKUs typically use the GUDID web application for manual entry, one device record at a time. Companies with large catalogs use HL7 Structured Product Labeling (SPL) files submitted through the FDA Electronic Submissions Gateway (ESG) for bulk uploads.
GUDID collects DI-level data only. The PI (lot, serial, expiration) never gets submitted; it lives on the physical label and in your internal quality records, not in the federal database.
Register for a GUDID account and request ESG credentials if you plan to submit HL7 SPL files.
Gather DI-level fields: device description, brand name, version/model, sterilization status, MRI safety information, storage and handling conditions, and package configuration.
Run a test submission in the GUDID test environment before submitting production data.
Cross-check your submitted records against an AccessGUDID export to confirm the data landed correctly.
Keep your Device Master Record (DMR) aligned with whatever you submit; auditors compare the two.
Pro Tip: Run your first few submissions as test transactions and validate them through an AccessGUDID search before going live. Catching a formatting error in the test environment costs you an afternoon. Catching it after a hospital orders the product costs you a recall correction.
UDI Compliance Dates and FDA Enforcement Policy
The FDA phased in UDI compliance dates by device class, starting with the highest-risk categories and working down. Class III devices and implantables came first, followed by Class II, then Class I and unclassified devices, with direct marking deadlines often trailing the general labeling deadlines by a year or more.
The most consequential recent update is the FDA’s July 22, 2022 guidance, which formalized enforcement discretion for GUDID submission on certain Class I consumer health products while leaving the underlying UDI labeling expectations intact.
Inventory manufactured and labeled before your applicable compliance date generally does not need to be pulled and relabeled.
Direct marking compliance dates for reusable devices typically extend past the general labeling deadline.
Full regulatory text sits in 21 CFR 801 and the original Federal Register UDI rule.
Our retail medical compliance guide breaks down how these dates interact with distributor and retailer obligations.
Direct Marking Requirements for Reusable Medical Devices
Direct marking applies when a device is meant to be used more than once, reprocessed between uses, or intended to be implanted or used to support life, under 21 CFR 801.45. A sticker that survives one autoclave cycle but peels off after ten doesn’t meet the standard.
Laser etching holds up through repeated sterilization cycles and is the most common method for surgical instruments.
High-durability direct marks (engraving, permanent ink stamping validated for the device’s expected reprocessing cycles) work for devices where etching isn’t feasible.
Adhesive labels routinely fail permanence testing on reusable devices and shouldn’t be your default plan for anything that gets sterilized repeatedly.
If direct marking is genuinely not technically feasible, on a device too small or too delicate, the FDA allows an exception request as part of your labeling strategy.
Pro Tip: Test your marking method through the full number of reprocessing cycles your labeling claims, not just one or two. A mark that survives five autoclave runs but fails on the fifteenth will surface during a hospital’s sterilization audit, not yours.
How to Get a Device Identifier From an Accredited Issuing Agency
You can’t invent a DI on your own. It has to come from an FDA-accredited issuing agency, which is what makes the identifier globally unique and traceable back to your company.
GS1 US is the issuing agency most American manufacturers use, and the resulting GTIN becomes the DI once assigned to a specific device version or model.
If your company already uses a GS1 company prefix for retail products, you can often extend that same numbering system to generate device-specific DIs without starting from scratch.
Register for a company prefix, generate a unique DI for each distinct model or version, and map each DI directly to the corresponding entry in your Device Master Record.
Reusing an established numbering system, rather than building a parallel one just for UDI, saves real labeling and documentation work down the line.
Searching AccessGUDID: What Procurement and Clinical Teams Can Find
AccessGUDID is the public search interface for GUDID, maintained with the National Library of Medicine. Anyone can search by DI, device name, or manufacturer and export results as structured data.
Records include device description, sterilization status, MRI safety, package configuration, and clinical safety flags, but never PI data like lot or serial numbers.
Hospital supply chain teams use it to verify a device before purchase or during a recall investigation.
EHR and health information teams often pull AccessGUDID data to populate device fields automatically; a resource like this clinical documentation integration guide covers how machine-readable identifiers feed into those systems.
A Practical UDI Compliance Checklist for Regulatory Teams
Run through this sequence before your first label goes to print, and revisit it whenever you add a new SKU:
Confirm device classification and intended use, then document the decision in your regulatory file.
Determine whether GUDID submission applies or falls under enforcement discretion for consumer Class I products.
Obtain a DI from an accredited issuing agency and set your PI formatting rules (lot vs. serial, expiration format).
Design label artwork with both human-readable text and AIDC, using YYYY-MM-DD for every date field.
Plan and test direct-mark methods for any reusable, implantable, or life-supporting device.
Set up your GUDID account, choose web entry or HL7 SPL via ESG, and run test submissions before going live.
Validate submitted records against an AccessGUDID export and reconcile against your DMR.
Pro Tip: Build a single spreadsheet that maps every SKU to its DI, classification, GUDID status, and direct-mark method. When an auditor or a hospital buyer asks a question about a specific product, you want a one-minute answer, not a scramble through three departments.
QC priorities worth flagging separately: permanence testing results for direct marks, a second-person review of date formatting before submission, and a quarterly check that label artwork still matches the live GUDID record. Labels get revised for unrelated reasons (new manufacturing address, updated sterilization claim) and it’s common for someone to update the physical label without remembering to update GUDID.
Why UDI Matters for Patient Safety and Supply Chain Visibility
The FDA built UDI as infrastructure for modern postmarket surveillance, not as a paperwork exercise. Before UDI, a hospital investigating an adverse event often had to rely on inconsistent product descriptions across different systems, sometimes tracing a device back through purchase orders and packing slips rather than a single identifier.
A standardized DI changes that. When a clinician scans a device before use, that scan can populate the electronic health record automatically, linking a specific device lot to a specific patient outcome. That link is what makes rapid recall response possible: instead of guessing which patients received a defective batch, a hospital can query its records by DI and PI and get an exact list.
On the supply chain side, UDI gives procurement teams and distributors a common language. A hospital system can compare the same device across multiple vendors using the DI rather than reconciling different internal SKU numbers, catalog codes, and manufacturer part numbers. That consistency reduces ordering errors and speeds up inventory reconciliation, particularly for large health systems running multiple facilities on shared purchasing contracts.
The objective behind all of this is fairly simple even though the regulatory mechanics are not: fewer devices that can’t be traced, faster recalls, and cleaner data feeding into safety databases the FDA and manufacturers both rely on. Treat UDI implementation as part of your device safety and recall-readiness program, not a separate labeling chore bolted onto the end of product development.
Common UDI Compliance Challenges and How to Fix Them
Most UDI problems trace back to a handful of recurring mistakes rather than genuinely ambiguous regulations.
Data field mismatches top the list. A manufacturer submits a device description to GUDID that doesn’t match the label artwork, often because label revisions happen in marketing or packaging while GUDID updates happen in regulatory, and the two teams don’t sync. The fix is procedural: route every label change through a single checklist that updates both the physical label and the GUDID record in the same workflow, not sequentially.
Legacy numbering conflicts show up when a company already has an internal SKU system and tries to force it to double as a DI without going through an accredited issuing agency. That fails FDA validation every time. Existing numbering can often be repurposed, but only if it meets the issuing agency’s format rules; retrofitting an ad hoc internal code rarely works.
Direct marking permanence failures happen when manufacturers test a marking method once, under ideal conditions, rather than across the device’s full expected reprocessing life. A laser-etched mark that looks fine after three sterilization cycles can degrade by cycle twenty. Test to the actual claimed reprocessing count, not a convenient sample.
Classification uncertainty trips up manufacturers with borderline products, items that could be marketed as consumer or professional use depending on packaging and channel. Since intended use determines whether enforcement discretion applies, get a documented classification decision early, ideally from someone who understands how the FDA has ruled on comparable products, rather than assuming based on how a competitor packages a similar item.
Submission backlog is the quiet one. Companies with hundreds of SKUs sometimes discover their manual GUDID entries can’t keep pace with new product launches. That’s usually the signal to move from web entry to HL7 SPL bulk submission through the ESG, even if the upfront setup takes longer.
How UDI Changes Inventory Management and Recall Speed
Inventory teams that adopt UDI scanning at receiving and dispensing get a level of visibility that manual SKU tracking never provided. Instead of counting boxes by generic product code, a hospital or distributor can track exact lots and expiration dates down to the unit, which matters enormously for anything with a shelf life.
Expiration management improves first. A supply chain system that scans PI data at receiving can flag near-expiry stock automatically and trigger a first-expired-first-out pull, cutting down on wasted inventory that sits until it expires on the shelf.
Recall response is where the difference becomes stark. Under the old model, a recall notice for a specific lot meant checking purchase records, calling distributors, and hoping paperwork was complete. With UDI in place, a facility can query its inventory and administration records by DI and lot number and get a precise answer: how many units came in, how many were used, on which dates, and whether any remain in stock. That turns a recall response that used to take days into one that can take hours.
The catch is that this only works if the data entered at every step, manufacturer submission, distributor receiving, hospital dispensing, stays accurate and consistent. A single mistyped lot number at receiving breaks the chain for that unit. Supply chain teams that treat UDI scanning as a genuine data quality function, not just a barcode to satisfy an audit, get the real benefit. Teams that scan inconsistently end up with a system that looks automated but still requires manual reconciliation during an actual recall.
How US UDI Fits Into Global Device Identification Standards
The United States was an early mover on mandatory UDI, but it’s not operating in isolation. The International Medical Device Regulators Forum (IMDRF) has worked for years to align UDI concepts across major regulatory markets, including the European Union’s EUDAMED system, so that the underlying logic, a fixed device identifier plus variable production data, stays consistent even when the specific database and submission mechanics differ country by country.
That harmonization matters directly for manufacturers selling into multiple markets. A device with a GS1 GTIN assigned as its U.S. DI can generally use that same GTIN as its EU UDI-DI, since GS1 operates as an accredited issuing agency in both jurisdictions. The identifier itself doesn’t need to change; what changes is where and how you submit the associated data, GUDID in the U.S., EUDAMED in the EU, and other national databases elsewhere.
Where the systems diverge is in submission timing, required data fields, and enforcement posture. The FDA’s enforcement discretion for certain Class I consumer products doesn’t necessarily have a direct equivalent in every other market, so a manufacturer can’t assume a US compliance strategy transfers cleanly overseas. Regulatory teams selling internationally need to map each market’s specific submission requirements separately, even while reusing the same core identifier across all of them.
For most manufacturers, the practical takeaway is straightforward: build your DI assignment process once, using an issuing agency with global reach like GS1, and treat each market’s database submission as a separate compliance task layered on top of that shared identifier.
Data Quality and Governance for UDI Records
A UDI system is only as reliable as the data behind it, and GUDID has a documented history of manufacturer-submitted errors, mismatched device descriptions, incorrect sterilization flags, and duplicate DIs created by different departments unaware of each other’s work.
Strong data governance starts with ownership. One team, typically regulatory affairs, should hold final authority over what gets submitted to GUDID, even if marketing or product management initiates label changes. Without a single owner, it’s common for a label update to happen without a corresponding GUDID update, or vice versa.
Version control matters just as much. Every time a device model changes in a way that affects safety-relevant fields (packaging configuration, sterilization method, MRI safety status), that change needs a new DI rather than an edit to the existing record. Editing an existing DI’s core attributes without issuing a new identifier creates a mismatch between what a clinician scans today and what a historical record says the device was.
Periodic reconciliation catches problems before an auditor does. Pulling your own AccessGUDID records quarterly and comparing them against your internal DMR and current label artwork surfaces drift early, a sterilization method that changed on the label but never got updated in GUDID, for instance. Our guide on Class II device regulatory requirements covers how classification-specific data fields factor into this reconciliation process.
Treat UDI data the way you’d treat any other regulated record: version it, assign clear ownership, and audit it on a schedule rather than only when a submission error forces the issue.
Publisher Perspective: Data That Actually Helps Compliance Teams
Most product catalogs treat model numbers and lot data as an afterthought. That’s backwards. Queenssurgical lists model numbers, packaging configuration, and labeling details on product pages specifically because procurement and regulatory teams need that information at the point of purchase, not buried in a separate document requested after the fact.
— QB
Source Compliant Disposables and Labeling-Ready Supplies
UDI compliance depends on clean data at every link in the supply chain, and that includes the vendor you buy consumables from. Queenssurgical stocks masks, gowns, and disposable supplies with clear model and packaging information listed right on the product page, so procurement teams aren’t left guessing what they’re actually ordering for a compliance-sensitive purchase.
Whether you’re restocking a clinic’s mask supply or sourcing lab uniforms for a facility that tracks every consumable by lot, Queenssurgical’s medical face masks and disposable laboratory uniforms come with the packaging and product detail your team needs for internal recordkeeping. Browse the full catalog at Queenssurgical and place an order directly from the product page that matches your facility’s specification.
Recommended
Comments