GUDIDGlobal Unique Device Identification Database

The Global Unique Device Identification Database (GUDID) is FDA’s publicly searchable catalog of device identifiers submitted under the U.S. Unique Device Identification (UDI) regulation. It centralizes the static identifier and standardized attributes that define a commercially distributed medical device in the United States. Hospitals, payers, EHR systems, distributors, investigators, and FDA program areas rely on this dataset to unambiguously reference devices, align master data, and power safety and quality analytics.

GUDID is mandated by 21 CFR 830 Subpart E, and its content is intrinsically linked to UDI labeling requirements in 21 CFR 801. A device’s UDI appears on the label and automatic identification carrier, where the device identifier (UDI-DI) is the fixed key and the production identifier (UDI-PI) conveys variable elements such as lot, serial number, and expiration date. GUDID stores the DI and device attributes. It does not store the PI.

In practice, GUDID acts as a master reference for downstream processes. Supply chain systems use it to validate catalog numbers and packaging hierarchies. Health IT queries it to display device brands, models, and MRI compatibility. FDA cross-references it during recalls and adverse event evaluations. When managed with discipline, the GUDID record becomes the single source of truth for device identity, reducing mislabeling risk and supporting effective traceability and recall management.

Because GUDID is public, errors propagate widely and quickly. Labelers must treat DI master data as a controlled record, integrate change control with product lifecycle decisions, and align submissions to issuing agency rules from GS1, HIBCC, or ICCBBA. Doing so ensures the UDI printed on labels precisely resolves to the same device identity in the database.

The legal basis for GUDID resides in 21 CFR 830, which establishes UDI system requirements, issuing agency recognition, and database obligations. 21 CFR 830 Subpart E requires labelers to submit device identifier records to the database. Complementary provisions in 21 CFR 801 set the labeling, formatting, and carrier presentation rules for the UDI on device labels and packaging, including direct marking requirements for certain reprocessed or reusable devices.

A “labeler” under FDA’s UDI regulation is the entity that causes a label to be applied to a device, and that determines the UDI on that label. Often this is the legal manufacturer, but it can also be an own-label distributor when they are responsible for the brand and label content. GUDID obligations apply to most Class I, II, and III devices, including in vitro diagnostics, subject to phase-in timelines and clearly described exceptions such as certain investigational devices, custom devices, and some Class I exemptions. Applicability must be verified against product-specific rules and any enforcement discretion notices.

Because GUDID content is integral to postmarket oversight, it interfaces with other regulations. For example, UDI information is leveraged during Medical Device Reporting under 21 CFR 803, during corrections and removals, and during inspectional activities under 21 CFR 820 and the updated FDA QMSR. Submissions, approvals, or clearances under premarket programs do not automatically populate GUDID; labelers must submit separately, and should align GUDID attributes with public premarket records such as the FDA 510(k) database when applicable.

For combination products, coordination with 21 CFR Part 4 is necessary to determine UDI labeling scope and the appropriate entity responsible for GUDID submissions. Labelers distributing private-labeled SKUs must ensure each brand-specific DI is correctly established and linked to the shared physical device configuration.

GUDID records are structured around the primary device identifier, with optional secondary DIs and linked package DIs to represent packaging hierarchy. The record includes standardized attributes such as brand or trade name, version or model, catalog number, device description, size, MRI safety status, sterilization method, whether it is single-use or contains latex, whether it is a kit, direct marking applicability, and whether it is an implantable or life-sustaining device. Many attributes are coded or controlled vocabulary fields to enable interoperable search and analytics.

Submission occurs either through FDA’s web interface for GUDID or via machine-to-machine transmission using Health Level Seven Structured Product Labeling (HL7 SPL) through the Electronic Submissions Gateway. Regardless of path, the labeler must ensure account management, roles, and data stewardship are defined, and that validations pass before records are published. AccessGUDID makes approved records publicly visible, which means any defect rapidly becomes a downstream problem for distributors, providers, and HTA systems.

It is critical to understand that the production identifier elements do not enter GUDID. Those elements live on the physical label, in device history records, and in enterprise systems such as manufacturing execution, distribution, and provider IT. GUDID presents the static device identity, while UDI-DI vs UDI-PI roles are preserved across labeling, scanning, and data exchange contexts.

• Primary DI anchors the device record, with optional secondary DIs for equivalent identifiers.
• Package DIs represent each level of packaging, tied to the base device DI.
• Coded attributes capture safety and use characteristics, enabling consistent interpretation by health IT.
• Web portal or HL7 SPL via ESG are the approved submission channels, each with pre-validation and error feedback.

The device identifier in GUDID is stable by design. Certain changes to a device’s characteristics trigger the need for a new DI, while other changes can be handled by updating attributes on the existing record. Labelers must operationalize clear rules to determine when to retire a DI and create a new one versus when to amend the same record, and they must synchronize that decision with labeling updates and distribution plans to avoid market confusion.

Typical DI change triggers include modifications that impact labeled use, safety classification, sterility status, MRI safety, or other fundamental characteristics relied upon by clinical or supply chain users. Cosmetic changes or clarifications may be handled as record updates. When a new DI is required, associated package DIs and catalog cross-references must be rebuilt to maintain packaging integrity. Records can be published, corrected, or inactivated in GUDID, and the public view shows the effective status, which helps trading partners understand which DI remains valid.

Good practice is to integrate DI governance into design control and release processes so that any engineering change notice triggers an automatic check for DI impact. Align DI timing with market release to ensure the public record is live before distribution. For regulated combinations or family variants, ensure that any kit configurations or configurable device options are modeled correctly to avoid proliferating near-duplicate DIs that confuse end users.

Because GUDID content is publicly referenced in complaints, vigilance, and recalls, version control for submitted attributes must be auditable. Maintaining a documented rationale for each DI issuance and each inactivation decision supports inspection readiness under 21 CFR Part 11 for electronic records in your internal systems and aligns with quality system expectations under 21 CFR 820.

Effective GUDID compliance depends on disciplined master data governance. Start by designating a DI owner, a submission specialist, and a cross-functional review team spanning regulatory, labeling, supply chain, and quality. Define the source of truth for each attribute, the approved issuing agency format (GS1, HIBCC, or ICCBBA), and the mapping between internal product codes and public identifiers. Catalog numbers, brand names, and version or model fields should be standardized to match what appears on the label.

Establish authoring templates that pre-validate attributes before submission. Use controlled vocabularies and code lists, and ensure that safety and special use characteristics are reviewed by subject matter experts. For packaging, build out the full hierarchy from each base device DI through every package DI level so purchasing and EHR barcode scanning can correctly interpret inner and outer levels. Keep the AccessGUDID public view as a checkpoint in your release checklist to confirm that the record is published as intended before shipping.

Synchronize GUDID updates with complaints, field actions, and recall classification activities so stakeholders can find the correct identity when researching an issue. Validate that your enterprise applications, including EBMR/eDHR, label design, and traceability, use the same DI reference. Use role-based access controls and audit trails in your quality management system to document who changed what and when.

Finally, treat external stakeholders as partners in data accuracy. Distributors and hospital systems can quickly surface inconsistencies. Monitoring their feedback and promptly correcting your GUDID records prevents broader data pollution. Consider publishing a master data change notice to key customers when a DI is replaced or inactivated so their systems update cleanly.

Most GUDID issues stem from misaligned master data, improper modeling of packaging, or misunderstanding the boundary between DI and PI. Because the database is public, small inconsistencies can cascade into procurement failures, inventory mismatches, and clinical scanning errors. Proactive controls prevent rework, customer complaints, and enforcement attention.

Another frequent source of error is failing to determine who the labeler is for private-label or contract-manufactured devices. If the brand owner is the labeler, they submit. If the contract manufacturer is the labeler, they submit. When the wrong party holds the account, corrections and inactivations become cumbersome and slow, complicating postmarket responses and post-market surveillance analytics.

• Uploading PI to GUDID: PI stays on the physical label and enterprise records, not in GUDID.
• Missing or incorrect package DI hierarchy: Build each level consistently against the base device DI.
• Inconsistent brand, model, or catalog numbers: Align text with the physical label and approved artwork.
• Using the wrong issuing agency rules: Ensure DI format matches GS1, HIBCC, or ICCBBA specifications.
• Delaying publication until after distribution: Publish before shipping so trading partners can resolve the DI.
• Creating a new DI for cosmetic changes: Reserve new DIs for changes that affect intended use or safety-relevant characteristics.

Avoid treating GUDID as a one-time project. The right approach is a controlled process embedded in design change, labeling review, and market release. Calibrate triggers that require a new DI, and maintain a clean mapping between legacy catalog numbers and current DIs to avoid stranded identifiers in the field.

GUDID is the U.S. database within a broader global trend toward UDI-enabled device surveillance and supply chain transparency. In the European Union, the Medical Device Regulation establishes a UDI system and the EUDAMED UDI/Devices module will play a role analogous to GUDID once fully operational. Convergence around issuing agencies such as GS1 and HIBCC allows manufacturers to reuse core identifiers across jurisdictions, while still respecting regional data models and submission portals.

Regulators in the United Kingdom, Canada, and Australia are advancing UDI frameworks with features familiar to U.S. stakeholders. While terminology and milestones differ, the foundational pattern remains: labelers must place a UDI on the label and packaging, assign a stable device identifier, and publish a public set of device attributes. Planning UDI as a multi-market capability reduces rework and harmonizes your label content and master data.

Within the U.S., GUDID underpins postmarket processes. Adverse event reporting under 21 CFR 803 benefits when device identities are unambiguous. Quality system documentation under 21 CFR 820 and the modernized FDA QMSR should treat DI governance as a controlled process with defined responsibilities and records. Premarket pathways such as the FDA 510(k) database provide public references that help align model names and indications with GUDID entries.

• EU MDR EUDAMED: parallel UDI database with EU-specific attributes and submission mechanics.
• UK and Canada: national UDI initiatives building on global issuing agency structures.
• Australia: TGA-led UDI program aligning with international standards.
• Global issuing agencies: GS1, HIBCC, and ICCBBA enable cross-border identifier reuse when compliant with local rules.

High-quality GUDID data depends on robust pre-submission validation and disciplined change management. Implement field-level validations that mirror FDA’s portal rules, ensure controlled vocabularies are used, and verify that free-text entries match approved labeling without abbreviations that could impede search. When using HL7 SPL, validate the XML against schema and business rules before transmission to reduce rejections and delay.

Your quality management system should define documented roles for authoring, independent review, and final approval of each DI record. Maintain an auditable trail showing the rationale for attribute selections, the evidence source, and the approver’s signoff. In electronic systems, apply controls consistent with 21 CFR Part 11 to electronic records and signatures. Train staff not only on how to submit, but also on the regulatory intent behind each data element so they can correctly classify edge cases.

During inspections, FDA may compare your labels, device master record, and GUDID entries. Discrepancies can trigger broader questions about design control and labeling control. Build an internal dashboard that monitors GUDID publication status, upcoming changes that may trigger new DIs, and records that require inactivation. Link this to complaint trending and post-market surveillance so that any safety signal prompts a quick data verification step.

Finally, coordinate GUDID governance with release processes for new or modified devices. Align go-live dates, carton production, and distribution releases so that AccessGUDID displays the correct device identity by the time any unit leaves your warehouse. This alignment prevents customer confusion and reduces the risk of field corrections solely due to data mismatches.

FDA implemented UDI and GUDID through a phased timeline tied to device class and special categories such as implantable, life-supporting, and reusable devices requiring direct marking. Enforcement discretion has adjusted specific dates for certain Class I products and for direct marking, but the core expectation is consistent: labelers must ensure compliant UDI labeling and a published GUDID record before U.S. commercial distribution. Always confirm current timing and scope on FDA’s UDI pages and in any Federal Register notices announcing enforcement changes.

When seeking exemptions, partial exemptions, or alternative labeling approaches, labelers should document the regulatory basis and maintain correspondence or decisions. Some devices are exempt from bearing a UDI or from GUDID submission even if a UDI appears on the label. Clarify applicability for investigational devices, custom devices, and certain Class I GMP-exempt categories. For reusable devices requiring direct marking, verify whether physical constraints or patient safety considerations justify exceptions or alternative placements.

GUDID compliance interacts with broader enforcement. Inaccurate or missing records can complicate adverse event reporting, recalls, and import screening. Quality system deficiencies in labeling or master data control may draw inspectional observations. Maintaining a clean, current, and complete set of DI records is a practical way to demonstrate control to investigators and to trading partners that rely on your master data.

Implementing GUDID well is a cross-functional discipline that blends product master data, labeling control, submission mechanics, and ongoing lifecycle governance. V5 Ultimate provides a configurable backbone that centralizes device master data, enforces review and approval workflows, and keeps your public record aligned with your physical labels and product changes. It connects engineering release, regulatory review, and packaging operations so that each change is evaluated for DI impact before it reaches customers.

Within V5, device attributes required for the DI record are stored as controlled fields tied to approved artwork, bill of materials, and packaging hierarchies. Built-in validations surface missing or nonconforming entries before submission. Integrations with label design, EBMR/eDHR, and traceability ensure that the DI on the label matches the DI in your master data and that production history links correctly to the UDI-PI captured at manufacture or distribution.

For data stewardship, role-based access, audit trails, and electronic approvals support a compliant process consistent with 21 CFR Part 11. Optional connectors and exports can feed machine-readable payloads to your submission pipeline. Dashboards and analytics alert teams to pending inactivations, open corrections, or packaging changes that may require a new DI. The result is a sustained capability, not a one-time project, that scales across portfolios and geographies.

Finally, when postmarket events arise, V5’s controlled records accelerate the response. Complaint handlers and recalls can immediately locate the correct DI, validate packaging DIs, and confirm that AccessGUDID reflects current status. That alignment reduces customer confusion and helps investigators reconcile evidence quickly during field actions.