Anatomy of a failure: A sociotechnical evaluation of a laboratory physician order entry system implementation

https://doi.org/10.1016/j.ijmedinf.2009.06.008Get rights and content

Abstract

Objective

To investigate the human, social and organizational issues surrounding a Computerized Physician Order Entry system for Laboratory ordering (CPOE-L) implementation process and to analyze their interrelated effects on the system implementation failure in an academic medical setting. Second, to provide lessons learned and recommendations on to how to manage challenges of human, social and organizational nature surrounding CPOE-L implementations.

Methods

The themes surrounding CPOE introduction were identified by a heuristic analysis of literature on CPOE implementations. The resulting set of themes was applied as a reference model for 20 semi-structured interviews conducted during the CPOE-L implementation process with 11 persons involved in the CPOE-L project and in reviewing all CPOE-L related project documentation. Data was additionally gathered by user questionnaires, by user discussion rounds and through an ethnographical study performed at the involved clinical and laboratory departments. In analyzing the interview transcripts, project documentation and data from user questionnaires and discussion rounds a grounded theory approach was applied by the evaluation team to identify problem areas or issues deserving further analysis.

Results

Outlined central problem areas concerning the CPOE-L implementation and their mutual relations were depicted in a conceptual interpretative model. Understanding of clinical workflow was identified as a key theme pressured by organizational, human and social issues ultimately influencing the entire implementation process in a negative way. Vast delays in CPOE introduction, system immaturity and under-functionality could all be directly attributed to a superficial understanding of workflow. Consequently, final CPOE integration into clinical and laboratory workflows was inhibited by both end-users as well as department managers and withdrawal of the CPOE-L system became inevitable.

Conclusion

This case study demonstrates which human, social and organizational issues relevant to CPOE implementation cumulatively led to a failure outcome of the CPOE-L pilot introduction. The experiences and considerations described in this paper show important issues for CPOE systems to be successfully introduced and to be taken into account in future CPOE implementations. Understanding and consideration of (clinical) workflow aspects by project managers and the involved clinical organization is of extreme importance from the very start of a CPOE implementation process.

Introduction

Though potential benefits abound [1], [2], [3], successful implementation of Computerized Physician Order Entry (CPOE) systems for electronic entering and retrieving of medical orders is known to be difficult and expensive [4], [5]. Failure of CPOE introduction seems to be tied to the current lack in understanding of current clinical practices surrounding order creation and of how to integrate CPOE into the apparent complexity of order workflow [6]. Sociotechnical approaches that focus on this interrelation of organizational environment and technology are considered valuable in enhancing the understanding of the CPOE implementation process [7]. This paper describes the evaluation of a failed implementation of a CPOE system for ordering laboratory tests (CPOE-L) at a large university hospital, the Academic Medical Center (AMC) in Amsterdam. For a good understanding of the issues influencing the CPOE-L project's failure, the aim of this study is to characterize the nature of involved key issues, explore their interrelations, and use these insights to support new implementation efforts in our institution and possible other institutions. Frameworks or models that focus on analyzing factors that influence the adoption of Information and Communication Technology (ICT) have been applied in research for decades. Models such as those of Delone and McLean (IS Success model [8]), Seddon (variance model of Information System success [9]), Mirani and Lederer (framework to measure benefits derived from IS projects [10]), Grover (framework for measuring IS effectiveness [11]) and Smithson and Hirscheim (conceptual framework for IS evaluation [12]) analyze the impact, success and effectiveness of a system based on different classes of measures such as, among others, system quality, information quality, service quality, organizational impact, productivity and system usage. However, these models of ICT success cannot be applied in analyzing the variables and interpret their mutual interrelations influencing a complete system implementation process, from feasibility study to a first pilot phase. Delone and McLean themselves for example argue that ‘top management support’ and ‘user involvement’ may cause success rather than being a part of success and that their model does not take these variables into account. Other issues that might be relevant to an implementation study, such as the culture and organizational characteristics are also not included in these IT success models. Sociotechnical based frameworks could yet offer more insight into the sociotechnical transfusion of Information Technology (IT) in healthcare and its adoption by its intended users. However, existing frameworks such as the IT Adoption Model (ITAM) focuses on the individual users’ perspective and attributes of users’ system adoption but fails to operationalize the organizational, human and social aspects surrounding a system development and (first) implementation effort [13]. The review by Van Der Meijden et al. [14] was likewise aimed at identifying attributes to assess the success of electronic health care systems after implementation, not at revealing variables and their mutual interdependencies that might have influenced the software development life cycle and in the end may explain the nature of the cause of systems’ successes or failures.

We were specifically interested in analyzing and interpreting the variables and problem areas that may cause CPOE success or failure in order to explain what went wrong during the CPOE-L implementation process. Our research focus is on interpreting human, social and organizational problems encountered in the entire CPOE-L implementation process, from feasibility to pilot implementation. We interpret our results by developing a three layer conceptual model based on the analysis of factors influencing CPOE implementation described by Ash et al., Kuperman, Sittig and Massaro [4], [15], [16], [17], [18], [19], [20]. Research of these factors dates back to 1970 and so the knowledge base of CPOE implementations has been built on over more than 25 years of experience [21], [22].

Recent studies on CPOE implementation underscored the importance of understanding clinical workflow as a key issue for effective CPOE adoption in clinical practice [6]. But although success and failure factors for CPOE implementation have been thoroughly explored in studies on CPOE adoption, the influence of the human, social and organizational issues surrounding an implementation process has only limited been examined in the literature [23]. The main objective of this study is to investigate the impact and interrelation of experienced implementation problems on the whole CPOE-L implementation process from feasibility study to pilot introduction in the Academic Medical Center of Amsterdam. In doing so, we provide lessons learned and recommendations for acting upon challenges concerning human, social and organizational issues during a complete CPOE implementation process.

Section snippets

Research methodology

A longitudinal study design was chosen to analyze the implementation process of the CPOE-L system; from January 2004 until December 2004 [24]. From the restart of the project in June 2004 until the pilot implementation in September 2004 we conducted 20 semi-structured interviews of approximately 2 h, with 11 persons involved in the CPOE-L implementation process. All interviews were taped and transcribed with consent of the interviewees. The interview script was developed on the basis of insights

Setting and background of the CPOE-L implementation process

The CPOE-L project dated back to 1997. The main purposes of CPOE introduction at that time were to improve quality and efficiency in ordering and to offer clinicians the possibility to order diagnostic or therapeutic tests electronically. The decision to commence with the laboratory functionality was made from the early start of the project. The outpatient laboratory seemed ideal to start with CPOE implementation for several reasons: the large volume of laboratory orders requested, the apparent

Analysis of human, social and organizational issues of the CPOE-L implementation and their impact on workflow understanding and vice-versa

Table 3 provides an overview of the frequency in which implementation problem themes were mentioned and discussed in relation to each other during the interviews.

Eight out of the 36 implementation themes covered in the interviews and document analysis appeared to be associated with direct problems in the system implementation process finding its central problem in the ‘understanding of clinical workflow’. The observation study at the outpatient neurology department and the outpatient laboratory

Discussion and conclusions

Studies that describe CPOE implementation efforts have shown that implementing these kind of systems is challenging and not only in need of organizational transformation. A broad variety of implementation preconditions should also be fulfilled, including resource commitment, good leadership and organizational readiness [30], [31], [32], [33]. However, as failure stories continue to arise, it seems that issues influencing the course of an implementation process and finally inducing

Conflict of interest

None declared.

Acknowledgements

The authors thank all members of the CPOE-L project team and all project contacts involved for their cooperation in conducting this study.

References (45)

  • H.S. Mekhjian et al.

    Immediate benefits realized following implementation of physician order entry at an academic medical center

    J. Am. Med. Inform. Assoc.

    (2002)
  • J.M. Overhage et al.

    Research paper—controlled trial of direct physician order entry: effects on physicians time utilization in ambulatory primary care internal medicine practices

    J. Am. Med. Inform. Assoc.

    (2001)
  • D.W. Bates et al.

    The impact of computerized physician order entry on medication error prevention

    J. Am. Med. Inform. Assoc.

    (1999)
  • T.A. Massaro

    Introducing physician order entry at a major Academic Medical-Center Impact on organizational culture and behavior

    Acad. Med.

    (1993)
  • J. Aarts et al.

    Same systems, different outcomes—comparing the implementation of computerized physician order entry in two Dutch hospitals

    Methods Inf. Med.

    (2006)
  • W.H. DeLone et al.

    Measuring e-commerce success: applying the DeLone & McLean Information Systems Success Model

    Int. J. Electron. Comm.

    (2004)
  • P.B. Seddon et al.

    Dimensions of information systems success

    Commun. AIS

    (1999)
  • R. Mirani et al.

    An instrument for assessing the organizational benefits of IS projects

    Decis. Sci.

    (1998)
  • S. Smithson et al.

    Analyzing information systems evaluation: another look at an old problem

    EJIS

    (1998)
  • M.J. Van Der Meijden et al.

    Determinants of success of inpatient clinical information systems: a literature review

    J. Am. Med. Inform. Assoc.

    (2003)
  • G.J. Kuperman et al.

    Computer physician order entry: benefits, costs, and issues

    Ann. Intern. Med.

    (2003)
  • J.S. Ash et al.

    Principles for a successful computerized physician order entry implementation

    AMIA Annu. Symp. Proc.

    (2003)
  • Cited by (46)

    • Health professionals’ expectations of a national patient portal for self-management

      2018, International Journal of Medical Informatics
      Citation Excerpt :

      They were also asked how they expected the future implementation of a new patient portal to happen by rating whether they agreed that six good implementation practices will be used in their organizations. The six good implementation practices were identified from the literature [22,27,29,37–40]. Thus, the content validity of these survey items was established through a literature review [41].

    • Physician satisfaction with transition from CPOE to paper-based prescription

      2017, International Journal of Medical Informatics
      Citation Excerpt :

      Nevertheless, failure often concerns just one function, or a few wards [13]. Despite calls for other hospitals to share experience on suboptimal implementation [14,15], only a few cases of failure have been described in the literature [16,17]. All of these reported failures, whether partial or total, have allowed the identification of factors associated with successful implementation of CPOE, which are now well described in the literature [18,19].

    • Organizational and Behavioral Issues

      2017, Key Advances in Clinical Informatics: Transforming Health Care through Health Information Technology
    • Understanding barriers and facilitators to the use of Clinical Information Systems for intensive care units and Anesthesia Record Keeping: A rapid ethnography

      2015, International Journal of Medical Informatics
      Citation Excerpt :

      Therefore, we designed a study to identify barriers, facilitators, and suggested improvements to currently implemented CIS and ARK systems at a sample of VA Medical Centers (VAMCs). We framed our study with sociotechnical systems theory, which has been used and discussed prominently in the medical informatics literature [4–14]. Although there is no one “sociotechnical approach” [4], studies that rely on a sociotechnical perspective all have a high-level recognition that organizational and health systems at large have a substantial influence in shaping HIT and that the technology and context are intertwined [5].

    View all citing articles on Scopus
    View full text