From the Family Health Manager to the Family Health Agent: HealthVault 2030 and the Household Care Circle
How a forgotten HealthVault insight about households, delegated care, and the real operating unit of healthcare points toward the next platform in the industry.
Sealab 2020 and the futures we actually got
One of my favorite cartoons as a kid was Sealab 2020. Not the later Adult Swim spoof Sealab 2021, which was magnificently deranged in the way only Adult Swim can be, but the earnest original: scientists living in an undersea base, peering through giant windows into the abyss, confidently occupying a future that seemed both inevitable and properly overengineered. It ran for a single season, but childhood has a way of turning thirteen episodes into an epoch, and in my memory Sealab 2020 lasted approximately as long as the Roman Empire. The funny thing, of course, is that the future almost never arrives where you expect it. We did not get undersea cities. We did not get moon hotels. We barely got the sort of space station that 2001 seemed to regard as an administrative inevitability. What we got instead was the network, the smartphone, and now AI systems capable of moving information, intent, and action across institutions that still behave as though the fax machine was not just viable, but spiritually correct.
That turns out to matter a great deal in healthcare, because healthcare has never really suffered from a lack of information. It suffers from a lack of coherent movement between islands of information. Hospitals know things. Specialists know things. Labs know things. Payers know things. Pharmacies know things. Family members know things. But the system as a whole has spent decades behaving as though assembling those fragments into a usable story were somebody else’s problem — ideally somebody underpaid, sleep-deprived, and already on hold with an insurer. When we started building HealthVault, that was the problem we were really trying to solve. The insight that made the product different was not just technical, and it certainly was not merely a prettier way to store PDFs. It was a shift in where we thought the center of gravity actually was.
The first Copernican shift in healthcare software
When Peter Neupert launched HealthVault, the line we used was that “the family is the center of healthcare.” I should probably note, once and only once, that I wrote that line in Peter’s speech. But the reason it landed had very little to do with rhetoric and everything to do with the research. By then, we had already spent months studying how healthcare actually worked inside households, and the conclusion was difficult to miss once you saw it. If you want to inspect the public artifact, Peter’s launch remarks are still worth reading, because they capture the public expression of a much deeper product thesis than most people realized at the time.
Peter had hired me quite deliberately for that job. He did not want only someone from the healthcare establishment, fully steeped in its assumptions and acronyms, though God knows the industry never suffers from an undersupply of acronyms. He wanted someone who could blend consumer research with technology thinking, which happened to line up rather neatly with my own background: nearly a decade at Procter & Gamble learning how households actually behave, followed by another stretch in technology companies trying to build systems that could scale. So instead of beginning with a conference room full of experts explaining how healthcare ought to work, we started by observing how it actually worked.
We brought in a research team I had worked with for years and asked them to spend time with families over several months, not just dropping in for a tidy interview but watching the real logistics of care management unfold in the wild. What they found was almost embarrassingly obvious once you saw it. Healthcare was rarely managed by “the patient” in isolation. More often than not, it was coordinated by someone inside the household who quietly carried the operational burden for everyone else: tracking appointments, remembering medication changes, dealing with insurance forms, keeping the immunization records straight, and making sure the right information arrived at the right doctor at the right time. We started calling that person the Family Health Manager. Usually it was mom, though certainly not always. The point was the role, not the gender. Once you saw that pattern, a great many personal health records suddenly looked as though they had been designed around the wrong center of gravity.
What the families taught us
The thing I remember most vividly from that field work is how little any of it resembled the clean boxes on healthcare PowerPoints. You did not need a white paper once you had spent a few afternoons in Midwestern kitchens and family rooms. Somewhere between the half-sorted school forms, the bottle of children’s acetaminophen, the insurance EOB that appeared to have been drafted by Kafka’s least cheerful nephew, and the pediatrician’s after-hours number written on an index card in increasingly urgent handwriting, the whole theory of the product would reveal itself. Every household seemed to contain a stack of forms reproducing quietly by mitosis on the countertop, which I realize is not a medically approved reproductive pathway, but it certainly appeared to be the dominant one, and one person — again, often mom, but not always — serving as the unpaid systems integrator for the entire family. The official story in healthcare IT was always patient, provider, chart. The actual story was calendar, caregiver, chaos.
And families, of course, are not static. Children turn eighteen and the access rules change. Parents age into needing help themselves. Couples divorce. Grandparents move in. Someone develops cognitive decline and responsibility shifts to an adult child. Someone dies, which is heartbreaking in the human sense and administratively clarifying in the grimmest possible way, because nothing reveals the true design of a system faster than asking who is still allowed to do what after the worst has happened. The old PHR model — one patient, one record, one owner — could not really metabolize that reality because it had started from the wrong cosmology. It assumed healthcare was an interaction between an individual and an institution. The field work told us something messier and, in my view, much more useful: healthcare is managed inside a changing household, by delegated authority, under conditions of permanent mild confusion.
That was the original Copernican shift of HealthVault. We did not move the patient out of the picture. We moved the model closer to reality. The patient still mattered, obviously. But the patient was not the only operational unit in the system, and often not even the primary one. The real unit of care was the household care circle — the patient plus whoever was actually carrying responsibility that week, whether that meant a spouse, a parent, an adult child, or some other designated helper with a calendar full of appointments and a thousand-yard stare from too many calls to the specialty pharmacy. Healthcare, in other words, was being run on a household operating system nobody had bothered to model.
How Sean Nolan turned insight into architecture
This is the part of the story that can get flattened if you tell it too quickly. The Family Health Manager insight was not just a marketing observation. It became architecture because Sean Nolan immediately understood what it implied for the platform. Sean and I ran HealthVault two-in-a-box: I handled the go-to-market side, Sean ran the technology platform, and one of the pleasures of that partnership was that when a piece of user insight surfaced, he could often see the structural consequence faster than anyone else in the room.
Most personal health records at the time assumed a fairly simple world: one patient, one record, one owner. But that model falls apart the moment you place it inside a real household. So Sean built something different. HealthVault supported multiple records, multiple levels of sharing, delegated custodianship, and transfer of responsibility as family circumstances changed. If you want to see that design logic in its own native habitat, it shows up very clearly in Microsoft’s old HealthVault Application Integration Recommendations, in the support guidance for sharing a HealthVault record, and in the old HealthVault Service Specification. The product did not treat caregiving as a feature. It treated caregiving as part of the underlying object model.
There was a quiet legal elegance to that model as well, and any serious 2030 version has to preserve it. One of the reasons the original HealthVault architecture mattered was that once the record was under the patient’s control, the patient could authorize where it went. That lined up neatly with rights HIPAA already recognizes: individuals have the right to access and obtain copies of their PHI, direct a covered entity to send that information to a designated third party, and rely on a personal representative to act on their behalf within the scope of the relevant authority. If you want the current source material, HHS lays this out in its guidance on Individuals’ Right under HIPAA to Access their Health Information and Personal Representatives. That mattered then, and it matters even more now, because the future version only works if it remains patient-controlled, family-delegated, auditable, and permissioned all the way down. Otherwise you do not have a care platform. You have a compliance incident with a pleasant onboarding flow.
Google Health as the control group
Google is useful here not as a punching bag but as a control group. When Google launched Google Health in 2008, the framing was unmistakably about the individual gathering and managing his or her own record online. You can see that in Marissa Mayer’s “Google Health, a first look”, and you can see the same framing in contemporary coverage like Wired’s “Google Launches Medical Records App”. That was a perfectly reasonable place to start if you believed the atomic unit of the system was the solitary patient with a solitary record. In fairness, most of the industry believed exactly that.
What makes the comparison interesting is that you can watch Google discovering the same reality we had stumbled onto earlier. In 2009, Google published “Google Health: helping you better coordinate your care”, which is a revealing title because the problem has suddenly widened from “my record” to “the care of loved ones.” But the product expression of that discovery was still essentially a sharing model layered on top of an individual record worldview. Caregiving appeared as an extension. In HealthVault, by contrast, delegated management had already become a native concept in the system. That sounds like a subtle difference until you live with it for a while, at which point it turns out not to be subtle at all. In healthcare software, permissioning is architecture. It is the difference between adding a guest room and realizing, somewhat late in the renovation, that the family actually lives in the kitchen.
By 2011, Google posted its shutdown note, saying the service was not having the broad impact it had hoped for, even though it had developed a loyal following among health and wellness enthusiasts, and among tech-savvy patients and caregivers. I do not think the correct lesson is “Microsoft good, Google bad.” That is too shallow to be useful, and besides, triumphalism ages even worse than software. The better lesson is that both companies were grappling with the same underlying reality, but one of them discovered caregiving as a feature request while the other let it reshape the data model. One added another epicycle. The other moved the sun.
Why HealthVault was early, not wrong
If you want the best retrospective account of why HealthVault now looks more plausible than it did when we launched it, Sean’s later writing is still the place to go. His essays “Health IT: More I, less T”, “SMART Part 4: Healthcare data sucks, and FHIR is no exception”, “explain my notes”, and “Refine your search for ‘gunshot wound’” form a kind of accidental archive of the long arc here. Sean makes two points in particular that are worth preserving. First, healthcare data is story-shaped before it is schema-shaped. Second, “comprehensive messy data trumps spotty clean data” far more often than tidy software people would prefer. Both observations were true in the HealthVault era. They are, if anything, more true now.
What has changed is that the rails are finally real. FHIR is no longer a standards-body hobby; SMART App Launch gives applications a workable model for launch and authorization; TEFCA’s designated QHINs mean there is at least an emerging exchange fabric; and Blue Button 2.0 made it normal to imagine large-scale patient-mediated claims access. None of that means healthcare interoperability has become elegant, and I would caution against getting drunk on a standards deck. But it does mean the world is no longer empty. The original HealthVault insight was right before the infrastructure could really carry it.
From the Family Health Manager to the Family Health Agent
This is where the next conceptual leap begins. In the original HealthVault research, the hidden operator in the system was the Family Health Manager — the spouse, parent, adult child, or other household coordinator carrying the memory, logistics, and emotional labor required to make care hang together. But once you see that role clearly, another question starts to present itself. What if the Family Health Manager did not have to be a human at all?
This is where Sangeet Paul Choudary’s idea of “coordination without consensus” becomes so powerful. In “AI’s Big Payoff Is Coordination, Not Automation” and in his Substack piece “The ‘bento box’ guide to the Reshuffle of professional services”, he argues that AI lowers the cost of translation and orchestration across fragmented actors who do not share a single process, ontology, or incentive system. You do not have to squint very hard to see healthcare in that description. If you were designing an industry specifically to test whether coordination without consensus is possible, you would build something very like healthcare and then perhaps apologize to everyone involved. Providers, payers, pharmacies, labs, schools, caregivers, specialists, and patients are all participating in the same drama with different vocabularies, different systems, and occasionally the unmistakable vibe of different planets.
So when I say Family Health Agent, I do not mean an artificial doctor. The world does not need a large language model in a lab coat with the bedside manner of Clippy. I mean something much more practical and, to my mind, much more valuable: a software chief of staff for the care circle. A patient-authorized, family-delegated system that can coordinate records, permissions, follow-ups, medications, summaries, handoffs, and administrative tasks across the household without pretending that every institution in the chain has suddenly become modern, interoperable, and spiritually well. The point is not to abolish the care circle. The point is to give the care circle a new operating layer. Mom has been the middleware for long enough.
A useful way to make that concrete is to look at Heydex, which positions itself as an AI chief of staff. Right now the product is pitched in the language of productivity, which makes sense; “chief of staff” is a polite way of saying that your current operating system consists of memory, tabs, calendar invites, and the rising suspicion that something important has already fallen off the back of the truck. But imagine the same core idea pointed at the household health graph rather than the knowledge worker’s calendar. Suddenly the Family Health Manager has software assistance that actually resembles the work being done: notice the cardiology follow-up never got booked, assemble the prior-auth packet, keep track of the refill gap, summarize what the nephrologist actually needs before the visit, and ask the right human for the right permission when the kid turns eighteen or Grandpa’s power of attorney changes. In that world, Heydex stops looking like a productivity tool and starts looking like an early prototype of a healthcare asset.
That is also the point at which the organizing unit of the system changes again. I do not think the patient is quite the right unit in 2030 any more than the chart was the right unit in 2007. The operational unit is the care circle: the patient, yes, but also the spouse, the adult child, the designated helper, the PCP, the specialist, the pharmacy, the plan, and whoever else is actually carrying responsibility in the moment. The Family Health Agent is the software layer that sits inside that care circle and does what families have been doing by hand for generations. It keeps the longitudinal story coherent. It understands delegated authority. It knows when to inform, when to ask permission, when to summarize, when to nudge, and when to get out of the way. In pediatrics, that means helping a family transition gracefully when a child ages into adulthood instead of dropping everyone through a bureaucratic trap door. In eldercare, it means turning the adult daughter from unpaid ETL pipeline into actual daughter again. In oncology, it means recognizing that a care journey is not a chart plus a claim plus a pharmacy event; it is a cross-institutional relay race whose baton has been dropped far too many times.
The next platform in healthcare
If this is right, then a depressing amount of the last two decades of healthcare IT has been several powerful industries fighting over the wrong map. EHR vendors assumed the center of gravity was the chart. Payers assumed it was the claim. Consumer health startups periodically assumed it was the motivated individual with an iPhone, a dashboard, and a saintly appetite for administrative labor. Each of them saw part of the truth. None of them really captured the operating reality, which is that care is coordinated inside a changing care circle by someone carrying delegated authority, household context, and an exhausting amount of memory. That person has historically been a spouse, a parent, an adult child, or some other Family Health Manager. The next great care platform will be built for that role.
And that is why the category claim is stronger than it first sounds. The next platform in healthcare will not be an EHR, because EHRs were built for institutions, and it will not be a payer network, because payer networks were built to adjudicate reimbursement. It will be the system that understands the household graph, the delegation graph, the permission graph, and the care timeline well enough to absorb the coordination labor families have been doing by hand for generations. Or, to put it a little less politely: the patient was never the problem. The patient was the workaround. The next platform in healthcare will not be an EHR or a payer network. It will be the Family Health Agent.