Medical device labeling is where regulatory requirements become physical reality. A label that fails — a UDI carrier that doesn't decode correctly, an IFU missing a required language version, a symbol drawn from the wrong ISO standard — isn't a document problem. It's a product problem, with traceability, safety, and compliance consequences that can't be corrected after the device ships.
This guide covers what medical device labels must contain under FDA and EU MDR requirements, what UDI requires across every packaging level, when electronic IFU is permitted and when a physical copy is required, and what ISO 15223-1:2021 symbols devices are expected to carry. The final sections cover where labeling errors actually enter the process and what a defensible review process looks like at the verification stage.
Scope note: this guide covers device labeling requirements specifically — what must appear on the label, and how to verify it. It does not cover the regulatory submission process, conformity assessment pathways, clinical evaluation, or device classification.
FDA Medical Device Labeling Requirements
US medical device labeling is governed by Title 21 of the Code of Federal Regulations, primarily 21 CFR Part 801. Part 801 applies to all devices regulated by FDA and establishes the content and format requirements that apply regardless of device class.
Required content under 21 CFR Part 801: The device label must include the device name — including any trade name and recognized common or usual name — the name and place of business of the manufacturer, packer, or distributor, the net quantity of contents where applicable, and any required warnings, precautions, or contraindications. For prescription devices, 21 CFR 801.109 adds specific requirements including a statement restricting the device to sale by or on the order of a licensed practitioner.
Directions for use are required unless the device is exempt or the directions would be impractical on a label of the required size. Where directions are not on the device label itself, they must appear in the Instructions for Use packaged with the device.
UDI under 21 CFR Part 801 Subpart B: FDA's Unique Device Identification system requires that most medical devices bear a UDI on the device label and on the label of each higher-level package. The UDI consists of two components: the Device Identifier (UDI-DI), which identifies the device model and labeler, and the Production Identifier (UDI-PI), which identifies the specific production unit through lot, serial, manufacturing date, or expiry date as applicable to the device class and use.
FDA requires the UDI to be both human-readable (HRI) and machine-readable in Automatic Identification and Data Capture (AIDC) format. Acceptable AIDC formats include linear barcodes and two-dimensional symbols such as DataMatrix. Implantable devices and certain Class III devices must carry both a UDI-DI and a UDI-PI in AIDC format.
Device UDIs must be submitted to the Global Unique Device Identification Database (GUDID), maintained by FDA. The issuing agency — GS1, HIBCC, or ICCBBA for blood products — must be FDA-accredited. New device labeling must include UDI from first market placement.
EU MDR Labeling Requirements
Medical device labeling in the European Union is governed by Regulation (EU) 2017/745 (the Medical Device Regulation), which has applied fully since May 2021. The labeling requirements are set out in Annex I, Chapter III, Section 23.
Required content under MDR Annex I Section 23: The device label must carry: the device name, model number, trade name, or common name; the name, registered trade name or trademark, and registered address of the manufacturer; for non-EU manufacturers, the name and address of the EU Authorised Representative; the country of manufacture where this would help identify the manufacturer; the UDI carrier; the lot or batch number, serial number, software version, catalogue number, or applicable code; an unambiguous indication of the manufacturing date or expiry date; the device's intended purpose where not immediately obvious; the route of administration where applicable; statements about incorporated medicinal substances, human blood derivatives, or cells of animal origin where applicable; CE marking and the four-digit notified body identification number where conformity assessment involved notified body participation; any special storage or handling conditions; and any warnings or precautions required.
Language requirements: MDR requires that device labels and IFUs be provided in the official language(s) of the EU member state(s) in which the device is made available. A multilingual label covering all target markets is compliant, provided all required languages are present and accurate.
In practice, this creates a persistent verification challenge. An update to the label in one language must be propagated correctly to every other language version before the label is approved for release. Character-level comparison across all language versions — not sequential review of each version independently — is the only reliable method for catching propagation failures. A review that signs off each language version in isolation can miss an error that only becomes visible when versions are compared against each other.
Authorised Representative: For manufacturers outside the EU, the name and address of the EU Authorised Representative must appear on the label. This is a legally required data point that is distinct from the manufacturer's own address — carrying the manufacturer's address alone is not compliant. When a manufacturer changes its Authorised Representative arrangement, the device label must be updated to reflect the current AR before the device is placed on the EU market.
UDI — What the Requirement Actually Covers
The UDI obligation under MDR is set out in Articles 27, 28, and 29 and Annex VI, Part C. It is one of the most operationally complex MDR requirements because it applies at every level of packaging — not just the unit label.
The two-part structure: The UDI consists of a Device Identifier (UDI-DI) and a Production Identifier (UDI-PI). The UDI-DI identifies the specific device model and packaging configuration — it changes when the device description, labeler, or packaging configuration changes, and each packaging level (unit, intermediate, case) has its own UDI-DI. The UDI-PI identifies the specific production unit: lot or batch number, serial number, manufacturing date, expiry date, or software version as applicable to the device type.
What must appear on the label: The UDI carrier must include both the AIDC representation — DataMatrix for implantable devices and Class III devices; DataMatrix or linear barcode for other device classes — and the HRI (human-readable interpretation) alongside it. The HRI is the text string encoding the same information as the AIDC symbol and allows visual verification that the machine-readable and human-readable content match.
The consistency requirement across all packaging levels: MDR requires the UDI to appear on the device or its sterile barrier system, on the sales packaging, and on all higher levels of packaging. Each level carries its own UDI carrier. The consistency obligation is the specific requirement that generates the most non-conformities in practice: all packaging levels must carry accurate, consistent UDI information, and the AIDC must encode exactly the same data as the HRI alongside it.
The error pattern is predictable. A label revision updates the UDI-DI at unit level — because the packaging configuration or catalogue number changed — but intermediate packaging and case labels are not updated in the same revision cycle. Or the HRI is updated to reflect the new value but the DataMatrix still encodes the original. Neither error is visible in a visual review of a single packaging level; it only surfaces when all levels are compared systematically against the approved specification.
EUDAMED registration: Device UDI-DIs must be registered in the EUDAMED UDI and device registration module, which became mandatory on 28 May 2026 per Commission Decision (EU) 2025/2371 and the transitional provisions of Regulation (EU) 2024/1860. From that date, new MDR and IVDR devices must be registered in EUDAMED before their first unit is placed on the EU market. Devices already on the market before 28 May 2026 and continuing to be marketed must be registered by 27 November 2026 — twelve months from the Official Journal publication date.
For IVD devices, parallel requirements apply under Regulation (EU) 2017/746 (IVDR), with the same EUDAMED registration obligations. The Vigilance and post-market surveillance modules of EUDAMED remain under development and are not yet mandatory.
IFU Requirements — Electronic and Print
Instructions for Use are a labeling element with their own specific requirements under MDR Annex I Section 23.4. The IFU must accompany every device unless the device is simple enough that safe use can be ensured without one — a limited exemption that applies primarily to the lowest-risk device categories.
Required IFU content: The IFU must include: the intended purpose of the device; the intended users and any required qualifications or training; device performance characteristics and limitations; contraindications; warnings and precautions; information on residual risks and side effects; installation and commissioning instructions; operating instructions; cleaning, disinfection, and maintenance instructions; a reference to the device model(s) the IFU applies to; and the date of issue or latest revision. The IFU must be in the official language(s) of each EU member state in which the device is made available — the same language requirement as the device label.
Electronic IFU: Commission Implementing Regulation (EU) 2021/2226 permits electronic delivery of IFUs — eIFU — instead of or alongside paper IFUs for specified device categories. eIFU is permitted where the device is intended for use by professional users rather than lay users, and where the device is not a single-use device intended for individual patients. Where eIFU is used, the physical device label must carry a URL or other means of accessing the eIFU. Paper IFUs must still be provided on request at no additional cost.
For devices intended for home use, for implantable devices, and where a paper IFU would be a patient safety safeguard, the paper IFU requirement is not waived. Manufacturers implementing eIFU should verify which device categories their products fall into under the Regulation before removing printed IFUs from packaging.
For FDA-regulated devices, 21 CFR 801.109 covers prescription device labeling and directions for use. FDA has a separate eIFU program under 21 CFR 801.150, which applies to specific device types and requires prior FDA authorization for eIFU use.
The IFU verification challenge: IFU documents are revised frequently — for regulatory updates, new contraindications, changes to supported configurations, corrections to translated content. Each revision creates the same risk as any other label revision: a change made to the current version rather than verified against the approved master, and an unintended change — a section missing after a format conversion, a translated paragraph that has drifted from the source, a warning present in version N but absent in version N+1 — that survives into the released version without being detected. IFU errors are a documented contributor to medical device recalls and field safety corrective actions, precisely because the consequences of incorrect instructions reach users at the point of clinical use.
ISO 15223-1:2021 — Symbols on Medical Device Labels
ISO 15223-1:2021 defines internationally recognized graphical symbols for use on medical device labels and in IFUs. MDR permits these symbols to replace text descriptions on device labels, on the condition that a legend or glossary is available to users who are not familiar with the symbols — typically in the IFU.
Why the 2021 revision matters: ISO 15223-1:2021 supersedes the 2016 version and introduced additions and revisions to the symbol set. Device manufacturers who updated their labels for MDR compliance in 2021 or 2022 should confirm that their label artwork references ISO 15223-1:2021 specifically, not the previous version. A label that uses a symbol defined under the 2016 standard but that has been revised or superseded in the 2021 edition constitutes a labeling non-conformity.
Commonly used symbols: The symbols appearing most frequently on medical device labels include: the manufacturer (building icon), the EU Authorised Representative, date of manufacture, use-by date, catalogue number, lot number, serial number, single-use indicator, sterile with method identifier, keep dry, keep away from sunlight, fragile — handle with care, and temperature range. Each symbol carries a specific reference number in the ISO standard; that number should be traceable from the artwork specification to the approved and released label.
Why symbol verification requires graphics-level comparison: Symbol accuracy cannot be verified by text comparison alone. A symbol at slightly the wrong size, with a missing element, or replaced by a visually similar but incorrect symbol does not appear in a text comparison report. It requires a graphic comparison pass against the artwork file in which the symbol was approved — pixel-level verification that each symbol in the released artwork matches the symbol in the approved master.
Where Device Labeling Errors Enter the Process
Analysis of FDA Class I and II device recall data and notified body inspection findings identifies a consistent set of labeling error origins. These are not the result of careless teams — they are the result of processes that rely on human attention at points where systematic comparison would be more reliable. Source: FDA recall database; NCBI StatPearls — medical device recalls.
UDI inconsistency across packaging levels. A label update changes a packaging configuration or catalogue reference that alters the UDI-DI at unit level. Intermediate packaging and case labels are not updated in the same revision cycle. The inconsistency passes visual review at unit level because the unit label is correct — it only surfaces when all three packaging levels are compared against the approved specification, or when a EUDAMED registration cross-check is run.
ISO symbol version error. A device label carries a symbol from ISO 15223-1:2016 that has been revised in the 2021 version. The symbol looks visually similar to the current version in a casual review. It is not caught by text comparison and is not obvious in a visual check of a complex label that carries many symbols.
IFU language version not propagated. An IFU update — a revised contraindication, a corrected torque or dosage specification, a new warning — is applied to the source-language master. Translated versions are not updated in the same revision cycle. The inconsistency does not surface in a review of any individual language version; it surfaces only when versions are compared against each other and against the master.
Authorised Representative information outdated. A change in AR arrangement is processed administratively but the label artwork is not updated before the next production run. The device ships carrying the previous AR's contact details, constituting a labeling non-conformity under MDR Annex I Section 23.
Comparison against the wrong baseline. The final comparison before release is run against the previous approved version rather than against the approved master specification. This is a delta review — it shows what changed since last time — but it does not show whether the complete document matches the current specification. An error introduced earlier in the revision history, or a change that entered informally outside the formal revision process, is invisible in a delta review.
Building a Defensible Device Label Review Process
The verification layer sits between the final artwork file and the print vendor. It is the step that confirms what is about to be released matches what was approved — across every requirement covered in this guide.
A controlled master document. The approved label specification, IFU, and UDI specification are locked as the master source. Every comparison runs against this master, not against the previous version. A delta review answers "what changed from last time?" — a master comparison answers "does this document match the approved specification?" The second question is the one that matters at release.
Text comparison across all language versions. Every language version of the device label and IFU is compared character by character against the master. Language-independent comparison means the reviewer does not need to read the language being checked — the comparison detects every deviation from the master regardless of script or character set.
Graphic comparison for symbols and layout. ISO symbol accuracy, logo placement, layout integrity, and any graphic element carrying regulatory information is verified at the pixel level. This is the only reliable method for detecting symbol version errors and layout deviations that text comparison cannot surface.
UDI verification against the approved specification. The UDI carrier on every packaging level is decoded, the data structure checked against the approved GTIN and production identifier specification, and the barcode or DataMatrix graded against ISO quality standards. The HRI is verified against the AIDC output.
An audit trail that meets 21 CFR Part 11 and EU GMP Annex 11. Every comparison session is timestamped, version-linked, and electronically signed. The audit trail documents what was compared, against which master, by whom, and what deviations were identified and resolved. It is available for inspection without reconstruction or manual assembly from multiple sources.
Content Compare handles all four comparison types in a single validated session — text, graphic, UDI and barcode, and Braille where applicable — producing one structured deviation report and one audit trail into QA sign-off. The platform is validated to GAMP 5 and 21 CFR Part 11 standards, with the validation package provided with each release.
This guide reflects regulatory requirements as of June 2026. EU MDR, FDA UDI, eIFU, and EUDAMED requirements are subject to ongoing guidance updates — verify against the current regulatory text before acting on specific requirements. The EUDAMED Vigilance and post-market surveillance modules are not yet mandatory and will follow a separate implementation timeline.
See what device label verification looks like in practice. InformaIT can run your own label or IFU through a live comparison in 30 minutes — your documents, no slides. Request a demo at informait.com.
