UDI and GUDID Requirements: A Guide for Medical Device Makers

2026-10-09 · Caduvo Team

Learn how to structure your Unique Device Identifier (UDI), navigate FDA-accredited issuing agencies, submit to GUDID, and manage compliance across hospital supply chains.

A medical device label without a compliant barcode is an unsellable product. Under the FDA's Unique Device Identification System regulations in 21 CFR Part 801 Subpart B and 21 CFR Part 830, commercial distribution of medical devices in the United States requires physical label compliance as well as master data entry into federal systems. If you fail to assign an identifier correctly or misconfigure your database record, hospital inventory systems reject your shipments, enterprise resource planning (ERP) systems fail to recognize your catalog numbers, and commercial intake stalls.

Understanding the mechanics of the unique device identifier (UDI) is essential for regulatory affairs, quality assurance, and supply chain teams. Getting compliant means knowing how identifiers are generated, how they split into static and dynamic components, what data must flow to the FDA's database, and how hospital supply chain teams use those records.

Deconstructing the UDI: Device Identifier (DI) vs. Production Identifier (PI)

A compliant unique device identifier consists of two distinct components: a fixed Device Identifier (DI) and a variable Production Identifier (PI).

+-------------------------------------------------------------+
|                 Unique Device Identifier (UDI)              |
+------------------------------+------------------------------+
|    Device Identifier (DI)    |   Production Identifier (PI) |
|      [Mandatory, Fixed]      |   [Conditional, Variable]    |
|   - Identifies labeler       |   - Lot or batch number      |
|   - Model / catalog version  |   - Serial number            |
|   - Primary key for GUDID    |   - Expiration date          |
|                              |   - Manufacturing date       |
|                              |   - Distinct HCT/P code      |
+------------------------------+------------------------------+

The Device Identifier is the mandatory, fixed portion of the code. As defined in 21 CFR Part 801 Subpart B, it identifies the labeler (the manufacturer, specification developer, single-use device reprocessor, convenience kit assembler, repackager, or relabeler) and the specific version or model of the device. The DI serves as the primary key to access device information in federal repositories.

The Production Identifier is conditional and tracks variable production data. Under FDA regulations, the PI identifies one or more of the following tracking attributes when they appear on the device label:

The lot or batch number within which a device was manufactured
The serial number of a specific device
The expiration date of a specific device
The date a specific device was manufactured
The distinct identification code required by 21 CFR § 1271.290(c) for a human cell, tissue, or cellular and tissue-based product (HCT/P) regulated as a device

The device labeler must provide the UDI on labels and packages in two forms: easily readable plain-text and machine-readable Automatic Identification and Data Capture (AIDC) technology. AIDC includes any technology, such as linear barcodes or 2D DataMatrix codes, that conveys the UDI or the DI in a form that can be entered into an electronic patient record or computer system via an automated process. When dates appear on device labels and packages, labelers must present them in a standard international format: YYYY-MM-DD (e.g., 2026-05-15).

Direct marking introduces an additional mandate for reusable equipment. If a device is intended for more than one use and must be reprocessed before each use, the labeler must also mark the UDI directly on the device under 21 CFR § 801.45.

Accredited Issuing Agencies and Compliance Deadlines

Device manufacturers cannot generate their own arbitrary numbering formats for a UDI. Federal regulations require device identifiers to be assigned under an FDA-accredited issuing agency's system. Labelers must work directly with one of the accredited issuing agencies to assign and maintain their UDIs:

GS1
HIBCC (Health Industry Business Communications Council)
ICCBBA

Under 21 CFR § 830.310(a)(3), labelers must submit the name of each issuing agency whose system is used to assign their UDIs when providing device information to the FDA. Labelers must evaluate how their target hospital customers, distributors, and clinical users process barcoded inventory to select the agency system that best matches their operational environment.

Regulatory enforcement deadlines for udi requirements followed a phased rollout based on medical device classification. For Class I and unclassified devices—excluding implantable, life-supporting, or life-sustaining (I/LS/LS) devices—the FDA published a compliance policy establishing a compliance date of December 8, 2022, for Global Unique Device Identification Database submission requirements. Implantable, life-supporting, and life-sustaining devices, including Class I I/LS/LS devices, were required to comply with GUDID submission requirements prior to that date.

What Goes into GUDID: Submission Workflows and Data Elements

The Global Unique Device Identification Database (GUDID) serves as the FDA's central public catalog for medical devices bearing a UDI. Administered under 21 CFR Part 830 Subpart E, GUDID provides structured product information to the public, healthcare systems, and clinical researchers.

A fundamental design rule governs the database: GUDID contains only the Device Identifier (DI). It never stores individual Production Identifiers such as actual serial numbers, batch numbers, or production dates. Instead, GUDID records contain PI flags—binary indicators showing which production attributes appear on the physical device label.

Under 21 CFR § 830.310, data elements required for each DI record include:

The name of the labeler, along with contact details for the designated device identification contact
The name of each issuing agency whose system is used to assign the labeler's UDIs
The device identifier portion of the UDI assigned to the version or model
Any previously assigned device identifier if reporting a substitution
Direct mark statements (whether the direct mark DI is identical to the primary DI or assigned separately under 21 CFR § 801.45)
Proprietary, trade, or brand name as it appears on the device label
Any version, model number, or similar reference appearing on the label
A statement indicating whether the device is labeled as sterile
Premarket submission numbers (e.g., what is a 510(k) clearance or PMA approval numbers, where applicable)
Global Medical Device Nomenclature (GMDN) code and term
MR safety status

Per the FDA's guidance update on the Global Unique Device Identification Database, the FDA is removing FDA Preferred Term (PT) codes from GUDID. Because GMDN codes are available to users without fee barriers, labelers must use GMDN codes directly in their records rather than legacy FDA PT codes.

Device labelers submit their master data using two pathways provided by the FDA data submission system:

Manual Entry via the GUDID Web Application: Labelers log in to an online portal to create, draft, and submit individual DI records one at a time. This option is best suited for labelers that have a small number of records to submit.
HL7 SPL Submission via the FDA Electronic Submissions Gateway (ESG): Labelers transmit device data as XML files adhering to Health Level 7 (HL7) Structured Product Labeling (SPL) standards. This option allows bulk upload of multiple DI records simultaneously.

Labelers must prepare operational details before submitting. According to FDA GUDID onboarding guidance, labelers must identify appropriate Dun and Bradstreet (DUNS) numbers. Obtaining a free DUNS number from D&B can take up to 30 business days. Companies submitting via the ESG must also set up an ESG account and complete HL7 SPL file testing before the FDA permits live transmissions.

Searching AccessGUDID and How Supply Chains Use UDIs

Once submitted and validated, device information enters the public domain through AccessGUDID. Health systems, payers, and commercial teams search AccessGUDID using primary device identifiers, proprietary names, company names, premarket submission numbers, or GMDN terms.

+-------------------------------------------------------------------------+
|                            AccessGUDID Search                           |
|           (Query: DI, Brand Name, Premarket Number, or GMDN)            |
+------------------------------------+------------------------------------+
                                     |
                                     v
+------------------------------------+------------------------------------+
|      Hospital & Clinical Use       |    Market Access & Intelligence    |
+------------------------------------+------------------------------------+
| - Barcode scanning at intake       | - Link DI to premarket clearance   |
| - AIDC entry into patient records  | - Audit competing product catalogs |
| - Traceability in product recalls  | - Map GUDID data to FDA product    |
| - Verification for billable items  |   codes in Caduvo                  |
+------------------------------------+------------------------------------+

Hospitals and health care systems rely on this data for everyday workflows:

Point-of-Care Data Capture: Scanning the machine-readable AIDC barcode at the bedside automatically populates device identification into electronic patient records without manual transcription errors.
Inventory Management and Traceability: Scanning the DI at receiving allows hospital inventory systems to match deliveries directly against purchase orders and catalog records.
Recall Execution: When safety alerts occur, supply chain teams use the DI and production identifiers (such as lot or serial numbers) to pinpoint affected stock on hospital shelves, avoiding extensive physical reviews of non-affected lots.
Reimbursement and Item Master Maintenance: Hospital billing departments match scanned DIs against internal charge master items to verify procedure coding before submitting claims to commercial insurers.

Beyond supply chain mechanics, UDI data provides regulatory and market-access teams with strategic competitive visibility. Because each GUDID entry links back to premarket submission numbers, teams can identify competing manufacturers and cross-reference them in the FDA product code database. Regulatory intelligence platforms like Caduvo link GUDID device records to corresponding FDA product codes, enabling teams to benchmark competitors, monitor predicate devices, and identify changes across related product classifications.

When presenting new technology to a hospital value analysis committee, having complete GUDID records ensures that hospital procurement staff can ingest your device identifiers into their inventory management systems without delay.

Actionable Takeaways for Regulatory and Supply Chain Teams

Obtain and verify DUNS numbers early: If your company or manufacturing facility needs a new DUNS number, request it immediately through Dun & Bradstreet, as standard processing can take up to 30 business days.
Select the appropriate issuing agency: Work with an FDA-accredited agency—GS1, HIBCC, or ICCBBA—whose formatting system aligns with the commercial purchasing systems used by your primary hospital and distributor accounts.
Assign separate DIs for each version or model: Ensure every distinct version, model, or packaging level required to bear a UDI receives its own unique DI before you initiate commercial shipments.
Verify physical label formatting: Confirm that all physical product packaging presents the UDI in both plain-text and machine-readable AIDC format, and format every printed date strictly as YYYY-MM-DD.
Adopt GMDN codes for GUDID updates: Discontinue using legacy FDA Preferred Term codes in your master data systems and transition entirely to active GMDN codes to remain compliant with current FDA GUDID guidance.
Determine your submission method based on catalog volume: Use the manual GUDID web application if you manage a small volume of records, or configure HL7 SPL transmissions through the FDA Electronic Submissions Gateway if you manage large product lines requiring bulk upload.

Sources

General information, not regulatory, legal or reimbursement advice. Company and product names belong to their owners; a mention does not imply affiliation or endorsement. Report an error. Data and corrections policy.