FDA GUDID submission services

We prepare, validate, and submit your device records to the FDA's Global Unique Device Identification Database — and work the correction cycles until every record shows Published.

Why GUDID submissions stall

From a distance, GUDID looks like a form. Up close it is up to 65 data elements per device record, each with its own format rules, controlled vocabularies, and cross-field validation logic. Multiply that by a catalogue of several hundred SKUs and the reason first-time programmes take months stops being mysterious.

In our experience three patterns account for most rejections:

• Vocabulary mismatches. Free text entered where GUDID expects a controlled term. Size units, sterilisation methods, and MRI safety status are the usual offenders.
• Identifier inconsistencies. Package DI hierarchies that do not reconcile with the primary DI, or GTIN check digits that fail validation before the record is even assessed.
• Cross-field logic conflicts. Combinations the database refuses — a sterility claim that contradicts the sterilisation fields, for example, or a single-use flag on a device also marked as reprocessed.

None of these are hard problems individually. They are expensive because they surface one at a time, late, after the submission has already been attempted.

What we do

Data preparation and validation

We gather the required attributes per device identifier and validate them against FDA's format rules before submission rather than discovering problems in rejection notices. That includes FDA product codes, GMDN terms, clinically relevant size with correct unit vocabularies, sterility and sterilisation method, MRI safety status, latex content, single-use flags, and labeler DUNS.

HL7 SPL submission through the FDA gateway

Records travel to GUDID as HL7 SPL XML documents through the FDA Electronic Submissions Gateway, or can be entered record-by-record in the GUDID web interface. Small catalogues can survive manual entry. High-SKU catalogues cannot — the SPL route plus validation tooling is the only realistic path, and it is the one we run for clients.

Correction cycles to publication

A submitted record is not a compliant record. We work the validation errors and correction cycles through to publication, so the deliverable is accepted data rather than an attempted filing.

Who is responsible

FDA places responsibility for GUDID data on the device labeler — the entity named on the device label. Not your distributor, not your notified body, not your consultant. We do the work; the accountability remains with you, which is exactly why the data quality matters.

Compliance dates in the United States

Device class	Compliance date
Class III	September 2014
Class II	September 2016
Class I	September 2018
Reusable Class I direct marking	December 2022

The US phase-in is complete. There is no upcoming deadline to prepare for — you are either compliant today or you are exposed today. Class I devices and unclassified devices were required to submit GUDID data by 8 December 2022.

Inspection risk has changed

FDA's compliance programme CP 7382.850 applies a Total Product Life Cycle approach: inspectors trace UDI data from design and manufacturing through post-market surveillance. Two consequences follow. GUDID data must match your actual product labelling, and inconsistencies can support a misbranded or adulterated device charge. And GUDID updates are due within 30 days of any change to device information.

That second point is what turns UDI from a project into a process. A submission is finished; a catalogue is never finished. Change control that flags UDI-triggering changes before they ship is the difference between a clean inspection and a remediation programme.

Related

Many clients arrive with a GUDID problem and leave with a global programme. See EUDAMED UDI consulting if Europe is next, or UDI labeling compliance if the label itself needs review. Our free UDI decoder validates GS1 strings and GTIN check digits in your browser.