Medical Wearable FDA Clearance: A Practical Guide to 510(k) Submission for Wearable Devices
Author: Geyan Technology Innovation Regulatory Team
Date: 2025
Category: Regulatory Affairs / FDA Submission
Introduction: Why FDA Clearance Defines the Medical Wearable Market
The global medical wearable device market is projected to surpass $80 billion by 2028, driven by advances in sensor miniaturization, real-time health monitoring, and AI-powered diagnostics. Yet for every device that reaches the U.S. market, there is a regulatory gauntlet that separates commercial success from indefinite delay: the FDA 510(k) premarket notification.
The numbers tell a clear story. In fiscal year 2025, the FDA cleared approximately 3,238 devices through the 510(k) pathway, maintaining a steady volume of 3,000–3,300 annual clearances over the past several years (FY2023: 3,326; FY2024: 3,107). The 510(k) remains the dominant route to market, accounting for roughly 55–58% of all FDA marketing authorizations. Yet approximately 33% of submissions receive a Refuse to Accept (RTA) hold at least once, and roughly 67% encounter at least one Additional Information (AI) request during substantive review. For medical device startups and OEM manufacturers entering the wearable space, these statistics underscore a critical reality: preparation is everything.
This guide provides a practical roadmap through the 510(k) process for wearable medical devices, covering classification strategy, the three submission types, substantial equivalence determination, software documentation under IEC 62304, biocompatibility testing per ISO 10993, and clinical data considerations. It is written for regulatory affairs managers, device startup founders, and OEM procurement decision-makers who need actionable intelligence, not marketing generalities.
1. FDA Classification: Where Your Wearable Device Falls
The FDA classifies medical devices into three classes based on risk. Understanding where your wearable fits is the first—and most consequential—regulatory decision you will make.
Class I: Low-Risk Devices (General Controls)
Class I devices pose minimal risk to patients and are subject to general controls covering establishment registration, device listing, labeling, and adverse event reporting. Approximately 47% of all medical device types fall into Class I, and roughly 95% are exempt from 510(k) submission.
Wearable examples: Basic fitness trackers that count steps or monitor sleep duration without making diagnostic claims. Heart rate monitors marketed solely for wellness or exercise tracking, without disease detection language.
Key point: The same hardware can shift classification based entirely on intended use claims. A wrist-worn optical sensor that “tracks heart rate during exercise” is a wellness device. The same sensor that “detects atrial fibrillation” is a Class II medical device requiring 510(k) clearance.
Class II: Moderate-Risk Devices (General Controls + Special Controls)
Class II represents the largest category for regulated medical wearables—approximately 43% of all device types. Most Class II devices require 510(k) clearance. Special controls may include performance standards, post-market surveillance, patient registries, and device-specific FDA guidance.
Wearable examples with FDA product codes:
| Product Code | Device Description | Classification |
|---|---|---|
| QRZ | Over-the-counter ECG software | Class II |
| QKI | PPG-based irregular rhythm notification software | Class II |
| DQA | Pulse oximeter | Class II |
| DXN | Non-invasive blood pressure measurement system | Class II |
| MDS | Cardiac monitor (patch/Holter) | Class II |
| QMT | Photoplethysmograph oximetry software | Class II |
Landmark devices that define this space include the Apple Watch ECG App (De Novo DEN180044, product code QRZ), Samsung Galaxy Watch sleep apnea detection (De Novo, 2024), Abbott FreeStyle Libre 3 Plus CGM (510(k), 2024–2025), and Dexcom Stelo—the first OTC continuous glucose monitor (De Novo, 2024).
Class III: High-Risk Devices (PMA Pathway)
Class III devices sustain or support life, are implanted, or present potential unreasonable risk of illness or injury. These represent approximately 10% of device types. While most wearables fall into Class II, certain therapeutic wearables—such as wearable cardiac defibrillators or implantable neurostimulators—require the Premarket Approval (PMA) pathway rather than 510(k).
The De Novo Alternative
For genuinely novel wearable devices without a suitable predicate, the De Novo classification request provides a pathway to Class I or II designation. This is how Apple established the ECG and irregular rhythm notification categories in 2018. Once a De Novo classification is granted, subsequent similar devices can use the 510(k) pathway referencing the De Novo-authorized device as a predicate.
2. The 510(k) Submission: Three Pathways, One Goal
The FDA offers three 510(k) submission types. Choosing the right one can significantly affect your timeline and resource allocation.
Traditional 510(k)
The standard route for devices with a clear predicate. This submission requires a comprehensive comparison demonstrating that the new device is substantially equivalent to the predicate in intended use and technological characteristics. The FDA’s 90-day statutory review clock applies, but in practice, the average review time in 2025 was approximately 146 days. The submission must be filed using the mandatory eSTAR electronic template, which has been required for all 510(k) submissions since October 1, 2023.
Special 510(k)
For modifications to a manufacturer’s own previously cleared device. This streamlined pathway leverages the existing design control documentation and focuses on the specific changes. Review timelines are typically 30–60 days. This is the appropriate route for iterative improvements to an already-cleared wearable platform—such as adding a new sensor modality to an existing cleared device.
Abbreviated 510(k)
Relies on FDA-recognized consensus standards, guidance documents, or special controls to demonstrate substantial equivalence. When a device conforms to applicable FDA-recognized standards, the abbreviated pathway can reduce the documentation burden. Typical review runs 2–4 months.
The eSTAR Mandate: What Changed
Since October 2023, all 510(k) submissions must use the eSTAR template. This structured format standardizes the submission content and has been credited with reducing RTA hold rates. However, it also means reviewers can more efficiently identify gaps—making thorough preparation even more critical.
3. Substantial Equivalence: The Core of Every 510(k)
The FDA’s 510(k) program is not a direct approval of safety and effectiveness. It is a finding of substantial equivalence (SE) to a legally marketed predicate device. The FDA’s decision-making flowchart asks four sequential questions:
1. Is the predicate device legally marketed? If the predicate has been recalled, is in violation of the FD&C Act, or is not legally marketed, the SE determination fails at this gate.
2. Do the devices have the same intended use? “Intended use” encompasses both the general purpose of the device and the specific indications for use, including the target patient population. A change in indications that introduces new risks—such as expanding from professional use to home use with diagnostic claims—can result in a Not Substantially Equivalent (NSE) determination.
3. Do the devices have the same technological characteristics? In practice, very few devices have identical technological characteristics. Differences in materials, sensor configuration, energy source, or software algorithms are common.
4. Do the different technological characteristics raise different questions of safety and effectiveness? This is the most critical decision point. If the differences do not raise new questions, the FDA proceeds to evaluate performance data—bench testing, biocompatibility, software validation, and, where applicable, clinical data—to determine whether the new device is as safe and effective as the predicate.
A practical example: A wrist-worn ECG device using a new electrode material represents a different technological characteristic. The biocompatibility question this raises is not new—it is the same question asked of the predicate’s electrodes. The submission must include ISO 10993 testing data on the new material, but the device can still be found substantially equivalent. Conversely, if the same device replaces the ECG sensing mechanism with an entirely different modality (e.g., bioimpedance instead of electrical sensing), the FDA may determine that this raises different questions of safety and effectiveness, potentially triggering an NSE.
4. Software Documentation: IEC 62304 Compliance
For wearable medical devices, software is rarely an afterthought—it is often the device itself. The FDA expects software developed for medical devices to follow the IEC 62304 standard for software lifecycle processes.
Software Safety Classification
IEC 62304 requires classifying each software component into one of three safety classes:
– Class A: No harm possible from software failure. Documentation requirements are minimal but still include requirements specification, system testing, and release procedures.
– Class B: Potential non-serious injury. Requires architecture documentation, integration testing, and verification.
– Class C: Potential serious injury or death. Requires full documentation including detailed design, unit testing, and comprehensive traceability.
The default classification—if no formal classification is performed—is Class C, the most rigorous level. This is a common trap for first-time submitters.
Documentation Deliverables by Safety Class
| IEC 62304 Clause | Class A | Class B | Class C |
|---|---|---|---|
| Software Development Plan | ✓ | ✓ | ✓ |
| Requirements Specification | ✓ | ✓ | ✓ |
| Architecture Documentation | ✓ | ✓ | ✓ |
| Detailed Design | — | — | ✓ |
| Unit Verification | — | Recommended | ✓ |
| Integration Testing | — | ✓ | ✓ |
| System Testing | ✓ | ✓ | ✓ |
| Release Documentation | ✓ | ✓ | ✓ |
| Configuration Management | ✓ | ✓ | ✓ |
| Problem Resolution | ✓ | ✓ | ✓ |
SOUP: Software of Unknown Provenance
Most wearable devices incorporate third-party software—embedded Linux, Bluetooth stacks, open-source libraries. IEC 62304 classifies these as SOUP (Software of Unknown Provenance) and requires documented risk assessment and mitigation strategies. For each SOUP component, the submission should include a description of its function, the version used, known anomalies, and the risk controls applied.
5. Biocompatibility: ISO 10993 for Skin-Contacting Wearables
Wearable medical devices that contact the skin require biocompatibility evaluation per ISO 10993-1. Under the 2018 edition (currently recognized by the FDA), skin-contacting devices with prolonged contact (greater than 24 hours to 30 days) require at minimum:
– ISO 10993-5: Cytotoxicity testing—evaluates whether materials release substances toxic to cultured cells.
– ISO 10993-10: Skin sensitization testing—assesses allergic response potential.
– ISO 10993-23: Skin irritation testing (introduced 2021, consolidating irritation assessment previously under -10).
For devices with electrodes or adhesives that maintain continuous skin contact for 24 hours or more, these three endpoints form the regulatory minimum. Testing should be conducted on the final finished device, including all materials that contact the patient—housing, strap, electrodes, and adhesive components.
Important note: The 2025 revision of ISO 10993-1 (sixth edition, published November 2025) introduces restructured contact categories and expanded evaluation requirements. As of early 2026, the FDA has not yet recognized the 2025 edition. For U.S. submissions, the 2018 edition remains the recognized consensus standard. Manufacturers pursuing simultaneous EU MDR and FDA submissions should plan for both editions.
6. Clinical Data: When Bench Testing Isn’t Enough
A common misconception is that 510(k) submissions always require clinical trials. In reality, less than 10% of Class II 510(k) submissions include human clinical data. Most substantial equivalence determinations are supported by non-clinical bench performance testing, including:
– Electrical safety and electromagnetic compatibility (IEC 60601-1 series)
– Sensor accuracy and signal quality validation
– Software verification and validation
– Biocompatibility evaluation
– Sterilization validation (where applicable)
– Shelf-life and packaging integrity
Clinical data becomes necessary when bench testing cannot adequately address differences in technological characteristics or when the device’s intended use involves a novel clinical claim. For example, a wearable that claims to detect sleep apnea episodes—a diagnostic function—may require a clinical study comparing its output to polysomnography (the gold standard). The FDA’s Pre-Submission (Pre-Sub) program under the Q-Submission framework is the appropriate venue to discuss whether clinical data will be required for a specific device.
Clinical Study Design Considerations
When clinical data is required, the study design must align with the device’s risk profile and intended use:
– Endpoints: Primary endpoints should be clinically meaningful and aligned with FDA guidance specific to the device type.
– Comparator: For wearable sensors, the comparator is typically a cleared reference device or clinical gold standard.
– Population: The study population must reflect the intended use population, including relevant demographic and clinical characteristics.
– Sample size: Must be statistically justified with adequate power to support the primary endpoint.
7. Quality System: QMSR Has Replaced QSR 820
On February 2, 2026, the FDA’s Quality Management System Regulation (QMSR) officially replaced the long-standing Quality System Regulation (QSR 820). This is the most significant quality system change in nearly 30 years, aligning U.S. requirements more closely with ISO 13485:2016.
The QMSR introduces a more integrated approach to quality management, emphasizing management responsibility, risk-based decision-making, and design control throughout the product lifecycle. For wearable device manufacturers, the practical implications include:
– Enhanced design control documentation requirements
– Greater emphasis on supplier management and verification
– Risk management integration across all quality system elements
– More rigorous change control procedures
The 510(k) holder must maintain design control documentation and be prepared for FDA quality system inspection at any time after clearance.
8. Common Pitfalls and How to Avoid Them
Pitfall 1: Inadequate predicate selection. Selecting a predicate that has different indications for use or fundamental technological differences can lead to an NSE determination. Conduct a thorough 510(k) database search and, if possible, use a recently cleared device from the same product code.
Pitfall 2: Insufficient substantial equivalence rationale. The FDA needs more than a table comparing features. Each technological difference must be accompanied by an explanation of why it does not raise new safety or effectiveness questions, supported by testing data.
Pitfall 3: RTA hold due to missing documentation. The eSTAR template has reduced RTA rates, but approximately 33% of submissions still receive at least one RTA hold. Common missing items include incomplete device descriptions, missing biocompatibility test reports, and inadequate software documentation.
Pitfall 4: Software documentation gaps. Classifying all software as Class A without justification, or failing to document SOUP risk assessments, are frequent causes of AI requests during review.
Pitfall 5: Underestimating biocompatibility scope. Testing only the device housing while neglecting the strap material, electrode gel, or adhesive—all of which contact the skin—can result in a deficiency letter.
How Geyan Technology Innovation Supports Your 510(k) Journey
For medical device startups and OEM manufacturers, navigating the FDA 510(k) process requires both regulatory expertise and practical manufacturing experience. Geyan Technology Innovation brings years of hands-on experience supporting wearable medical device companies through the 510(k) submission process.
Our team provides regulatory documentation support, including device description preparation, substantial equivalence analysis, software documentation aligned with IEC 62304, and biocompatibility test planning per ISO 10993. We work alongside your regulatory affairs team to ensure submission packages are complete, well-organized, and responsive to FDA reviewer expectations.
For OEM partners, Geyan Technology Innovation supports the full product realization cycle—from design for manufacturability and prototype development through design control documentation and quality system compliance. We understand that a successful 510(k) is not just about the submission itself; it is about building a device that is manufacturable at scale, supported by robust quality systems, and positioned for post-market success.
Whether you are preparing your first 510(k) submission or scaling an existing cleared product line, our team is ready to collaborate.
Contact Geyan Technology Innovation Regulatory Support:
– Email: jine@xdunmedical.com
– Phone/WhatsApp: +86-13544254314
Disclaimer: This article provides general regulatory information and does not constitute legal or regulatory advice. Device manufacturers should consult with qualified regulatory professionals and the latest FDA guidance documents for submission-specific requirements. FDA regulations and guidance are subject to change.