Skip to main content

Replacing a Legacy Clinical Record System: A Four-Phase Migration Method

Jeremy Bloom, Co-founder · · Updated

Replacing the clinical record system is a project the operator runs. The four phases below are a method: inventory what you have, move and check the data, configure the new system and train your own staff, then run the old and new systems together until the outputs match. The phases do not have a duration in this post. How long each one takes depends on the number of sites, the systems you are leaving, and the condition of the data.

Phase 1: Inventory

List every system that holds patient, billing, staff, or compliance records, who uses it, and which outside parties it still has to reach: laboratories, pharmacies, payers, and state reporting. Write down where a fact is entered once and where it is copied. ONC’s System Management SAFER Guide identifies recommended safety practices associated with the configuration, validation, and maintenance of EHR hardware, software, and system-to-system application programming interfaces. That includes the physical environment in which the EHR operates and the implementation and testing of technically complex components of the clinical information system [1]. Use that guide while you are still on the old system, so the inventory includes how the current system is configured, not only which vendor sent the invoice.

Phase 2: Move the data and check it

Move structured records through a repeatable process the operator can rerun. Have people review scanned documents and free-text notes, because a script will not know which scan is the signed consent. After each load, compare record counts and a sample of charts to the source. Do not load real patient information into a test environment that lacks the access controls of the live system.

Two retention rules are easy to mix up. The HIPAA Security Rule’s six-year period in 45 CFR 164.316(b)(2) applies to required security documentation, kept from creation or from the date it was last in effect, whichever is later [3]. It is not a retention period for the clinical chart. How long to keep the chart is a medical-records statute. In Arizona, A.R.S. § 12-2297 says that, unless otherwise required by statute or by federal law, a health care provider shall retain an adult patient’s medical record for at least six years after the last date the adult patient received medical or health care services from that provider, and shall retain a child’s record for at least three years after the child’s eighteenth birthday or for at least six years after the last date the child received medical or health care services from that provider, whichever date occurs later [2]. Other states set different periods. Keep the legacy store available for the period that applies to your program, including after the new system is the one staff open each day.

Phase 3: Configure, then train your own teams

Department leads should set forms, roles, and workflows for the work they supervise, then teach those workflows to their own staff. Clinicians need the clinical path. Billing staff need the claim path. House managers need the census path. That teaching is the operator’s job. This post does not describe a vendor certification program or a vendor support desk.

Phase 4: Run both systems until the outputs match

Keep the legacy system available while staff work in the new one, and compare the outputs that matter: census, charges, and the compliance records you would pull for a survey. Move one site or one service line when that comparison holds, then the next. ONC’s Contingency Planning SAFER Guide identifies recommended safety practices associated with planned or unplanned EHR unavailability, when clinicians or other end users cannot access all or part of the EHR [1]. Write the downtime steps before the first day staff depend on the new system, and practice them.

The point of the parallel run is to find differences while you can still look them up in the old system. It is not a promise that leadership will see every operation on one screen.

Sources

  1. SAFER Guides, ASTP/ONC. Accessed September 28, 2026.
  2. A.R.S. 12-2297, Retention of records, Arizona State Legislature. Accessed September 28, 2026.
  3. 45 CFR 164.316, Policies, procedures, and documentation, eCFR, HHS. Accessed September 28, 2026.

Encore OS runs clinical care, recovery housing, billing, finance, staff and compliance work from the same records.

Explore the platform