top of page

FDA 483 Citations for Unique Device Identification Under 21 CFR 801.20 and Part 830

23 hours ago
5 min read

Unique device identification looks like a labeling detail, but FDA cites it often. In fiscal year 2025, investigators recorded these observations on system-generated Form FDA 483s:

  • "The labels of the medical device(s) do not bear a unique device identifier (UDI) that meet the requirements of 801 Subpart B and 21 CFR 830," 801.20(a), 54 times

  • "The information required by the Global Unique Device Identification Database for each medical device version or model required to bear a unique device identifier (UDI) was not provided," 830.300(a), 47 times

  • "The correct unique device identifier (UDI) information ... was not provided to the FDA via the Global Unique Device Identification Database (GUDID)," 830.310(b), 11 times

UDI is how FDA, hospitals and distributors trace a device through recalls, adverse event reports and supply chains. A missing or wrong UDI weakens all of them, which is why UDI observations are now routine at inspections.

What the citations mean

Examples written after "Specifically" usually describe:

  • Device labels or packages with no UDI, or a UDI without the required plain-text or machine-readable form

  • A UDI missing from one packaging level, such as the shipping carton or the unit of use

  • No GUDID record for a model that carries a UDI on its label

  • GUDID records with the wrong brand name, model number, sterility status, latex statement, MR safety status or premarket submission number

  • A label change that created a new version or model without a new device identifier

  • Devices intended to be reprocessed and reused with no permanent direct mark

What the UDI rules require

The UDI requirements are in 21 CFR Part 801 Subpart B (labeling) and 21 CFR Part 830 (the UDI system and GUDID). They were not changed by the Quality Management System Regulation.

Labeling (Part 801 Subpart B). Under 801.20, the label of every medical device and every device package must bear a UDI, unless an exception or alternative applies under 801.30 or another provision. Under 801.40, the UDI must appear in both plain-text form and a form that uses automatic identification and data capture (AIDC) technology, such as a barcode. Section 801.45 requires a permanent direct mark on devices intended to be used more than once and reprocessed before each use, and 801.50 covers stand-alone software.

The UDI system (Part 830). The UDI must be issued under a system operated by an FDA-accredited issuing agency (830.20). The device identifier identifies the labeler and the specific version or model, and the production identifier carries the lot or batch, serial number, expiration date or manufacturing date that appears on the label. Under 830.50, a new device identifier is required when a change results in a new version or model, or a new device package.

GUDID (830.300 to 830.360). The labeler must submit the information listed in 830.310 to GUDID for each version or model required to bear a UDI, and must keep it current. Required data includes the device identifier, brand name, version or model, size where applicable, sterility, natural rubber latex, MR safety, the type of production identifiers on the label, the premarket submission number, the GMDN term or code, and the quantity in the package.

QMSR. Labeling controls remain in 21 CFR 820.45 under QMSR, so your labeling inspection must check that the correct UDI is printed before labeling is released.

How to respond to the 483

FDA generally considers responses received within 15 business days of the close of the inspection before deciding on further action.

Inventory every version, model and package level

List every device version or model you label, and every package level for each. For each one, record whether it requires a UDI, the device identifier, whether the label carries it in plain text and AIDC form, and whether the GUDID record exists and is correct.

Correct labels and GUDID records

Submit missing GUDID records and correct wrong ones. Revise labels that lack UDIs and state when compliant labels will be in use. Decide what to do with inventory and devices already distributed, and record the rationale.

Fix the process

  • A UDI procedure that assigns responsibility for issuing device identifiers, labeling and GUDID

  • A change control step that asks whether a label, packaging or design change needs a new device identifier and a GUDID update

  • A label review checklist that verifies the UDI, the barcode grade and the data on the label against GUDID

  • A periodic reconciliation between your product list and GUDID

What a compliant UDI procedure contains

  • Scope, exceptions and responsibilities

  • Issuing agency and how device identifiers are assigned

  • Label content and format, including plain-text and AIDC forms

  • Direct marking for reusable devices that are reprocessed

  • GUDID data entry, review and updates

  • Triggers for a new device identifier

  • Label verification and barcode quality checks

  • Records

Common mistakes in UDI responses

  • Fixing the models named in the observation but not checking the rest of the product line

  • Updating labels without updating GUDID, or the reverse

  • Forgetting shipping and higher-level packages

  • Treating UDI as a regulatory affairs task only, outside labeling controls and change control

  • Assuming a class I exemption applies without documenting it

Example: how one response section might read

This illustrates structure only; your response must describe your own facts.

Observation 2: The labels of the medical devices do not bear a UDI. Specifically, the 10-unit shipping carton for catheter model 2200 does not bear a UDI.

Response:

  • Correction: A device identifier was assigned to the 10-unit package and the GUDID record was updated on a stated date. Revised carton labels with the UDI in plain text and GS1-128 barcode form were released on a stated date.

  • Extended review: All 46 models and 112 package configurations were reviewed against label artwork and GUDID. Seven corrections were made by a stated date.

  • Root cause: Package configurations were added by operations without a regulatory review of UDI needs.

  • Corrective action: A UDI procedure was issued, and change control now requires a UDI and GUDID assessment for every labeling or packaging change.

  • Verification: Regulatory affairs will reconcile the product list against GUDID every six months.

Frequently asked questions

Does every package level need a UDI?

Generally, yes. Each device package must bear a UDI unless an exception applies. Shipping containers are excepted, but higher-level packages that are not shipping containers usually need one.

Did QMSR change UDI requirements?

No. Parts 801 and 830 were not changed by QMSR. QMSR labeling controls in 820.45 still require you to inspect labels for accuracy, including the UDI.

When do we need a new device identifier?

When a change results in a new version or model, or a new device package, under 21 CFR 830.50.

How A.P. Lyon documents help

A.P. Lyon's Unique Device Identification Procedure covers device identifier assignment, label content, direct marking and GUDID maintenance. It works with the ISO 13485 Label Review and Approval Procedure, and both are in the Medical Device Labeling Procedure Bundle.

Documents are editable Word and Excel files and must be adapted to your devices and organization. GUDID submissions and labeling remain the labeler's responsibility.

Next steps

  • Inventory every model and package level against labels and GUDID

  • Correct labels and GUDID records, and decide on existing inventory

  • Add UDI checks to change control and label review

  • Respond within 15 business days with dates for each action

To build a complete set of procedures at a volume discount, use Build Your QMS. For help with a 483 response, see A.P. Lyon consulting services.

Not sure where your quality system stands? Take the free QMS gap check: about 20 questions, an instant report of your gaps by clause, and the procedures that close each one.

Comments


bottom of page