In a previous post, I briefly mentioned how the U.S. Department of Health and Human Services has started developing regional networks of electronic health information. Eventually, these networks will merge into a “network of networks,” thus working toward a nationwide, compatible system of electronic health records by 2014.
Unfortunately this “network of networks” approach of regional heath information organizations (RHIOs) has some serious faults. And the alternative system currently favored by many, health record data banks, still poses a lot of unanswered questions.
According to an October report from the Information Technology and Innovation Foundation (ITIF), the major problem with RHIOs is coordination: “multiple, heterogeneous databases” require “the extensive use of middleware—that is, software used to interface between incompatible databases and data formats.” Otherwise it’s like trying to run Mac software on a PC. Other coordination challenges include accurate patient identification (is John Smith in the Bronx the same as John Q. Smith in Cleveland?) and ensuring comparable service quality—each network needs to be as fast and secure as its peers.
With all of these inefficiencies, the ITIF study notes that RHIOs don’t make a very compelling business case to the health care providers who are expected to implement and operate the networks. Most of the system’s savings go to patients (because they can expect better care) and insurers (because mistakes can be avoided) rather than hospitals and doctors, who incur all the costs of transitioning to a new IT platform—a fact of which they’re well aware. A 2006 JAMA study showed that health care providers are worried about IT transitions primarily because of start-up costs (installation, consultation, training, etc), ongoing costs (such as compliance with privacy laws—no small matter, given the ambiguity of HIPPA) and the potential loss of productivity as employees learn the new system.
In lieu of RHIOs, ITIF recommends health record data banks (HRDBs), a model that has gotten a lot of buzz over recent months—including its own bill in Congress last year.
The simplest way to explain HRDBs is via analogy: think of how you engage with a commercial bank account, and you’re on the right track. Just as you choose a bank from a competitive marketplace of financial institutions, so would you pick an HRDB provider from many vying for your business; just as you open a bank account, so would you start a medical record account; and just as you log in to access financial information, make transactions, and monitor your activity with a bank, so would the HRDB service let you sign in online to access to your medical history, test results, and so on.