User-Competence and Other Usability Aspects when Introducing a Patient Administrative System: A Case Study

Abstract An empirical study of a development project implementing a patient administrative system at a major hospital is reported. An analysis is made of the training given to the end-users and how this was affected by the events in the project. The results show how usability aspects such as user-competence are affected by a number of different factors in the project. The most important of these are deficiencies in the contract between the delivering consultant and the health authority, delays in the delivery of the program and the manual, and a lack of concern in the project for software usability aspects. For example, the contract between the delivering consultant and the health authority did not include any agreement about responsibility for usability aspects, and the delays in the project caused difficulties for user training. The results show a number of deficiencies in the training, for example: very little training material was given to the trainees and the computer exercises were not closely related to the trainees' future work tasks. We believe that future implementations of patient administrative programs will be more successful if the deficiencies found in the project studied are avoided.

[1]  John M. Carroll,et al.  Exploring Exploring a Word Processor , 1985, Hum. Comput. Interact..

[2]  Franz Schmalhofer,et al.  MENTAL MODEL AND PROCEDURAL ELEMENTS APPROACHES AS GUIDELINES FOR DESIGNING WORD PROCESSING INSTRUCTIONS , 1987 .

[3]  Carl Martin Allwood,et al.  A survey of the training of computer users in Swedish companies , 1991 .

[4]  O. Östberg,et al.  Social Aspects of Computer Use , 1988 .

[5]  Richard Catrambone,et al.  Learning a word processing system with training wheels and guided exploration , 1987, CHI '87.

[6]  Gerhard Fischer,et al.  Knowledge-based help systems , 1985, CHI '85.

[7]  Clayton Lewis,et al.  Learning to use a text processing system: Evidence from “thinking aloud” protocols , 1982, CHI '82.

[8]  Mary Beth Rosson,et al.  ROLE OF EXPERIENCE IN EDITING. , 1985 .

[9]  Mats Lind,et al.  The interface is often not the problem , 1987, CHI 1987.

[10]  John D. Gould.  Chapter 35 – How to Design Usable Systems , 1988 .

[11]  John L. Bennett,et al.  Usability Engineering: Our Experience and Evolution , 1988 .

[12]  Carl Martin Allwood.  Programkontrakten måste bli tydligare , 1992 .

[13]  Mike Fitter,et al.  The process of deriving requirements for a hospital information system , 1992 .

[14]  Kalle Lyytinen,et al.  Information systems failures—a survey and classification of the empirical literature , 1988 .

[15]  Carl Martin Allwood,et al.  Using a patient administrative system: A performance evaluation after end-user training , 1993 .

[16]  John D. Gould,et al.  How to design usable systems , 1995 .

[17]  Mats Lind,et al.  The interface is often not the problem , 1986, CHI '87.

[18]  Alan L. Rector,et al.  User centered development of a general practice medical workstation: the PEN&PAD experience , 1992, CHI '92.

[19]  Nancy C. Goodwin,et al.  Functionality and usability , 1987, CACM.