Insurance companies skip patient-specific data collection (wearables, health history) and apply algorithms to incomplete data, leading to inaccurate risk assessments and harmful coverage denials
API platform that aggregates patient-consented wearable data (Fitbit, Apple Watch, CGMs) into standardized health profiles that plug into insurer risk models, ensuring individual circumstances are factored in per CMS Final Rule requirements
B2B SaaS subscription per-member-per-month pricing to insurers
The pain is real but diffuse. MA plans lose millions from inaccurate risk adjustment (both over- and under-coding), and RADV audits create clawback risk. However, most plans have survived without wearable data — this is a 'better inputs = better outcomes' argument, not a 'we're bleeding and need to stop it now' emergency. The CMS V28 model changes make this more urgent by dropping ~2,000 diagnosis codes and demanding specificity that wearable/CGM data can uniquely support. Pain will intensify through 2026 as V28 fully phases in.
Narrow TAM (wearable data APIs for health insurers): $500M–$1B. MA-specific opportunity: 33M+ members, plans spend $200-400/member/year on risk adjustment ops — capturing even a thin slice is meaningful. If 10% of MA members have wearable data integrated at $2-5 PMPM, that's $80M-$200M for MA alone. Broader TAM including commercial insurers and Medicaid managed care pushes toward $1B+. Not a massive market, but large enough for a very good outcome and with clear expansion paths.
MA plans absolutely spend on risk adjustment tools — this is a proven budget category. But willingness to pay specifically for wearable data integration is unproven. The value proposition requires demonstrating that wearable data meaningfully improves RAF scores or reduces RADV audit risk, which demands clinical validation studies. Plans are conservative buyers with 12-18 month sales cycles. The PMPM model is familiar to them, which helps. Score would jump to 8 if you can show a 0.5%+ RAF score improvement in a pilot.
This is where it gets hard. A solo dev CANNOT build a credible MVP in 4-8 weeks. Challenges: (1) Wearable API integrations are fragile and each vendor (Fitbit/Google Health Connect, Apple HealthKit, Dexcom, Abbott) has different auth flows, data models, and rate limits — minimum 3-4 weeks per integration. (2) HIPAA compliance requires BAAs, encryption, audit logging, and hosting on HIPAA-eligible infrastructure. (3) FHIR R4 data modeling is complex and must be done correctly for payer trust. (4) Patient consent management has legal requirements varying by state. A realistic MVP (one wearable source + FHIR output + basic consent flow) is 12-16 weeks for a strong health IT developer. Getting to production-grade with multiple sources is 6-12 months.
This is the strongest dimension. No single platform today combines: (1) wearable/CGM data aggregation, (2) FHIR normalization, (3) CMS-HCC risk adjustment code mapping, and (4) MA plan compliance packaging. Validic has devices but no risk adjustment. 1upHealth has CMS compliance but no wearables. Cotiviti/Inovalon have the risk adjustment pipeline but no device data. You sit in the clear whitespace between these categories. The risk is that one of these players builds or acquires into your niche — but the window is open now.
Textbook recurring revenue. PMPM pricing is the standard in health plan SaaS — plans budget annually and pay monthly per enrolled member. Wearable data is inherently continuous (daily steps, glucose readings, heart rate), creating ongoing data processing that justifies ongoing fees. Once integrated into a plan's risk adjustment pipeline, switching costs are very high (revalidation, compliance re-certification, member re-consent). Net revenue retention in health plan SaaS typically exceeds 110%.
- +Clear whitespace — no one combines wearable data aggregation with CMS-HCC risk adjustment mapping for MA plans
- +Powerful regulatory tailwind: CMS-0057 (Jan 2026) and V28 model changes create urgency that didn't exist 2 years ago
- +PMPM pricing model is proven and expected in this market, with very high switching costs once embedded
- +Massive exit potential — PE firms and strategics are acquiring health data companies at 8-15x revenue multiples
- +The Reddit signal is directionally correct: the industry knows 'garbage in, garbage out' is the real problem, not fancier algorithms
- !Enterprise sales cycle to health plans is 12-18 months — runway must survive this valley of death before first meaningful revenue
- !HIPAA compliance, BAA requirements, and SOC 2 certification create a significant upfront cost and complexity burden before you can sell
- !Clinical validation is needed — you must PROVE wearable data improves RAF scores, not just assert it, and that requires pilot data with real plans
- !Wearable adoption among Medicare beneficiaries (65+) is lower than general population — data availability may be thinner than expected
- !Regulatory risk: CMS could change rules around what supplemental data qualifies for risk adjustment, or a major player (1upHealth, Validic) could pivot into your exact niche
Aggregates clinical records and consumer health device data with patient consent, focused on life and health insurance underwriting. Combines EHR data with some wearable data for accelerated underwriting decisions.
Connects 500+ wearable and medical device types, normalizes data via REST APIs. Serves health plans like Humana and Kaiser Permanente for care management and population health.
FHIR-native health data aggregation platform built specifically for payer interoperability. Helps plans comply with CMS interoperability mandates by connecting claims, clinical, and provider data via FHIR R4 APIs.
Health data network accessing nationwide clinical data through HIE networks
Enterprise platforms that power risk adjustment, payment accuracy, and quality measurement for Medicare Advantage plans. Inovalon taken private at $7.3B; Cotiviti acquired for $4.9B. They ARE the risk adjustment pipeline that PatientData Bridge would plug into.
Single-integration proof of concept: Fitbit/Google Health Connect data → FHIR R4 normalized profiles → diabetes-specific HCC code support evidence (HCC 17-19, 35-38). Target one MA plan's diabetes population. Show that CGM/activity data from wearables can support or identify missed HCC codes that chart review alone would miss. Package as a pilot with 500-1,000 members. Skip building the full multi-device platform — prove the actuarial value with one device and one condition first.
Free pilot (500 members, 90 days) with one MA plan to generate clinical validation data → Paid pilot ($2-3 PMPM) expanding to full diabetes population → Production contract ($3-5 PMPM) covering multiple chronic conditions → Platform expansion to multiple device types and commercial insurers → Enterprise licensing to risk adjustment vendors (Cotiviti, Inovalon) as an embedded data source
9-15 months. Expect 3-4 months to build a HIPAA-compliant MVP with one wearable integration, 2-3 months to land a pilot partner (likely through a health IT consulting relationship or accelerator like Plug and Play Health or Dreamit), 3-6 months to run the pilot and generate validation data, then 1-2 months to convert to a paid contract. First meaningful ARR ($100K+) is likely 18-24 months out.
- “skipping the first step and applies rocket science to the second”
- “if the inputs are weak then better analytics just scale the mistake faster”
- “the boring work of getting patient specific data right usually matters more than a flashy prediction layer”
- “available using inexpensive worn monitors like the FitBit”