Why we don't track health data passively (and what we do instead)

When we were designing FamAI's health features, the obvious move was wearable integration. Connect to a fitness tracker, pull in step counts and heart rate, generate a nice dashboard. It's what health apps do.

We didn't do it. Here's why.

The passive tracking problem

Wearables and fitness apps generate a continuous stream of numbers: heart rate, steps, sleep stages, blood oxygen. For a young person optimizing performance, this data is useful. For a 68-year-old with hypertension and diabetes, it tends to produce anxiety rather than insight.

Continuous heart rate monitoring, for example, will catch normal variation during activity or sleep and flag it as unusual. The data is accurate. But "accurate" is not the same as "useful." An elderly person seeing a heart rate spike notification at 2am has no way to contextualize whether it's benign (deep sleep phase) or concerning (arrhythmia). The most common response is worry, followed by a call to their adult child, followed by a doctor visit that confirms everything is fine.

Passive tracking creates a monitoring dynamic that feels intrusive. Many elderly parents resist it for exactly this reason — not because they don't care about health, but because they don't want to feel surveilled by their own devices.

What active logging actually measures

The health conditions that matter most for Indian seniors in their 60s-70s are Type 2 diabetes and hypertension. Both require tracking two numbers: glucose and blood pressure. Both are typically measured with devices the parent already owns — a glucometer, a BP monitor.

The problem isn't the measurement. It's the recording. Most parents check their sugar, note it in their head or on a scrap of paper, and forget about it until the next doctor visit. By then, they have a vague memory of "it was a bit high last Tuesday" but nothing concrete to share.

FamAI's approach: your parent checks their reading and tells FamAI. "Sugar 168, fasting." That's it. FamAI logs it with a timestamp and provides immediate context — normal, slightly elevated, high — without being alarmist. Over weeks, those readings build into a trend that's actually useful for a doctor's appointment.

Why active is more honest

A wearable gives you continuous data, but much of it is low-quality or uncontextualized. A glucose reading that your parent actively reports — with context ("fasting", "after lunch", "post-walk") — is more honest than a continuous glucose monitor that doesn't know why the number spiked.

We know less than a wearable. We know what the parent chose to tell us. That's a limitation, but it's also a kind of data integrity. Every reading in FamAI's log was intentionally submitted, with context, by the person whose health it represents. That's a stronger signal than a sensor that runs all day in the background.

Wellness signals, not diagnoses

When your parent logs a reading, FamAI replies immediately with a wellness signal: normal, slightly elevated, or high. We deliberately avoided more specific feedback.

The reason: FamAI is not a medical device. A reading of 210 mg/dL in the morning means something different if the parent just ate, if they're sick, if they've changed their diet, if their medication was recently adjusted. FamAI doesn't have that context. A doctor does.

The right thing to say is not "your sugar is dangerously high, go to the hospital." The right thing to say is "this is elevated — worth discussing with your doctor." That's what we do.

The privacy question

Adult children see a summary and trend through the FamAI dashboard — not individual readings in real time. This was a deliberate choice. Your parent's daily blood sugar log is not something their kid should be monitoring as a live feed. That's surveillance, not care.

The right dynamic: the parent logs for their own awareness, the kid sees the trend if they want to, and the doctor gets a summary when needed. FamAI facilitates all three without making any one of them feel more important than the others.