Medical Device Labeling & UDI System: The Complete Regulatory Guide

Master FDA and EU MDR medical device labeling requirements, UDI system implementation, GUDID database submissions, and global UDI harmonization — practical guide with compliance checklists and common pitfalls.

What Is Medical Device Labeling?

Labeling is one of those regulatory topics that sounds simple until you start reading the actual regulations. Most people think "labeling" means the sticker on the box. It does not. In both the FDA and EU MDR frameworks, labeling is a far broader concept, and misunderstanding its scope is one of the most common — and most expensive — compliance mistakes a manufacturer can make.

FDA Definition: Label vs. Labeling

The FDA draws a critical distinction between a label and labeling, and the difference has significant regulatory consequences.

Label — Under Section 201(k) of the Federal Food, Drug, and Cosmetic Act (FD&C Act), a label is "a display of written, printed, or graphic matter upon the immediate container of any article." This is the physical label affixed to the device or its immediate packaging — the sticker, the printing on the box, the information molded into the device housing.
Labeling — Under Section 201(m) of the FD&C Act, labeling includes "all labels and other written, printed, or graphic matter (1) upon any article or any of its containers or wrappers, or (2) accompanying such article." The word "accompanying" has been interpreted extremely broadly by the FDA and courts. It does not require physical proximity. The Supreme Court ruled in Kordel v. United States (1948) that materials can "accompany" a device even if they are shipped separately, as long as they are part of an integrated distribution scheme.

This means labeling includes:

The physical label on the device and all packaging levels
Instructions for use (IFU)
User manuals and quick-start guides
Physician manuals and surgical technique guides
Patient information leaflets
Training materials distributed with the device
Website content that describes the device's intended use
Brochures, catalogs, and promotional materials
Software user interfaces (for SaMD and software-driven devices)

Critical implication: Every piece of written or graphic material that a manufacturer creates about a device is potentially "labeling" under FDA law. This includes your marketing website, your sales brochures, and your trade show materials. If any of these materials make claims that are inconsistent with your cleared or approved intended use, the FDA can take enforcement action — and it regularly does.

EU MDR Labeling Definition

Under the EU Medical Devices Regulation (EU 2017/745), Article 2(12) defines a label as "the written, printed or graphic information appearing on the device itself, or on the packaging of each unit, or on the packaging of multiple devices." Article 2(13) defines instructions for use (IFU) as "the information provided by the manufacturer to inform the user of a device's intended purpose and proper use and of any precautions to be taken."

The EU MDR does not use the term "labeling" as a catch-all the way the FDA does. Instead, it separates the requirements for labels (Annex I, Section 23), instructions for use (Annex I, Section 23), and implant cards (Annex I, Section 23.4). However, the practical effect is similar: manufacturers must ensure that all information provided with, on, or about the device is accurate, consistent, and meets the essential requirements laid down in Annex I, Chapter III.

Label vs. Labeling vs. Promotional Materials

Category	FDA Scope	EU MDR Scope	Regulatory Impact
Physical label	21 CFR 801 — on the device and immediate container	Annex I, Section 23.2 — on the device and each packaging level	Must include manufacturer name, UDI, intended use indicators, lot/serial, expiry
IFU / User manual	Part of "labeling" under Section 201(m)	Annex I, Section 23.4 — separate detailed requirements	Must include adequate directions for use, contraindications, warnings
Promotional materials	FDA treats as "labeling" if they accompany the device or make claims about it	Regulated under Article 7 (claims) — separate from Annex I labeling	Claims must be consistent with intended purpose; no misleading claims
Website content	Can be "labeling" if it describes device use	Article 7 applies; also MDCG guidance on electronic IFU	Increasingly scrutinized; must align with cleared/approved indications

Practical tip: Maintain a single source of truth for your device's intended use statement, indications, contraindications, and warnings. Every piece of labeling and promotional material should reference this source document. When the intended use changes, a formal change control process must update all downstream materials simultaneously.

FDA Labeling Requirements (21 CFR Part 801)

The FDA's labeling requirements for medical devices are found primarily in 21 CFR Part 801, with additional requirements scattered across Part 809 (IVD devices), Part 812 (investigational devices), Part 814 (PMA devices), and Part 820/QMSR (quality system controls for labeling). Understanding these requirements in detail is essential for any manufacturer selling devices in the United States.

General Labeling Provisions (21 CFR 801.1 - 801.5)

Every medical device marketed in the United States must comply with the general labeling requirements:

Manufacturer identification (801.1) — The label must bear the name and place of business of the manufacturer, packer, or distributor. This must include street address, city, state, and ZIP code. A P.O. box alone is not sufficient.
Intended use (801.4) — The intended use of a device may be determined from labeling claims, advertising, oral or written statements by the manufacturer or their representatives, and the circumstances surrounding the device's distribution. This is a broad net — the FDA can infer intended use from how you market the device, not just what you print on the label.
Adequate directions for use (801.5) — All devices must bear labeling with adequate directions for use, which must include: the statements of all conditions, purposes, or uses for which the device is intended; quantity of dose for each use and frequency of administration; directions for use preparation; and any relevant warnings, precautions, and side effects.
Language — Labeling must be in English for devices marketed in the United States. If the device is distributed in Puerto Rico or a territory where another language is predominant, bilingual labeling may be required.

Prescription Device Labeling (21 CFR 801.109)

Prescription devices — those that are not safe for use except under the supervision of a licensed practitioner — have specific labeling requirements:

The label must bear the statement: "Caution: Federal law restricts this device to sale by or on the order of a ___" (physician, dentist, or other designated practitioner).

Prescription device labeling must include:

Indications for use — A clear statement of the medical conditions or purposes for which the device is intended
Contraindications — Conditions under which the device should not be used
Warnings and precautions — Known hazards, limitations, and adverse reaction information
Adverse reactions — Known adverse events associated with use
Directions for use — How to use the device, including preparation, dosing (if applicable), and technique
How supplied — Description of available configurations, sizes, and packaging

Common mistake: Many manufacturers assume that because their device is "prescription only," they do not need to provide the level of detail required by 801.5. This is incorrect. Prescription devices are exempt from the lay-language adequate directions for use requirement, but they must still provide full professional labeling adequate for the practitioner to use the device safely and effectively.

OTC Device Labeling (21 CFR 801.60 - 801.63)

Over-the-counter (OTC) medical devices must be labeled so that the layperson — not a trained clinician — can use the device safely and effectively without professional supervision. This means:

Directions for use must be written in plain language understandable by the average consumer
The principal display panel must include the device name, intended use, and quantity of contents
Warning statements must use specific formatting — the word "Warning" or "Caution" in capital letters followed by the warning text
FDA-mandated specific warnings apply to certain device categories (e.g., thermometers, hearing aids, condoms)

Warning and Caution Requirements

The FDA distinguishes between warnings and cautions:

Warning — Indicates a situation that could result in serious injury or death. Must use the signal word "WARNING."
Caution — Indicates a situation that could result in minor or moderate injury, or damage to the device. Must use the signal word "CAUTION."

For specific device categories, the FDA mandates standardized warning language. For example:

Devices containing latex must include the statement: "Caution: This Product Contains Natural Rubber Latex Which May Cause Allergic Reactions" (21 CFR 801.437)
Devices with MRI safety concerns must include appropriate MRI safety labeling consistent with ASTM F2503

IVD Device Labeling (21 CFR 809.10)

In vitro diagnostic (IVD) devices have their own comprehensive labeling requirements under 21 CFR 809.10, which are more prescriptive than general device labeling. IVD labeling must include:

Proprietary and established names of the device
Intended use, including the specific analyte(s) measured and the type of specimen
Summary and explanation of the test methodology
Chemical, physical, and biological principles of the procedure
Reagent descriptions, including active ingredients and concentrations
Instrument requirements
Specimen collection, handling, and storage requirements
Step-by-step test procedure
Calibration procedures and materials
Quality control procedures and acceptable ranges
Results calculation and interpretation
Limitations of the procedure (interfering substances, etc.)
Expected values (reference ranges) for the intended population
Performance characteristics — accuracy, precision, sensitivity, specificity, and analytical measurement range
Bibliography of relevant references

Why this matters: IVD labeling is one of the most common areas where 510(k) submissions receive Refuse to Accept (RTA) letters or Additional Information (AI) requests. The FDA expects your proposed labeling to be complete and consistent with your performance data at the time of submission. Submitting incomplete or placeholder IVD labeling is a near-guarantee of delays.

Combination Product Labeling

Combination products (drug/device, biologic/device) require labeling that addresses all constituent parts. Under 21 CFR Part 4, the constituent part labeling requirements of the lead Center apply, but the labeling must also meet the requirements for the other constituent part(s). In practice, this means combination product labeling is the most complex of any category and frequently requires coordination between CDER/CBER and CDRH.

Quality System Labeling Controls (QMSR / 21 CFR 820.45)

Labeling content is only half the regulatory equation. The FDA also requires that manufacturers maintain quality system controls over labeling operations. Under the new Quality Management System Regulation (QMSR), which became effective February 2, 2026 — replacing the former Quality System Regulation (QSR) — labeling controls are addressed in 21 CFR 820.45.

The QMSR incorporates ISO 13485:2016 by reference, but the FDA determined that ISO 13485's labeling and packaging controls were not sufficiently detailed. As a result, the FDA added explicit labeling requirements that manufacturers must comply with in addition to the ISO 13485 framework. Key requirements under 820.45 include:

Label integrity inspection — Before release for distribution, each production unit's label must be inspected to verify that the correct label has been applied and that label content is accurate with respect to the device identity, any control numbers (lot/serial), storage and handling instructions, and any expiry dates.
Label storage controls — Labels must be stored in a manner that provides proper identification and prevents mix-ups. Access to labeling storage areas should be limited to authorized personnel.
Obsolete label control — Procedures must ensure that obsolete or superseded labels are destroyed or otherwise prevented from inadvertent use. This is a frequent Form 483 observation — inspectors find outdated labels in storage areas that could potentially be applied to production units.
Label inspection records — Documentation of labeling inspection activities must be maintained as part of the Device History Record (DHR).

Under the former QSR, these requirements were found in 21 CFR 820.120 (Device Labeling) and 820.130 (Device Packaging). Companies that had established processes under 820.120/820.130 should review them against the new 820.45 requirements, as the QMSR reorganizes and in some cases refines these obligations.

Practical tip: The most common labeling-related Form 483 observations involve label mix-ups (wrong label applied to a device), failure to inspect labeling accuracy before release, and inadequate control of obsolete labels. Implement a barcode verification step at the packaging line that confirms the correct label has been applied to the correct device — this single control addresses all three of the most common observations.

Misbranding: The Legal Framework for Labeling Violations

Understanding misbranding is critical because it defines the legal consequences of labeling noncompliance. Under Section 502 of the FD&C Act (21 U.S.C. 352), a device is deemed misbranded if:

Its labeling is false or misleading in any particular
It is in package form and does not bear a label containing the name and place of business of the manufacturer, packer, or distributor, and an accurate statement of the quantity of contents
Any required word, statement, or other information is not prominently and conspicuously displayed on the label as required
It is a device subject to a performance standard and does not bear labeling prescribed in the standard
It does not bear adequate directions for use (unless exempt under 801.109 for prescription devices)
It is dangerous to health when used in the manner prescribed, recommended, or suggested in the labeling
It is a restricted device and its advertising is false or misleading in any particular
It does not bear the required UDI under 21 CFR 801.20

Enforcement mechanisms for misbranding include:

Warning Letters — The most common initial enforcement action. In 2025, 32 CDRH enforcement letters targeted medical device marketing and labeling violations. Five specifically cited UDI/GUDID noncompliance.
Import Alerts — The FDA can issue detention without physical examination (DWPE) orders for imported devices that appear misbranded, effectively blocking the product at the border.
Seizure — The FDA can obtain a court order to seize misbranded devices found in interstate commerce.
Injunction — Courts can issue injunctions prohibiting the continued distribution of misbranded devices.
Civil Monetary Penalties — Under certain provisions, the FDA can seek substantial financial penalties.
Criminal Prosecution — The FD&C Act provides for criminal penalties for introducing or delivering for introduction misbranded devices into interstate commerce. While rare for labeling-only violations, criminal prosecution has been pursued in cases involving intentional fraud or deception.

Critical point: Misbranding is a strict liability offense under the FD&C Act. The government does not need to prove that the manufacturer intended to misbrand the device. If the labeling is false, misleading, or fails to include required information, the device is misbranded regardless of intent. This is why robust labeling review and quality system controls are not optional — they are the primary defense against inadvertent misbranding.

EU MDR Labeling Requirements (Annex I, Chapter III)

The EU MDR (Regulation 2017/745) sets out labeling requirements in Annex I, Chapter III, Sections 23.1 through 23.4. These requirements are significantly more detailed than the previous Medical Devices Directive (MDD 93/42/EEC) and have created substantial compliance work for manufacturers transitioning from the MDD.

General Requirements for Labels (Section 23.2)

The label on the device or its packaging must include the following information, where relevant:

Device name or trade name
Details strictly necessary for the user to identify the device, the contents of the packaging, and the manufacturer
Name, registered trade name, or registered trademark, and address of the manufacturer
If the manufacturer is outside the EU, the name and address of the Authorized Representative
Indication that the device is a medical device (if not obvious)
Device class
Lot number or serial number (preceded by "LOT" or "SN" or equivalent symbol)
UDI carrier (in machine-readable and human-readable format)
Date of manufacture and expiry date (if applicable)
Indication of sterile status and sterilization method (if applicable)
Warnings or precautions (using appropriate symbols)
Single-use indication (if applicable)
If custom-made, the words "custom-made device"
Indication that the device is an investigational device (if applicable)
Storage and handling conditions
Special operating instructions
Any warnings or precautions
Year of CE marking affixation and Notified Body number

Symbols: ISO 15223-1 and EN 980

The EU MDR strongly encourages (and in practice effectively requires) the use of harmonized symbols from ISO 15223-1 (Symbols to be used with information to be supplied by the manufacturer of medical devices) and EN 980 (Symbols for use in the labelling of medical devices). Using standardized symbols eliminates the need for text translations for those specific elements, which is a significant practical benefit given the EU's multilingual requirements.

Common symbols include:

Symbol Meaning	ISO 15223-1 Reference	Usage
Manufacturer	5.1.1	Identifies the legal manufacturer
Authorized Representative	5.1.2	Identifies the EU Authorized Representative
Date of manufacture	5.1.3	Calendar date when the device was manufactured
Use-by date / Expiry	5.1.4	Date after which the device should not be used
Lot number	5.1.5	Manufacturer's batch code
Serial number	5.1.6	Unique identifier for a specific device
Single-use	5.4.2	Device intended for single use, do not reuse
Sterilized using EO	5.2.3	Sterilization method: ethylene oxide
Sterilized using irradiation	5.2.4	Sterilization method: irradiation
Do not use if package is damaged	5.2.8	Integrity of sterile barrier
Consult instructions for use	5.4.3	Directs user to the IFU
Contains latex	5.4.5	Warns of natural rubber latex
MR Safe / MR Conditional / MR Unsafe	ASTM F2503	MRI safety status

Practical tip: Create a symbol library and usage matrix for your organization. For each symbol, document the ISO 15223-1 reference number, the meaning, the applicable product lines, and the specific packaging level where it appears (unit label, inner packaging, outer carton, shipper). This prevents the all-too-common error of omitting symbols from one packaging level while including them on another.

Language Requirements per Member State

One of the most operationally burdensome aspects of EU MDR labeling is the language requirement. Article 10(11) requires that the information on the label and in the IFU be supplied in the official language(s) of the Member State where the device is made available to the user or patient. Each Member State determines which language(s) it accepts.

Member State(s)	Required Language(s)
Germany, Austria	German
France	French
Italy	Italian
Spain	Spanish (Castilian)
Portugal	Portuguese
Netherlands	Dutch
Belgium	Dutch, French, German (all three)
Luxembourg	French, German
Finland	Finnish, Swedish
Greece	Greek
Poland	Polish
Czech Republic	Czech
Nordic countries (DK, SE, NO, FI, IS)	National language(s); Scandinavian languages often mutually accepted for professional devices

Operational reality: For a manufacturer selling a single device across the EU, this can mean producing labeling in 20+ languages. Most companies handle this through multilingual booklet IFUs (accordion-fold inserts with all languages) or, where permitted, electronic IFU (eIFU) under Commission Regulation (EU) 2021/2226. The eIFU regulation allows manufacturers of certain devices (primarily professional-use and implantable devices) to provide the IFU electronically rather than in paper form, significantly reducing the logistical burden and environmental impact.

EUDAMED and Implant Cards

The EU MDR introduced the European Database on Medical Devices (EUDAMED) as a central database for device registration, UDI, certificates, clinical investigations, vigilance, and market surveillance. While EUDAMED's full functionality has been delayed (the UDI/device registration module became available for voluntary registration, but mandatory use timelines have been repeatedly extended), manufacturers should be preparing for full compliance.

For implantable devices, Article 18 requires manufacturers to provide an implant card to the patient. The implant card must include:

Device identification: name, serial number, lot number, UDI, device model
Manufacturer name, address, and website
Warnings, precautions, or measures to be taken by the patient or a healthcare professional regarding reciprocal interference with reasonably foreseeable external influences, medical examinations, or environmental conditions
Information about the expected device lifetime and necessary follow-up
Any other information to ensure safe use of the device by the patient

Electronic Instructions for Use (eIFU) — EU Regulation 2021/2226

The EU's implementing regulation on electronic IFU (Commission Implementing Regulation (EU) 2021/2226), which applied from January 4, 2022, provides a detailed legal framework for when and how manufacturers may replace paper IFUs with electronic versions. This is one of the most operationally significant provisions of the EU MDR labeling framework, and understanding it in detail is essential for manufacturers looking to reduce the logistical burden of multilingual paper IFUs.

Devices eligible for eIFU (Article 2):

Implantable and active implantable devices and their accessories
Fixed installed medical devices and their accessories
Devices fitted with a built-in system that visually displays the IFU (e.g., ultrasound machines, patient monitors with integrated displays)
Software that is itself a medical device (standalone software/SaMD)
Devices intended for use exclusively by professional users (not patients or lay users)

Devices NOT eligible for eIFU:

Devices intended for use by patients or lay persons (unless they have an integrated display showing the IFU)
Class I and Class IIa devices where no IFU is required under Annex I, Section 23.1(d)

Conditions that must be met (Articles 3-8):

Risk assessment — The manufacturer must conduct and document a risk assessment demonstrating that providing the IFU electronically maintains or improves the level of safety compared to a paper IFU. The assessment must consider whether users have reliable internet access at the point of use, whether the device can be used safely without immediate access to the IFU, and whether interruption of internet access could create safety risks.
Labeling of eIFU availability — The device packaging must clearly indicate that the IFU is provided in electronic form rather than paper. The label must include the symbol specified in ISO 15223-1 for "Consult electronic IFU," the website URL or QR code where the eIFU can be accessed, and a statement of the languages in which the eIFU is available.
Website requirements — The eIFU must be hosted on a website that is accessible 24/7 with 99.5% minimum uptime, does not require user registration or login to access the IFU, is accessible from all EU Member States, and clearly identifies the device to which each IFU applies (using the UDI-DI as the link).
Paper IFU upon request — The manufacturer must provide a paper copy of the IFU free of charge upon request, and must deliver it within 7 calendar days. The label must include instructions on how to request a paper copy.
Version management — The website must display the current IFU and maintain all previous versions. Historical versions must remain accessible, and the date of each revision must be clearly indicated.
Retention periods — The eIFU must remain accessible online for:
- 10 years after the last device with a defined expiry date has been placed on the market
- 15 years after the last device without an expiry date (including implantable devices) has been placed on the market
Privacy compliance — If the website collects any user data (analytics, access logs), it must comply with GDPR requirements and include an appropriate privacy policy.

Practical tip: Before switching to eIFU, survey the clinical settings where your device is used. If the device is used in operating theaters, catheterization labs, or other areas where internet access is unreliable or restricted by IT security policies, the risk assessment may not support eIFU as the primary delivery method. Many manufacturers adopt a hybrid approach — eIFU for routine reference, with a condensed quick-start guide included in paper form with the device.

FDA approach to electronic labeling:

The FDA has not enacted a regulation equivalent to EU 2021/2226. However, the FDA does accept electronic labeling for certain device categories, particularly software/SaMD products where the IFU is inherently electronic (displayed within the software interface). The FDA finalized guidance in 2024 addressing electronic labeling considerations for specific categories. For physical devices, most manufacturers still provide paper IFUs in the US market, although the FDA has signaled openness to electronic delivery for professional-use devices in hospital settings where the institution has confirmed digital access capabilities.

The UDI System Explained

What Is UDI?

The Unique Device Identification (UDI) system is a globally harmonized framework for identifying medical devices throughout their distribution and use. Every medical device is assigned a unique identifier that appears on the device label and packaging, enabling unambiguous identification from manufacturing through patient use.

The UDI system is not a single regulation — it is a coordinated global initiative driven by the International Medical Device Regulators Forum (IMDRF) and implemented through national and regional regulations. The two most significant implementations are the FDA UDI Rule (21 CFR Part 830) and the EU MDR UDI requirements (Articles 27-29 and Annex VI, Part C).

UDI-DI vs. UDI-PI

Every UDI consists of two components:

UDI-DI (Device Identifier) — A fixed, mandatory portion that identifies the labeler (manufacturer) and the specific version or model of a device. The UDI-DI is the primary lookup key for accessing device information in databases like GUDID and EUDAMED. A new UDI-DI is required whenever there is a change that could affect device safety or performance identification — for example, a change in device model, a new sterilization method, or a change in packaging configuration.
UDI-PI (Production Identifier) — A variable, conditional portion that identifies one or more of the following: lot or batch number, serial number, manufacturing date, and expiration date. Not all PI elements are required for every device — the specific elements depend on the device type and labeling practices. The UDI-PI changes with each production lot or unit.

Example UDI structure (GTIN format):

(01)00884838839aboratory(17)261231(10)ABC123
 |                          |             |
 UDI-DI (GTIN)        Expiry Date     Lot Number
                       (UDI-PI)       (UDI-PI)

Purpose and Benefits of UDI

The UDI system was designed to address fundamental traceability gaps in the medical device supply chain:

Improved adverse event reporting — When clinicians report adverse events, the UDI enables precise identification of the specific device involved, eliminating the ambiguity that previously plagued post-market surveillance
More effective recalls — UDI enables manufacturers and the FDA to identify exactly which devices are affected by a recall, down to the lot or serial number level
Reduced medical errors — UDI scanning at point of use helps prevent wrong-device and wrong-size errors in clinical settings
Supply chain efficiency — UDI provides a common identifier across the supply chain, enabling hospitals and GPOs to track inventory, utilization, and costs at the device level
Better post-market surveillance — UDI enables linkage of device identity to clinical outcomes data, making it possible to identify device performance trends across populations
Clinical decision support — When UDI is captured in electronic health records (EHRs), clinicians can identify all patients who received a specific device, enabling targeted patient notification during recalls

FDA UDI Rule (21 CFR Part 830)

The FDA finalized the UDI Rule on September 24, 2013 (78 FR 58786). The rule established phased compliance dates based on device class:

Device Class	Label and Package UDI	Direct Marking	GUDID Submission
Class III (PMA, high risk)	September 24, 2014	September 24, 2016	September 24, 2014
Class III (life-sustaining)	September 24, 2015	September 24, 2016	September 24, 2015
Class II	September 24, 2016	September 24, 2018	September 24, 2016
Class I and unclassified	September 24, 2018	Exempt (most)	September 24, 2018

Key provisions of the FDA UDI Rule:

Each device label and package must bear a UDI in both human-readable (plain text) and machine-readable (barcode or RFID) format
Reusable devices that must be reprocessed before each use must bear a UDI as a permanent direct marking on the device itself
GUDID submission — The labeler must submit device identification data to the Global Unique Device Identification Database (GUDID) before the device can be commercially distributed
Exceptions and exemptions — Certain devices are exempt, including individual single-use devices distributed within a kit, devices with very small labels where UDI placement is impractical, and devices regulated as both devices and drugs where the NDC is sufficient

EU MDR UDI Requirements (Article 27)

The EU MDR incorporated UDI requirements directly into the regulation, with Article 27 establishing the framework and Annex VI, Part C providing the detailed technical requirements. Key elements:

Basic UDI-DI — A unique concept in the EU MDR not found in the FDA system. The Basic UDI-DI is the primary identifier for a device model in EUDAMED. It is not placed on the label. It serves as the main key for linking regulatory information (certificates, clinical evaluations, vigilance reports) to a device model. Think of it as the "regulatory umbrella" identifier under which multiple UDI-DIs (specific packaging configurations, sterilization variants, etc.) are grouped.
UDI-DI and UDI-PI — Same concept as the FDA system, appearing on device labels
EUDAMED registration — Manufacturers must register their UDI-DIs and Basic UDI-DIs in EUDAMED. The timeline has been repeatedly delayed due to EUDAMED readiness issues. As of 2026, the UDI/device registration module is available, and manufacturers are urged to register voluntarily ahead of mandatory deadlines.
Issuing entities — The EU MDR recognizes the same issuing agencies as the FDA (GS1, HIBCC, ICCBBA, IFA GmbH)

Key difference from FDA: The EU MDR's Basic UDI-DI is a regulatory concept with no physical counterpart on the device label. It exists only in EUDAMED. Manufacturers transitioning from FDA-only UDI compliance to dual FDA/EU compliance often find this concept confusing, but it is essential for EUDAMED data architecture.

UDI Format and Structure

Issuing Agencies

The UDI system does not mandate a single format. Instead, regulators accredit "issuing agencies" that define the UDI syntax. Both the FDA and EU MDR recognize the following issuing agencies:

Issuing Agency	Identifier Format	Primary Users	Website
GS1	GTIN (Global Trade Item Number) — 14-digit numeric	Most medical device manufacturers globally	gs1.org
HIBCC	HIBC (Health Industry Bar Code) — alphanumeric	Primarily used by some US and European manufacturers	hibcc.org
ICCBBA	ISBT 128 — alphanumeric	Blood, tissue, cell, and organ products	iccbba.org
IFA GmbH	PPN (Pharmacy Product Number)	Primarily EU pharmaceutical and some device manufacturers	ifaffm.de

GS1 is by far the most widely used system globally, and most medical device companies will use GTIN-based UDIs. However, the choice depends on your supply chain, existing barcode systems, and customer requirements.

How to Obtain a UDI

For GS1 (GTIN) — the most common path:

Join GS1 — Register with your national GS1 organization (e.g., GS1 US for US-based companies). You will receive a GS1 Company Prefix.
Assign GTINs — Using your GS1 Company Prefix, assign a unique GTIN to each device version/model and packaging configuration. Each unit-of-use, each inner pack, and each case-level configuration needs its own GTIN.
Determine PI elements — Identify which production identifier elements (lot number, serial number, manufacturing date, expiry date) apply to each device.
Create UDI strings — Combine the GTIN (DI) with the applicable PI elements using GS1 Application Identifiers (AIs): AI (01) for GTIN, AI (10) for lot number, AI (17) for expiry date, AI (21) for serial number, AI (11) for manufacturing date.
Generate barcodes — Encode the UDI string into the appropriate barcode symbology.

UDI Carrier: Barcodes and RFID

The UDI must be presented on the device label in two forms:

Machine-readable format — A barcode or RFID tag that can be scanned. Acceptable barcode symbologies include:

GS1-128 (linear barcode) — Widely used on outer packaging; supports all GS1 AIs
GS1 DataMatrix (2D barcode) — Preferred for small labels and direct marking; high data density in a small footprint
GS1 QR Code — Less common for medical devices but acceptable
HIBC 128 / HIBC DataMatrix — For HIBCC-based UDIs
ISBT 128 — For ICCBBA-based identifiers

Human-readable interpretation (HRI) — The UDI must also appear as plain text adjacent to or below the barcode, so it can be read and recorded manually if scanning is not possible. The HRI must include the full UDI string with appropriate data delimiters.

Practical tip: Always verify your barcodes with a barcode verifier (not just a scanner). Scanners confirm that a barcode can be read; verifiers grade the barcode quality against ISO/IEC standards (ISO/IEC 15415 for 2D, ISO/IEC 15416 for linear). A barcode that scans in your clean, well-lit office may fail in a hospital receiving dock. Aim for a minimum grade of C (1.5) per ISO standards — most healthcare facilities and GPOs require grade C or better.

Direct Marking Requirements

For reusable devices that must be reprocessed between uses, the FDA requires a permanent UDI direct mark on the device itself (not just on the packaging, which is discarded after opening). Direct marking requirements include:

The UDI must be a permanent mark that remains legible through the device's expected service life, including repeated cycles of reprocessing (cleaning, disinfection, sterilization)
Common direct marking methods: laser etching, dot peen engraving, chemical etching, and electrochemical marking
The direct mark must be machine-readable (typically a DataMatrix barcode) — HRI alone is not sufficient
Direct marking must survive the device's reprocessing method (e.g., autoclave cycles, chemical disinfection)

Devices where direct marking is technically impractical (due to size, material, or other constraints) may apply for an exemption or alternative under 21 CFR 801.55.

UDI Exceptions and Exemptions (21 CFR 801.30)

While the UDI Rule applies to virtually all commercially distributed medical devices, the FDA provides specific exceptions and exemptions under 21 CFR 801.30 and related sections. Understanding these is critical for correctly scoping your UDI compliance program.

General exceptions from the UDI label requirement (801.30):

Individual single-use devices distributed together — Individual single-use devices, all of a single version or model, that are distributed together in a single device package and are intended to be stored in that package until removed for use are excepted from individually bearing a UDI. However, the outer device package must still bear a UDI. Important: this exception does not apply to implantable devices — every individual implantable device must bear a UDI regardless of packaging.
Devices manufactured before the compliance date — Finished devices manufactured and labeled before the applicable compliance date are excepted from bearing a UDI. However, this exception expires 3 years after the compliance date for the device. Since all compliance dates have now passed (the final phase for Class I devices was September 24, 2018, with the 3-year exception expiring September 24, 2021), this exception is no longer available for newly manufactured devices.
Class I devices exempt from GMP — Class I devices that the FDA has exempted from the current good manufacturing practice requirements of Part 820 by regulation are excepted from UDI requirements.

Additional exemptions (801.55 and related):

Research, teaching, and chemical analysis devices — Devices used solely for research, teaching, or chemical analysis purposes, and not intended for clinical use, are exempt from UDI requirements.
Custom devices — Devices manufactured on an individual basis per a physician's order for a specific patient (custom devices under Section 520(b) of the FD&C Act) are exempt.
Investigational devices — Devices under an approved Investigational Device Exemption (IDE) are exempt from UDI requirements, though many sponsors voluntarily apply UDIs to investigational devices to facilitate tracking.
Devices intended for export only — Devices manufactured in the US exclusively for export and not sold domestically are exempt.
Low-risk devices with very small labels — Where the physical size of the device or its label makes UDI placement impractical, the labeler may request an alternative placement or exemption. The FDA evaluates these on a case-by-case basis under 801.55.

EU MDR UDI exemptions:

The EU MDR provides fewer exemptions than the FDA. Under the MDR, UDI is required for all devices placed on the EU market. However, practical accommodations exist:

Custom-made devices are exempt from UDI requirements under the MDR
Devices for performance studies (investigational devices) are generally exempt
For devices with very small labels, the MDR permits placement of the UDI on a higher packaging level if placement on the device or unit packaging is impractical

Common mistake: Manufacturers sometimes assume that because a device is low-risk (Class I) or an accessory, it is exempt from UDI. In the vast majority of cases, it is not. The exceptions are narrow and specific. When in doubt, apply a UDI — it is far easier to apply a UDI proactively than to defend an exemption claim during an FDA inspection.

GUDID Database

What Is GUDID?

The Global Unique Device Identification Database (GUDID) is the FDA's publicly accessible repository of device identification information. Every medical device with a UDI that is commercially distributed in the United States must have its UDI-DI and associated device data submitted to GUDID. GUDID does not contain patient-specific or production-level data — it stores only the device identifier (DI) level information.

GUDID is publicly searchable at accessgudid.nlm.nih.gov and serves as the authoritative reference for device identification in the US healthcare system.

Data Submission Requirements

When submitting a UDI-DI record to GUDID, manufacturers must provide the following data elements:

Required data elements:

UDI-DI (the device identifier)
Brand name
Version or model number
Company name (labeler)
Device description
Whether the device is labeled as containing natural rubber latex
Whether the device is labeled as "not made with natural rubber latex"
MRI safety status (MR Safe, MR Conditional, MR Unsafe, or MR Safety Information not provided)
Whether the device is labeled as single-use
Whether the device is a kit
Whether the device requires sterilization prior to use
Device publish date and commercial distribution status

Conditional data elements (required if applicable):

GMDN (Global Medical Device Nomenclature) code or FDA product code
Sterilization method
Device size and dimensions
Storage and handling conditions
Packaging details (quantity per package, packaging type)
Direct marking status

GUDID Submission Process

Manufacturers can submit data to GUDID through two methods:

GUDID Web Interface — A web-based data entry form suitable for manufacturers with a small number of device listings. Available through the FDA's Unified Registration and Listing System (FURLS).
GUDID HL7 SPL (Structured Product Labeling) — An XML-based electronic submission format for bulk data uploads. This is the preferred method for manufacturers with large device portfolios. The HL7 SPL format follows a specific schema defined by the FDA, and submissions are uploaded via the FDA's Electronic Submissions Gateway (ESG).

Submission workflow:

Obtain an FDA GUDID account through FURLS
Prepare device data according to GUDID data element specifications
Submit data via web interface or HL7 SPL upload
GUDID performs automated validation checks
If validation fails, correct errors and resubmit
Upon successful validation, the DI record is published to the public GUDID database
Maintain records — update GUDID within specified timeframes when device data changes

Common GUDID Errors and Fixes

Error	Cause	Fix
Duplicate DI	A DI record already exists for this identifier	Check if a prior submission exists; use the Update function rather than creating a new record
Invalid GTIN check digit	The 14th digit of the GTIN does not match the calculated check digit	Recalculate the GTIN check digit using the GS1 algorithm
Missing required field	A mandatory data element was left blank	Complete all required fields; common omissions include MRI safety status and latex content
Invalid date format	Dates not in the required YYYYMMDD format	Convert all dates to the GUDID-required format
SPL schema error	HL7 SPL XML does not conform to the FDA schema	Validate XML against the current FDA SPL schema before submission; use the FDA's SPL validation tool
Inactive company account	The DUNS number associated with the submission is not active in FURLS	Verify and update your establishment registration in FURLS
Product code mismatch	The submitted product code does not match the device description or intended use	Review the FDA product classification database to confirm the correct product code

Practical tip: Before your first GUDID submission, perform a dry run using the GUDID sandbox environment. The FDA provides a test environment where you can submit sample data and identify formatting or validation issues without affecting your production records. This is especially important if you are using the HL7 SPL bulk upload method, where schema errors can cause entire batch submissions to fail.

AccessGUDID: Public Search, Downloads, and API

While manufacturers interact with GUDID through the FURLS submission portal, the public-facing side of GUDID is AccessGUDID, hosted by the National Library of Medicine (NLM) at accessgudid.nlm.nih.gov. AccessGUDID serves healthcare facilities, researchers, regulators, and the general public by providing free access to all published device identification data.

Search capabilities:

Device lookup by DI — Enter a UDI-DI (GTIN, HIBC, or ISBT 128 identifier) to retrieve the full device record, including brand name, model, manufacturer, device description, MRI safety status, latex content, sterilization information, and all associated packaging levels.
Barcode scan lookup — Paste or scan the full UDI string (DI + PI) and AccessGUDID will parse it and display the corresponding device record. This is heavily used by hospital receiving departments and materials management teams.
Text search — Search by brand name, company name, or device description keywords.
Advanced filtering — Filter by device class, product code, MRI safety status, sterile status, single-use status, and other attributes.

Bulk data downloads:

AccessGUDID provides daily-updated full database downloads in delimited text format. These downloads are used by:

Hospital ERP/EHR systems — Healthcare facilities import GUDID data into their item master databases to auto-populate device records when a UDI is scanned at the point of care
Group purchasing organizations (GPOs) — GPOs use GUDID data to standardize device identification across their member hospitals
Post-market surveillance researchers — Researchers link GUDID data with adverse event reports (MAUDE database), recall data, and clinical outcomes data to study device performance at the population level

GUDID API:

The NLM provides a RESTful API for programmatic access to GUDID data. The API supports:

Device lookup by DI, brand name, company name, or product code
Batch queries for integration with enterprise systems
JSON and XML response formats
No authentication required for read access (rate limits apply)

The API is documented at accessgudid.nlm.nih.gov/resources/developers and is the recommended integration method for healthcare IT systems, regulatory information management systems (RIMS), and supply chain platforms.

Practical tip: If you are a manufacturer, periodically search AccessGUDID for your own devices to verify that the published data matches your current label claims. Discrepancies between your physical label and your GUDID record are a compliance risk — and they are discoverable by anyone with internet access, including FDA inspectors, hospital procurement teams, and competitors.

EUDAMED UDI Module

How EU UDI-DI Registration Works

EUDAMED is the EU's centralized database system established under Article 33 of the EU MDR. The UDI/Device Registration module is one of six EUDAMED modules. In this module, manufacturers register:

Basic UDI-DI — The top-level identifier for a device model (not placed on labels)
UDI-DI(s) — Each specific packaging configuration and variant under that Basic UDI-DI
Device data — Product information, classifications, intended purpose, risk class, applicable certificates, and other regulatory data

The registration workflow:

Manufacturer (or Authorized Representative for non-EU manufacturers) creates an actor registration in EUDAMED
Assign Basic UDI-DI using an accredited issuing entity (GS1, HIBCC, ICCBBA, IFA)
Register the Basic UDI-DI in EUDAMED with the required device data
Register each UDI-DI under the Basic UDI-DI
Link certificates (issued by Notified Bodies) to the Basic UDI-DI
Update records when device data, certificates, or market status changes

The Basic UDI-DI Concept

The Basic UDI-DI is unique to the EU system and has no direct equivalent in the FDA framework. It serves as the regulatory anchor point:

One Basic UDI-DI encompasses all variants of a device model that share the same intended purpose, risk class, and essential design characteristics
Multiple UDI-DIs can be linked to a single Basic UDI-DI (representing different packaging sizes, sterile vs. non-sterile variants, etc.)
Notified Body certificates, clinical evaluation reports, vigilance reports, and FSCA (Field Safety Corrective Action) notices are linked to the Basic UDI-DI — not to individual UDI-DIs
The Basic UDI-DI is assigned by the manufacturer using the same issuing entity as the UDI-DI

Example hierarchy:

Basic UDI-DI: 04056631100199DM  (Surgical Stapler Model X)
  ├── UDI-DI: 04056631100205  (Model X, 30mm cartridge, sterile, box of 6)
  ├── UDI-DI: 04056631100212  (Model X, 45mm cartridge, sterile, box of 6)
  ├── UDI-DI: 04056631100229  (Model X, 60mm cartridge, sterile, box of 6)
  └── UDI-DI: 04056631100236  (Model X, 30mm cartridge, sterile, box of 1)

EUDAMED Timeline

EUDAMED has experienced significant delays. The original EU MDR timeline envisioned full EUDAMED functionality by May 2020 (the original MDR application date). As of 2026:

The UDI/Device Registration module and Actor Registration module are operational
Manufacturers are strongly encouraged to register voluntarily
Mandatory registration deadlines are tied to EUDAMED's official "fully functional" declaration, which the European Commission must confirm
Notified Body certificate data and vigilance modules are at varying stages of deployment
The practical reality is that manufacturers should be registering now rather than waiting for mandatory deadlines, as Notified Bodies and Competent Authorities increasingly expect EUDAMED data to be available

Labeling for Specific Device Types

IVD Device Labeling (21 CFR 809.10)

IVD labeling is among the most prescriptive in the medical device world. Beyond the general requirements of 21 CFR Part 801, IVD devices must comply with 21 CFR 809.10, which mandates detailed technical and performance information in the labeling:

Intended use must specify: the analyte(s) or condition(s) detected, the specimen type(s), the intended testing population, and whether the test is for professional use, point-of-care, or over-the-counter (home use)
Performance characteristics must be stated: sensitivity, specificity, accuracy, precision (repeatability and reproducibility), analytical measurement range, limit of detection (LOD), limit of quantitation (LOQ), interfering substances, and cross-reactivity data
Specimen handling: detailed requirements for specimen collection, transportation, storage, and preparation
Quality control: required QC materials, frequency of QC testing, and acceptable QC result ranges
Limitations: every known limitation must be disclosed, including substances that interfere with the assay, populations in which the test has not been validated, and conditions under which false positives or false negatives are more likely

Under the EU IVDR (Regulation 2017/746), IVD labeling requirements are similarly comprehensive, with Annex I, Chapter III specifying requirements that parallel and in some cases exceed the FDA's 809.10 requirements.

Software and SaMD Labeling

Software as a Medical Device (SaMD) presents unique labeling challenges because the "device" is intangible. Key considerations:

The software user interface is labeling — Under FDA interpretation, the screens, menus, alerts, and outputs of medical device software constitute labeling. This means the UI must comply with labeling requirements, including displaying intended use, warnings, and relevant safety information.
Version identification — Software labeling must clearly identify the software version. For SaMD, the UDI-DI must change with each version that could affect safety, performance, or intended use.
Electronic IFU — Most SaMD products provide their IFU electronically (within the software or via a linked document). This is acceptable under both FDA and EU MDR frameworks, though the EU requires compliance with the eIFU regulation.
Cybersecurity labeling — FDA guidance (and the EU MDR MDCG guidance) increasingly requires that software labeling include cybersecurity information: supported operating systems, hardware requirements, network requirements, end-of-support date, and instructions for applying security patches.
AI/ML-specific labeling — For AI/ML-enabled devices, the FDA expects labeling to describe the algorithm's intended use, the training data characteristics, known performance limitations, and situations where the algorithm's performance may degrade.

Implantable Device Labeling

Implantable devices carry additional labeling requirements due to the long-term presence of the device in the patient's body:

EU MDR implant card (Article 18) — As described above, manufacturers must provide patients with an implant card containing key device identification and safety information
MRI safety labeling — Must be clearly stated per ASTM F2503 (MR Safe, MR Conditional with conditions stated, or MR Unsafe)
Device lifetime and follow-up — Labeling must include information on the expected service life of the implant and recommended follow-up schedule
Patient information — Both FDA and EU MDR require that patient-facing information be provided in lay language that a non-clinician can understand
Explant information — If applicable, instructions for safe removal of the device

Sterile Device Labeling

Sterile medical devices have specific labeling requirements related to their sterile status:

Sterilization method — Must be identified using ISO 15223-1 symbols (EO, irradiation, steam, aseptic processing, etc.)
"STERILE" indicator — Clear indication of sterile status on the label
Sterile barrier system integrity — Statement such as "Do not use if package is damaged" (with corresponding ISO 15223-1 symbol)
Single-use indication — If single-use, must be clearly labeled with the ISO 15223-1 single-use symbol and text
Re-sterilization instructions — If the device can be re-sterilized, the labeling must include validated re-sterilization instructions
Shelf life / Expiry date — Sterile devices must include an expiration date based on packaging shelf-life validation studies

Global UDI Harmonization

IMDRF UDI Guidance

The International Medical Device Regulators Forum (IMDRF) published the foundational UDI guidance document, "Unique Device Identification (UDI) of Medical Devices" (IMDRF/UDI WG/N7FINAL:2013), which serves as the global framework that individual regulators reference when implementing their own UDI requirements. The IMDRF guidance established the core principles:

Every device should have a UDI
UDI should consist of DI and PI components
UDI should be affixed to device labels and packages
UDI data should be submitted to a public database (UDID)
UDI should be captured in health information systems

Country-Specific UDI Requirements

UDI implementation is progressing at different rates around the world:

Country / Region	UDI Status	Regulatory Basis	Database	Notes
United States	Fully implemented	21 CFR Part 830	GUDID	All device classes covered since September 2018
European Union	Partially implemented	EU MDR Article 27, Annex VI Part C	EUDAMED	Phased timeline tied to EUDAMED functionality; Class III and implantable devices first
Japan	Implemented	MHLW/PMDA notification	MEDIS-DC database	Japan has its own UDI system but recognizes GS1/HIBCC/ICCBBA identifiers
South Korea	Implemented	MFDS UDI regulation	MFDS UDI database	Mandatory since 2019 for implantable devices; phased expansion
China	Partially implemented	NMPA UDI regulation (2019/2021)	China UDI database (NMPA)	Phased implementation; first phase (Class III implantable) effective 2021; expanding to all Class III and select Class II
Saudi Arabia	Implemented	SFDA UDI regulation	SFDA device listing system	Aligned with IMDRF guidance; mandatory for all devices
Brazil	In progress	ANVISA Resolution RDC 591/2021	ANVISA database	UDI requirements published; Class IV by July 2025; phased expansion
Canada	Not yet implemented	Health Canada — no formal UDI process	None	Canada has no mandatory UDI system as of 2026; Health Canada is monitoring IMDRF progress and may align with US/EU in the future
Singapore	Implemented (phased)	HSA medical device regulations	SMDR / Class A database	Class D devices by November 2024; phased rollout to lower classes
Taiwan	Implemented	TFDA UDI regulation	TUDID	Class II devices by June 2023; mandatory for marketed devices in phases
India	In planning	CDSCO draft UDI regulations	Planned	Draft rules published; final timelines pending
Turkey	Partially implemented	T.C. TITCK regulations	TUYS system	Aligned with EU MDR requirements
Australia	In planning	TGA UDI framework	AusUDID (planned)	TGA has signaled intent to implement UDI aligned with IMDRF; Q1 2025 target date not yet achieved

Convergence Efforts

The global trend is clearly toward UDI harmonization, but practical convergence remains incomplete. Key challenges include:

Database interoperability — GUDID, EUDAMED, and national databases do not currently share data automatically. A manufacturer selling globally must submit device data to each database separately.
Format differences — While all major regulators recognize the same issuing agencies (GS1, HIBCC, ICCBBA), the required data elements and submission formats differ by jurisdiction.
Timeline misalignment — The US has been fully implemented since 2018, the EU is still phasing in, and many other countries are years behind.
Basic UDI-DI — The EU's Basic UDI-DI concept is not used by the FDA or most other regulators, adding complexity for manufacturers who must manage both systems.

Strategic advice: If you sell devices in multiple markets, design your UDI strategy around the most comprehensive set of requirements (currently the EU MDR) and then adapt for other markets. Assign GTINs through GS1, as this is the most universally accepted system. Build your master data management system to accommodate the EU's Basic UDI-DI hierarchy even if you are currently selling only in the US, because retrofitting this structure later is significantly more expensive than building it from the start.

UDI in Healthcare Settings: EHR Integration and Clinical Workflows

The UDI system was designed not only for regulatory compliance but also to transform how medical devices are tracked and managed within healthcare facilities. The downstream adoption of UDI — from the hospital loading dock to the operating room to the patient's electronic health record — is where the system delivers its greatest value. Manufacturers who understand this downstream ecosystem can better design their labeling and UDI strategies to support clinical adoption.

Point-of-Care UDI Scanning

When UDI is implemented at the point of care, clinicians or materials management staff scan the device barcode at the time of use. This single scan event triggers multiple downstream actions:

Inventory decrement — The device is automatically removed from facility inventory, enabling just-in-time resupply
Procedure documentation — The device identity (manufacturer, model, lot/serial, expiry) is captured in the patient's procedural record without manual data entry
Charge capture — The device cost is automatically linked to the patient encounter for billing purposes
EHR documentation — The UDI is recorded in the patient's electronic health record, creating a permanent link between patient and device
Recall readiness — If the device is later recalled, the facility can instantly identify all patients who received a device from the affected lot or serial number range

UDI in Electronic Health Records (EHR)

The United States Core Data for Interoperability (USCDI) standard includes UDI as a required data class for health information exchange. This means that EHR systems certified under the ONC Health IT Certification Program must support the capture, storage, and exchange of UDI data. The goal is to create a nationwide infrastructure where device identity is linked to patient outcomes, enabling:

Population-level device surveillance — By aggregating UDI data across EHR systems, regulators and researchers can identify device performance trends, failure patterns, and adverse event clusters that would be invisible at the individual facility level
Patient notification during recalls — When a recall occurs, healthcare facilities can query their EHR for all patients who received the recalled device, enabling targeted outreach rather than broad public notices
Longitudinal device tracking — For implantable devices, the UDI in the EHR creates a permanent record that follows the patient across providers and healthcare systems, ensuring that every clinician who treats the patient knows what device is implanted

Challenges in Healthcare UDI Adoption

Despite the clear benefits, healthcare facility adoption of UDI scanning and integration remains uneven. Key challenges include:

Item master data management — Healthcare facilities must build and maintain an item master database that maps UDI-DIs to their internal product codes, pricing, and clinical categories. This is a significant data management undertaking, particularly for large health systems with tens of thousands of device SKUs.
Scanner infrastructure — Point-of-care scanning requires investment in barcode scanners, wireless network infrastructure, and integration with existing clinical information systems (EHR, materials management, billing).
Workflow integration — Adding a scanning step to clinical procedures must be done carefully to avoid disrupting surgical and procedural workflows. Staff training and change management are essential.
Barcode quality variability — When manufacturer barcodes are low quality (poor print, low contrast, damage during shipping), scanning failure rates increase, and clinicians revert to manual entry or skip documentation entirely. This is why barcode verification at the manufacturer level (per ISO/IEC 15415/15416) is so important.

For manufacturers: Understanding how your customers use UDI data downstream can inform your labeling design. Place barcodes where they will be accessible during clinical use (not just on outer cartons that are discarded in the supply room). Ensure your barcodes are high quality — grade C or better. And ensure your GUDID data is accurate and complete, because that is the data that populates your customers' item master systems.

Common Labeling Deficiencies

Top FDA Warning Letter Findings

Labeling is consistently among the top categories of FDA warning letters and Form 483 observations. The most frequently cited deficiencies include:

Labeling claims inconsistent with cleared/approved intended use — Marketing materials or website content make claims that go beyond the cleared 510(k) or approved PMA indications. This is the single most common labeling enforcement action.
Failure to include adequate directions for use — IFU is missing, incomplete, or does not provide sufficient information for the device to be used safely and effectively.
Missing or incorrect UDI — UDI barcode does not scan, UDI data does not match GUDID records, or UDI is absent from the label.
Failure to include required warnings — Mandatory warnings (latex content, MRI safety, single-use) are missing or inadequately prominent.
Misbranding — The label does not include the manufacturer name and address, or the information is incorrect.
Promotional labeling with unsubstantiated claims — Claims of superiority, efficacy, or safety that are not supported by clinical evidence or that have not been reviewed and cleared/approved by the FDA.
Failure to update labeling after design changes — Device design or manufacturing process changes were made, but the labeling was not updated to reflect the changes.

Common 510(k) Labeling Deficiencies

FDA reviewers frequently issue Refuse to Accept (RTA) or Additional Information (AI) requests for labeling deficiencies in 510(k) submissions:

Proposed labeling is incomplete — Draft labeling submitted with the 510(k) is missing required sections (indications, contraindications, warnings, directions for use)
Indications for use form inconsistency — The indications stated in the Indications for Use (FDA Form 3881) do not match the indications in the proposed labeling
IVD labeling missing performance data — For IVD 510(k)s, the proposed labeling does not include the performance characteristics required by 21 CFR 809.10
Labeling claims exceed supporting data — The proposed labeling makes claims that the submitted bench, animal, or clinical data do not support
Predicate device comparison gaps — The proposed labeling makes claims or includes indications that differ from the predicate device but are not supported by additional data

EU MDR Notified Body Findings

Notified Body auditors under the EU MDR commonly identify these labeling deficiencies:

Missing or incorrect symbols — ISO 15223-1 symbols are missing, outdated (using withdrawn symbol versions), or used incorrectly
Language compliance gaps — IFU is not available in all required languages for the target Member States
UDI not present or not machine-readable — UDI carrier is missing from one or more packaging levels, or the barcode does not scan
Basic UDI-DI not registered in EUDAMED — Manufacturer has not registered the Basic UDI-DI and associated device data
Implant card missing or incomplete — For implantable devices, the implant card does not contain all required elements per Article 18
Label does not reflect current Technical Documentation — The label references outdated specifications, addresses, or Authorized Representative information
CE mark improperly displayed — CE mark is not accompanied by the Notified Body number, or the format does not comply with Annex V requirements

Practical Implementation Guide

Step-by-Step UDI Implementation

For a manufacturer implementing UDI for the first time, the process typically follows these phases:

Phase 1 — Assessment and Planning (2-4 months)

Inventory all device models, versions, packaging configurations, and markets
Determine which UDI issuing agency to use (GS1 recommended for most manufacturers)
Map each device to its required UDI-DI(s) — remember that each packaging configuration needs its own UDI-DI
Identify which PI elements (lot, serial, expiry, manufacturing date) apply to each device
Assess current labeling artwork and determine what changes are needed
Identify direct marking requirements for reusable devices
Estimate budget for GS1 membership, barcode generation software, verification equipment, label artwork changes, and GUDID submissions

Phase 2 — Data Architecture (1-3 months)

Establish a master data management system for UDI data (this can be a module within your ERP/PLM system or a standalone UDI database)
Create UDI-DI assignment procedures — who can assign a new DI, what triggers a new DI, and how assignments are documented
For EU MDR compliance, define your Basic UDI-DI hierarchy and assignment rules
Map GUDID and EUDAMED data element requirements to your master data fields
Establish data governance procedures — who owns UDI data, how changes are controlled, and how data quality is verified

Phase 3 — Label Artwork and Barcode Generation (2-6 months)

Update label artwork to include UDI carriers (barcode + HRI)
Select barcode generation software and verify it produces barcodes that meet ISO/IEC quality standards
Procure barcode verification equipment and train label operations staff
For direct marking: validate marking methods, verify readability after reprocessing cycles
Produce sample labels and verify scanability across multiple scanner types
Conduct a formal design review of updated labeling per your design control process

Phase 4 — Database Submissions (1-2 months)

Submit device data to GUDID (FDA market)
Register Basic UDI-DIs and UDI-DIs in EUDAMED (EU market)
Submit to any other required national databases
Verify published data accuracy by searching the public databases
Establish a recurring audit process to verify database records remain accurate

Phase 5 — Production and Distribution (Ongoing)

Transition to UDI-bearing labels in production
Implement barcode quality checks in production (scan verification at packaging line)
Train distribution and warehouse staff on UDI scanning and documentation
Coordinate with customers (hospitals, distributors) on UDI scanning at point of receipt

Labeling Review Process

Every labeling change should follow a structured review and approval process:

Initiation — A change request identifies the need for a labeling update (new product launch, design change, regulatory requirement, corrective action, etc.)
Drafting — Regulatory affairs drafts the updated labeling content, ensuring compliance with all applicable requirements
Cross-functional review — At minimum, the following functions should review and approve labeling changes:
- Regulatory Affairs (regulatory compliance)
- Quality Assurance (QMS compliance, change control)
- Clinical/Medical Affairs (clinical claims accuracy)
- Marketing (promotional consistency)
- Legal (intellectual property, liability)
- Manufacturing/Operations (label printing feasibility, barcode verification)
Artwork preparation — Graphic design converts approved content into print-ready artwork
Artwork verification — A formal proofreading step comparing the artwork against the approved content, character by character
Final approval — Regulatory affairs (and in some organizations, the medical director or quality director) provides final release authorization
Implementation — Labels are printed, existing inventory is managed (labeled, relabeled, or scrapped per change control), and the transition is documented
Verification — Post-implementation verification confirms that commercially distributed product bears the correct labeling

Common pitfall: Many companies have a robust review process for primary device labels but a weak or nonexistent process for IFU updates, website content, and promotional materials. All labeling — in the FDA's broad definition — should go through the same controlled review process. A promotional brochure that contradicts your cleared indications creates the same regulatory risk as a mislabeled device.

Labeling Change Management

Labeling changes are among the most common changes in a medical device quality system, and poor change management is a leading cause of labeling deficiencies. Your change control procedure should address:

Triggering events — Define what triggers a labeling change: design changes, regulatory submissions, post-market feedback, corrective actions, address changes, Authorized Representative changes, UDI updates, etc.
Impact assessment — Every labeling change must be assessed for regulatory impact. Questions to ask: Does this change require a new 510(k) submission? A PMA supplement? A change notification to the Notified Body? A GUDID update? An EUDAMED update?
Affected materials inventory — Identify every piece of labeling affected by the change — not just the primary label, but also IFU, outer packaging, shipper labels, website content, sales literature, and training materials
Transition plan — Define how existing labeled inventory will be handled: use-up period, relabeling, quarantine, or scrap
Distribution hold — If the labeling change is safety-critical, distribution may need to be halted until the new labeling is in place
Regulatory notifications — Submit required notifications (GUDID updates, EUDAMED updates, regulatory authority notifications) within the required timeframes

Template Labeling SOPs

Organizations should maintain at minimum the following labeling-related SOPs:

SOP	Purpose	Key Content
Labeling Control Procedure	Master procedure governing all labeling activities	Definitions, roles, labeling types covered, review and approval workflow, storage and obsolescence
UDI Assignment and Management	Governs UDI-DI assignment, PI element selection, and database submissions	Triggering events for new UDI-DI, assignment workflow, GUDID/EUDAMED submission process, data maintenance
Label Artwork Review and Approval	Detailed procedure for reviewing and approving label artwork	Proofreading checklist, reviewer roles, approval signatures, artwork version control
Barcode Generation and Verification	Ensures barcode quality meets ISO/IEC standards	Barcode symbology specifications, verification equipment, minimum grade requirements, verification frequency
Labeling Change Control	Governs changes to existing labeling	Change request, impact assessment, affected materials identification, transition plan, regulatory notification
Electronic Labeling (eIFU)	Governs provision of electronic instructions for use	Applicability (which devices qualify for eIFU), website hosting requirements, accessibility, language availability, paper IFU availability upon request

Frequently Asked Questions

Does every medical device need a UDI?

In the United States, yes — with very limited exceptions. The FDA UDI Rule applies to all medical devices commercially distributed in the US, across all device classes. Certain exemptions exist for devices where UDI placement is impractical (very small devices, devices distributed before the compliance date without labeling changes), but these exemptions are narrow. In the EU, UDI is required under the EU MDR for all devices, with implementation phased by risk class.

When does a device need a new UDI-DI?

A new UDI-DI is required whenever there is a change that could affect device identification at the model/version level. Specific triggers include: a change in device name or model number, a change in intended use, a change in sterilization method, a change in packaging configuration (e.g., from a box of 10 to a box of 25), a change in the device version that involves different specifications, and a change of labeler (manufacturer). Lot number changes, serial number changes, and expiry date changes do NOT require a new UDI-DI — these are UDI-PI elements and are variable by definition.

Can I use the same UDI across FDA and EU markets?

Yes. The same UDI-DI (e.g., the same GTIN) can be used for both FDA (GUDID) and EU (EUDAMED) submissions, provided the device being identified is the same. This is strongly recommended as it simplifies data management and supply chain operations. However, remember that the EU additionally requires a Basic UDI-DI, which is a separate identifier not submitted to GUDID.

What happens if my device labeling does not comply?

The consequences depend on the nature and severity of the deficiency. In the US, the FD&C Act classifies devices with noncompliant labeling as "misbranded," which can trigger: warning letters, import alerts, injunctions, seizure of product, civil monetary penalties, and in egregious cases, criminal prosecution. In the EU, non-compliant labeling can result in Notified Body suspension of certificates, Competent Authority market restrictions, mandatory recalls, and FSCA (Field Safety Corrective Action) requirements.

Is an electronic IFU (eIFU) acceptable instead of paper?

Under FDA regulations, the answer is nuanced. The FDA has not issued a general rule permitting eIFU for all devices, but it has accepted electronic labeling for certain device types (particularly software/SaMD). The FDA finalized guidance in 2024 addressing electronic labeling for specific categories. Under the EU MDR, Commission Regulation (EU) 2021/2226 explicitly permits eIFU for professional-use devices and implantable devices, subject to conditions: the device must be safely usable without the IFU at the time of use, a paper IFU must be available upon request, and the manufacturer must maintain a website where the eIFU is accessible and up-to-date.

How do I handle labeling for devices sold in multiple EU countries?

You must provide labeling in the official language(s) of each Member State where the device is made available to users. In practice, most manufacturers produce multilingual IFU booklets or use eIFU (where permitted) to manage the language burden. For symbols, use ISO 15223-1 harmonized symbols wherever possible, as these are language-independent. For the label itself, symbols can replace text for standardized information elements, but the device name, specific warnings, and certain text elements may still require translation.

What is the difference between a GTIN and a UDI?

A GTIN (Global Trade Item Number) is one possible format for the UDI-DI component. The UDI-DI can be expressed as a GTIN (if you use GS1 as your issuing agency), an HIBC identifier (if you use HIBCC), or an ISBT 128 identifier (if you use ICCBBA). The UDI itself is the complete string comprising the DI plus any applicable PI elements. So a GTIN is a type of UDI-DI, but a UDI is more than just a GTIN — it also includes the production identifiers.

How often must I update GUDID records?

The FDA requires that GUDID records be updated within a specific timeframe whenever there is a change to any of the data elements associated with a UDI-DI. For most data element changes, the update must be submitted before the device bearing the updated information is commercially distributed. For changes to commercial distribution status (e.g., discontinuation), updates should be submitted promptly. There is no periodic "re-certification" of GUDID data, but manufacturers should conduct regular internal audits of their GUDID records to ensure accuracy.

Do accessories and components need their own UDI?

Under the FDA UDI Rule, accessories that are devices in their own right (i.e., they have their own device listing and intended use) require their own UDI. Components that are not separately sold or distributed as finished devices generally do not need a UDI. However, if a component is commercially distributed as a replacement or spare part and is itself a finished device, it needs a UDI. In the EU MDR, Article 27 applies to all devices placed on the market, including accessories (which the MDR explicitly defines as devices per Article 2(2)).

What are the penalties for non-compliance with UDI requirements?

In the United States, failure to comply with the UDI requirements constitutes misbranding under the FD&C Act. The FDA can issue warning letters, refuse entry of imported devices, seek injunctions, seize products, and impose civil monetary penalties. The FDA has also made UDI compliance a routine part of its establishment inspection program, so non-compliance may be identified during routine inspections and cited on Form 483 observations. In the EU, non-compliance with UDI requirements is grounds for Competent Authority enforcement action, including restrictions on making the device available on the market.

Conclusion

Medical device labeling and UDI compliance are not peripheral regulatory tasks — they are foundational. Every regulatory pathway, every market authorization, every post-market obligation connects back to what you put on your label and how you identify your device. The manufacturers that treat labeling as a strategic discipline — investing in robust processes, master data management, and cross-functional review — consistently experience fewer regulatory delays, fewer enforcement actions, and more efficient global market access.

The UDI system, while complex to implement, delivers real value: better traceability, more effective recalls, improved adverse event reporting, and the eventual integration of device identity into clinical outcomes data. The investment in doing it right pays dividends far beyond mere compliance.

Start with a thorough gap assessment against the requirements outlined in this guide. Build your processes around the most stringent requirements you face (typically the EU MDR), and adapt downward for other markets. And treat every piece of labeling — from the physical label to the website — as what the FDA says it is: part of your device's regulatory identity.