GUDID Submission Is More Than Entering a UDI

A GUDID submission can look like a data-entry task, but the FDA database is a public reference record used in supply chains, electronic health records, registries, and regulatory review. Accuracy therefore depends on decisions made before anyone logs into the portal and on controls that continue after publication.

Start With the Identifiers, Not the Portal

Before preparing a record, the labeler should select an FDA-accredited issuing agency and obtain the identifiers needed for the product. The two systems most commonly encountered are GS1 and HIBCC. GS1 uses a company prefix to construct Global Trade Item Numbers, while HIBCC uses a Labeler Identification Code to construct HIBC device identifiers.

A manufacturer ordinarily selects one system for its primary device identifier; it does not need both GS1 and HIBCC. It does, however, need the appropriate GS1 or HIBCC identifiers before completing the related GUDID records.

A separate Global Medical Device Nomenclature code is also required for each device version or model. The GMDN code describes the common device type; it is not a barcode or substitute for a GS1 or HIBCC identifier. Both the issuing-agency identifiers and the GMDN code should be in place before the manufacturer attempts to register its DIs in GUDID.

Build a Controlled Source-Data Record

GUDID fields draw from approved labeling, FDA registration and listing, premarket submissions, engineering specifications, quality records, packaging configurations, and issuing-agency data.

A controlled source-data file should identify each approved value, its authoritative source, and the person responsible for confirming it. Copying from a website, distributor catalog, old submission, or draft label can create inconsistencies that later become publicly visible.

Map the Packaging Hierarchy

The primary device identifier generally corresponds to the lowest package level required to bear the full UDI. Higher packaging configurations may require separate package identifiers and quantities.

Kits, multipacks, unit-of-use identifiers, direct-mark identifiers, and alternate identifiers require additional analysis. A valid identifier can still be linked to the wrong packaging level if the hierarchy is not mapped first.

Separate Data Entry From Review

GUDID provides Coordinator and Labeler Data Entry roles, but system validation does not establish that the information is substantively correct. An independent reviewer should compare the completed record against the final label, issuing-agency records, FDA information, and approved source data.

Published records receive a seven-calendar-day editing grace period before release through AccessGUDID. Reviewer availability should therefore be confirmed before publication. After that period, editing is more restricted.

A Coordinator may unlock a record for error correction, but unlocking cannot replace assigning a new DI when a changed data element requires one, and prior versions remain in the public history.

Treat GUDID as Continuing Change Control

Product, labeling, packaging, regulatory, or nomenclature changes should be assessed to determine whether the existing record must be updated or a new DI and record are required. GMDN assignments do not update automatically.

GUDID should therefore be included in formal product-change review rather than treated as a one-time launch activity.

Coordinate GUDID Within the U.S. Operating Structure

Through the MDD Options Hybrid model, manufacturers can place GUDID governance within the same U.S. operating structure used for FDA registration, listing, importation, complaint handling, and distribution.

MDD Options can coordinate GS1 or HIBCC and GMDN readiness, develop the source-data record, map packaging, submit and independently review DI records, and maintain change control without requiring a separate U.S. regulatory-administration function.