FDA Class II Medical Devices: The Complete Guide to Regulations, 510(k), and Special Controls

What Is a Class II Medical Device?

A Class II medical device is a device for which general controls alone are insufficient to provide reasonable assurance of safety and effectiveness, and for which sufficient information exists to establish special controls to provide that assurance. This definition comes directly from Section 513(a)(1)(B) of the Federal Food, Drug, and Cosmetic Act (FD&C Act) and is implemented through 21 CFR Parts 862 through 892.

Class II devices represent the largest single category in the FDA's classification system. Approximately 43% of all classified medical device types fall into Class II, covering roughly 750 of the more than 1,700 generic device types recognized by the FDA. These devices occupy the middle tier of the FDA's risk-based framework — they pose moderate risk to patients or users, enough that basic general controls need reinforcement, but not so much that the device demands the full clinical evidence package required for Class III premarket approval (PMA).

The defining regulatory characteristic of Class II is the requirement for special controls in addition to general controls. Every Class II device has a specific set of special controls established either in the classification regulation itself (the relevant section of 21 CFR), in a standalone Class II Special Controls Guidance Document, or in a De Novo decision summary that created the classification. Understanding and complying with these special controls is the single most important regulatory task for any Class II device manufacturer.

How the FDA Determines a Device Is Class II

The FDA assigns a device to Class II when two conditions are met simultaneously:

1. General controls alone are insufficient — The risk profile of the device is such that the baseline regulatory requirements (registration, listing, GMP, labeling, MDR) are not enough to provide reasonable assurance of safety and effectiveness
2. Sufficient information exists to establish special controls — There is enough knowledge about the device type, its risks, and its performance characteristics that the FDA can define specific additional controls (performance standards, labeling requirements, post-market studies, etc.) that, combined with general controls, do provide reasonable assurance

If general controls alone are sufficient, the device is Class I. If neither general controls nor special controls are sufficient — typically because the device sustains life, is implanted long-term, or presents a potential unreasonable risk — the device is Class III and requires premarket approval (PMA) with clinical evidence.

This classification determination is made either through the original classification panels established after the 1976 Amendments, through rulemaking (reclassification), or through the De Novo process for novel devices. In every case, the determination is device-type-specific, not manufacturer-specific. All devices of the same type share the same classification regardless of who makes them.

Legal Basis: Where Class II Lives in the Regulations

The three-class system was established by the Medical Device Amendments of 1976, which amended the FD&C Act. The relevant statutory provisions are:

• Section 513(a)(1)(B) of the FD&C Act — defines Class II and the concept of special controls
• Section 510(k) of the FD&C Act — establishes the premarket notification requirement for most Class II devices
• Section 513(f)(2) of the FD&C Act — the De Novo classification pathway, which can classify novel devices into Class II
• Section 514 of the FD&C Act — authorizes the FDA to establish performance standards and recognize consensus standards for Class II devices
• 21 CFR Parts 862–892 — the classification regulations organized by medical specialty panel, where each device type's class, special controls, and exemption status are codified
• 21 CFR Part 807, Subpart E — the procedural requirements for 510(k) premarket notifications
• 21 CFR Part 860 — the general framework for medical device classification, including procedures for reclassification and De Novo

Practical tip: When someone refers to a device's "classification regulation," they mean the specific section of 21 CFR that describes the device type. For example, 21 CFR 870.2700 is the classification regulation for pulse oximeters. That regulation tells you the device is Class II, identifies the applicable special controls, and indicates whether the device is 510(k) exempt. Always read the actual regulation text — it is the authoritative source.

Class II by the Numbers

To put Class II in perspective:

• ~750 generic device types are classified as Class II (out of approximately 1,700 total)
• 43% of all classified device types fall into Class II
• The FDA clears approximately 3,000–3,500 510(k) submissions per year, and the vast majority of these are for Class II devices
• Over 1,450 AI/ML-enabled devices have been authorized through 2025, with approximately 97% classified as Class II
• Class II devices span all 16 medical specialty panels — no specialty is without Class II devices
• Several hundred Class II device types are 510(k) exempt, meaning they can be marketed without a premarket submission

General Controls: The Baseline for Every Medical Device

Before understanding what makes Class II unique, you need to understand general controls, because they apply to every Class II device just as they do to every Class I and Class III device. General controls are the foundation upon which special controls are built. Think of general controls as the floor — they set the minimum requirements for any device sold in the US, regardless of risk level. Special controls are the additional measures built on top of that floor for Class II devices.

General controls are defined in Sections 501 (adulteration), 502 (misbranding), 510 (registration and listing), 516 (banned devices), 518 (notification and other remedies), 519 (records and reports), and 520 (general provisions) of the FD&C Act. They include:

• Establishment registration (21 CFR Part 807) — Every domestic manufacturer, contract manufacturer, contract sterilizer, repackager/relabeler, specification developer, and initial importer must register their establishment with the FDA annually. Foreign manufacturers must also register and designate a US agent.
• Device listing (21 CFR Part 807) — Every device commercially distributed in the US must be listed with the FDA, including the product code, proprietary name, and marketing status.
• Quality System Regulation (21 CFR Part 820, transitioning to the Quality Management System Regulation under ISO 13485) — Manufacturers must maintain a quality system covering design controls, production and process controls, corrective and preventive action (CAPA), document controls, and records management. Unlike most Class I devices, Class II devices are not exempt from design controls.
• Labeling (21 CFR Part 801) — Devices must bear proper labeling including the manufacturer's name and address, adequate directions for use, and any required warnings or contraindications.
• Medical Device Reporting (MDR) (21 CFR Part 803) — Manufacturers must report to the FDA any event where their device may have caused or contributed to a death or serious injury, or where a malfunction would be likely to cause or contribute to a death or serious injury if it were to recur.
• Premarket notification — Unless specifically exempted, a device must receive FDA clearance or authorization before it can be legally marketed.
• Banned devices (21 CFR Part 895) — Certain device types are banned outright.
• Notification and repair/replacement/refund (Section 518 of the FD&C Act) — The FDA can require manufacturers to notify users and either repair, replace, or refund the purchase price of a device that presents an unreasonable risk.

Practical tip: The transition from QSR (21 CFR Part 820) to the Quality Management System Regulation (QMSR), which harmonizes FDA requirements with ISO 13485:2016, has a compliance date of February 2, 2026. If you are a Class II device manufacturer, you should already be operating under a quality system that conforms to both ISO 13485 and the QMSR. See our QSR to QMSR transition guide for detailed implementation steps.

Special Controls: What Makes Class II Different

Special controls are the regulatory requirements that distinguish Class II from Class I. The FD&C Act defines special controls as measures that, combined with general controls, provide reasonable assurance of the safety and effectiveness of the device. They are device-specific — different Class II device types have different special controls tailored to the particular risks those devices present.

Types of Special Controls

The FDA uses several categories of special controls. A given Class II device type may be subject to one or more of these:

1. Performance standards

These can be FDA-specific performance criteria written into the classification regulation or De Novo decision, or references to FDA-recognized consensus standards (e.g., ISO, IEC, ASTM, AAMI standards). Performance standards define the minimum testing and design criteria a device must meet.

Example: Pulse oximeters (21 CFR 870.2700, product code QKQ) must demonstrate accuracy performance per ISO 80601-2-61, which specifies SpO2 accuracy requirements (Arms) across a range of saturation levels and skin pigmentation types.

2. Specific labeling requirements

Beyond the general labeling rules in 21 CFR Part 801, special controls may mandate specific warnings, contraindications, patient information sheets, or instructions that must appear in the device labeling.

Example: Over-the-counter (OTC) pulse oximeters (product code QKQ) must include labeling that clearly states the device is not intended for use as the sole basis for clinical decision-making, and must provide information about factors that can affect accuracy (motion, nail polish, poor perfusion).

3. Premarket testing requirements

The special controls may specify exactly which bench tests, animal studies, or clinical data must be included in the premarket submission. These go beyond the general expectation of "adequate evidence" and spell out precisely what the FDA expects to see.

Example: Intervertebral body fusion devices (21 CFR 888.3080) require static and dynamic mechanical testing, wear testing, biocompatibility testing per ISO 10993, and specific imaging compatibility assessments.

4. Post-market surveillance requirements

Some Class II device types require ongoing data collection after the device is on the market — either through mandatory post-market studies, participation in patient registries, or periodic reporting.

Example: Metal-on-metal hip resurfacing devices have required post-market surveillance studies tracking metal ion levels and revision rates.

5. Patient registries

The FDA may require manufacturers to enroll patients receiving a device in a registry to track long-term outcomes across the installed base.

Example: Certain cardiovascular devices and orthopedic implants require participation in registries to collect real-world performance data.

6. Design restrictions

Special controls can restrict specific design characteristics — materials, energy levels, dimensions, or configurations — to mitigate known risks.

Example: Powered surgical instruments have energy output limits specified in their special controls to prevent tissue damage beyond the surgical site.

7. Class II Special Controls Guidance Documents

For many device types, the FDA publishes a standalone guidance document that functions as the special controls for that device. These guidance documents describe the specific testing, labeling, design, and performance requirements the FDA expects manufacturers to address.

Example: The "Full Field Digital Mammography System — Class II Special Controls Guidance" specifies detailed image quality requirements, phantom testing protocols, and quality control procedures specific to digital mammography systems.

Special Controls in Practice: A Worked Example

To make special controls concrete, consider a continuous glucose monitor (CGM) classified under 21 CFR 862.1355 (product code NFT, Class II). The special controls for this device type include:

1. Clinical performance testing — Accuracy studies demonstrating device performance compared to a laboratory reference method across the full glycemic range (40–400 mg/dL), including testing in populations with different skin tones, ages, and body compositions
2. Sensor biocompatibility — Testing per ISO 10993 for the sensor that is inserted subcutaneously, with particular attention to cytotoxicity, sensitization, and irritation given the multi-day wear period
3. Wireless communication validation — Testing of the Bluetooth or NFC communication link between the sensor and receiver/smartphone, including data integrity, latency, and performance under interference
4. Alarm/alert functionality — Validation that hypo- and hyperglycemia alerts function reliably with appropriate sensitivity and specificity
5. Labeling — Specific requirements for user instructions on sensor insertion, calibration (if required), interference substances (acetaminophen, ascorbic acid), and limitations of the device
6. Software validation — Documentation of the algorithm that converts raw sensor signals to glucose readings, including the training and validation data used
7. Sterilization — Validation of the sterilization method for the sterile sensor inserter

Each of these special controls addresses a specific risk associated with the device. Missing any one of them in your 510(k) submission would result in a deficiency letter or Additional Information (AI) request from the FDA reviewer.

How to Find the Special Controls for Your Device

Identifying the applicable special controls is one of the first regulatory tasks after classification. Here is the systematic approach:

1. Look up your product code in the FDA Product Classification Database at accessdata.fda.gov/scripts/cdrh/cfdocs/cfPCD/classification.cfm
2. Read the classification regulation — The product code page links to the CFR section (e.g., 21 CFR 870.2700). The regulation text identifies the class and typically references the applicable special controls in subsection (b)(2) or similar
3. Check for a guidance document — The product code page often lists applicable guidance documents. Also search the FDA Guidance Document Database for "Class II Special Controls" plus your device type
4. Check De Novo decision summaries — If your device type was created through De Novo, the decision summary document contains the special controls established for that classification. These are published on the FDA's De Novo database
5. Review the Total Product Life Cycle (TPLC) report — Accessible from the product code page, this report shows all historical submissions, recalls, and guidance documents associated with your product code

Practical tip: Do not assume the special controls listed in the CFR are the only requirements. FDA reviewers routinely expect compliance with FDA-recognized consensus standards relevant to your device type, even if those standards are not explicitly named in the classification regulation. Check the FDA Recognized Consensus Standards Database for your product code and plan your test matrix accordingly.

The 510(k) Pathway for Class II Devices

The 510(k) premarket notification is the primary regulatory pathway for Class II medical devices. It requires manufacturers to demonstrate that their device is substantially equivalent (SE) to a legally marketed predicate device — a device that was either on the market before May 28, 1976 (a "pre-amendment" device) or that has itself been cleared through 510(k) or classified through De Novo.

The FDA does not "approve" 510(k) devices. It "clears" them by making a finding of substantial equivalence. This distinction matters in regulatory communications, labeling, and investor presentations. Using "approved" instead of "cleared" in marketing materials or investor decks signals to experienced reviewers and regulators that you do not understand the regulatory landscape.

What Is Substantial Equivalence?

Substantial equivalence (SE) is the legal standard for 510(k) clearance. A new device is substantially equivalent to a predicate if it:

1. Has the same intended use as the predicate, AND
2. Has the same technological characteristics as the predicate, OR
3. Has different technological characteristics but the manufacturer can demonstrate that the differences do not raise new questions of safety and effectiveness, and the device is at least as safe and effective as the predicate

The SE determination is the intellectual core of a 510(k). It is not a rubber stamp. FDA reviewers critically evaluate whether the predicate is appropriate, whether the intended use comparison is valid, and whether any technological differences have been adequately addressed through testing.

Key nuances of the SE determination:

• Same intended use does not mean identical labeling. The intended use comparison is based on the general purpose of the device (e.g., "monitoring blood oxygen saturation"), not on every detail of the labeling. However, expanding the indications for use beyond what the predicate covers will raise questions.
• Technological differences are acceptable if justified. A new material, a different power source, a different algorithm, or a different form factor can all be acceptable if supported by performance data showing equivalent or better safety and effectiveness.
• The predicate must be legally marketed. A device that has been recalled, withdrawn, or never actually marketed cannot serve as a valid predicate. The FDA maintains databases you can use to verify predicate status.

Practical tip: Select your predicate device before you begin product development, not after. The predicate choice drives your entire regulatory strategy — your testing plan, your labeling scope, and your SE argument. Search the 510(k) database for recently cleared devices under your product code, review their 510(k) summaries, and choose a predicate whose intended use and technological characteristics most closely match your device. The FDA generally prefers predicates that are recent — ideally cleared within the last 10 years — because older predicates may reflect outdated technology and performance standards. Using a very old predicate can invite additional scrutiny about whether the comparison is still meaningful.

Intended Use vs. Indications for Use

A critical distinction in the 510(k) process — and one that trips up many first-time submitters — is the difference between intended use and indications for use. These terms are related but legally distinct:

• Intended use is the general purpose of the device — the broad reason it exists. For example, "monitoring arterial blood oxygen saturation and pulse rate."
• Indications for use are the specific clinical scenarios, conditions, patient populations, or body parts for which the device is intended. For example, "for spot-checking and continuous monitoring of functional arterial oxygen saturation (SpO2) and pulse rate in adult and pediatric patients in hospitals and clinics."

The intended use is what the FDA compares to the predicate for substantial equivalence. The indications for use (documented on FDA Form 3881) provide the clinical context. You can have the same intended use as a predicate while having slightly different indications for use — but the narrower your indications, the narrower your marketing claims, and the broader your indications, the more data the FDA may require to support them.

Getting this distinction wrong is one of the most common reasons for AI (Additional Information) letters and RTA holds. Define both statements precisely, review them against your predicate's cleared indications (available in the predicate's 510(k) summary), and ensure consistency across every section of your submission — the Form 3881, device description, labeling, and performance testing sections.

The Three Types of 510(k)

The FDA offers three types of 510(k) submissions, each suited to different situations:

Traditional 510(k)

This is the standard submission type and the most commonly used. The manufacturer provides a complete submission including device description, intended use, predicate comparison, performance testing data, labeling, and the substantial equivalence argument. There is no reliance on guidance documents or recognized standards as a substitute for the technical content.

• When to use: When your device has meaningful differences from the predicate that require detailed discussion and supporting data
• Typical content volume: 200–1,000+ pages depending on device complexity
• Review timeline: FDA decision goal is 90 FDA days (approximately 108–142 calendar days, accounting for hold times)

Special 510(k)

A Special 510(k) is an expedited pathway available when the manufacturer is modifying its own legally marketed device (not a competitor's device) and the modification is adequately addressed through design controls. The submission includes a summary of the design control process, a risk analysis showing the modification does not adversely affect safety or effectiveness, and verification/validation summaries. The key feature is reliance on the manufacturer's own design control documentation rather than full performance testing submissions.

• When to use: When modifying your own previously cleared device and the changes are well-characterized through your design control process
• Typical content volume: 50–200 pages
• Review timeline: FDA goal is 30 FDA days

Abbreviated 510(k)

An Abbreviated 510(k) allows the manufacturer to rely on FDA guidance documents, special controls, or recognized consensus standards to streamline the submission. Instead of providing full test reports, the submitter can reference conformance to a recognized standard through a Declaration of Conformity and provide a summary rather than full data.

• When to use: When applicable FDA guidance documents or recognized consensus standards exist and your device fully conforms to them
• Typical content volume: 100–300 pages
• Review timeline: FDA decision goal is 90 FDA days

Key Components of a 510(k) Submission

Every 510(k) must be submitted electronically using the eSTAR (electronic Submission Template And Resource) format through the CDRH Customer Collaboration Portal. As of October 1, 2023, eSTAR is mandatory for all 510(k) submissions. The eSTAR template walks you through each required section:

Section	Content
Cover letter	Submission type, submitter information, device identification
Indications for use	Precise statement of the device's clinical indications (using the FDA Form 3881)
510(k) summary or statement	Public summary of the SE determination, or statement that information will be made available upon request
Device description	Technical specifications, materials, components, operating principles, comparison to predicate
Substantial equivalence comparison	Side-by-side comparison to predicate on intended use, technological characteristics, and performance
Proposed labeling	Draft labels, instructions for use (IFU), packaging
Sterilization	If applicable: sterilization method, validation data, shelf-life testing
Biocompatibility	If applicable: ISO 10993-1 risk assessment and testing per the biocompatibility matrix
Software documentation	If applicable: software level of concern (now replaced by documentation level per 2023 guidance), software description, hazard analysis, SBOM
Electromagnetic compatibility (EMC)	If applicable: IEC 60601-1-2 testing
Performance testing	Bench testing, animal testing, or clinical data demonstrating equivalence
Clinical data	If required by special controls or to support equivalence for a different technological characteristic

Practical tip: The eSTAR template flags missing elements and helps prevent Refuse to Accept (RTA) holds. Still, run your completed submission against the FDA's official RTA checklist (available on the FDA website) before submitting. The most common RTA causes are missing sections, incomplete performance test summaries (missing acceptance criteria or results), and inconsistent indications for use between the Form 3881 and the device description.

510(k) Acceptance and Clearance Rates

Understanding the FDA's historical acceptance and clearance rates helps set realistic expectations for your submission:

• RTA acceptance rate: Approximately 68% of 510(k) submissions pass the initial Refuse to Accept (RTA) screening on the first attempt. The remaining 32% are placed on hold for missing information, incomplete sections, or administrative deficiencies — meaning roughly one in three submissions fails the first acceptance check. The most common RTA deficiencies involve missing performance data, incomplete eSTAR sections, and inconsistent indications for use.
• Substantial equivalence determination rate: Approximately 85% of 510(k) submissions that complete review receive a Substantially Equivalent (SE) determination. The remaining 15% receive a Not Substantially Equivalent (NSE) determination or are withdrawn by the submitter before a final decision.
• Average review time: The FDA's average total time to a 510(k) decision has been trending downward under MDUFA V, reaching approximately 142 calendar days in recent fiscal years — down from approximately 160 days in FY2023.

These numbers underscore two points: (1) the RTA screening is a genuine gatekeeping step — invest time in completeness checks before submitting, and (2) once past RTA, the odds of clearance are favorable if your device is truly substantially equivalent to your predicate.

Do You Need a 510(k)? Decision Logic

Determining whether your Class II device requires a 510(k) submission is one of the first regulatory decisions you will make. Use this decision logic:

1. Is your device a Class II medical device? If no, different rules apply. If yes, proceed.
2. Is your product code listed as "510(k) Exempt" in the FDA Product Classification Database? If yes, check the three limitations on exemption (new intended use, different fundamental technology, or device presents potential unreasonable risk in preventing impairment of human health). If none of the limitations apply, you do not need a 510(k) — but you must still comply with all general controls and special controls. If any limitation applies, a 510(k) is required.
3. Does a legally marketed predicate device exist for your product code? If yes, submit a 510(k). If no, consider the De Novo pathway.
4. Are you modifying your own previously cleared device? If yes, evaluate whether the modification could significantly affect safety or effectiveness. If it could, a new 510(k) is required (consider a Special 510(k) for design-control-documented changes). If it could not, document the change assessment in your DHF but no new 510(k) is needed.

For a detailed walkthrough of the 510(k) process, see our Complete Guide to FDA 510(k) Submissions.

Class II Devices Exempt from 510(k)

Not every Class II device requires a premarket submission. The FDA has determined that certain Class II device types pose sufficiently low risk that premarket review is unnecessary. These devices are designated "510(k) exempt" in the Product Classification Database.

How Many Class II Devices Are Exempt?

Out of approximately 750 Class II device types, several hundred have been granted 510(k) exemption over the years through legislative action (the FDA Modernization Act of 1997, the 21st Century Cures Act of 2016) and FDA rulemaking. The full, current list is maintained on the FDA's Medical Device Exemptions 510(k) and GMP Requirements page and can be filtered by panel category.

Examples of 510(k) Exempt Class II Devices

Device Type	Regulation Number	Panel
AC-powered adjustable hospital beds	21 CFR 880.5100	General Hospital
Dental amalgam alloy	21 CFR 872.3050	Dental
Powered exercise equipment	21 CFR 890.5380	Physical Medicine
Manual radionuclide applicator system	21 CFR 892.5650	Radiology
Clinical chemistry calibrators (certain)	21 CFR 862.1150	Clinical Chemistry
Irrigating or aspirating unit, ENT	21 CFR 874.4250	Ear, Nose, and Throat
Dental hand instrument	21 CFR 872.4200	Dental
Ophthalmic trial lens set	21 CFR 886.5840	Ophthalmic
Electrode, cutaneous	21 CFR 882.1320	Neurological
Neonatal incubator (certain)	21 CFR 880.5400	General Hospital

The FDA has been expanding the list of 510(k) exempt Class II devices over time. The 21st Century Cures Act of 2016 directed the FDA to identify additional Class II device types suitable for exemption, and the FDA has periodically published final rules granting permanent exemptions to additional device types. The rationale is straightforward: if decades of marketing history demonstrate that a device type has an acceptable safety profile without premarket review, requiring 510(k) submissions wastes FDA resources and delays market access without measurable patient benefit.

Limitations on 510(k) Exemptions

Exemptions are not unconditional. A 510(k) exempt Class II device loses its exemption if:

1. The device has a new intended use — Any intended use that differs from what is described in the classification regulation triggers a 510(k) requirement
2. The device uses a different fundamental scientific technology — If your device achieves its purpose through a fundamentally different technology than what the exemption contemplated, the exemption does not apply
3. The device is for a use of substantial importance in preventing impairment of human health and presents a potential unreasonable risk — This catch-all ensures that higher-risk applications within otherwise exempt product codes still receive premarket review

How to Check if Your Device Is Exempt

1. Identify your product code using the FDA Product Classification Database
2. Look at the "Submission Type" field — if it says "510(k) Exempt," your device type is exempt
3. Verify that none of the three limitations above apply to your specific device
4. Document your exemption determination in your regulatory file or Design History File (DHF)

Practical tip: Even exempt Class II devices must still comply with all general controls — establishment registration, device listing, labeling, MDR reporting, and quality system requirements (including design controls for Class II). "510(k) exempt" means you do not need FDA clearance before marketing. It does not mean you are unregulated.

Major Class II Device Categories by Medical Specialty Panel

The FDA organizes classified devices into 16 medical specialty panels, each corresponding to a Part of 21 CFR. Class II devices span every single panel. Below is a representative selection showing the breadth and diversity of Class II devices.

Panel	21 CFR Part	Example Class II Devices
Anesthesiology	868	Ventilator (certain types), gas machine for anesthesia, pulse oximeter accessories
Cardiovascular	870	Pulse oximeters, ECG electrodes, blood pressure monitors, external pacemakers, cardiac monitors
Clinical Chemistry	862	Blood glucose monitors, continuous glucose monitors, clinical chemistry analyzers, cholesterol test systems
Dental	872	Dental implants (endosseous), dental cements, orthodontic brackets, dental amalgamators
Ear, Nose, and Throat	874	Hearing aids (OTC and prescription), tympanometers, audiometers, nasal splints
Gastroenterology/Urology	876	Endoscopes (flexible and rigid), urological catheters, lithotripters, colostomy bags
General and Plastic Surgery	878	Surgical mesh, absorbable sutures, wound closure strips, electrosurgical devices
General Hospital	880	Infusion pumps, powered hospital beds, patient scales, clinical thermometers, surgical gloves
Hematology	864	Blood cell counters, automated coagulation analyzers, platelet aggregometers
Immunology	866	Pregnancy test kits (home use), allergy test kits, flow cytometers
Neurological	882	EEG electrodes, cranial electrotherapy stimulators, nerve stimulators (certain types)
Obstetrical/Gynecological	884	Fetal monitors, fetal Doppler ultrasound, cervical dilators, condoms
Ophthalmic	886	Contact lenses (daily/extended wear), ophthalmic laser systems, retinoscopes
Orthopedic	888	Bone screws, spinal pedicle screw systems, orthopedic casting materials, knee braces
Physical Medicine	890	Powered wheelchairs, ultrasonic diathermy devices, CPM (continuous passive motion) devices
Radiology	892	X-ray systems (diagnostic), MRI coils, ultrasound imaging systems, radiological CAD software

This table illustrates a critical point: Class II is not a single category of devices. It encompasses everything from a pregnancy test stick to an MRI coil to a spinal pedicle screw system. The common thread is that these devices need more than general controls but less than PMA-level evidence.

High-Volume Class II Device Types

Some Class II product codes generate a disproportionate number of 510(k) submissions because they cover widely manufactured device types. The following are among the most commonly submitted Class II product codes:

• DQO — Stent, coronary, drug-eluting (frequently submitted for modifications)
• QKQ — Pulse oximeter
• DXN — Orthopedic bone screw
• NFT — Continuous glucose monitor
• QAS — Radiological computer-assisted detection/diagnosis software
• FRN — Clinical electronic thermometer
• JJX — Pregnancy test kit (home use)
• DSN — Blood glucose test system
• MNH — Spinal pedicle screw system
• OLK — Pulse oximeter (OTC)

Understanding which product codes are most active helps you identify predicate devices, understand FDA reviewer expectations, and benchmark your submission against industry practice. Search the TPLC report for your product code to see the complete history of submissions.

Class I vs. Class II vs. Class III: Comparison Table

Characteristic	Class I	Class II	Class III
Risk level	Low	Moderate	High
Regulatory controls	General controls only	General controls + special controls	General controls + PMA
Typical premarket pathway	Exempt (most) or 510(k)	510(k) (most), some exempt, De Novo for novel devices	PMA
Design controls required?	No (most are exempt)	Yes	Yes
Special controls apply?	No	Yes (device-specific)	Sometimes (but PMA is the primary control)
Clinical data typically required?	Rarely	Sometimes (depends on device type and special controls)	Almost always
Percentage of device types	~47%	~43%	~10%
User fee (FY2026, standard)	$0 (if exempt) / $26,067 (if 510(k) required)	$26,067 (510(k)) / $173,782 (De Novo)	$579,272 (PMA)
Average review timeline	N/A (exempt) or ~90 FDA days (510(k))	~90 FDA days (510(k)) / ~150–250 days (De Novo)	~12–18 months (PMA)
Post-market reporting	MDR (mandatory)	MDR (mandatory), possible post-market surveillance	MDR (mandatory), PMA annual report, possible post-market studies
Examples	Bandages, tongue depressors, manual stethoscopes	Infusion pumps, pulse oximeters, contact lenses, hearing aids	Pacemakers, heart valves, breast implants, cochlear implants

The most important takeaway from this table: Class II devices occupy a vast middle ground. They are more heavily regulated than Class I but far less burdensome (in time, cost, and clinical evidence) than Class III. For most medical device companies, the Class II 510(k) pathway is the primary route to the US market.

FDA-Recognized Consensus Standards for Class II Devices

Consensus standards — developed by organizations such as ISO, IEC, ASTM, and AAMI — play a critical role in Class II device submissions. Section 514(c) of the FD&C Act authorizes the FDA to recognize national and international standards as applicable to medical devices. When the FDA recognizes a standard, manufacturers can declare conformity to that standard in their premarket submission, which can reduce the amount of supporting data and documentation required.

How Recognized Standards Work in Practice

When you declare conformity to an FDA-recognized consensus standard, you are telling the FDA: "We tested our device according to this standard, and it passed." The FDA reviewer can then accept your declaration (potentially with supporting summary data) instead of reviewing full test reports.

This approach is particularly valuable for Class II devices because many of the performance requirements that special controls impose are addressed by recognized consensus standards. For example:

Requirement Area	Common Recognized Standard
Risk management	ISO 14971:2019
Biocompatibility	ISO 10993 series
Electrical safety	IEC 60601-1 (general) + device-specific particular standards
EMC	IEC 60601-1-2
Usability engineering	IEC 62366-1
Software lifecycle	IEC 62304
Sterilization validation	ISO 11135, ISO 11137, ISO 17665
Quality management system	ISO 13485:2016
Pulse oximetry performance	ISO 80601-2-61
Infusion pump safety	IEC 60601-2-24
Blood pressure monitors	ISO 81060-2

How to Find Recognized Standards for Your Device

1. Go to the FDA Standards Database
2. Search by product code, standard number, or keyword
3. Note whether the standard is fully recognized or partially recognized — the FDA sometimes recognizes only specific sections of a standard
4. Check the recognition date — older recognitions may reference superseded versions of a standard. The FDA periodically updates its recognized standards list
5. Cross-reference with the special controls for your device type — special controls may reference specific standards that should be addressed even if you are not declaring formal conformity

Full vs. Partial Recognition

The distinction between full and partial recognition matters. When the FDA fully recognizes a standard, a Declaration of Conformity to that standard satisfies the corresponding requirement without additional explanation. When the FDA only partially recognizes a standard — meaning it has excluded certain clauses or sections — you must identify which sections are recognized, declare conformity only to those sections, and address any excluded sections separately if they are relevant to your device.

For example, the FDA may recognize an ISO standard but exclude informative annexes or clauses that conflict with FDA-specific requirements. The recognition listing on the FDA Standards Database specifies exactly which portions are recognized.

Declaration of Conformity

A Declaration of Conformity (DoC) is a formal statement by the manufacturer that the device conforms to a specified recognized consensus standard. The DoC should identify:

• The exact standard (number, edition year, and title)
• Whether conformity is full or partial (if partial, which specific sections)
• A statement that testing was conducted according to the standard's requirements
• Summary results demonstrating conformity (pass/fail, key numerical results)
• The test laboratory and its accreditation status (for testing standards)

The FDA may accept the DoC with a test summary rather than the full test report, which can significantly reduce the volume of the submission. However, the FDA reserves the right to request the full test report during review.

Practical tip: A Declaration of Conformity to recognized standards is most effective in an Abbreviated 510(k) but can be used in any 510(k) type. Even in a Traditional 510(k), citing conformity to recognized standards strengthens your submission by demonstrating that your testing follows internationally accepted methodologies. Always identify the exact edition and sections of each standard you are declaring conformity to. Using an outdated edition of a standard — one that has been superseded and for which the FDA has recognized the new version — can trigger an AI letter.

Special Controls Guidance Documents: How to Find and Use Them

The FDA has published dozens of Class II Special Controls Guidance Documents, each tailored to a specific device type or category. These guidance documents are a critical resource because they translate the high-level requirement for "special controls" into specific, actionable testing, labeling, and design requirements.

What Is in a Typical Special Controls Guidance Document?

A typical document includes:

• Scope — Which device types and product codes the guidance covers
• Device description and intended use — What the device is and how it is used clinically
• Risks to health — A table of identified risks and the corresponding mitigations (special controls)
• Performance testing — Specific bench tests, with acceptance criteria, that the FDA expects. These may reference consensus standards or describe FDA-specific test methods
• Labeling requirements — Specific warnings, precautions, patient information, or IFU content that must be included
• Clinical data requirements — When clinical data is needed and what study design is acceptable
• Software requirements — If the device contains software, the documentation expectations (level of documentation, hazard analysis, cybersecurity)

How to Use a Special Controls Guidance Document

1. Treat it as your submission blueprint. Map every requirement in the guidance document to a section in your 510(k) or De Novo submission. If the guidance says "provide mechanical fatigue testing per ASTM F2077," your submission must include that test report or an explanation of why it does not apply.

2. Use it to build your test plan early. The testing requirements in the guidance document should drive your verification and validation plan during product development — not be discovered after you have already designed the device.

3. Address every item — even those that do not apply. If a guidance document lists a requirement that does not apply to your specific device variant, explicitly state that in your submission with a rationale. Silence is interpreted as an oversight, not as intentional omission.

4. Combine with recognized consensus standards. Special controls guidance documents often reference specific consensus standards. Conforming to both the guidance and the referenced standards gives reviewers maximum confidence.

Practical tip: When the FDA issues a De Novo authorization, the resulting classification order establishes the special controls for that new device type. If your device is classified under a product code that was created through De Novo, the De Novo decision summary document is your special controls guidance. Download it from the FDA's De Novo database and use it as your primary regulatory reference.

De Novo as a Pathway to Class II Classification

The De Novo classification pathway (Section 513(f)(2) of the FD&C Act) is how novel devices that are low-to-moderate risk but have no predicate enter the FDA classification system as Class I or Class II. A successful De Novo does not just authorize a single device — it creates an entirely new classification regulation, complete with:

• A new product code
• A new regulation number in 21 CFR
• Defined special controls (for Class II)
• A classification that subsequent devices of the same type can use as a predicate for 510(k) clearance

When De Novo Leads to Class II

The majority of De Novo authorizations result in Class II classification. The FDA classifies a De Novo device into Class II when it determines that general controls plus defined special controls are sufficient to provide reasonable assurance of safety and effectiveness. If general controls alone suffice, the device is classified into Class I instead.

De Novo vs. 510(k): Key Differences

Factor	510(k)	De Novo
Predicate required?	Yes	No (you become the predicate)
Creates new classification?	No	Yes (new product code, regulation, special controls)
Standard of review	Substantial equivalence	Reasonable assurance of safety and effectiveness
User fee (FY2026)	$26,067 (standard) / $6,517 (small business)	$173,782 (standard) / $43,446 (small business)
Review timeline	~90 FDA days (~108–142 calendar)	~150–250 calendar days
Outcome	Clearance (SE determination)	Authorization (De Novo grant + new classification)

De Novo Strategic Considerations

• Competitive advantage: A De Novo device becomes the predicate for its classification. Competitors who follow will file 510(k)s referencing your device. You define the regulatory framework for your category.
• Higher evidence bar: Because there is no predicate to benchmark against, the FDA typically expects more comprehensive performance data and may request clinical data.
• Cost: The FY2026 standard De Novo user fee is $173,782 — roughly 6.7x the standard 510(k) fee. Small businesses pay $43,446.
• Growing pathway: The FDA has seen increasing De Novo submissions, driven particularly by digital health, AI/ML-enabled software, and novel diagnostic devices.

Key Components of a De Novo Submission

While the 510(k) submission components are well-understood, the De Novo submission has a different structure that reflects its role as both an authorization request and a classification proposal. A De Novo submission must include:

Section	Content
Device description and intended use	Comprehensive description of the device, its operating principles, and its clinical intended use — more detailed than a typical 510(k) because there is no predicate to reference
Proposed classification and product code	Your proposed class (I or II), proposed regulation number, and proposed product code name
Regulatory rationale	Explanation of why De Novo is the appropriate pathway — why no suitable predicate exists and why the device is not high-risk enough for PMA
Risk analysis and proposed special controls	A comprehensive risk assessment (per ISO 14971) identifying all risks and your proposed mitigations, which become the proposed special controls for the new classification
Non-clinical performance data	Bench testing, biocompatibility, electrical safety, EMC, sterilization validation, software V&V, and all other applicable test data
Clinical data	Clinical evidence demonstrating safety and effectiveness — the FDA typically expects more clinical data for De Novo than for 510(k) because there is no predicate performance benchmark
Labeling	Proposed labeling including IFU, patient information (if applicable), and all proposed special control labeling requirements
Comparative analysis	While there is no predicate, the FDA expects comparison to similar (non-predicate) devices to contextualize the risk profile
Proposed performance criteria	The acceptance criteria you propose for performance testing, which may become the basis for special controls that future 510(k) submitters must meet

The De Novo submission is submitted electronically through the CDRH Customer Collaboration Portal using the eSTAR format, just like a 510(k). The key conceptual difference is that in a De Novo, you are not just seeking authorization for your device — you are proposing the regulatory framework for an entire new device category. This is why De Novo submissions require more strategic thought and typically more comprehensive data packages than 510(k)s.

For a deeper exploration of the De Novo pathway and how it relates to classification, see our FDA Device Classification Guide.

Confirming Your Device Is Class II: The 513(g) Request

If you have researched the Product Classification Database, reviewed the CFR, and consulted with regulatory experts but still cannot definitively determine whether your device is Class II, the FDA offers a formal mechanism: the 513(g) Request for Information.

A 513(g) is a written request to the FDA asking for the agency's determination of how your device should be classified. The FDA responds with a letter identifying the product code, device class, and applicable regulatory pathway. Key points about 513(g) requests:

• When to use: When your device does not fit cleanly into any existing product code, when there are multiple plausible product codes with different classifications, or when you need formal FDA confirmation of your classification determination before committing to a regulatory strategy
• What to include: A detailed device description, the proposed intended use, a description of the device's technological characteristics, and your analysis of potential product codes and classifications
• Response time: The FDA typically responds within 60 days, though complex requests may take longer
• Binding nature: The FDA's 513(g) response is not legally binding in the same way as a classification regulation, but it represents the agency's formal position and is relied upon by industry
• No user fee: There is no fee for a 513(g) request

Practical tip: A 513(g) is most useful when you have done your homework and identified the most likely product codes but need the FDA to resolve ambiguity. If you are truly unsure about classification and also need feedback on your testing strategy, consider a Pre-Submission instead — it covers classification questions plus regulatory strategy in a single interaction.

How to Classify Your Device: A Decision Framework

Determining the correct classification for your medical device is the single most consequential regulatory decision you will make. It dictates your pathway, your timeline, your budget, and your testing requirements. Follow this systematic framework:

Step 1: Define Your Intended Use Precisely

Write a clear, specific intended use statement that describes what your device does, the medical condition or purpose it addresses, the target patient population, and the clinical setting. The intended use is the primary driver of classification — two devices with identical technology but different intended uses can fall into different classes.

Step 2: Identify Candidate Product Codes

Search the FDA Product Classification Database using keywords related to your device's function, clinical specialty, and intended use. Identify all candidate product codes that could potentially apply. For each candidate:

• Read the device type description in the classification regulation
• Note the class (I, II, or III)
• Note the submission type (510(k), 510(k) exempt, PMA, De Novo)
• Review the listed special controls

Step 3: Assess the Risk Profile

Evaluate your device against these risk factors:

• Duration of patient contact — Transient (under 24 hours), short-term (1–30 days), or long-term (over 30 days)
• Degree of invasiveness — Non-invasive, surface contact, externally communicating, or implantable
• Local vs. systemic effects — Does the device affect only the site of contact or the entire body?
• Criticality — Does the device sustain or support life? Is it of substantial importance in preventing impairment of health?
• Active vs. non-active — Does the device depend on an energy source for its operation?

Devices with transient contact, non-invasive use, and local effects are typically Class I. Devices with moderate duration, some invasiveness, and clinical significance are typically Class II. Life-sustaining, long-term implantable, or high-consequence devices are typically Class III.

Step 4: Search for Predicate Devices

Search the FDA 510(k) Database for cleared devices under your candidate product codes. Review 510(k) summaries to confirm the intended use, technological characteristics, and testing approaches of potential predicates. If predicates exist, the 510(k) pathway is likely appropriate. If no predicates exist for a low-to-moderate-risk device, the De Novo pathway applies.

Step 5: Consider Novel Technology

If your device incorporates technology that differs fundamentally from existing classified devices — such as a new mechanism of action, a novel AI/ML algorithm, or a first-of-kind sensor — it may not fit existing product codes. This does not automatically make it Class III. Novel, low-to-moderate-risk devices can be classified into Class II through the De Novo pathway. However, novel technology that presents potential unreasonable risk or is life-sustaining will require PMA.

Step 6: Confirm or Seek Formal Guidance

If your analysis points clearly to a Class II product code with available predicates, you can proceed with confidence. If there is ambiguity — multiple candidate product codes with different classes, no predicates, or novel technology — use one of these formal mechanisms:

• 513(g) Request — For a formal classification determination from the FDA (free, ~60-day response)
• Pre-Submission (Pre-Sub) — For classification questions combined with regulatory strategy feedback (free, ~70–90-day process)
• De Novo — If your device is novel and low-to-moderate risk with no predicate

Practical tip: Do not self-classify without thorough research. According to FDA data, approximately 32% of 510(k) submissions fail the initial RTA acceptance check, and inappropriate classification or predicate selection is a contributing factor. Investing time in proper classification upfront saves months of delay and tens of thousands of dollars in rework.

SaMD Classification for Class II Devices

Software as a Medical Device (SaMD) — software that performs a medical function without being part of a hardware medical device — has its own classification considerations that merit specific discussion. The FDA uses a risk-based framework informed by the International Medical Device Regulators Forum (IMDRF) SaMD framework to classify software devices.

IMDRF SaMD Risk Categories

The IMDRF framework considers two factors to determine SaMD risk:

1. Significance of the information provided by the SaMD — Does it treat or diagnose, drive clinical management, or inform clinical management?
2. State of the healthcare condition — Is it critical, serious, or non-serious?

The combination of these two factors creates a matrix:

	Critical Condition	Serious Condition	Non-Serious Condition
Treat or diagnose	Class III (IV in IMDRF)	Class II–III (III in IMDRF)	Class II (II in IMDRF)
Drive clinical management	Class II–III (III in IMDRF)	Class II (II in IMDRF)	Class I–II (I in IMDRF)
Inform clinical management	Class II (II in IMDRF)	Class I–II (I in IMDRF)	Class I (I in IMDRF)

Most SaMD that falls into Class II provides diagnostic assistance, clinical decision support, or imaging analysis for serious but non-life-threatening conditions. The FDA maps the IMDRF categories to US device classes but retains the authority to classify specific SaMD products differently based on the specifics of their intended use.

Clinical Decision Support (CDS) Exemptions

Not all clinical decision software is regulated as a medical device. The 21st Century Cures Act (Section 3060) exempts certain CDS functions from device regulation if they meet all four criteria:

1. Not intended to acquire, process, or analyze a medical image, signal, or specimen
2. Intended for the purpose of displaying, analyzing, or printing medical information
3. Intended for the purpose of supporting or providing recommendations to a healthcare professional
4. Intended for the purpose of enabling the healthcare professional to independently review the basis for the recommendation

Software that meets all four criteria is not a device and does not require FDA clearance. However, software that provides time-critical information to guide immediate clinical action, or that processes medical images or signals, remains regulated — and is most commonly classified as Class II.

Humanitarian Device Exemption (HDE)

While not exclusive to Class II, the Humanitarian Device Exemption (HDE) is an alternative pathway relevant to some Class II devices designed for rare conditions. The HDE pathway applies to devices intended to benefit patients with a condition that affects or is manifested in no more than 8,000 individuals in the United States per year.

How HDE Works

• Humanitarian Use Device (HUD) designation: Before applying for an HDE, the manufacturer must request HUD designation from the FDA's Office of Orphan Products Development (OOPD). The FDA grants HUD designation if the device is intended for a condition affecting no more than 8,000 individuals per year in the US.
• Reduced clinical evidence: Unlike PMA, an HDE does not require evidence of effectiveness — it requires only a showing that the device will not expose patients to an unreasonable or significant risk of illness or injury, and that the probable benefit to health outweighs the risk of injury or illness from its use.
• Profit restrictions: Devices approved under HDE were historically subject to profit restrictions (the manufacturer could not profit from the device). However, the 21st Century Cures Act of 2016 eliminated profit restrictions for HDE-approved devices intended for pediatric populations and expanded circumstances under which profit is permitted for other HUDs.
• IRB approval: Use of an HDE-approved device generally requires approval by the Institutional Review Board (IRB) of the facility where the device will be used.

When HDE Is Relevant for Class II

Some devices that would otherwise be classified as Class II may use the HDE pathway when they target extremely rare conditions. The HDE pathway can be faster and less expensive than a standard 510(k) or De Novo when the target population is very small and clinical trial enrollment would be impractical.

Practical tip: If your Class II device targets a condition affecting fewer than 8,000 US individuals per year, explore the HDE pathway. The reduced evidence requirements and shorter review timeline can be significant advantages for rare-disease devices where conducting a clinical trial with sufficient enrollment would be impractical or unethical.

Recent Trends: AI/ML, Digital Health, and Combination Products

AI/ML-Enabled Software as a Medical Device (SaMD)

The vast majority of AI/ML-enabled medical devices authorized by the FDA are Class II devices cleared through the 510(k) pathway. As of the end of 2025, the FDA had authorized over 1,450 AI/ML-enabled medical devices, with approximately 295 authorized in 2025 alone. About 97% of these were cleared via 510(k), making Class II the dominant classification for AI/ML devices.

Key trends in AI/ML Class II devices:

• Radiology dominates: Approximately 76% of all authorized AI/ML devices are in radiology, including computer-aided detection (CADe), computer-aided diagnosis (CADx), and radiological image processing
• Cardiology is growing fast: AI/ML clearances in cardiology increased from 62 in 2024 to 92 in 2025, covering ECG interpretation, cardiac imaging analysis, and hemodynamic monitoring
• Software as Medical Device (SaMD) is the majority: About 62% of 2025 AI/ML clearances were pure SaMD — software that functions as a medical device without being part of a hardware device
• Predetermined Change Control Plans (PCCPs): As of 2025, approximately 10% of AI/ML clearances included a PCCP, which allows manufacturers to make certain pre-specified modifications to their algorithms without a new 510(k). The FDA's January 2025 draft guidance on AI-enabled device software functions is expected to formalize this framework
• Foundation models: In early 2025, the first foundation-model-powered clinical AI (Aidoc's CARE1) received FDA clearance, signaling a new era for AI/ML Class II devices
• Expanding beyond radiology: While radiology remains dominant, AI/ML Class II devices are increasingly appearing in pathology (digital pathology image analysis), ophthalmology (diabetic retinopathy screening), dermatology (skin lesion analysis), and gastroenterology (polyp detection during colonoscopy)

AI/ML Regulatory Framework for Class II

The regulatory framework for AI/ML Class II devices is evolving rapidly. Key regulatory documents and developments include:

• FDA's AI/ML Action Plan (2021) — Established the FDA's framework for regulating AI/ML-based SaMD, including the concept of a Total Product Lifecycle approach
• Draft Guidance on AI-Enabled Device Software Functions (January 2025) — Proposed a TPLC approach to AI/ML regulation, including formalization of PCCPs, requirements for AI model transparency, and expectations for algorithm change protocols. Final guidance is expected in late 2025 or 2026
• Good Machine Learning Practice (GMLP) — Ten guiding principles jointly developed by the FDA, Health Canada, and the UK MHRA that address data management, model training, evaluation, and transparency for ML-enabled devices
• Transparency requirements — The FDA is increasingly expecting manufacturers to provide information about training data characteristics, model architecture, and performance metrics disaggregated by relevant demographic subgroups

For software-only Class II devices, the documentation requirements include the software description, architecture diagram, software development lifecycle documentation per IEC 62304, hazard analysis, cybersecurity assessment, SBOM, and clinical performance validation. The level of documentation scales with the device's risk classification within the IEC 62304 framework (Class A, B, or C software safety classification).

Practical tip: If you are developing an AI/ML-enabled Class II device, identify your product code early. Most AI/ML SaMD fall under product codes QAS (radiological CAD), QIH (clinical decision support), or specific CAD codes tied to clinical specialty areas. The special controls and FDA-recognized standards for these product codes will drive your software documentation, clinical validation strategy, and labeling requirements. Consider including a PCCP in your submission if you anticipate iterative algorithm updates — this allows you to modify your algorithm within pre-specified boundaries without filing a new 510(k).

Digital Health Devices

The digital health category has expanded rapidly within Class II, driven by several significant regulatory developments:

OTC Hearing Aids: In August 2022, the FDA finalized a rule creating a new category of OTC hearing aids as Class II devices (21 CFR 800.30). This regulatory change opened a multibillion-dollar market to new entrants — including consumer electronics companies — and eliminated the requirement for a medical evaluation, audiological exam, or professional fitting for adults with perceived mild-to-moderate hearing loss. OTC hearing aids are still subject to special controls, including maximum output limits, labeling requirements, and performance standards.

Continuous Glucose Monitors (CGMs): CGMs (21 CFR 862.1355) have evolved from prescription-only Class III devices requiring PMA to Class II devices cleared through 510(k). Integrated CGM systems that work with insulin delivery devices also involve interoperability considerations under the FDA's Interoperability Guidance. The emergence of CGMs marketed for general wellness (non-diabetic users) raises classification questions that the FDA continues to address.

Remote Patient Monitoring (RPM): Devices that transmit physiological data from patients in non-clinical settings to healthcare providers — including connected blood pressure monitors, connected scales, and connected pulse oximeters — are typically Class II. The COVID-19 pandemic accelerated adoption and regulatory flexibility for RPM devices, and many of these enforcement discretion policies have become permanent.

Clinical Decision Support (CDS) Software: Section 3060 of the 21st Century Cures Act carved out certain CDS functions from the definition of a device. However, CDS software that is intended to acquire, process, or analyze a medical image or signal, or that provides time-critical information for immediate clinical action, is still regulated as a device and frequently classified as Class II.

Combination Products

Combination products — devices combined with a drug or biologic — can fall into Class II when the device component is the primary mode of action. These products are assigned to a lead FDA center (CDRH for device-primary combinations) and follow the premarket pathway of the primary mode of action.

Key considerations for Class II combination products:

• Drug-eluting devices: A drug-coated catheter or antimicrobial wound dressing may be classified as a Class II device if the primary mode of action is the device function and the drug is an adjunct
• Device + biologic: Devices incorporating biological materials (e.g., collagen-based wound products) may be regulated as combination products
• Designation request: If there is ambiguity about which center should regulate the product, the manufacturer can submit a Request for Designation (RFD) to the FDA's Office of Combination Products, which determines the lead center and applicable regulatory pathway
• Additional requirements: Even when a combination product follows the 510(k) pathway, the FDA may require additional data on the drug or biologic component — such as bioavailability, drug release kinetics, or stability data — that would not be required for a device-only submission

Practical tip: If your Class II device incorporates any drug, biologic, or human tissue component — even as a coating, an antimicrobial agent, or a lubricant — evaluate whether the product meets the definition of a combination product under 21 CFR Part 3. Failure to identify a product as a combination product early can result in submission to the wrong FDA center, which adds months of regulatory delay.

Common Mistakes in Class II Submissions

Based on FDA RTA (Refuse to Accept) statistics and published deficiency summaries, the most common mistakes in Class II device submissions include:

1. Inadequate Predicate Selection

Choosing a predicate device with a different intended use, a different technological basis, or one that has been recalled or withdrawn from the market. The substantial equivalence argument collapses if the predicate is poorly chosen.

2. Inconsistent Indications for Use

The indications for use statement (FDA Form 3881) does not match the indications described in the device description section, the labeling, or the predicate device's cleared indications. FDA reviewers compare these carefully.

3. Missing or Incomplete Performance Data

Submitting test reports without pre-defined acceptance criteria, without describing the test methodology, or without summarizing results. This is the most common technical RTA cause.

4. Ignoring Special Controls

Failing to address the device-specific special controls — either because the manufacturer did not look them up, or because they assumed general testing was sufficient. Every special control must be addressed explicitly in the submission.

5. Insufficient Software Documentation

For devices with software, failing to provide the software documentation level appropriate to the risk. Since 2023, the FDA expects documentation aligned with the "Content of Premarket Submissions for Device Software Functions" guidance rather than the old Level of Concern framework. Missing or inadequate cybersecurity documentation — particularly the absence of a Software Bill of Materials (SBOM) — is an increasingly common deficiency.

6. Inadequate Biocompatibility Justification

Either over-testing (conducting unnecessary tests that can delay the submission) or under-testing (failing to address all relevant endpoints per the ISO 10993-1 biocompatibility matrix for the device's patient contact type and duration).

7. Not Using eSTAR Properly

Since October 2023, the eSTAR format is mandatory. Submissions that are improperly formatted, missing mandatory eSTAR fields, or that attach documents in incorrect locations cause administrative delays.

8. Predicate Splitting

Using different predicates for different device characteristics (e.g., one predicate for intended use and another for technology) when the predicates themselves are not equivalent. The FDA permits predicate splitting in some cases but scrutinizes it heavily. If your predicates do not share the same intended use or technological characteristics with each other, the FDA may conclude that your device is fundamentally different from either predicate.

9. Failing to Address Cybersecurity

For any Class II device that connects to a network, communicates wirelessly, or includes updateable software, the FDA expects a comprehensive cybersecurity assessment. This includes a threat model, a cybersecurity risk assessment, an SBOM (Software Bill of Materials), a plan for addressing post-market cybersecurity vulnerabilities, and documentation of design features that support cybersecurity (encryption, authentication, access controls). The FDA's 2023 Cybersecurity guidance ("Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions") made these expectations explicit, and missing cybersecurity documentation is a growing cause of RTA holds.

10. Underestimating Labeling Requirements

Submitting draft labeling that is incomplete, inconsistent with the indications for use, or missing required special control warnings and precautions. Labeling reviews are a separate track within the FDA review process, and labeling deficiencies can hold up an otherwise technically sound submission.

Practical tip: Before submitting, conduct a mock review. Have someone on your team who was not involved in writing the submission read it as an FDA reviewer would — checking for consistency, completeness, and explicit responses to every special control. Compare your submission against the RTA checklist item by item. Pay particular attention to consistency between the Form 3881 (Indications for Use), the device description, the predicate comparison, and the proposed labeling — discrepancies across these sections are the most common trigger for AI letters.

Pre-Submission (Pre-Sub) Meetings for Class II Devices

The Pre-Submission program is one of the most underutilized tools available to Class II device manufacturers. A Pre-Sub is a formal mechanism to obtain FDA feedback before investing the time and money in a full 510(k) or De Novo submission.

When to Use a Pre-Sub

Pre-Subs are recommended whenever you face uncertainty about:

• Classification — Is your device Class I, II, or III? Which product code applies?
• Predicate selection — Is your proposed predicate acceptable? Do you need a split predicate approach?
• Testing strategy — Are the bench tests you plan to conduct sufficient? Does the FDA expect clinical data?
• Clinical study design — If clinical data is needed, what study design, endpoints, and sample size does the FDA expect?
• Special controls interpretation — How do the special controls apply to your specific device variant?
• Software documentation level — What level of software documentation does the FDA expect for your device's risk profile?

What You Get from a Pre-Sub

The FDA provides written feedback (typically within 70–90 days of the Pre-Sub request) or holds a meeting (in-person, teleconference, or video conference) followed by meeting minutes. The feedback is non-binding but is taken seriously by the review division. If you follow the FDA's Pre-Sub feedback in your subsequent submission, the reviewer is far less likely to raise new objections.

Pre-Sub Process

1. Submit a Pre-Sub package to the CDRH through the CDRH Customer Collaboration Portal. Include your device description, proposed intended use, regulatory questions, proposed predicate (if applicable), and any preliminary testing data.
2. The FDA acknowledges receipt and schedules a response (written feedback only) or a meeting (if you request one).
3. For meeting requests, the FDA provides meeting minutes within 15 business days.
4. There is no user fee for Pre-Sub meetings.

Practical tip: Always request a meeting rather than written-only feedback. Meetings allow real-time dialogue and the ability to ask follow-up questions. Submit your Pre-Sub questions at least 3–4 months before you plan to submit your 510(k) or De Novo, because the entire Pre-Sub cycle — from submission to meeting to minutes — typically takes 3–4 months.

Regulatory Costs and Timelines for Class II Devices

FY2026 User Fees (October 1, 2025 – September 30, 2026)

Submission Type	Standard Fee	Small Business Fee
510(k)	$26,067	$6,517
De Novo	$173,782	$43,446
PMA (for reference)	$579,272	$144,818
Annual establishment registration	$11,423	$11,423

Small business qualification requires gross receipts or sales of no more than $100 million. Businesses with no more than $30 million in gross receipts may qualify for a fee waiver on their first PMA, PDP, or BLA submission.

Total Cost Estimates

The user fee is only one component of the total cost of bringing a Class II device to market. Realistic total cost estimates for a 510(k) submission include:

Cost Category	Typical Range
User fee	$6,517–$26,067
Testing (bench, biocompatibility, EMC, sterilization)	$50,000–$500,000+
Regulatory consulting (if used)	$30,000–$150,000
Clinical study (if required by special controls)	$100,000–$2,000,000+
Quality system development/maintenance	$50,000–$200,000/year
eSTAR preparation and submission	Internal or $10,000–$50,000 (consulting)
Total (without clinical study)	$150,000–$500,000
Total (with clinical study)	$250,000–$2,500,000+

Review Timelines

Under MDUFA V (FY2023–FY2027), the FDA's performance goals for 510(k) review are:

• 510(k): Decision within 90 FDA days for 95% of submissions (approximately 108–142 calendar days when accounting for hold times and weekends). The total time to decision goal is approximately 108–112 calendar days for FY2025–2027.
• De Novo: Decision within 150 FDA days for 70% of submissions (approximately 150–250+ calendar days)
• Special 510(k): Decision within 30 FDA days

These timelines assume a well-prepared submission that passes the RTA check. Submissions with deficiencies trigger Additional Information (AI) requests that add weeks or months to the timeline. Each AI round typically adds 30–90 calendar days, and some submissions go through two or three AI rounds before receiving a decision.

Realistic Timeline for a Class II 510(k)

Phase	Duration	Notes
Classification and predicate research	2–4 weeks	Confirm product code, identify predicates, review special controls
Pre-Submission meeting (if needed)	3–4 months	From submission of Pre-Sub to receipt of meeting minutes
Product development and design controls	6–18 months	Concurrent with testing planning; design freeze needed before formal testing
Verification and validation testing	3–12 months	Bench testing, biocompatibility, EMC, sterilization validation, software V&V, clinical study (if required)
Submission preparation	1–3 months	eSTAR assembly, QA review, mock RTA check
FDA review	3–5 months	Assuming no major deficiencies; add 1–3 months per AI round
Post-clearance activities	1–3 months	Final labeling, manufacturing scale-up, establishment registration, device listing, UDI submission
Total (typical, no clinical study)	12–24 months	From start of regulated testing to first commercial shipment
Total (with clinical study)	18–36 months	Clinical study adds 6–24 months depending on study size and endpoints

Practical tip: Build a realistic timeline that includes Pre-Submission meetings (allow 3–4 months from request to meeting), testing completion (3–12 months), submission preparation (1–3 months), and FDA review (3–5 months for 510(k)). For a typical Class II device with moderate complexity, plan for 12–18 months from the start of regulated testing to 510(k) clearance. Under-estimating timelines is the most common planning failure for first-time submitters.

Reclassification: Moving Devices Into (and Out of) Class II

The FDA does not treat classification as permanent. Devices can be reclassified between classes through rulemaking, and understanding this process is important for both existing manufacturers and those tracking regulatory developments in their market.

Down-Classification: Class III to Class II

The FDA has reclassified numerous device types from Class III to Class II over the past two decades. This process — called "down-classification" — occurs when the FDA determines, based on accumulated evidence and real-world experience, that special controls can provide reasonable assurance of safety and effectiveness without requiring PMA.

Notable down-classifications to Class II include:

• Automated external defibrillators (AEDs) — Reclassified from Class III to Class II for certain intended uses
• Certain orthopedic implants — Including some spinal devices and hip components
• Certain IVD tests — As sufficient clinical evidence accumulated
• OTC hearing aids — Created as a new Class II category through rulemaking in 2022

Down-classification benefits the entire industry: once a device type is reclassified to Class II, new market entrants can use the 510(k) pathway (or 510(k) exemption if granted) instead of PMA, significantly reducing the time, cost, and clinical evidence required to reach market.

Up-Classification: Class I or II to a Higher Class

Less commonly, the FDA may reclassify a device type to a higher class. This typically occurs when post-market surveillance reveals safety issues that existing controls cannot adequately address. Manufacturers of devices in up-classified categories must then meet the requirements of the new class — potentially including PMA submission for a device that was previously 510(k) cleared.

De Novo as a Classification Mechanism

As discussed earlier, the De Novo pathway is functionally a classification mechanism. Every successful De Novo establishes a new classification, most often in Class II. This is the primary way new Class II product codes are created today.

Labeling Requirements for Class II Devices

Class II devices must comply with the general labeling requirements in 21 CFR Part 801 and any additional special control labeling requirements specific to their device type. Labeling is one of the most scrutinized elements of a 510(k) submission, and labeling deficiencies are a frequent cause of review delays.

General Labeling Requirements (All Classes)

All medical devices must include:

• Manufacturer name and address (or distributor name and address, with the manufacturer identified)
• Intended use and adequate directions for use — Clear instructions enabling a layperson (for OTC devices) or a healthcare professional (for prescription devices) to use the device safely and for its intended purpose
• Warnings and precautions — Prominent disclosure of any conditions, situations, or populations for which the device poses known risks
• Contraindications — Conditions under which the device should not be used
• Rx or OTC designation — Whether the device is restricted to sale by or on the order of a licensed healthcare practitioner

Special Control Labeling Requirements (Class II Specific)

Beyond general labeling, each Class II device type may have labeling requirements specified in its special controls. These can include:

• Patient information sheets — Required for certain devices that patients interact with directly (e.g., contact lenses, hearing aids, CGMs)
• Specific warning language — Exact warning text that must appear on the label (e.g., "Not intended for use as the sole basis for diagnosis")
• Compatibility statements — Declarations of compatibility or incompatibility with other devices or substances
• Performance specifications on the label — Certain devices must display key performance parameters (accuracy, sensitivity, specificity) on the labeling
• Training requirements — Statements indicating that the device should only be used by trained personnel
• Shelf life and storage conditions — Particularly for sterile devices, IVDs, and devices with degradable components

Practical tip: Draft your labeling in parallel with your submission, not after. FDA reviewers compare your proposed labeling against your indications for use, your performance data, and the special controls. Any inconsistency — a claim in the labeling that is not supported by testing, a missing warning that the special controls require, or indications that differ from the Form 3881 — will result in an AI letter. Have your regulatory and labeling teams review the proposed labeling as a unit before finalizing the submission.

Post-Market Requirements for Class II Devices

Clearance or De Novo authorization is not the end of your regulatory obligations. Class II device manufacturers have ongoing post-market requirements.

Medical Device Reporting (MDR) — 21 CFR Part 803

Manufacturers must report to the FDA:

• Death or serious injury reports: Within 30 calendar days of becoming aware that a device may have caused or contributed to a death or serious injury
• 5-day reports: Within 5 working days if the FDA requests expedited reporting or if the manufacturer becomes aware of an event requiring remedial action to prevent an unreasonable risk of substantial harm
• Malfunction reports: Within 30 calendar days for malfunctions that would be likely to cause or contribute to a death or serious injury if the malfunction were to recur. Some device types are eligible for Summary Malfunction Reporting (quarterly aggregate reports instead of individual reports)

Corrections and Removals — 21 CFR Part 806

If you correct or remove a device from the market due to a defect or regulatory violation, you must report to the FDA within 10 working days. This applies whether the action is voluntary or mandated.

Recalls

Medical device recalls are classified by the FDA into three categories based on severity:

• Class I recall: Reasonable probability of serious adverse health consequences or death
• Class II recall: May cause temporary or medically reversible adverse health consequences, or where the probability of serious consequences is remote
• Class III recall: Not likely to cause adverse health consequences

Most recalls of Class II devices are Class II recalls. Manufacturers typically conduct voluntary recalls under 21 CFR Part 7.

Establishment Registration and Device Listing

Annual establishment registration ($11,423 in FY2026) and device listing must be maintained and updated whenever there are changes to products or facilities.

Quality System Maintenance

Ongoing compliance with the QMSR (formerly QSR), including management reviews, internal audits, CAPA, complaint handling, supplier management, and design control for any device modifications.

Key quality system elements for Class II device manufacturers:

• Design controls (21 CFR 820.30 / ISO 13485 Section 7.3) — Required for all Class II devices. Design controls must be applied not only during initial product development but also for any subsequent design changes. A new 510(k) may be triggered by design changes, but even changes that do not require a new 510(k) must go through design controls.
• Production and process controls — Manufacturing processes must be validated, monitored, and controlled to ensure consistent production of conforming devices
• CAPA — A systematic process for identifying, investigating, and correcting quality problems and preventing their recurrence. CAPA findings from complaint analysis, audit results, and process monitoring must be documented and tracked
• Complaint handling — Every complaint must be formally received, reviewed, and evaluated to determine whether it represents an adverse event that must be reported under MDR regulations
• Supplier management — Suppliers of components, materials, and services that affect device quality must be qualified, monitored, and periodically re-evaluated
• Internal audits — The quality system must be periodically audited to verify ongoing compliance. Audit findings must be addressed through CAPA

FDA Facility Inspections

FDA facility inspections can occur at any time and are a routine part of medical device regulation. For Class II device manufacturers, inspections typically focus on:

• Pre-approval inspections — The FDA may inspect your facility before granting 510(k) clearance, particularly for your first submission or for devices with complex manufacturing
• Routine surveillance inspections — Periodic inspections to verify ongoing compliance with the QMSR. Priority is based on a risk algorithm that considers the device class, the firm's compliance history, and the time since the last inspection
• For-cause inspections — Triggered by adverse event reports, complaints, or other signals suggesting a quality or safety problem
• Foreign manufacturer inspections — Foreign establishments are subject to the same inspection requirements, though logistics make foreign inspections less frequent. The FDA has been increasing foreign inspection frequency

Inspection observations are documented on FDA Form 483. Failure to adequately respond to 483 observations can escalate to Warning Letters, Import Alerts (for foreign manufacturers), or enforcement actions. Common 483 observations for Class II device manufacturers include inadequate CAPA procedures, incomplete complaint records, missing or inadequate design control documentation for device changes, and failure to follow established procedures.

Post-Market Surveillance Studies

For certain Class II device types — particularly those with limited pre-market clinical data or devices authorized through De Novo — the FDA may impose a post-market surveillance requirement (Section 522 of the FD&C Act). This requires the manufacturer to conduct a study on the device's performance in real-world conditions and report findings to the FDA.

Unique Device Identification (UDI)

Class II devices must comply with UDI requirements (21 CFR Part 830). Each device must bear a UDI on its label and packaging, and device information must be submitted to the FDA's Global UDI Database (GUDID). The UDI consists of two parts:

• Device Identifier (DI) — A fixed portion that identifies the specific version or model of the device and its labeler
• Production Identifier (PI) — A variable portion that includes the lot or batch number, serial number, manufacturing date, and expiration date (as applicable)

Class II devices were required to bear a UDI on their labels and packaging by September 24, 2016, and on the device itself (direct marking) by September 24, 2018 — but only for devices intended to be used more than once and reprocessed before each use.

Post-Market Cybersecurity Management

For Class II devices that connect to networks, communicate wirelessly, or include updateable software, post-market cybersecurity management is an increasingly critical obligation. The FDA's 2023 cybersecurity guidance and Section 524B of the FD&C Act (added by the Consolidated Appropriations Act of 2023) established mandatory cybersecurity requirements for cyber devices.

Key post-market cybersecurity obligations include:

• Vulnerability monitoring — Manufacturers must actively monitor for cybersecurity vulnerabilities throughout the total product lifecycle. This includes monitoring public vulnerability databases (NVD, CVE), coordinated vulnerability disclosure programs, and threat intelligence sources relevant to the device's software components.
• Software Bill of Materials (SBOM) maintenance — The SBOM submitted as part of the premarket submission must be maintained and updated as software components change. The FDA can request an updated SBOM at any time.
• Patching and update capability — Devices must be designed with the capability to receive validated security patches and software updates. When a vulnerability is identified, the manufacturer must assess risk, develop a patch or mitigation, validate the fix, and deploy it — all under the quality system.
• Coordinated vulnerability disclosure — Manufacturers should have a coordinated vulnerability disclosure policy and process for receiving and responding to vulnerability reports from external researchers and users.
• Cybersecurity incident response — Manufacturers must have procedures for responding to cybersecurity incidents, including assessing whether a cybersecurity event constitutes a reportable adverse event under MDR regulations.

The FDA treats cybersecurity as a patient safety issue, not just an IT issue. A cybersecurity vulnerability that could lead to unauthorized access, data integrity compromise, or device malfunction is a quality issue that may trigger CAPA, field action, or even recall obligations. The fact that a device passed all security tests at the time of clearance does not mean it will remain secure — continuous vigilance is required.

Device Modifications and When a New 510(k) Is Required

One of the most frequent post-market questions for Class II device manufacturers is: "Does this change require a new 510(k)?" The FDA's guidance document "Deciding When to Submit a 510(k) for a Change to an Existing Device" (2017) provides the framework. In general, a new 510(k) is required when a change could significantly affect the safety or effectiveness of the device.

Changes that typically require a new 510(k):

• Change in intended use or indications for use
• New materials in patient-contacting components
• New sterilization method
• Significant changes to the energy source or output
• New technological features that alter the device's mechanism of action
• Software changes that could affect clinical functionality (for SaMD, refer to the FDA's 2024 framework for software changes)

Changes that typically do not require a new 510(k) (but must be documented in the DHF):

• Manufacturing process changes that do not affect the finished device's form, fit, or function
• Component supplier changes (same specifications)
• Cosmetic changes (color, labeling layout) that do not affect clinical use
• Minor software bug fixes that do not change clinical functionality

Practical tip: Build post-market processes before you go to market, not after. Your complaint handling, MDR reporting, CAPA, and field safety corrective action procedures should be validated and operational before your first commercial shipment. FDA inspectors frequently cite inadequate complaint handling and late MDR reports as observations during facility inspections. Document every device modification decision — whether a new 510(k) is or is not required — in a formal change assessment. If the FDA questions a modification during an inspection, your documented risk assessment is your defense.

Development Strategy for Class II Devices

Understanding that your device is Class II should fundamentally shape your product development strategy. Unlike Class I devices (where regulatory effort is minimal) or Class III devices (where clinical trials dominate the timeline), Class II device development requires a balanced approach that integrates regulatory planning, engineering, testing, and quality system activities from day one.

Early-Stage Strategic Decisions

Before you write a line of requirements or build a prototype, make these strategic decisions:

1. Confirm classification and identify your product code — This determines everything else. Do not begin product development with an assumed classification.
2. Select your predicate device — The predicate drives your intended use scope, your testing strategy, and your SE argument. Choosing a predicate after development is complete often leads to misalignment.
3. Map all special controls to design inputs — Translate every special control requirement into a design input in your design control process. This ensures your device is designed to meet regulatory requirements, not retrofitted to them.
4. Identify applicable consensus standards — Knowing which IEC, ISO, and ASTM standards apply to your device type lets you design testing into the development plan rather than discovering test requirements late.
5. Decide on a Pre-Submission — If there is any uncertainty about classification, predicate choice, or testing strategy, plan a Pre-Sub early. The 3–4 month Pre-Sub cycle is well worth it if it prevents a costly misdirection.

Regulatory-Integrated Development Timeline

The most efficient Class II development programs integrate regulatory milestones with engineering milestones:

Development Phase	Regulatory Activity
Concept / Feasibility	Classification research, product code identification, predicate search, initial standards mapping
Design Input	Special controls analysis, Pre-Sub preparation and submission, risk management plan, design input traceability to special controls
Design Output / Verification	Bench testing per special controls and consensus standards, biocompatibility assessment, EMC testing plan, software hazard analysis
Design Validation	Clinical study (if required), usability testing per IEC 62366-1, simulated use testing, labeling review
Design Transfer	Manufacturing process validation, sterilization validation, quality system audit readiness, eSTAR assembly begins
Submission	510(k) or De Novo submission, RTA checklist verification, user fee payment
Post-Clearance	Establishment registration, device listing, UDI submission, final labeling production, commercial manufacturing ramp

Quality System Readiness

Your quality management system must be operational before you submit your 510(k) — not after clearance. FDA facility inspections can occur at any time, including as a pre-clearance inspection. At minimum, your quality system should include:

• Document control — Procedures, work instructions, and forms under revision control
• Design controls — A Design History File (DHF) with complete traceability from design inputs to verification/validation outputs
• Risk management — A living risk management file per ISO 14971, with post-production risk review procedures
• CAPA — A functional corrective and preventive action process
• Complaint handling — Procedures for receiving, investigating, and trending complaints, including MDR evaluation
• Supplier management — Qualified and approved suppliers for critical components
• Training — Documented training records for all personnel performing quality-affecting activities

Practical tip: The transition from QSR to QMSR (harmonized with ISO 13485:2016) means that if you are building a quality system from scratch, build it to ISO 13485 from the start. This satisfies both FDA requirements and positions you for international market access (EU MDR, Health Canada MDSAP, TGA) without maintaining parallel quality systems.

International Comparison: FDA Class II vs. EU MDR Classification

Understanding how FDA Class II maps (and does not map) to the EU's classification system is essential for manufacturers pursuing global market access.

EU MDR Classification Overview

The EU Medical Device Regulation (MDR 2017/745) uses a four-tier classification system: Class I, Class IIa, Class IIb, and Class III. The classification rules (Annex VIII of the MDR) are based on criteria including duration of contact, invasiveness, body system affected, and whether the device is active.

How FDA Class II Maps to EU MDR Classes

There is no one-to-one mapping between FDA Class II and any single EU MDR class. The mapping depends on the specific device type:

FDA Classification	Typical EU MDR Classification	Example
FDA Class II	EU MDR Class IIa	Blood pressure monitors, hearing aids, dental crowns
FDA Class II	EU MDR Class IIb	Ventilators (certain), infusion pumps, contact lenses (extended wear), surgical lasers
FDA Class II	EU MDR Class III	Certain implants (e.g., some spinal devices, surgical mesh for pelvic floor — reclassified under MDR Rule 8)
FDA Class II	EU MDR Class I (sterile/measuring)	Sterile surgical gloves, sterile surgical drapes

Key Differences Between the Systems

Factor	FDA (US)	EU MDR
Number of classes	3 (I, II, III)	4 (I, IIa, IIb, III)
Classification basis	Risk + intended use + predicate history	22 classification rules based on duration, invasiveness, body system, active/non-active
Assessment body	FDA (government agency) reviews directly	Notified Body (private organization designated by EU member state)
Clinical evidence	Substantial equivalence to predicate (510(k)); sometimes clinical data	Clinical evaluation required for all classes; PMCF (Post-Market Clinical Follow-up) required
Pathway for novel devices	De Novo	Conformity assessment with Notified Body under the applicable Annex
Software classification	Risk-based; most AI/ML SaMD is Class II	Rule 11 of Annex VIII; software intended to provide information used for diagnostic or therapeutic decisions is at least Class IIa

Beyond the EU: Other Major Markets

The classification challenge extends beyond the EU:

Market	Regulatory Body	How FDA Class II Typically Maps
EU	Notified Bodies under MDR	Class IIa, IIb, or III depending on device type
Canada	Health Canada	Class II, III, or IV (Canada uses four classes)
Japan	PMDA/MHLW	Class II or III (Japan uses four classes)
Australia	TGA	Class IIa or IIb (TGA follows the GHTF/IMDRF framework)
UK	MHRA under UKCA	Class IIa or IIb (currently aligned with legacy MDD, transitioning to UK MDR)
China	NMPA	Class II or III (China uses three classes with different criteria)
Brazil	ANVISA	Class II, III, or IV (Brazil uses four classes)
South Korea	MFDS	Class 2 or 3 (Korea uses four classes)

The key lesson: classification is jurisdiction-specific. A device classified as FDA Class II may require significantly more (or less) regulatory effort in other markets. Always perform independent classification for each target market at the start of your global regulatory strategy.

Practical tip: Do not assume that a Class II FDA clearance translates to a simple EU approval. Devices that are Class II under FDA may be Class IIb or even Class III under the EU MDR, particularly implantable devices, software providing diagnostic information for serious conditions, and devices that the MDR specifically up-classifies through its rules. Always perform an independent EU MDR classification before planning your CE marking strategy. See our EU MDR/IVDR Complete Guide for details.

Frequently Asked Questions

What percentage of medical devices are Class II?

Approximately 43% of all classified medical device types recognized by the FDA are Class II. This makes Class II the second-largest category after Class I (approximately 47%). Class III accounts for approximately 10%.

What is the difference between a Class II device and a Class III device?

Class II devices require general controls plus special controls and typically reach the market through a 510(k) or De Novo pathway. Class III devices require premarket approval (PMA), which demands clinical evidence of safety and effectiveness — usually from clinical trials. Class III devices are those that sustain or support life, are implanted, or present a potential unreasonable risk of illness or injury. The cost difference is substantial: a 510(k) user fee is $26,067 (FY2026) compared to $579,272 for a PMA.

Can a Class II device be reclassified?

Yes. The FDA can reclassify devices between classes through rulemaking. In recent years, the FDA has reclassified some devices from Class III to Class II (called "down-classification") when sufficient real-world data demonstrated that special controls could provide adequate assurance of safety and effectiveness without PMA. Conversely, devices can be up-classified if safety signals emerge. The FDA also reclassifies device types from Class I to Class II when warranted.

How long does it take to get a Class II device to market?

From the start of regulated testing to 510(k) clearance, a typical timeline is 12–18 months for a moderately complex Class II device. This includes testing (3–12 months), submission preparation (1–3 months), and FDA review (~90 FDA days). For devices requiring clinical data, add 6–24 months for the clinical study. De Novo submissions take longer because of the higher evidentiary bar and longer FDA review times (150–250+ calendar days).

Do all Class II devices require a 510(k)?

No. Some Class II device types are 510(k) exempt. You can check exemption status in the FDA Product Classification Database. Even exempt devices must comply with all other applicable requirements — registration, listing, labeling, MDR reporting, and quality system requirements.

What happens if my device does not have a predicate?

If your device has no legally marketed predicate, you cannot use the 510(k) pathway. Your options are (1) the De Novo pathway, if your device is low-to-moderate risk, which will classify it into Class I or Class II, or (2) the PMA pathway, if the device is high-risk. Most novel devices that would logically be Class II use the De Novo pathway.

Are software devices classified as Class II?

Many software devices are Class II, particularly AI/ML-enabled software that assists clinicians with diagnosis, triage, or monitoring. The FDA has cleared over 1,450 AI/ML-enabled devices, the vast majority as Class II via 510(k). However, classification depends on the software's intended use, the condition it addresses, and the significance of the information it provides. Software used to drive clinical treatment of serious conditions may be classified as Class III.

What are the annual costs of maintaining a Class II device on the market?

Ongoing costs include annual establishment registration ($11,423 in FY2026), quality system maintenance ($50,000–$200,000/year depending on company size and complexity), complaint handling and MDR reporting (internal labor), UDI database maintenance, and any post-market surveillance requirements. If you have multiple product lines or facilities, registration fees apply per establishment.

Can a Class II device be marketed without FDA clearance?

Only if the device falls under a 510(k) exempt product code and meets all conditions for exemption. Otherwise, marketing a Class II device without 510(k) clearance or De Novo authorization is illegal and can result in warning letters, injunctions, seizure of product, and civil or criminal penalties.

What is the role of Pre-Submissions for Class II devices?

A Pre-Submission (Pre-Sub) is a formal meeting request (in-person, teleconference, or written feedback) with the FDA review division before you submit your 510(k) or De Novo. Pre-Subs are used to discuss classification questions, predicate selection, testing strategies, clinical study design, and any novel aspects of the device. They are free (no user fee) and strongly recommended for any device with classification uncertainty, novel technology, or complex special controls.

What is the difference between "cleared" and "approved"?

The FDA "clears" 510(k) devices by finding them substantially equivalent to a predicate. It "approves" PMA devices based on a finding that there is reasonable assurance of safety and effectiveness. De Novo devices are "authorized" or "granted." These are distinct legal statuses with different marketing implications. Using "approved" when referring to a 510(k)-cleared device is technically incorrect and can undermine credibility with regulators, investors, and partners.

Can a foreign company submit a 510(k)?

Yes. Foreign manufacturers can submit 510(k)s and market Class II devices in the United States. However, they must designate a US Agent (21 CFR Part 807), register their foreign establishment with the FDA, and pay the same user fees and registration fees as domestic manufacturers. The US Agent serves as the FDA's point of contact for the foreign establishment. If using a US importer or distributor, the initial importer must also be registered with the FDA.

What is third-party review for Class II devices?

For certain Class II device types, the FDA allows accredited third-party review organizations (also called Accredited Persons) to conduct the primary review of a 510(k) submission and make a recommendation to the FDA. This program can significantly reduce review timelines — the FDA typically makes a final decision within 30 days of receiving the third-party recommendation. Not all Class II product codes are eligible for third-party review. Check the "Third Party Review Eligible" field in the Product Classification Database for your product code.

Does a Class II FDA clearance guarantee approval in other countries?

No. FDA Class II classification is specific to the United States. Each country or regulatory region has its own classification system and requirements. A device that is Class II under FDA may be classified as Class IIa, IIb, or even Class III under the EU MDR. Similarly, Health Canada, Japan (PMDA), Australia (TGA), and China (NMPA) each have independent classification criteria. You must perform a separate classification analysis for every market you intend to enter. See the International Comparison section above for mapping details.

Can software updates change my device's classification?

Minor software updates — such as bug fixes, UI improvements, or performance optimizations that do not change clinical functionality — typically do not affect classification. However, major algorithmic changes, new intended uses enabled by software features, or the addition of AI/ML capabilities may require reclassification or a new 510(k). For AI/ML-enabled devices, the FDA's Predetermined Change Control Plan (PCCP) framework allows certain pre-specified algorithm modifications without a new submission, provided the changes fall within the boundaries described in the approved PCCP.

What is the difference between a recall and a correction?

A recall is a manufacturer's removal of a device from the market or correction of a marketed device when the FDA determines the device to be in violation of laws it administers. A correction is a repair, modification, adjustment, relabeling, destruction, or inspection of a device without removing it from the market. Both must be reported to the FDA under 21 CFR Part 806. The FDA classifies recalls into three tiers (Class I, II, and III) based on the severity of the potential health consequences — this is separate from and unrelated to the device classification system (Class I, II, III devices).

How do I know if my Class II device needs clinical data?

Whether clinical data is required depends on the specific special controls for your device type, the nature of any technological differences from your predicate, and the risk profile of your device. In general, clinical data is more likely to be required when: (1) the special controls explicitly require clinical performance data, (2) your device has technological differences from the predicate that raise new questions of safety or effectiveness that cannot be resolved through bench testing alone, (3) the device is in a high-risk Class II category (such as certain implants or diagnostic devices), or (4) the FDA requests clinical data during the review or Pre-Sub process. A Pre-Submission meeting is the best way to get clarity on whether the FDA expects clinical data for your specific device.

Class II 510(k) Submission Compliance Checklist

Before submitting your 510(k), use this checklist to verify completeness and reduce the risk of an RTA hold or AI letter. Each item maps to a common deficiency identified by the FDA.

Pre-Submission Preparation:

• Product code confirmed via FDA Product Classification Database
• Classification regulation reviewed (21 CFR section for your device type)
• Special controls identified and mapped to submission sections
• Predicate device selected and verified as legally marketed (not recalled or withdrawn)
• Predicate 510(k) summary reviewed for intended use and technological characteristics
• Pre-Submission meeting completed (if applicable) and FDA feedback incorporated
• Applicable FDA-recognized consensus standards identified

Submission Content:

• Cover letter with correct submission type, contact information, and device identification
• FDA Form 3881 (Indications for Use) completed — consistent with device description and labeling
• 510(k) summary or statement included
• Device description with technical specifications, materials, and operating principles
• Predicate comparison table (side-by-side on intended use, technological characteristics, performance)
• Substantial equivalence argument clearly articulated
• Proposed labeling (labels, IFU, packaging) — consistent with indications for use and special controls
• Sterilization validation data (if applicable)
• Biocompatibility assessment per ISO 10993-1 (if applicable) — with risk assessment and test reports
• Software documentation per FDA's 2023 guidance on device software functions (if applicable)
• Cybersecurity assessment with SBOM (if device is a cyber device)
• EMC testing per IEC 60601-1-2 (if applicable)
• Electrical safety testing per IEC 60601-1 (if applicable)
• Performance testing addressing every applicable special control — with pre-defined acceptance criteria and summarized results
• Clinical data (if required by special controls or to address technological differences)
• Declarations of Conformity to FDA-recognized consensus standards (if relying on standards)
• Shelf-life / packaging testing data (if applicable)
• Usability / human factors assessment per IEC 62366-1 (if applicable)

Administrative and Format:

• Submission assembled in eSTAR format via CDRH Customer Collaboration Portal
• User fee paid ($26,067 standard / $6,517 small business for FY2026)
• Truthful and Accurate statement signed
• All documents are legible, properly referenced, and consistently formatted
• Internal RTA checklist review completed before submission
• Indications for use, device description, predicate comparison, and labeling are all mutually consistent

Practical tip: Have someone who was not involved in writing the submission review every item on this checklist before submitting. Fresh eyes catch inconsistencies that the author misses. The most common RTA causes — missing acceptance criteria, inconsistent indications, and incomplete eSTAR sections — are all preventable through a disciplined internal review process.

Step-by-Step: Getting Your Class II Device to Market

To tie together everything covered in this guide, here is the end-to-end process for bringing a Class II medical device to the US market:

1. Determine your device meets the FDA's definition of a medical device — Review Section 201(h) of the FD&C Act. If your product is intended to diagnose, cure, mitigate, treat, or prevent disease, or to affect the structure or function of the body, it is likely a medical device.

2. Classify your device — Search the FDA Product Classification Database by keyword, identify candidate product codes, and confirm the classification by reading the regulation text. If uncertain, submit a 513(g) request or include the classification question in a Pre-Sub.

3. Identify the applicable regulatory pathway — For most Class II devices, this is a 510(k). Check whether your product code is 510(k) exempt. If no predicate exists, the De Novo pathway applies.

4. Identify and understand all applicable special controls — Read the classification regulation, download any applicable Class II Special Controls Guidance Documents, and review the De Novo decision summary if the product code was created through De Novo.

5. Select your predicate device(s) — Search the 510(k) database for cleared devices under your product code. Review their 510(k) summaries. Choose a predicate whose intended use and technological characteristics most closely align with your device.

6. Submit a Pre-Submission (recommended) — Discuss your classification, predicate choice, and testing strategy with the FDA review division before investing in testing.

7. Develop your device under design controls — Maintain a Design History File (DHF) documenting design inputs, outputs, reviews, verification, validation, and transfer. This is mandatory for all Class II devices.

8. Execute your testing program — Conduct all bench testing, biocompatibility testing, sterilization validation, EMC testing, software V&V, and clinical studies (if required) per your test plan. Ensure testing addresses every applicable special control.

9. Prepare and submit your 510(k) — Assemble your submission in eSTAR format. Run an internal RTA check. Pay the user fee. Submit through the CDRH Customer Collaboration Portal.

10. Respond to FDA questions — If the FDA issues an AI letter, respond thoroughly and within the timeframe specified. Each AI round adds weeks to your timeline.

11. Receive clearance — Upon a finding of substantial equivalence, the FDA issues a clearance letter and a clearance order. You can now legally market your device.

12. Complete post-clearance activities — Register your establishment, list your device, submit UDI information to GUDID, finalize labeling and packaging, and begin manufacturing.

13. Maintain ongoing compliance — MDR reporting, quality system maintenance, annual registration renewal, and post-market surveillance (if required) are continuing obligations.

Key Takeaways

1. Class II is defined by special controls. The regulatory distinction between Class I and Class II is the need for device-specific special controls beyond general controls. Understanding and complying with your device's special controls is the single most important compliance task.

2. 510(k) is the primary pathway, but not the only one. Most Class II devices reach the US market through a 510(k) premarket notification. However, some are 510(k) exempt, and novel devices without predicates use the De Novo pathway.

3. Know your product code. Your three-letter FDA product code is the key to everything — classification, special controls, submission type, exemption status, recognized consensus standards, and predicate history. Determine it early and confirm it.

4. Special controls guidance documents are your submission blueprint. If a Class II Special Controls Guidance Document exists for your device type, treat it as a mandatory checklist. Address every item explicitly in your submission.

5. FDA-recognized consensus standards save time and strengthen submissions. Declaring conformity to recognized standards can reduce the documentation burden in your 510(k) and provides reviewers with confidence that your testing follows established methodologies.

6. AI/ML and SaMD are overwhelmingly Class II. The AI/ML-enabled medical device space is dominated by Class II 510(k) clearances. Predetermined Change Control Plans (PCCPs) are emerging as a key mechanism for managing algorithm updates post-clearance.

7. International classification does not mirror FDA classification. A device that is Class II under FDA may be Class IIa, IIb, or even Class III under the EU MDR. Perform independent classification for every market.

8. Post-market obligations are ongoing. Clearance is the beginning, not the end. MDR reporting, quality system maintenance, UDI compliance, and potential post-market surveillance studies are continuing obligations for as long as the device is on the market.

9. Budget realistically. A Class II 510(k) typically costs $150,000–$500,000 total (without a clinical study) and takes 12–18 months. A De Novo costs more and takes longer. Factor in ongoing annual costs of $75,000–$250,000+ for quality system maintenance and regulatory compliance.

10. Use Pre-Submissions. The Pre-Sub process is free and provides direct FDA feedback on your regulatory strategy before you invest in a full submission. Use it whenever there is uncertainty about classification, predicate selection, or testing requirements.