Posting in Design
Health IT vendors began construction of an "interoperability roadmap" just last year. Once the map is ready the roads must be built, connected and paid for. Each step is a massive system integration task.
The biggest challenge facing health reformers, whether public or private, is illustrated by the latest edition of Kaiser Permanente's Thrive commercials.
Kaiser's effort to create its Electronic Health Record (EHR) system was truly epic. As in Epic Systems, its lead contractor. Kaiser and Epic spent most of this decade wrestling with the contract for what is now called HealthConnect, and critics had a field day.
The Epic system is, in essence, a mainframe. It was designed years ago, before the Kaiser contract was signed. It may be 2009 where you live but in health IT it's still 1979.
Even with full cooperation from all sides, getting from there to here will not be easy, it will not be quick, and it will not be smooth.
The $1.8 billion Kaiser-Epic contract was signed in 2003, and while Kaiser is large it does not represent the whole market. Far from it. As other insurers, and hospital networks, build out their EHR systems, how are they all going to be connected?
Such data today is typically moved through a Regional Health Information Organization (RHIO) or Health Information Exchange (HIE). The key word in the above sentence is regional. There is, as yet, no national exchange of health information data. Nor will there be for several years.
All this spells big trouble for health reformers, regardless of party. The big Republican idea right now is to let insurers compete across state lines. How are they to then move the resulting data, if their service areas cross incompatible RHIOs? The big Democratic idea is a "public plan," which means an entirely new EHR infrastructure.
Health IT vendors began construction of an "interoperability roadmap" just last year. Once the map is ready the roads must be built. Then they must be connected. They must be paid for. Each step is a massive system integration task, with dozens of moving parts. Each will take years.
The industry is changing, in other words, faster than IT can adapt to it. Even national efforts to set standards are subject to industry sabotage.
Companies that have their plans in place, like Kaiser, will doubtless want to take full market advantage from their technology investment. They will not be anxious to surrender those advantages in the name of interoperability, changing or even transforming large hunks of infrastructure in response to outside demands.
The biggest health reform challenge, in short, is engineering.
Sep 3, 2009
Dan is right, healthcare is the "mother of all interoperability IT projects. Where's a "Ross the Boss Perot" or equivalient when we need leadership? If interoperability standards aren't laid out properly, *keyword is standards*, they might as well not even get started, every system will be silo'd and data hard to obtain. I live in Atlanta, Georgia and what if I go to the emergency room in Seattle during a visit, where/how with they get my up-to-date medical information and how long will it take in an emergency situation? Many issues involved with data privacy, security and access rights in addition to technical standards.
That's what you get when you are sold an EMR built on MUMPS http://en.wikipedia.org/wiki/MUMPS Does anyone know any MUMPS developers who were born after 1970? Then you build the largest Citrix farm on the planet to try and make it run. And all this for $4 BILLION. Not a bad deal. The answer is a browser based (ie. cloud + AJAX) EHR.
Since Kaiser Permanente is a nonprofit, I'm sure they would be willing to share their learnings, as they have in the past and currently do. Part of their mission is to give back to the community, and what better way to give back than to share one of the most sucessful Health IT ventures?