The New York Times wrote an article (yesterday) and published an editorial on the issue of “information blocking” by software providers and their users (hospitals and labs) in the electronic medical records market. Information blocking is defined as “when groups knowingly and unreasonably interfere with the exchange or use of electronic health information.” For those of us in the tech sector, information blocking is also known as “dragging your feet”, “adding some friction/grit”, or imposing economic barriers to interoperability.
Interoperability: Good for the patient, less clear for the provider
The federal government has spent almost $29 billion in incentives to encourage use of electronic medical records by healthcare providers. Electronic medical records are expected to improve the quality of care and reduce health care costs. Clearly there are some successes in this market, based on companies we read about like Inovalon. But, according to a report to Congress from The Office of the National Coordinator for Health Information Technology (ONC) of the Department of Health and Human Services efforts to share these medical records are being impeded by existing players in the market.
Any company that has ever built a fairly dominant platform or network (as the electronic medical records players have) understands the conundrum. As a platform provider, you have invested a lot of money penetrating the market and building market share. All of a sudden, under the guise of interoperability, you see a bunch of small upstarts potentially free-riding on your investment to compete with you! “How is that fair?”, you think to yourself.
Interoperability in electronic medical records makes sense for the end client (the patient), but it does not make a lot of economic sense for the hospital, lab, or software provider–especially in the short run. The smart strategy for the incumbents is to “drag their feet”, or as Muhammad Ali called it “The Rope a Dope”. Incumbents will claim to support interoperability and open standards, but will also limit the investment in adaptors, APIs, and consulting to make it happen. Incumbents will make it possible, but a little painful, for those who want the data to actually get it.
Based on the New York Times article, this may be what is happening in the electronic medical records market. The article has accusations being leveled by the relatively new guy on the block, AthenaHealth, and one of the incumbents, Epic, saying they do not participate in such activities. Cerner, another big player is mentioned, but not quoted. The New York Times, liberal publication that it is, of course wants regulation. And Congress is starting to oblige.
Bring on the Feds?
I’ve written before (here) on the issue of interoperability between networks/platforms. I’ve also studied how interoperability has been achieved (or thwarted) in everything from rail systems to pallets to cell phone chargers to instant messaging systems. (You can find a deck on this topic in the Resources section of my website.) Not surprisingly, the lesson from this work is that interoperability is often a messy and long-term affair. If the industry players do not address it for their own good, it often does take some form of governmental pressure or at least standards making to make it happen in some reasonable time frame.
Look for battle between electronic medical records vendors to be played out in the marketplace and with the regulators. Increasingly, this is the life of platform providers. You need a strategy for every side of the platform, including Washington!
Bob,
Is an EHR (which is really ERP for integrated healthcare delivery networks) really a “Platform”?
I would simply call it an enterprise application suite. I feel no sympathy for EHR vendors or ERP vendors who try to impose this restrictive licensing. It’s just like how SAP has attempted to charge my clients from implementing bolt-ons and extracts they needed because vanilla wasn’t adequate. Such “indirect access fees” (and non-compliance fees) can really add up.
Nor do I feel sympathy for the buyers of the apps. The responsibility to negotiate the data access fees out of the contracts ultimately lies with the buyer. If you want to broaden the term ‘Platform’ to incorporate a packaged app, then I’d argue that a platform needs to be open, and you can make money by licensing the app development tools (and apps on a marketplace), but not access to the core freaking data. It’s like buying a moated castle, with no access rights to the drawbridge.
The healthcare industry can learn from other industries how to do proper procurement, including enterprise app procurement (and also vice versa – how to automate procurement with apps).
Just my 2 cents! Keep up the great work!
I think you are right, this is largely just a problem of incompatibility of formats and lack of interoperability, rather than a strict platform issue. (I have a tendency to get a little loose in my “definition” of a platform.) Certainly there are true platforms that sit on top of these incompatible systems, like Inovalon. I guess I thought of these folks as platform-like in that they were supposed to be compatible with various labs, outpatient clinics, specialists, etc. not just within one system–so, in theory they went beyond the immediate enterprise. But maybe they were only supposed to work in one “integrated delivery network (IDN)” or “in network system”. (Ugh, healthcare jargon!)