FDA Clears the Runway for Wearables and AI: What Medtech Innovators Need to Know

The regulatory ground under wearable and AI-enabled devices is shifting—and for once, it’s in a direction many innovators will welcome. In early 2026, FDA issued updated guidance on low‑risk wellness products (including many wearables) and on clinical decision support (CDS) software, easing premarket requirements for certain functions while clarifying where full device regulation still applies. For startups building on-wrist, on‑body, or ambient sensing platforms, these changes open new doors—but also introduce new strategic choices around claims, data, and go‑to‑market plans. 

What Changed for “Wellness” Wearables 

FDA’s revised wellness guidance takes a broader view of what can qualify as a non‑device “general wellness product,” especially for noninvasive wearables that estimate health metrics like heart rate, heart rate variability, or even blood glucose and blood pressure under certain conditions. To fit within this lighter‑touch framework, a product must: 

• Be intended solely for general wellness (for example, sleep optimization, fitness, stress management), not diagnosis, cure, mitigation, prevention, or treatment of disease. 

• Present minimal risk to users, typically through noninvasive sensing and low‑risk use cases. 

• Avoid specific disease or condition claims and avoid characterizing outputs as “abnormal,” “concerning,” or diagnostic in nature. 

The practical impact: more consumer‑facing wearables that estimate health‑related metrics may be able to stay outside the medical device pathway—if their claims, labeling, and user experience stay firmly anchored in wellness. This is a meaningful shift from past interpretations that brought some functions, like blood pressure estimation, under medical device scrutiny by default. 

When Wearables Can Say “Talk to Your Doctor” 

One of the most notable updates is that wearables classified as general wellness products can now prompt users to seek evaluation from a healthcare provider when readings fall outside ranges appropriate for wellness use, without automatically becoming medical devices. For example, a wearable could flag a low oxygen saturation reading and suggest the user talk to a clinician, so long as it doesn’t label the result as a specific disease, or as “abnormal” in a diagnostic sense. 

This is a subtle but important shift. It gives companies more latitude to design meaningful, safety‑oriented alerts that nudge users toward care—while stopping short of diagnosis or treatment recommendations. However, the guidance leaves open questions, such as: 

• How to define “appropriate ranges” for general wellness versus medical use? 

• How to write notifications that are both useful and compliant, when you can’t name diseases or characterize outputs as abnormal?  

For product, regulatory, and UX teams, that means the wording of every alert, in‑app message, and marketing claim matters more than ever. 

AI and Clinical Decision Support: More Room to Innovate 

The companion guidance on CDS software clarifies when CDS functions fall under enforcement discretion (and thus lighter oversight) versus when they are treated as regulated devices. The core criteria for CDS haven’t changed, but FDA has adjusted how it views certain use cases. 

Under the updated approach: 

• Software can, in some cases, offer a single recommended option (such as a treatment or diagnostic pathway) and still be under enforcement discretion, if that recommendation is clinically appropriate and the clinician can independently review the basis for it. 

• Tools that predict longer‑term risk (for example, cardiovascular risk over several years) based on standard clinical variables may remain under enforcement discretion, while near‑term, high‑acuity predictions (for example, 24‑hour event risk) will more often fall under active FDA oversight.  

For wearable and digital health companies, this is directly relevant to AI‑driven features such as risk scoring, trend analysis, and clinician‑facing dashboards. The more your software looks like a direct diagnostic, immediate treatment selector, or automated interpreter of raw images or signals, the more likely it is to be regulated as a device. 

How Consumer Wearables See the New Landscape 

Major wearable and digital health brands are starting to shape the conversation around this new regulatory landscape, but few have been as explicit as Oura in calling for a modernized framework. In a recent discussion of the new guidance, CEO Tom Hale emphasized that as wearables advance, “It is crucial that modern regulations differentiate between early detection and medical diagnosis.” 

Oura has advocated for a category of “digital health screeners” that can alert users to potential issues and encourage follow‑up, without triggering the full weight of medical device regulation when the risk profile is low. The latest FDA moves—allowing certain blood pressure and similar features to be treated as wellness functions when positioned appropriately and enabling wearables to point users toward care—reflect this direction and may give companies like Oura more room to innovate while maintaining clear guardrails. 

For other wearable makers, Oura’s stance underscores a key strategic question: How far do you want to lean into medical claims and regulated indications versus remaining in a more flexible, wellness‑oriented space with broader consumer reach? 

Strategic Implications for Wearable and Digital Health Teams 

For medtech startups and established players alike, these guidances create both opportunity and complexity. A few high‑level implications: 

• Claim strategy is now a primary design decision. The same sensor stack can support radically different regulatory pathways depending on whether you frame outputs as wellness insights, early screeners, or medical diagnostics. 

• Labeling and UX will be scrutinized. Even if your core functionality appears to fit under wellness or CDS enforcement discretion, a single disease‑specific claim, risk timeframe, or “abnormal” label can pull you into device territory. 

• AI transparency expectations are rising. For CDS‑like features, FDA expects that clinicians can understand the logic behind recommendations, including input data, validation, and performance characteristics. This has design and documentation implications for any AI‑enabled wearable intended for clinical workflows. 

• Payers and health systems will respond in their own time. While FDA is loosening reins on low‑risk wearables, it’s not yet clear how quickly insurers and large providers will update coverage, purchasing, or integration strategies. 

How Avio Medtech Can Help 

The headline is simple: regulatory pathways for wearables and AI are getting more flexible—but not simpler. The details live in guidance documents, enforcement trends, and subtle distinctions in how you describe and deliver your product. 

If your team is unsure how these FDA updates apply to your roadmap, we can help you cut through the noise, focus on what matters, and move forward with confidence. To explore how these shifts affect your specific product, reach out to start the conversation.