Electronic health records: Physician's perspective on usability

Robert M. Schumacher, Lyle Berkowitz, Paul Abramson, David Liebovitz

Research output: Chapter in Book/Report/Conference proceedingConference contribution

5 Scopus citations

Abstract

The usability of electronic health records (EHRs) has received increased attention as it has been identified as one of the key barriers to adoption of EHRs. Every day, health care workers face many usability issues with EHRs such as workflows that do not match clinical processes, alert fatigue (both visual and audio), information overload and frustration with what is perceived as excessive clicks during routine tasks. All this contributes to frustration, and, ultimately, impacts patient care. But what does it mean to have a 'usable' application? Why are EHRs hard to use? This panel brings together practicing physicians trained in medical informatics to provide their unique and front-line perspective on what the real issues are with EHRs and how human factors affects usage. We will address three questions: (1) Why is usability a hard problem in EHRs? (2) From a user's view, what is the cost of poor usability? And (3) what can be done to increase adoption and usage of EHRs in the clinical setting?

Original languageEnglish (US)
Title of host publication54th Human Factors and Ergonomics Society Annual Meeting 2010, HFES 2010
Pages816-820
Number of pages5
DOIs
StatePublished - Dec 1 2010
Event54th Human Factors and Ergonomics Society Annual Meeting 2010, HFES 2010 - San Francisco, CA, United States
Duration: Sep 27 2010Oct 1 2010

Publication series

NameProceedings of the Human Factors and Ergonomics Society
Volume2
ISSN (Print)1071-1813

Other

Other54th Human Factors and Ergonomics Society Annual Meeting 2010, HFES 2010
CountryUnited States
CitySan Francisco, CA
Period9/27/1010/1/10

ASJC Scopus subject areas

  • Human Factors and Ergonomics

Fingerprint Dive into the research topics of 'Electronic health records: Physician's perspective on usability'. Together they form a unique fingerprint.

Cite this