Whats Wrong with EHR User Interfaces?
Whats Wrong with EHR User Interfaces?
A February HDM feature took an in-depth look at ongoing concerns about user interfaces for electronic health records systems. Heres a look at some of the problems and solutions identified by HIT experts.
In the Way

Theres no doubt that, at best, EHRs often get in the way. "The physician's day is a large set of interleaved tasks, and the tools should be designed to facilitate the safe conducting of that work," says Scott Finley, M.D., senior physician informaticist at the research company Westat, Rockville, Md.
"Most health I.T. tools tend to slow users down." He adds that most EHRs are bad at helping physicians juggle the simultaneous tasks they all face, like answering a question about one patient while in the middle of writing a prescription for another.
An Antiquated Look

One reason EHR user interfaces are generally poor is many of them originated years, or even decades, ago, before today's sophisticated interface tools were developed. "Sometimes what you want to do on the front end requires significant change on the back end," says Ted Shortliffe, M.D., president of the American Medical Informatics Association.
"It's not just a matter of mucking around with the interface. And retrofitting a large base of existing systems is extremely complex and expensive. Many vendors shudder at the thought."
Misunderstanding Physician Needs

Lack of understanding of what clinicians need is at the heart of the problem. Every vendor has armies of advisors with medical and nursing degrees, but advice isn't enoughor even useful most of the time, says Paul Tang, M.D., vice president of innovation and technology at Palo Alto Medical Foundation.
Instead, software developers should be standing at the user's elbow watching what he or she does all day, and then figuring out how the EHR can help. "Observing customers in the field is far more effective than listening to folks tell you what they would like to have," Tang says.
Lack of Information

Lack of information flow is another issue. Vendors are understandably protective of their intellectual property, which includes the appearance and function of user interfaces. Contracts frequently limit how much information customers are allowed to share about the interfaces.
"The problem is that this industry is closed," says computer science professor Ben Shneiderman of the University of Maryland "You talk about the iPad and everyone can buy one and see one, but no one will show me an EHR interface without my signing a nondisclosure agreement.
Chicken and Egg Problem

Here's a chicken-and-egg problem: in order to improve usability, a vendor may allow a hospital to accommodate individual users with customized templates and other modifications that make the system mirror how they work. If the vendor offers an upgrade that improves usability in the product as a whole, it might not work with the hospital's modifications. And different hospitals can't take advantage of one another's experiences.
"It's difficult even for customers using the same products to compare notes because their implementation is so different," says Art Swanson, director of user experience for ambulatory EHR vendor Allscripts. "A client will say, 'Oh, why can't we do X [that another hospital is doing],' and then they'll do some digging and realize it's because of how the other hospital has customized."
R-E-S-P-E-C-T

For improved usability, EHRs need several key characteristics, experts say. The first is implicit respect for the user. EHRs have horrible social skills, explains Scott Finley, M.D., senior physician informaticist at Westat, who specializes in usability issues.
"We have computer systems behaving like badly trained children," he says. "They scream interruptions without regard to how likely they are to be correct, and without regard to their own standing in the relationship." Instead, he says, an EHR should be like an exquisitely trained butler, quietly anticipating the user's needs, fixing problems before they get out of hand, whispering instead of shouting (and only the necessary information at the right time).
Dare to Be Different

Minimizing data entry is often cited as a necessity for improving interfaces, but effective EHRs also should allow for interfaces that reflect different purposes. Not every device needs to do everything. "There's a big difference between reviewing and creating information," says Harry Greenspun, M.D., senior advisor, healthcare transformation and technology at Deloitte.
A physician on call may want to find a few crucial pieces of information and can use a smartphone or touchscreen tablet with specialized views, whereas one that's catching up on documentation or e-mail will need a full keyboard.
Size Matters

While smartphones and tablets seem red-hot, experts say the single most useful recent technological development is large high-definition screens. "We've been constrained by screen real estate for so long," says Scott Lind, director of user experience at Siemens Healthcare. "Bigger screens let us make better use of space, using white space to frame information and focus the user's attention."
As engaging as the iPad interface is, its screen is just not big enough to deal with the amount of data clinicians typically want to see all at once, says Paul Tang, the chief innovation and technology officer at Palo Alto (Calif.) Medical Foundation. "We're trying to increase screen size, which helps us with the key problem of having to flip through screens. We want more information displayed properly on the screen at the same time."
Future Generations

All too often, EHRs have looked like an engineer's rendition of a paper chart, and usability experts should be able to do better with the next generation, says Mike Nolte, vice president and general manager of GE Health I.T.
"There were lots of good reasons to do it that wayit felt familiar to the users and didn't ask a lot of thembut the developers weren't thinking about how to best use software to enhance productivity and change the way physicians work."
More Info

To read the entire HDM feature about user interfaces, User Unfriendly, click here.