So now it’s time to put lessons to work. The Patient as the Platform is my latest post over at Linux Journal, and it proposes something that goes beyond merely giving patients control of their health care records. (As do, say, Google Health and HealthVault.) Specifically,
I believe that having a data store for health records is a necessary but insufficient condition for the true independence and control required for each of us to be the point of integration for the health care we get, and the point of origination for controlling that care — for getting second and third opinions, for summoning data across bureaucratic boundaries, for actually relating to the systems that serve us, rather than serving as dependent variables within them.
For patients to become platforms, we need more tools and capabilities that are native to the patient. All of us need to be able to walk around the world with the ability to jack into any health care system and drive it. How? I don’t know yet. I’m still new to this. But I do know that these are capabilities we need to add to ourselves, as independent drivers of health care services. And that these must be based on free and open standards and code.
The new health care infrastructure must be built on independent and autonomous patients, not on systems that surround and subordinate patients. Once it is, the systems will be vastly improved, and far more profitable for all.
It’s a VRM angle, of course. And it concludes with the same pitch I’ll give here. If you’re interested in putting a shoulder to this boulder, or to weigh in on any of the other development efforts we have underway, come to the VRM Workshop on July 14-15 at Harvard. That page is short on details, but we’ll be filling them in shortly.