Complementary methods of system usability evaluation: Surveys and observations during software design and development cycles

Jan Horsky*, Kerry McColgan, Justine E. Pang, Andrea J. Melnikas, Jeffrey A. Linder, Jeffrey L. Schnipper, Blackford Middleton

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

48 Scopus citations

Abstract

Poor usability of clinical information systems delays their adoption by clinicians and limits potential improvements to the efficiency and safety of care. Recurring usability evaluations are therefore, integral to the system design process. We compared four methods employed during the development of outpatient clinical documentation software: clinician email response, online survey, observations and interviews. Results suggest that no single method identifies all or most problems. Rather, each approach is optimal for evaluations at a different stage of design and characterizes different usability aspect. Email responses elicited from clinicians and surveys report mostly technical, biomedical, terminology and control problems and are most effective when a working prototype has been completed. Observations of clinical work and interviews inform conceptual and workflow-related problems and are best performed early in the cycle. Appropriate use of these methods consistently during development may significantly improve system usability and contribute to higher adoption rates among clinicians and to improved quality of care.

Original languageEnglish (US)
Pages (from-to)782-790
Number of pages9
JournalJournal of Biomedical Informatics
Volume43
Issue number5
DOIs
StatePublished - Oct 2010

Keywords

  • Adoption of HIT
  • Clinical information systems
  • Design and development
  • Health information technology
  • Usability evaluations

ASJC Scopus subject areas

  • Computer Science Applications
  • Health Informatics

Fingerprint Dive into the research topics of 'Complementary methods of system usability evaluation: Surveys and observations during software design and development cycles'. Together they form a unique fingerprint.

Cite this