FDA 2026 Guidance + Enforcement Research¶

Date: April 15, 2026 Prepared by: Gene Lang, PharmD | Director of Pharmacy Operations Purpose: Primary-source verification of the regulatory landscape for Rx360's dual-track (Track B (Clinical) clinical / Track A (Wellness) wellness) pivot. This document supplements the existing "Medication Risk Tools and FDA Boundary Analysis for Rx360's Tiering System" PDF in this folder. Classification: Confidential — Internal Strategy

Executive summary¶

Three primary-source findings anchor Rx360's dual-track strategy:

FDA's 2026 General Wellness guidance update is real. Published January 6, 2026, supersedes the 2019 version. The two-factor framework (wellness intent + low risk) is unchanged, but the guidance adds explicit boundary language for non-invasive sensors measuring physiological parameters.
The WHOOP warning letter (July 14, 2025) set the enforcement precedent that marketing language alone cannot save a biometric measurement feature from device classification — but the January 2026 guidance simultaneously clarified that optical-sensing biometrics CAN remain in wellness IF no "medical-grade" claims are made.
The SeniorLife Technologies warning letter (August 21, 2025) is directly analogous to Rx360's risk profile. FDA cited fall risk prediction and early-Alzheimer's detection as diagnostic functions that could not hide under a "Measuring Exercise Equipment" (21 CFR 890.5360) registration. Specific flagged claim: "proactively identifies fall risk, recommends interventions, and continuously tracks patient mobility over time." This is Rx360's neighborhood — we must avoid this language pattern in any user-facing Track A (Wellness) surface.

01 FDA General Wellness Policy — 2026 Update¶

Document: General Wellness: Policy for Low Risk Devices Status: Final, published January 6, 2026 Supersedes: September 27, 2019 version FDA page: https://www.fda.gov/regulatory-information/search-fda-guidance-documents/general-wellness-policy-low-risk-devices

Core framework (unchanged from 2019)¶

Enforcement discretion applies when BOTH: 1. The device is intended only for general wellness use, AND 2. The device presents a low risk to the safety of users or other persons.

What's new in 2026¶

Non-invasive physiological sensors get a new section. Products measuring blood pressure, oxygen saturation, blood glucose, or heart rate variability via optical/non-invasive means can qualify as general wellness IF the intended use is wellness-focused and NO diagnostic or treatment claims are made.
Minimally invasive microneedle technology is explicitly OUT. A glucose measurement product using microneedles is invasive (penetrates the stratum corneum) and does not qualify for enforcement discretion, even if explicitly contraindicated for diabetics.
FDA held a Town Hall refresh on February 11, 2026 to walk the industry through the updated boundaries.

Implication for Rx360¶

The 2026 guidance is favorable for Rx360's Track A (Wellness) positioning. Rx360's device does not currently measure blood pressure, glucose, or other regulated physiological parameters via invasive means. The core features — haptic/audio medication reminders, dose confirmation, SOS, activity tracking — all sit comfortably inside the General Wellness envelope IF framed as wellness, not therapy.

Sources¶

02 WHOOP Warning Letter — July 14, 2025¶

Subject: WHOOP, Inc. — Blood Pressure Insights (BPI) feature Status: Issued July 14, 2025; FDA position softened slightly with the January 2026 General Wellness guidance update

What WHOOP was marketing¶

WHOOP's MG and Life memberships included a "Blood Pressure Insights" (BPI) feature in the companion app. BPI displayed estimated systolic and diastolic blood pressure ranges on a color-coded gauge, derived from heart rate, heart rate variability, and blood flow patterns measured during sleep.

FDA's position¶

Any function that measures or estimates blood pressure is inherently associated with diagnosing hypertension and hypotension, and is therefore intended for the diagnosis, cure, mitigation, treatment, or prevention of disease. The wellness exception does not apply. FDA further concluded that blood pressure estimation is not low-risk because inaccurate outputs can cause harm — either by falsely reassuring hypertensive users or delaying care for a frequently asymptomatic condition.

WHOOP's response¶

CEO Will Ahmed went on CNBC defending the feature. WHOOP publicly disagreed with FDA's classification but has not prevailed. A class-action lawsuit has since been anchored on the warning letter.

2026 update — partial walk-back¶

The January 2026 FDA General Wellness guidance update includes new language indicating that optical-sensing blood pressure measurement CAN remain in the general wellness category if no "medical-grade" claims are made and the use is wellness-focused. This is widely interpreted as a partial response to the WHOOP case — creating a narrow path for non-invasive biometric tracking to stay in wellness, provided marketing language is rigorously controlled.

Implication for Rx360¶

Two lessons:

Marketing language alone cannot save a feature from device classification if the underlying function is inherently diagnostic. Rx360 must have functional divergences in Track A (Wellness), not just different disclaimers. (This is the foundation of the "Track A (Wellness) is a delta, not just a rebrand" principle in the dual-track plan.)
Non-invasive biometrics have a narrow wellness path. Rx360's existing Mark I features (activity, dose confirmation button, haptic reminders) are all comfortably inside the envelope. Future features (HR, HRV, sleep, gait) should be designed from day one under the updated 2026 boundary language — specifically, no "medical-grade," "clinical," or "diagnostic" claims in marketing or UI.

Sources¶

03 SeniorLife Technologies Warning Letter — August 21, 2025¶

Subject: SeniorLife Technologies, Inc. — SeniorLife.AI mobile application FDA letter number: 707021 FDA inspection dates: March 24–26, 2025 (Bellevue, WA) Warning letter issue date: August 21, 2025

Why this matters most for Rx360¶

This is the single most directly analogous enforcement precedent for Rx360. SeniorLife was targeting the same population (older adults), marketing on a wearable/mobile platform, and making claims in the same clinical adjacency (fall risk, mobility, cognitive decline). The FDA's action sets the specific red lines Rx360 must not cross in any user-facing Track A (Wellness) surface.

What SeniorLife.AI was marketing¶

AI-based assessment of mobility and cognitive health in older adults
Fall risk prediction
Early Alzheimer's detection via a 5-minute gaze-based iPad test
Registered under 21 CFR 890.5360 (Measuring Exercise Equipment)

Specific flagged claims (verbatim from FDA letter)¶

"proactively identifies fall risk, recommends interventions, and continuously tracks patient mobility over time"
"conducts a 5-minute gaze-based test on an iPad to detect early signs of Alzheimer's"

FDA's findings¶

FDA determined the product's intended use far exceeded the scope of the 21 CFR 890.5360 classification. The app was found to be:

Adulterated under §501(f)(1)(B) — lacking required PMA or IDE
Misbranded under §502(o) — failing to submit a 510(k) notification
Further misbranded under §502(a) — falsely claiming FDA approval and certification on its website and app store listings

Implication for Rx360 (the hard red lines)¶

These SeniorLife claim patterns are BANNED in any Track A (Wellness) user-facing surface:

❌ "proactively identifies fall risk" — classification-triggering language
❌ "recommends interventions" — CDS crossing into therapy recommendation
❌ "continuously tracks patient mobility" — the word "patient" + clinical monitoring framing
❌ "detect early signs of [disease]" — explicit diagnostic claim
❌ Registering under a wrong CFR category — does not shield from intended-use analysis

Safe equivalents Rx360 CAN use in Track A (Wellness):

✅ "stay on top of your routine"
✅ "healthy aging support"
✅ "celebrate your active days"
✅ "share updates with your circle" (opt-in, no auto-alerts)
✅ "activity summary" (not "mobility tracking")

Sources¶

04 Consumer Data Flows — Surescripts vs. Blue Button 2.0¶

A critical architecture finding for Track A (Wellness)'s medication import workflow (PP-B4).

Surescripts — NOT a direct consumer API¶

Surescripts connects ~310 million patients (~95% of Americans) but access is gated to certified healthcare providers — prescribers, pharmacists, care teams, PBMs.
There is no consumer-authorized direct API for a wellness app to pull a user's medication history from Surescripts.
Historical consumer access (e.g., the 2009 Microsoft HealthVault integration) was pharmacy-mediated and has largely been deprecated.
Conclusion: Track A (Wellness) cannot use Surescripts as a consumer data pull. This corrects an earlier architecture assumption.

Medicare Blue Button 2.0 — IS a consumer-authorized API¶

CMS Blue Button 2.0 is a standards-based API delivering Medicare Part A, B, and D data for ~60 million Medicare beneficiaries.
Technical stack: HL7 FHIR for data format, OAuth 2.0 for beneficiary authorization.
Data available: Type of Medicare coverage, drug prescriptions (Part D), primary care treatment, cost.
Beneficiary control: The beneficiary authorizes app access via Medicare.gov. Data refreshes weekly; CMS recommends daily fetches.
Eligibility: Organizations must register for production API access; individual beneficiaries then authorize connection to trusted apps.
Coverage limitation: Only Medicare Part D prescription data — NOT commercial insurance, cash fills, or non-Medicare plans.

Implication for Rx360 Track A (Wellness) medication import¶

Primary flow: User self-entry via app UI with autocomplete from a drug dictionary (FDA OpenFDA + NLM RxNorm). This is the default and must work for every user regardless of insurance.

Secondary flow (Medicare Part D beneficiaries only): User authorizes Blue Button 2.0 connection, app pulls Part D prescription history, user reviews and confirms the imported list. This dramatically reduces friction for the ~60M Medicare beneficiary population — which is essentially Rx360's core demographic (65+).

Not available in Track A (Wellness): Surescripts pull, pharmacy system API integration, EHR FHIR direct connect. All of these are Track B (Clinical) infrastructure that gets reactivated in Phase 2/3.

Sources¶

05 Key takeaways for the dual-track plan¶

Track A (Wellness) has a cleaner regulatory path than we thought. The January 2026 FDA guidance update expanded the general wellness envelope. Rx360's core Mark I features sit comfortably inside it.
Functional divergence remains mandatory. WHOOP's warning letter is the textbook proof that marketing language does not override inherent medical function. Track A (Wellness) must have real feature-level differences from Track B (Clinical).
SeniorLife.AI is the closest enforcement precedent to Rx360. Every Track A (Wellness) deliverable must be checked against the specific claim patterns FDA flagged in that letter.
The Track A (Wellness) medication import architecture changes. No Surescripts consumer pull. Primary = user self-entry. Secondary = Blue Button 2.0 for Medicare Part D beneficiaries. PP-B4 draft needs this correction.
All of this feeds forward into the Wellness Lexicon + Claims Audit (Step 2a), the Architecture Brief v6 (Step 3), and the Peyman briefing (Step 7). Every downstream Track A (Wellness) deliverable can now cite primary sources from this document.

06 Research gaps still open¶

Legal opinion status — has Peyman actually received a legal read on IRB applicability yet, or is this still informal? Affects the tone of the Peyman briefing.
"Upper level want Track B (Clinical) vs B" clarification — Gene's typed language was ambiguous; pending confirmation.
Advarra NHSR determination pathway — still the fastest route if Track B (Clinical) holds. No change to prior research.
FDA CDS Software guidance (final, March 2026) — companion update to the General Wellness guidance. Should be pulled for completeness if we build a pharmacist-facing dashboard under Track B (Clinical) Phase 2/3.