Medical
Devices
One of the most technically complex FDA categories. Device regulation depends entirely on classification — and classification determines everything: the pathway, the cost, the timeline, the data required, and what you can legally claim on your label. Covers the Class I/II/III system in depth, the 510(k) premarket notification process step by step, PMA approval for Class III devices, De Novo for novel devices, UDI requirements, establishment registration and device listing, the Quality System Regulation, device labeling, and post-market surveillance obligations.
What Is a Medical Device Under FDA Law
Under 21 U.S.C. § 321(h), a medical device is defined as an instrument, apparatus, implement, machine, contrivance, implant, in vitro reagent, or other similar article that is intended for use in the diagnosis, cure, mitigation, treatment, or prevention of disease — or intended to affect the structure or function of the body — and that does not achieve its primary intended purpose through chemical action within or on the body, and is not dependent upon being metabolized.
That final clause — "does not achieve its primary intended purpose through chemical action" — is the fundamental distinction between a device and a drug. A scalpel cuts tissue through physical force. A blood pressure cuff measures pressure mechanically. An X-ray machine emits radiation. None of these rely on chemical reactions in the body. A drug, by contrast, achieves its effect through pharmacological, immunological, or metabolic action.
This distinction matters for classification, but breaks down for combination products — products that combine drug and device elements (drug-eluting stents, autoinjectors, prefilled syringes). For those, the Office of Combination Products determines which center has primary jurisdiction based on primary mode of action.
The "Mechanism of Action" Test for Device vs. Drug
Ask: How does this product achieve its primary intended purpose?
- Physical, mechanical, thermal, electrical, or acoustic action → Likely a device
- Chemical reaction within or on the body; metabolized for its effect → Likely a drug
- Both mechanisms equally important → Combination product → Request for Designation with OCP
- Software making a diagnostic decision using patient-specific data → Software as a Medical Device (SaMD) — regulated as a device under CDRH
The Three-Class Classification System
The Medical Device Amendments of 1976 created a risk-based classification system with three classes. Every device type has a specific 3-character product code assigned by CDRH, and that code determines the class, the required pathway, and applicable special controls. Before advising any device client, finding the correct product code is always the first step.
Selecting the Right Pathway — The Decision Framework
Before filing anything with FDA, you must determine which pathway applies. The pathway decision is sequential — work through these questions in order.
The 510(k) — America's Most Common Device Pathway
The 510(k) Premarket Notification is the pathway for most Class II medical devices entering the U.S. market. The name comes from Section 510(k) of the FD&C Act, which requires manufacturers to notify FDA 90 days before marketing a device that is substantially equivalent to a legally marketed predicate.
The single most important concept: 510(k) clearance is NOT approval. A cleared device has been determined to be substantially equivalent to a predicate — meaning it is as safe and effective as that predicate. FDA has not independently concluded the device is safe and effective. It has concluded it is comparable to something already on the market. This distinction matters for what you can say about the device in marketing.
What "Substantially Equivalent" Means in Practice
A device is substantially equivalent to a predicate if it has:
- The same intended use as the predicate device, AND
- The same technological characteristics as the predicate, OR
- Different technological characteristics but those differences do not raise different questions of safety and effectiveness, AND the device is at least as safe and effective as the predicate
The 510(k) Process — Step by Step
• Biocompatibility (ISO 10993 series) — for any device that contacts the patient
• Electrical safety and EMC (IEC 60601 series) — for powered devices
• Software validation (FDA guidance on software in medical devices) — for any device containing software
• Sterility and bioburden — for sterile devices
• Shelf life / packaging validation — for devices with expiry dates
• Performance testing — demonstrating the device meets claimed specifications
• Dimensional and materials testing — confirming physical characteristics match predicate
1. Administrative information (device name, applicant, contact, product code)
2. Device description (comprehensive technical description with drawings/photos)
3. Substantial equivalence comparison (predicate identification + comparison table)
4. Proposed labeling (device label and IFU in final or draft form)
5. Sterility and biocompatibility (if applicable)
6. Performance testing (all bench test reports, standards compliance)
7. Software documentation (if applicable — full Software Documentation per FDA guidance)
8. Biocompatibility (ISO 10993 evaluation and test reports)
9. Electrical safety and EMC (if applicable — IEC 60601 test reports)
10. Declaration of Conformity to standards (where applicable)
Not Substantially Equivalent (NSE): The device is not cleared. Options: (1) appeal the decision, (2) submit a new 510(k) with a different predicate, or (3) pursue De Novo if the device is novel and low-to-moderate risk.
Premarket Approval (PMA) — The Highest Bar
PMA is the most rigorous device review process — reserved for Class III devices that are life-sustaining, implantable, or present unreasonable risk if they fail. Unlike the 510(k) (which relies on predicate comparison), PMA requires the applicant to independently demonstrate that the device is safe and effective for its intended use through valid scientific evidence — typically clinical data from human subjects.
The IDE — Investigational Device Exemption
Before conducting significant risk device clinical studies in U.S. human subjects, manufacturers must obtain an IDE (Investigational Device Exemption) from CDRH. The IDE is the device equivalent of the IND for drugs. It allows the device to be shipped across state lines for clinical study purposes before it has been cleared or approved.
De Novo Classification — The Novel Device Pathway
The De Novo pathway was created to address a gap in the device classification system: novel devices that present low-to-moderate risk but have no valid predicate (so can't use 510(k)) and don't require the full PMA process. Before De Novo, these devices were often stuck — NSE on 510(k) with no viable alternative.
De Novo does two things: it classifies the device (creates a new Class I or Class II device type) AND it issues an order authorizing marketing. Crucially, once a device receives De Novo authorization, it becomes a legally marketed device that can serve as a predicate for future 510(k) submissions. This makes De Novo extremely valuable for first-movers in new device categories.
| Attribute | Detail |
|---|---|
| Eligibility | Novel device — no valid predicate exists in the 510(k) database or pre-1976 market. Device presents low-to-moderate risk. Not appropriate for devices that are life-sustaining or implantable (those go to PMA). |
| Submission | De Novo Request submitted through CDRH eSTAR, similar format to 510(k). Must include: device description, proposed classification, proposed special controls, risk analysis, performance testing, labeling. |
| Review Timeline | 150 days (total). FDA has 70 days to accept the submission; 150 days from acceptance for a decision. Clock stops during Additional Information periods. |
| Fee (FY2025) | ~$21,000 (same as standard 510(k)). Small business reduced fee: ~$5,250. |
| Outcome if Successful | FDA issues a De Novo authorization order — device is classified (typically Class II) and may be marketed. Establishes special controls that must be met. Creates a predicate that others can use for 510(k). |
| Strategic Value | First-mover advantage: if you win De Novo for a new device category, competitors must file 510(k)s citing your device as predicate — a significant competitive position. FDA often requires 510(k) filers to demonstrate they meet the same special controls you proposed. |
Device Establishment Registration and Device Listing
Every device establishment — whether a manufacturer, specification developer, repackager, relabeler, contract manufacturer, or distributor — must register with FDA annually and list its devices. These are two separate but related obligations.
Establishment Registration
Device Listing
Separately from establishment registration, every device you market must be listed with FDA through FURLS. Device listing must include: device name, product code, FDA submission type (510(k) number, PMA number, or exemption status), and whether the device is currently being marketed. Listings must be updated within 30 days of any significant change.
UDI — Unique Device Identification
The Unique Device Identification (UDI) system, mandated under 21 CFR Part 830, requires most medical devices to bear a unique identifier on their labels. UDI data must also be submitted to FDA's Global Unique Device Identification Database (GUDID), which is publicly accessible. The UDI system creates a universal, standardized way to identify specific device versions/models in post-market surveillance, adverse event reports, and recalls.
GUDID — Global UDI Database
Every device DI must be submitted to FDA's GUDID before the device is distributed. GUDID is publicly searchable — hospitals, clinicians, and patients can look up any registered device. Mandatory GUDID data elements include: device description, brand name, company name, version/model, number of units in base package, sterile indicator, expiration date use indicator, and applicable standards.
UDI Compliance Deadlines by Class: Class III devices: required since September 2014. Class II devices: since September 2016. Class I and unclassified devices: since September 2022. Implantable devices additionally require UDI to appear on device itself (not just label). If your device is not UDI-compliant, it is misbranded under 21 CFR § 801.20.
Quality System Regulation (QSR) — 21 CFR Part 820
The Quality System Regulation is the device GMP framework — the legal minimum quality standards for device manufacturing. Unlike drug GMP, QSR includes design controls (for drugs, design is not regulated by FDA) — making it a more comprehensive quality management system. QSR is currently being harmonized with ISO 13485 (the international medical device quality standard), with the updated rule (Device Quality System Regulation or DQSR) incorporating ISO 13485 requirements.
Device Labeling Requirements
Device labeling is governed by 21 CFR Part 801 and must comply with the requirements applicable to the device class. All required labeling elements must be in English (though additional languages are permitted). The intended use on the label must match exactly what was cleared or approved in the 510(k) or PMA — any deviation is misbranding and potentially off-label promotion.
| Required Element | Regulation | Key Requirement | Common Error |
|---|---|---|---|
| Device Name | 21 CFR § 801.3 | Common or usual name of the device; or if none, established name. Trade name may be used in addition but not instead of. Must be prominent on principal display panel. | Using trade name only without the common device name (e.g., "XYZ Pro" without "Infusion Pump") |
| Manufacturer Name & Address | 21 CFR § 801.1 | Name and place of business of manufacturer, packer, or distributor. For foreign manufacturers: must include country of manufacture. "Manufactured by," "Distributed by," or "Imported by" qualifying phrases acceptable. | Missing country of manufacture for imported devices; using P.O. box without physical address |
| Quantity of Contents | 21 CFR § 801.7 | Net quantity of contents by numerical count, weight, or measure. For packaged devices: number of units per package. | Ambiguous quantity statements; not specifying components included in kit packaging |
| Intended Use / Indications | 21 CFR § 801.4 | Must match the cleared or approved intended use exactly. Cannot add conditions, expand patient populations, or include unapproved uses. Any deviation = misbranding + potential off-label promotion violation. | Expanding cleared use in IFU or marketing materials; claiming uses not in cleared 510(k) |
| Directions for Use (IFU) | 21 CFR § 801.5 | Adequate directions for use for the device's intended purpose. Must be written in plain language. For complex devices: full Instructions for Use (IFU) required, which may be a separate document packaged with the device. | Overly technical IFUs that layperson users cannot follow; IFUs that reference cleared use but describe broader applications |
| UDI | 21 CFR § 801.20 | Both human-readable (HRI) and machine-readable (barcode/RFID) format required on device label and carton. Must be submitted to GUDID before distribution. Implantable devices must also have UDI on the device itself. | Missing machine-readable format; GUDID not updated before distribution; incorrect DI submitted to GUDID |
| Warnings and Precautions | 21 CFR § 801.109 | All required warnings from the cleared/approved submission must appear. ISO 15223-1 symbols may be used on labels if accompanied by English equivalents (or if the symbol is universally recognized). | Using ISO symbols without English equivalents; omitting warnings that appeared in the cleared 510(k) labeling |
| Expiration Date / Use By Date | 21 CFR § 801.129 | Required for devices with a defined shelf life. Format must be unambiguous — month and year minimum (e.g., "2026-06" or "Jun 2026"). Cannot use date formats that could be misread (e.g., 06/26 could be June 2026 or the 6th day of 2026 in some formats). | Ambiguous date formats; expiry date not tied to validated shelf life study |
Post-Market Surveillance Obligations
Getting a device cleared or approved is only the beginning. Post-market obligations for devices are substantial and permanent — they include adverse event reporting, recalls, post-market studies, and periodic safety reporting for PMA devices.
Software as a Medical Device (SaMD)
Software as a Medical Device is one of the fastest-growing and most actively regulated areas in medical device law. SaMD is software intended to be used for one or more medical purposes without being part of a hardware medical device.
• Software that analyzes ECG data and identifies atrial fibrillation
• Clinical decision support software that uses patient-specific data to recommend a specific drug dose
• Software that controls an insulin pump
• Software that analyzes retinal images to detect diabetic retinopathy
Key test: Does it make or support a clinical decision specific to an individual patient? Does it analyze medical images or signals? Does it drive or inform treatment?
• Administrative software (scheduling, billing, claims processing)
• Electronic health records (EHR) — data display only, no clinical decision
• Clinical decision support software that: displays, analyzes, or prints medical information AND is not intended to replace clinical judgment AND provides transparent basis for recommendations that clinicians can independently review
FDA's 2017 final guidance "Clinical Decision Support Software" defines the boundary between regulated and non-regulated CDS.
AI/ML in Medical Devices — Rapidly Evolving: FDA has issued guidance on AI/ML-based Software as a Medical Device and continues to develop the regulatory framework for adaptive AI that "learns" from new data after deployment. If you have clients developing AI diagnostic tools, imaging analysis software, or clinical decision support using machine learning — this is an area requiring specialized regulatory expertise and very close monitoring of FDA guidance updates.
From Factory in Seoul to U.S. Pharmacy Shelf — The Complete Regulatory Journey
A South Korean medical device company manufactures a validated automatic blood pressure monitor (upper arm cuff). They want to sell it in U.S. pharmacies. Here is the complete regulatory sequence:
- Step 1 — Classification: Search CDRH Product Classification Database for "blood pressure monitor" → Product code: DQD → Class II device → 510(k) required → Subject to special controls including performance standard ANSI/AAMI SP10
- Step 2 — Q-Sub Meeting: Submit a Q-Sub to CDRH confirming: (a) the correct product code, (b) the predicate device they intend to use, (c) whether blood pressure accuracy testing data from their clinical validation study will be acceptable, and (d) whether labeling translations are needed. FDA responds in writing within 75 days — free.
- Step 3 — Testing: Conduct blood pressure accuracy validation per ANSI/AAMI SP10 (or equivalent ISO 81060-2) in clinical subjects — typically 85 subjects, comparing device readings to auscultatory reference. Conduct electrical safety testing per IEC 60601-1 and EMC testing per IEC 60601-1-2. Conduct biocompatibility testing on any patient-contacting components (cuff material, rubber bulb). Validate software per FDA software guidance.
- Step 4 — 510(k) Preparation: Build the eSTAR submission with all test reports, device description, predicate comparison, proposed labeling (including IFU in English), and UDI information.
- Step 5 — Register Establishment: Register the Seoul manufacturing facility as a foreign device establishment via FURLS. Pay foreign establishment registration fee (~$6,800). Receive EI number.
- Step 6 — Submit 510(k) and Pay Fee: Submit via ESG. Pay ~$21,000. Receive 510(k) number and acceptance decision within 15 days. 90-day review clock begins.
- Step 7 — UDI Setup: Obtain GS1 Company Prefix. Assign DI to the blood pressure monitor. Submit DI to GUDID before first distribution. Label device with both HRI and DataMatrix barcode.
- Step 8 — Device Listing: Upon 510(k) clearance, list the device in FURLS, linking the listing to the 510(k) number and the EI of the manufacturing facility.
- Step 9 — QSR Implementation: Ensure the Seoul facility's quality management system meets 21 CFR Part 820 requirements — design controls, CAPA, complaint handling, MDR procedures. This should be done before the pre-clearance inspection, not after.
- Medical devices are defined by their mechanism of action — physical, mechanical, or electrical, not chemical or metabolic. This distinction separates devices from drugs and determines which center (CDRH vs. CDER) has jurisdiction, including for combination products.
- The three-class system (Class I: general controls, ~47%; Class II: special controls + 510(k), ~43%; Class III: PMA, ~10%) determines the entire regulatory pathway. Always confirm classification using CDRH's Product Classification Database before advising any device client.
- 510(k) clearance is NOT approval. It is a finding of substantial equivalence to a predicate device. You can say "FDA-cleared" — not "FDA-approved." Only PMA devices are "FDA-approved." Using "approved" for a cleared device is a misbranding violation and a common marketing error.
- The Q-Submission (Pre-Sub) program is the most underutilized and most valuable tool in device regulatory strategy. It is free, produces written FDA guidance within 75 days, and can confirm your predicate, testing requirements, and submission format before you spend $21,000+ on a filing. Always recommend Q-Sub before any significant submission.
- UDI is mandatory for virtually all devices. Both human-readable and machine-readable formats required on all labels. GUDID submission required before distribution. Non-compliant devices are misbranded. Class I compliance deadline was September 2022 — check every device client's UDI compliance status.
- The Quality System Regulation (21 CFR Part 820) is more comprehensive than drug GMP because it includes design controls — a requirement unique to devices. The Design History File (DHF), Device Master Record (DMR), and Device History Record (DHR) are the three foundational quality documents FDA inspectors review. CAPA records are always among the first documents requested.
- Software as a Medical Device (SaMD) is regulated as a device when it makes or supports patient-specific clinical decisions. AI/ML diagnostic tools, imaging analysis software, and clinical decision support using patient data are device-regulated. General wellness apps, administrative software, and EHR display functions are not regulated. This is one of the fastest-evolving areas in device regulation.
Need medical device registration or 510(k) strategy support?
Regovant supports device establishment registration, device listing, UDI setup, GUDID submission, and regulatory strategy for international device manufacturers entering the U.S. market.