The EHR vendor lock-in business model is under attack by frustrated physicians and patients and the reality that health care cost and quality are more opaque than ever. Doug Fridsma of ONC politely talks of the need to move from vertical integration of health care services to horizontal integration where patients can choose with their feet. Farzad Mostashari calls for moral behavior and price transparency. The Society for Participatory Medicine says “Gimme My DAM Data” and Patient Privacy Rights asks HHS to allow physicians to prescribe health IT without interference from the institution or the vendor.
The vendors’ response is a charm offensive called CommonWell Health Alliance with a pastel .org website. The website is presumably the official source of information about CommonWell and it lays out the members’ strategy to preserve the vendor lock-in business model for a few $Billion more. Ok, maybe more than a few.
The core of the CommonWell strategy is to avoid giving patients their data in a timely and convenient way.
Podcast: Play in new window | Download
In a few days, I will be releasing the most controversial healthcare project I have ever worked on. But you do not need to take my word for it. I will be releasing a completely new healthcare data set. That data set, which will remain a “Mystery Data Set” until its release to the healthcare data scientists attending Strata RX, should completely revolutionize the way we think about healthcare delivery in the United States.
This mystery data set is the first real outcome of the Patient Skunkworks project. Patient Skunkworks is a new way for me to try and create high-impact but low-profit software projects. This is part of a new Not Only For Profit software development model that I have been working on. The new company forming to do this work will be called Not Only Development.
I will be releasing this data during the last keynote on the first morning (Oct 16) of the 2012 Strata RX conference. There is simply no way, in a single keynote, to even begin understanding all of the ways that this data set will be leveraged to improve healthcare. More importantly, there is really no way to adequately explain why I would choose to give away such a valuable and dangerous data set.
To help people digest the implications of this data set, I will be writing two articles about the data set. This one, before the release which helps to explain the underlying motivation behind the release, and another one after the release explaining what the data set is, and how I think it can be leveraged.
I am releasing this dataset because I believe that the only way to solve the problems in healthcare is to embrace a radical openness with health data. Healthcare data, with the exception of patient identity data, belongs in the open, in the sunlight. When used correctly, I believe that healthcare data should make patients feel empowered, and everyone else in the healthcare industry uncomfortable. I believe that patients deserve deep, dangerous and real access to data. I think when we start talking about how data might actually be dangerous for patients, its just a sign that we are “doing it right”. I call this concept Radical Access to Data (and yes, that recursively spells “RAD”).
Yesterday, Meaningful Use Stage 2 was released.
You can read the final rule here and you can read the announcement here.
As we read and parse the 900 or so pages of government-issued goodness, you can expect lots of commentary and discussion. Geek Doctor already has a summary and Motorcycle Guy can be expected to help us all parse the various health IT standards that have been newly blessed. Expect Brian Ahier to also be worth reading over the next couple of days.
I just wanted to highlight one thing about the newly released rules. As suspected, the actual use of the Direct Project will be a requirement. That means certified electronic health record (EHR) systems will have to implement it, and doctors and hospitals will have to exchange data with it. Awesome.
More importantly, this will be the first health IT interoperability standard with teeth. The National Institute of Standards and Technology (NIST) will be setting up an interoperability test server. It will not be enough to say that you support Direct. People will have to prove it. I love it. This has been the problem with Health Level 7 et al for years. No central standard for testing always means an unreliable and weak standard. Make no mistake, this is a critical and important move from the Office of the National Coordinator for Health Information Technology (ONC).
(Note: the following commentary was co-authored with Tory Wolff, a founding partner of Recon Strategy, a healthcare strategy consulting firm in Boston; Tory and I gratefully acknowledge the insightful feedback provided by Jay Chyung of Recon Strategy.)
Medicine has been notoriously slow to embrace the electronic medical record (EMR), but, spurred by tax incentives and the prospect of cost and outcomes accountability, the use of electronic medical records (EMRs) is finally catching on.
There are a large number of EMR vendors, who offer systems that are either the traditional client server model (where the medical center hosts the system) or a product which can be delivered via Software as a Service (SaaS) architecture, similar to what salesforce.com did for customer relationship management (CRM).
Historically, the lack of extensive standards have allowed hospital idiosyncrasies to be hard-coded into systems. Any one company’s EMR system isn’t particularly compatible with the EMR system from another company, resulting in – or, more fairly, perpetuating – the Tower of Babel that effectively exists as medical practices often lack the ability to share basic information easily with one another.
There’s widespread recognition that information exchange must improve – the challenge is how to get there.
One much-discussed approach are health information exchanges (HIE’s), defined by the Department of Health and Human Services as “Efforts to rapidly build capacity for exchanging health information across the health care system both within and across states.”
With some public funding and local contributions, public HIE’s can point to some successes (the Indiana Health Information Exchange, IHIE, is a leading example, as described here). The Direct Project – a national effort to coordinate health information exchange spearheaded by the Office of the National Coordinator for Health IT – also seems to be making progress. But the public HIEs are a long way from providing robust, rich and sustainable data exchange.