What motivates an EHR to change and improve?

Posted on

A recent article in The Health Care Blog about how some Electronic Health Records (EHR) systems are poorly enough designed to where they present bad information, and thus can lead to potential patient harm, got me to thinking. What motivates an EHR to make changes? Are hospital and ambulatory EHRs to be thought of in the same way? Do they respond to change differently?

The anecdote cited in the article concerns a hospital-based EHR – Cerner, in this case. As illustrated by Meaningful Use data on the hospital side, Cerner is one of the 5 predominant EHRs used in hospitals, and “should” be pretty good at what they do. In particular, what was identified as especially heinous was the medication list for a patient:

Looking at this list, something becomes evident: this is a list of prescriptions written for the patient, not a list of the medications the patient is on. As a result, multiple instances of prescriptions for the same medication appear, and there is no way of determining which medications are current and which ones have been stopped.

I have seen this kind of mistake made elsewhere as well. One of the better ways to think of the relationship between diagnoses, medications, and prescriptions is to recognize that they are hierarchically related – a diagnosis can have several medications “under” it, and a medication (which may be active, or may be discontinued) may have multiple prescription events “under” it. Visually, it might best be displayed somewhat like this:

Ambulatory EHRs have recognized this issue and more commonly have addressed it properly (though the mistake of showing a prescriptions-filled list, instead of a medications list, is still made). So the bigger issue is this: how do EHRs make changes and what kinds of pressures motivate them to do so?

Regulation vs. market pressure
The article lambasting the Cerner “medication list” made the argument that this is a bad enough problem that regulation should be leveraged – that EHRs should be regulated like “medical devices.”

Of course, this raises the question of who should do the regulating, if EHRs are to be thought of this way. The FDA has made a case for regulating EHRs for “safety,” like they do other medical devices – but this adds tremendous cost and delay to the development process, and could squash innovation. The Institute of Medicine (IOM) recently reviewed the issue at length and took a strong stance against the FDA regulating EHRs, given their ever-changing nature and the routine individual customization done at every installation site.

Others have argued that market pressure, not regulation, should be what causes change and improvements. After all, product and delivery are the main things that determine any business’ success in a competitive arena.

Perhaps ambulatory EHRs and hospital EHRs should be considered differently. On the ambulatory side, as we have seen, there are hundreds of products competing for physician adoption, with a dozen or so taking the majority of the market share. This is a scenario that lends itself well to market competition, and is a market segment that we have seen blossom with innovation. Federal policy should encourage, not inhibit, such innovation. Best practices, novel data visualizations, and products that actually streamline the workflows that are in place in ambulatory offices are all things that emerge from the competitive landscape seen here.

Hospital products, on the other hand, are a different beast. In part due to the very complex ecosystem that is the hospital environment, EHR products for inpatient use are concentrated in a much smaller array of companies – only 58 products (not 284) were used for achievement of hospital Meaningful Use, and most of the concentration was in 5 different companies (Cerner – the one highlighted by the THCB article – is one of them). Such systems are massive, enterprise installations, and much more difficult to rip-and-replace. The large hospital EHR systems are slow to change – there is little market pressure to do so, their technology is fairly legacy-based, and they are large enough to be heavy-handed (read that “gag clauses” in their contracts preventing detailed public criticism).

Perhaps a regulatory approach is more appropriate in that setting, where market pressures are less likely to cause change. Perhaps it is appropriate to think of hospital EHRs as a different creature, with different market dynamics, than ambulatory EHRs, which exist in a much more open and competitive arena. In the ambulatory space, regulation (if it is done poorly) may severely stifle innovation, and delay the movement to a unified national health IT platform – a key goal of the Office of the National Coordinator for Health IT (ONC). A delicate balance to achieve.

Robert Rowley

Robert Rowley

Dr. Rowley is a practicing family physician and healthcare information technology consultant. From its inception through 2012, Dr. Rowley had been Practice Fusion’s Chief Medical Officer, having created the underlying technology in his own practice, and using that as the original foundation of the Practice Fusion web-based EHR. Dr. Rowley brings a depth of experience and expertise in health care as well as health IT, having been in clinical practice for 30 years, including experience as a Medical Director with Hill Physicians Medical Group and as a developer of the early EMR system Medical ChartWizard. His family practice in Hayward, CA has functioned without paper charts since 2002.

More Posts - Website

Follow Me:
TwitterLinkedInGoogle Plus

Tags: , , ,


  • Pingback: Should EHR usability be regulated? - Robert Rowley MD

  • Pingback: EHR Usability as a corporate culture for vendors - Robert Rowley MD

  • Michael Esprit

    Dr. Rowley,
    I’m fairly new to the field of EHR (just finished school in Feb ’12 MISM/Healthcare). As look at the issue I’m leaning towards regulation. The stated purpose of EHR is the availiblity of individual health information and reduction of errors and costs. Now don’t get me wrong, I’m not necessarily a fan of regulation but the dynamics and size of the healthcare market in my view doesn’t respond to market pressures as other business. Adoption is the key to success and as long as confusion remains king medical practices will contuine to be slow to adopt, upcoming penalties will be evaluated against total cost of implementation including learning curve and treated as a cost of doing business. I think you can have both, 2008 is a prefect example when in prior years the banking industry was deregulated and no one was watching the store and the entire country almost failed. I almost inclined to treat EHR in a similar fashion as the railroad, electricity, and communications in the early years. The goverment should force standards without reducing competition and innovation. I believe standards will force the software houses to make their products comptetive in area’s where it counts and not in trying to be different for instance windows of Chevy’s and Fords, they operate in completely different directions; to me this just causes confussion not innovation.

  • pbug56

    I’ve noticed that it can be fairly difficult to get detailed info on the functionality of EHR’s (forget getting cost info on some). Some vendors, though, do have blogs or discussion areas or Facebook pages with lots of information and lots of user comments. Sometimes I’m a bit skeptical; one one site, I got the feeling that many of the comments – under different names, came from the same author! One that I found interesting is that of a free one, Practice Fusion. On both their site and FB pages, I see a lot of very frank discussion by users and PF staff, And the staff is very open about what they are doing, and what they are considering doing, and they are not stupid enough to rashly put early release dates out. They make it very clear that MU and government regs come first, but they listen very closely to what users say, and to a degree I believe they are influenced by user opinion.

    On a separate note, while I thing that the regs should be a lot more clear on things like data exchange, I don’t want the FDA involved. I’ve seen FDA involvement either cause huge delays for no apparent reason, and I’ve also seen vendors of medical products that have software use the FDA as an excuse for not doing software updates. A great example of that; a major insulin pump maker has still not updated it’s pump software for Windows 7, even though Windows 8 comes out in several weeks. They’ve had access to Win 7 since sometime in 2008, but whenever you inquire, they claim that it is being held up by the FDA. The thing is, the software is only used for dumping data from the pump and meter, and uploading food carb data to the meter, and my guess is that the FDA has minimal if any requirements for this. And even if FDA insists on approving such a software update, that update should have been out by fall 2009.

    I would like to see Stage 2 include some real standards. For instance, here is the EXACT format (presumably in XML) for HIE. Here is how you connect. Etc. Same thing for labs returning data – it should all be LOINC. And far more. And require competing regional HIE’s and private networks to work and play well together. Because without that, a lot of the rest is nearly a waste of time.