<XML><RECORDS><RECORD><REFERENCE_TYPE>0</REFERENCE_TYPE><REFNUM>8820</REFNUM><AUTHORS><AUTHOR>Johnson,C.W.</AUTHOR></AUTHORS><YEAR>2006</YEAR><TITLE>Why Did That Happen? Exploring the Proliferation of Barely Usable Software in Healthcare Systems</TITLE><PLACE_PUBLISHED>BMJ Journal of Quality and Safety in Healthcare, Volume 15</PLACE_PUBLISHED><PUBLISHER>N/A</PUBLISHER><PAGES>76-81</PAGES><LABEL>Johnson:2006:8820</LABEL><KEYWORDS><KEYWORD>Safety</KEYWORD></KEYWORDS<ABSTRACT>Clinicians and support staff are faced with increasingly complex computer applications. This complexity stems, in part, from the integration of heterogeneous systems ranging from computerized patient records to theatre management and dosage planning applications. Complexity also stems from the increased functionality offered by this new generation of IT systems. Many members of clinical staff are bewildered by the vast array of configuration options and operating modes that are supported by computer-based systems. Conversely, manufacturers often feel compelled to offer more and more software features in order to retain market position. These factors combine to create ‘usability’ problems that have had a direct impact on patient outcomes. The poor usability of clinical software also has a number of indirect effects. For example, the costs of replacing and upgrading inadequate computer systems carry significant opportunity costs in terms of the services that might otherwise have been funded. This paper addresses the following issues: 1. There is a tradition of ‘making do’ with poorly designed software that should be questioned. 2. Poor ‘usability’ has a direct impact on patient outcomes; 3. Poor ‘usability’ also has an indirect impact on opportunity costs of replacing computer systems; In the future: 1. We need to educate staff to reject substandard computer interfaces early in the acquisition process; 2. We need to encourage the use of human computer interaction techniques in healthcare; 3. We need to train staff to recognize the dangers of ‘working around’ poor interface design</ABSTRACT><URL>http://www.dcs.gla.ac.uk/~johnson/papers/Chris_Johnson_Usability.pdf</URL></RECORD></RECORDS></XML>