Journal Home
Search for

Volume 50, Issue 4, Pages 433-435 (October 2007)


View previous. 18 of 38 View next.

When Is a Defibrillator Not a Defibrillator? When It’s Like a Clock Radio … . The Challenge of Usability and Patient Safety in the Real World

Ben-Tzion Karsh, PhD1Corresponding Author Informationemail address, Matthew Scanlon, MD2

Received 24 August 2007 published online 28 August 2007.

Refers to article:
Usability Study of Two Common Defibrillators Reveals Hazards , 11 May 2007
Rollin J. Fairbanks, Stanley H. Caplan, Paul A. Bishop, Aaron M. Marks, Manish N. Shah
Annals of Emergency Medicine
October 2007 (Vol. 50, Issue 4, Pages 424-432)
Abstract | Full Text | Full-Text PDF (1178 KB)

Article Outline

Understanding of Usability Science

Usability Testing Procedures

Market Demand and Regulation

Acknowledgment

References

Copyright

SEE RELATED ARTICLE, P. 424.

[Ann Emerg Med. 2007;50:433-435.]

Fairbanks et al1 describe how usability testing can be used to uncover medical device design flaws that compromise the safe and efficient delivery of care. Their experience is consistent with other published reports,2, 3, 4, 5 which tested readily available technologies and found dramatic human-automation interactions problems that could be linked to poor device design. These findings are likely the tip of a proverbial iceberg of medical technology and devices, that, by design, have limited usability. And yet health care delivery organizations continue to purchase devices and information technologies that lack usability.

This brings up many questions. Why do hospitals and health care providers continue to purchase devices and technology with poor usability? Why don’t manufacturers address these shortcomings? And how, if at all, are regulatory agencies involved in this problem? After all, the US Federal Aviation Administration, Department of Defense, Department of Transportation, Nuclear Regulatory Commission, Department of Energy, and the National Aviation and Space Administration use usability and human-factors engineering design. The full answers to these questions are the subject of textbooks, PhD theses, and international meetings. We examine 3 of the major issues that we believe in part address those questions: lack of understanding usability science, lack of good usability testing practices, and lack of market demand for usability.

Understanding of Usability Science 

return to Article Outline

First, providers, many users, manufacturers, and even regulatory agencies do not necessarily know or understand usability. Anyone who has struggled with programming a DVD player or setting the alarm on a novel clock radio in a hotel room inherently understands the problem of usability but may be unaware that usability science exists. Usability is grounded in the field of human factors engineering,6, 7 which is the science that studies human performance capabilities and limitations and designs built systems (eg, medical devices, information technology, scalpels, computer monitors) to support performance needs. Unfortunately, many decisionmakers and designers erroneously believe that “identifying performance needs,” also referred to as “user-centered design,” is common sense. Users themselves often share the same erroneous assumption; this leads to blaming (I can’t believe that person can’t figure it out) and even ironically leads to much self-blaming (Why can’t I figure this out? or If only I had been paying more attention, this wouldn’t have happened) when in fact the real problem was poor design.

Consider a defibrillator; the obvious or common-sense need is for the user to be able to save the life of a patient by correctly diagnosing and treating a life-threatening rhythm disturbance. But a human factors engineer or usability scientist analyzes usability at a much deeper level. He or she realizes there are physical and cognitive performance needs that must be met for all the different environments of use and possible users. The physical performance needs include having buttons, knobs, and dials designed to accommodate the hand and finger sizes of different users to maximize correct usage and minimize incorrect usage or accidental activation. The actual design could vary, depending on where the device is used; in emergency transport vehicles, there is significant vibration, so the affordances must be even greater. The device should also accommodate lifting and carrying needs by having correctly designed handles and a weight that can be carried by the majority of users. The device needs to be designed so that it can be read (visual sensation) in dark or bright light and the auditory cues (alarms or confirmatory sounds) can be heard in environments with varying noise and with the possibility of vibration in a transport vehicle. Cognitive performance needs may include planning, decisionmaking, attention focusing, pattern matching, problem solving, and many others. The defibrillator can be designed to make all of these tasks easier, and Fairbanks et al clearly demonstrate how readily available devices failed to meet many of these design requirements. Fortunately, dozens of scientifically validated design guidelines exist to support each of those tasks.8, 9, 10, 11, 12 The bad news is that it is not clear how much of this available guidance is used.

Additionally, many people, including health care administrators, clinicians, and manufacturers, believe proper training and compliance with correct use protocols are sufficient for avoiding errors when automation is used. This problem is not a lack of awareness of the existence of a science behind usability but a lack of awareness of the concept itself. This belief, which is not evidence based, brings with it a host of problems. Users get blamed (think user error) for mistakes caused by bad design, and users themselves even think all bad outcomes stemming from human automation interactions are their fault! Norman13 explains that this self-blame phenomenon is the result of misunderstanding in causality, as well as both a learned and taught helplessness. Although training is crucial for effective use of automation, it cannot completely compensate for poor design. Training is unlikely to overcome interfaces that do not conform to population stereotypes for where information is located or what colors mean or what “enter” or “return” means. And all the training in the world will not help someone hear an alert in a noisy environment or read a small display in a vibrating ambulance, especially during a time-critical task. Each of these cases requires better system design.6, 14

Usability Testing Procedures 

return to Article Outline

A second major issue is the challenge of performing usability testing. Even if one possesses a robust understanding of usability science, good usability testing is not ensured. Dozens of resources describe the plethora of usability methods,15, 16, 17, 18 including many specific to medical devices or health information technology.5, 19, 20, 21, 22, 23, 24 Bad conclusions result when the methods are incorrectly applied. One important consideration for testing requires knowing how to select representative end users and representative environments of use. Whether the studies are conducted by manufacturers or hospitals, if the sample includes only “expert users” or “well-trained users,” the results will likely not be generalizable. Similarly, if the device or information technology will be used in environments with different lighting intensities and sources (fluorescent tube versus sunlight), different levels of noise (intensive care unit versus surgical suite) and even different levels of distraction (emergency department versus general medicine ward), then testing must be conducted in those different environments to determine if and when the device is usable. Putting a handful of subjects in a nice, clean, simulated patient care room and having them use the device there may not simulate the real environments of use, in which the alarms might not be audible, the displays easily visible, or buttons easily activated. The key point here is that usability is not proven by demonstrating that a handful of people can use the device in a given environment. Usability is determined by the interaction among users, the technology, the environment (lighting, noise, vibration, distractions), the task characteristics (time pressure, need for concentration) and the organization (culture, policies). Good usability testing must attempt to mimic these interactions.

Understanding the many human biases that can lead to wrong conclusions during testing is another important consideration for good usability. For example, hindsight bias may lead a tester to conclude that a user error during testing could “obviously” be corrected with better training. The fundamental attribution error may lead to conclusions that it was just the “ignorant” subjects who did not understand how to use the device. These biases and many more exist, and a well-trained tester must be aware of them and not fall victim to them. The pervasive blame culture in health care, which is likely rooted in the fundamental attribution error and similar biases, may reduce the understanding of the contribution of bad design in the same way. These biases even exist in heuristic evaluations and expert testing. Experts in a laboratory setting do not view or use technology the same way as novice users in a real-world environment. Consequently, even if end users, regulatory agencies, and manufacturers all understood the issues of usability and more usability testing was mandated, there is no assurance that proper testing would occur.

Market Demand and Regulation 

return to Article Outline

The final major issue affecting usability of medical devices is weak market demand for improvements, in part attributable to the lack of understanding of the importance of usable technology and devices. However, this issue also illustrates the role health care providers and organizations play in the problem of poorly usable devices by largely demanding and purchasing devices that function at the lowest price possible. At the same time, many providers insist on added features that may increase complexity and decrease usability. The combination of purchasing for price while requesting added features, without any requirement for usability, creates a potentially dangerous combination. Although some organizations request highly usable products, they are a minority, and thus, their numbers are insufficient to change device and technology design.

Alternatively, some consumers of these products, primarily health care delivery organizations, may assume they are purchasing “tested” products. The US Food and Drug Administration requires manufacturers to “address the intended use of the device, including the needs of the user and patient,” whereas information technology vendors have no such requirements.25 However, compliance with this regulation may yield very different results, according to their understanding and execution of usability principles. At best, this means that the device does work if used exactly as intended under ideal circumstances. Perfect conditions rarely exist in health care delivery organizations, rendering the possibility that a device will function in its intended manner largely fatuous.

The lack of current market demand takes on added significance in light of the fact that those most likely to be hurt by poorly usable devices and technology, ie, patients, are not involved in the selection and purchasing processes. Meanwhile, it is unlikely that providers, clinicians, and even manufacturers will see the direct consequence (patient harm) of their decisions. Ironically, in an environment of increased transparency of medical errors and harm, manufacturers might leverage enhanced safety through improved usability for a market advantage.

What does this all mean? Devices and technology with poor usability are endemic in health care and will remain so until there is a fundamental shift in knowledge that leads to changes in purchasing. Groups such as the US Food and Drug Administration and the Joint Commission probably should demand better product usability at both the manufacturer and consumer levels, but improvements will not happen unless good usability testing practices are implemented. Until then, the next time you see a clock radio, think of the ventilators, defibrillators, and pumps on which your patients depend.

 

return to Article Outline

The authors would like to thank Arielle Silver, BA, for her editorial assistance.

References 

return to Article Outline

1. 1Fairbanks RJ, Caplan SH, Bishop PA, et al. Usability study of two common defibrillators reveals hazards. Ann Emerg Med. 2007;50:424–431. Abstract | Full Text | Full-Text PDF (1178 KB) | CrossRef

2. 2Gosbee JW, Gosbee LL. Using Human Factors Engineering to Improve Patient Safety. Oakbrook Terrace, IL: Joint Commission Resources; 2005;.

3. 3Lin L, Isla R, Harkness H, et al. Applying human factors to the design of medical equipment: patient-controlled analgesia. J Clin Monitor Comput. 1998;14:253–263.

4. 4Scanlon M. Computer physician order entry and the real world: we’re just humans. Jt Comm J Qual Saf. 2004;30:342–346. MEDLINE

5. 5Wiklund ME. Medical Device and Equipment Design: Usability Engineering and Ergonomics. Buffalo Grove, IL: Interpharm Press; 1995;.

6. 6Karsh B, Alper SJ, Holden RJ, et al. A human factors engineering paradigm for patient safety—designing to support the performance of the health care professional. Qual Saf Health Care. 2006;15(suppl I):i59–i65. CrossRef

7. 7Scanlon MC, Karsh B, Densmore E. Human factors and pediatric patient safety. Pediatr Clin North Am. 2006;53:1105–1119. Full Text | Full-Text PDF (348 KB) | CrossRef

8. 8Eastman Kodak Company. Ergonomic Design for People at Work. 2nd ed.. Hoboken, NJ: John Wiley and Sons; 2004;.

9. 9In:  Salvendy G editors. Handbook of Human Factors and Ergonomics. 3rd ed.. Hoboken, NJ: John Wiley and Sons; 2006;.

10. 10Sanders MS, McCormick EJ. Human Factors Engineering and Design. 7th ed.. New York, NY: McGraw-Hill; 1993;.

11. 11Wickens CD, Lee JD, Liu Y. An Introduction to Human Factors Engineering. 2nd ed.. Upper Saddle River, NJ: Pearson Education; 2004;.

12. 12Association for the Advancement of Medical Instrumentation. Human Factors Design Process for Medical Devices (ANSI/AAMI HE74:2001). Association for the Advancement of Medical Instrumentation; 2001;.

13. 13Norman D. The Design of Everyday Things. New York, NY: Currency Doubleday; 1988;.

14. 14Carayon P, Hundt AS, Karsh B, et al. Work system design for patient safety: the SEIPS model. Qual Saf Health Care. 2006;15(suppl I):i50–i58. CrossRef

15. 15Federal Aviation Administration. Usability training module. Available at: http://www.hf.faa.gov/Webtraining/Usability/usability1.htm. Accessed May 11, 2007.

16. 16Nielsen J. Usability Engineering. San Francisco, CA: Morgan Kaufmann; 1994;.

17. 17Nielsen J. Usability information technology. Available at: http://www.useit.com. Accessed May 14, 2007.

18. 18Rubin JR. Handbook of Usability Testing. New York, NY: John Wiley & Sons; 1994;.

19. 19Coble JM, Karat J, Orland MJ, et al. Iterative usability testing: ensuring a usable clinical workstation. Proc AMIA Annu Fall Symp. 1997;744–748.

20. 20Gosbee J, Klancher J, Arnecke B, et al. The role of usability testing in healthcare organizations. In: 2001;p. 1308–1311Proceedings of the Human Factors and Ergonomics Society 40th annual meeting. Minneapolis, MN, October 8-12.

21. 21Kushniruk A. Evaluation in the design of health information systems: application of approaches emerging from usability engineering. Comput Biol Med. 2002;32:141–149. Abstract | Full Text | Full-Text PDF (106 KB) | CrossRef

22. 22Kushniruk AW, Patel VL, Cimino JJ. Usability testing in medical informatics: cognitive approaches to evaluation of information systems and user interfaces. Proc AMIA Annu Fall Symp. 1997;218–222.

23. 23Rogoski RR. Opening the floodgates of usability (Clinical information systems allow free flow of patient data to clinicians when and where they need it). Health Manage Technol. 2003;24:12–17.

24. 24Sawyer D. Do it by design: an introduction to human factors in medical devices. Available at: http://www.fda.gov/cdrh/humanfactors. Accessed May 17, 2007.

25. 25Lowery A, Strojny J, Puleo J. Division of Small Manufacturers Assistance, Office of Health and Industry Programs. Medical device quality systems manual: a small entity compliance guide. HHS Publication FDA 97-4179. Available at: http://www.fda.gov/cdrh/qsr/intro.html. Accessed May 15, 2007.

1 Department of Industrial and Systems Engineering, University of Wisconsin–Madison, Madison, WI

2 Department of Pediatrics, Medical College of Wisconsin, Milwaukee, WI.

Corresponding Author InformationAddress for correspondence: Ben-Tzion Karsh, PhD, Department of Industrial and Systems Engineering, University of Wisconsin–Madison, 1513 University Avenue, Room 4155, Madison, WI 53706; 608-262-3002, fax 608-262-8454

 Funding and support: By Annals policy, all authors are required to disclose any and all commercial, financial, and other relationships in any way related to the subject of this article, that might create any potential conflict of interest. See the Manuscript Submission Agreement in this issue for examples of specific conflicts covered by this statement. Dr. Karsh is funded by the Agency for Healthcare Research and Quality, National Library of Medicine, and the Robert Woods Johnson Foundation. Dr. Scanlon is funded by the Agency for Healthcare Research and Quality, National Library of Medicine.

Supervising editor: Robert L. Wears, MD, MS

Publication dates: Available online August 24, 2007.

Reprints not available from the authors.

PII: S0196-0644(07)01250-4

doi:10.1016/j.annemergmed.2007.06.481


View previous. 18 of 38 View next.