Skip to main page content
U.S. flag

An official website of the United States government

Dot gov

The .gov means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site.

Https

The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.

Access keys NCBI Homepage MyNCBI Homepage Main Content Main Navigation
. 2012 Oct 10;3(4):367-76.
doi: 10.4338/ACI-2012-04-R-0014. Print 2012.

Transitioning from a legacy EHR to a commercial, vendor-supplied, EHR: one academic health system's experience

Affiliations

Transitioning from a legacy EHR to a commercial, vendor-supplied, EHR: one academic health system's experience

A Gettinger et al. Appl Clin Inform. .

Abstract

Objective: Describe the planning, decisions, and implementation results experienced during the large-scale transition from one EHR to another throughout a large academic health system, which occurred simultaneously throughout both in-patient and all ambulatory settings.

Methods: Review of internal decision-making documents, interviews with key participants, and data from conversion software.

Results: Over 7,000 unique users caring for a population of more than 1.2 million patients in both inpatient and outpatient venues and distributed across two states were successfully transitioned to a new EHR simultaneously. Challenges in data conversion were encountered resulting in more work for end-users than desired or anticipated. Users continued to access older information (principally schedules) in the legacy EHR one year later.

Conclusion: Data conversion from one EHR to another can be unsuccessful due to differences in how EHR's structure data obtained from underlying feeder applications or databases. Abstraction of only the pertinent clinical content is difficult in the context of transitioning to a new EHR. Clinicians require facile access to legacy content that can be achieved by implanting CCOW compliant solutions.

Keywords: CCOW; Electronic Health Record (EHR); enterprise conversion; legacy systems; medical record conversion.

PubMed Disclaimer

Figures

Fig. 1
Fig. 1
Legacy System Patient-Centric Information Display
Fig. 2
Fig. 2
CIS Legacy Medication Lists and New System Medication List
Fig. 3
Fig. 3
Ongoing Use of the CCOW-mediated Legacy Software

Similar articles

Cited by

References

    1. Yoon-Flannery K, Zandieh SO, Kuperman GJ, Langsam DJ, Hyman D, Kaushal R.A qualitative analysis of an electronic health record (EHR) implementation in an academic ambulatory setting. Informatics in Primary Care. 2008; 16: 277–284 - PubMed
    1. Chaudhry B, Wang J, Wu S, Maglione M, Mojica W, Roth E, et al. Systematic Review: Impact of Health Information Technology on Quality, Efficiency, and Costs of Medical Care. Ann Int Med. 2006; 144 (10): 742–752 - PubMed
    1. McAlearney AS, Robbins J, Hirsch A, Jorina M, Harrop JP. Perceived efficiency impacts following electronic health record implementation: An exploratory study of an urban community health center network. Int J Med Inform. 2010; 79 (12): 807–816 - PubMed
    1. Zandeith SO, Yoon-Flannery K, Kuperman G, Langsam D, Hyman D, Kaushal R.Challenges to EHR Implementation in Electronic-Versus-Paper-based Office Practices. J Gen Inter Med. 2008; 23 (6): 755–761 - PMC - PubMed
    1. Sittig DF, Wright A, Meltzer S, Simonaitis L, Evans RS, Nichol WP, et al. Comparison of clinical knowledge management capabilities of commercially-available and leading internally-developed electronic health records. BMC Med Inform Decis Mak. 2011; 11: 13 - PMC - PubMed

MeSH terms