Flexibility in interaction: sociotechnical design of an operating room scheduler.

Purpose: The purpose of this study was to learn about factors that influence the design and implementation of situated computing solutions that support hospital work. This includes social and technical aspects of the actual systems that will be implemented, as well as the appropriate design methodology for developing these systems.

Methods: Staff at a surgical department at a University hospital were engaged in a participatory design (PD) process to help solve a problem that was presented by the staff: scheduling of patients and surgery rooms, and creating awareness of the status of ongoing surgeries. The PD process was conceptually aided by a model that describes Medical Informatics Systems as comprising of three components, a service component, a technical component and a social component. The process included the use of ethnographic field work and iterative redesign of both technical and social components of the system after it had been implemented into day-to-day work practice.

Results: The PD process resulted in the creation of a system that was iteratively created over a period of about 2 years, and which then handed over to the IT department of the hospital and used by the surgical department for a period of about 1 additional year. The first version of the prototype that was implemented contained usability flaws that made the system difficult to use in time critical situations. As a result of observations and a redesign of the technical component and social component of the system a new version was possible to implement that managed to overcome this problem. A key feature of this second version of the system was that some responsibility for data entry validation was shifted from the technical component of the system to the social component of the system. This was done by allowing users to input poor data initially, while requiring them to fix this data later on. This solution breaks from "traditional" usability design but proved to be quite successful in this case. A challenge with the solution, however, was that the IT department could not understand the concept of systems being described as comprising of both social components and technical components, and thus they had difficulty in understanding the overall design of the system during the handover process.

Conclusions: Situated computing can present a number of design challenges that may not be easy for designers and hospital workers to understand before a system has been implemented. Situated computing development may thus need to be aided by PD that includes both ethnographic observations and iterative redesign of the system after it has been implemented. Traditional data validation mechanisms may create poor system performance in cases where users are rushed to input data into the computer due to pressures created by other more critical work activities. In this case it may be better to rely on social mechanisms for correcting errors later on, rather than error catching mechanisms that reject incorrect data. It can be challenging, however, to maintain such systems over time, as IT-departments may lack skills and interest in social components.