Background:Epic Beaker Clinical Pathology (CP) is a relatively new laboratory information system (LIS) operating within the Epic suite of software applications. To date, there have not been any publications describing implementation of Beaker CP. In this report, we describe our experience in implementing Beaker CP version 2012 at a state academic medical center with a go-live of August 2014 and a subsequent upgrade to Beaker version 2014 in May 2015. The implementation of Beaker CP was concurrent with implementations of Epic modules for revenue cycle, patient scheduling, and patient registration.Methods:Our analysis covers approximately 3 years of time (2 years preimplementation of Beaker CP and roughly 1 year after) using data summarized from pre- and post-implementation meetings, debriefings, and the closure document for the project.Results:We summarize positive aspects of, and key factors leading to, a successful implementation of Beaker CP. The early inclusion of subject matter experts in the design and validation of Beaker workflows was very helpful. Since Beaker CP does not directly interface with laboratory instrumentation, the clinical laboratories spent extensive preimplementation effort establishing middleware interfaces. Immediate challenges postimplementation included bar code scanning and nursing adaptation to Beaker CP specimen collection. The most substantial changes in laboratory workflow occurred with microbiology orders. This posed a considerable challenge with microbiology orders from the operating rooms and required intensive interventions in the weeks following go-live. In postimplementation surveys, pathology staff, informatics staff, and end-users expressed satisfaction with the new LIS.Conclusions:Beaker CP can serve as an effective LIS for an academic medical center. Careful planning and preparation aid the transition to this LIS.

Background:Beaker is a relatively new laboratory information system (LIS) offered by Epic Systems Corporation as part of its suite of health-care software and bundled with its electronic medical record, EpicCare. It is divided into two modules, Beaker anatomic pathology (Beaker AP) and Beaker Clinical Pathology. In this report, we describe our experience implementing Beaker AP version 2014 at an academic medical center with a go-live date of October 2015.Methods:This report covers preimplementation preparations and challenges beginning in September 2014, issues discovered soon after go-live in October 2015, and some post go-live optimizations using data from meetings, debriefings, and the project closure document.Results:We share specific issues that we encountered during implementation, including difficulties with the proposed frozen section workflow, developing a shared specimen source dictionary, and implementation of the standard Beaker workflow in large institution with trainees. We share specific strategies that we used to overcome these issues for a successful Beaker AP implementation. Several areas of the laboratory-required adaptation of the default Beaker build parameters to meet the needs of the workflow in a busy academic medical center. In a few areas, our laboratory was unable to use the Beaker functionality to support our workflow, and we have continued to use paper or have altered our workflow. In spite of several difficulties that required creative solutions before go-live, the implementation has been successful based on satisfaction surveys completed by pathologists and others who use the software. However, optimization of Beaker workflows has continued to be an ongoing process after go-live to the present time.Conclusions:The Beaker AP LIS can be successfully implemented at an academic medical center but requires significant forethought, creative adaptation, and continued shared management of the ongoing product by institutional and departmental information technology staff as well as laboratory managers to meet the needs of the laboratory.