Moving Patient Records to a New System: A Checklist
What to decide, test and check when you move patient records from an old system to a new one, in the order to do it.
- Decide what moves before anyone writes code: which patients, how far back, and what stays in a read-only archive.
- Map every field with someone who does the clinical work, not only with a developer.
- Rehearse the move at least once on a copy, and have nurses check real records.
- Prove nothing was lost by counting and comparing, not by trusting that the script finished.
- Keep the old system read-only after the switch, until you are sure.
To move patient records to a new system safely: decide which records move, map each old field to a new one, clean the data, run a trial move on a copy, have clinical staff compare a sample of records, fix what they find, then freeze the old system, run the final move, check the counts and switch over. Keep the old system available read-only afterwards.
Changing clinical systems is the project agencies put off longest, because the records matter and nobody wants to be the person who lost one. It is manageable when done in order. We moved more than 4,000 patient records from a legacy system into the nursing assessment platform described in our home care case study. This is the checklist we would give another agency.
Before you start
- Name one owner at the agency. Someone who knows the clinical work and can decide what a field means.
- List what the old system holds. Patients, assessments, diagnoses, medications, allergies, physician orders, plans of care, certification periods, visit notes, scanned documents, signatures.
- Decide what moves. Active patients only, or discharged ones too? How many years back? What goes to a read-only archive instead?
- Confirm your retention obligations with your compliance lead, so the archive is kept for as long as it must be.
- Get a full export, and a copy to practise on. Ask the old vendor what format they can provide and how long they will keep your access open.
- Agree who may see the data during the move, and where the practice copy is kept and when it is destroyed.
Map and clean
- Map every field. For each field in the old system, write where it goes in the new one, or that it is being left behind and why.
- Agree how to match people. Use stable identifiers such as the HHAeXchange patient ID and the Medicaid ID, not names.
- Translate lists and codes. A status called "On hold" in one system may be two different statuses in the other. Diagnoses should land as proper ICD-10 codes, not free text.
- Find the duplicates and decide which record wins.
- Fix what you can at the source. Missing dates of birth, impossible dates, test patients. It is easier to clean before the move than after.
- Decide what happens to free-text notes that have no home in the new system. Usually they move as a dated note on the patient.
Rehearse
- Run the whole move on a copy.
- Count. Patients, assessments, orders, medications and documents, old against new.
- Have nurses check real records. Pick a sample that includes long-standing patients, recent admissions and the messy cases, and compare each one field by field.
- Open the documents. A file that moved but will not open has not moved.
- Write down every problem, fix it, and run the rehearsal again.
Switch over
- Pick a quiet time and tell staff the date well ahead.
- Train before the switch, on the new system with practice data.
- Freeze changes in the old system for the shortest period you can manage.
- Run the final move and repeat the counts.
- Have the same nurses repeat the sample check.
- Open the new system, with someone on hand to answer questions on the first days.
Afterwards
- Keep the old system read-only for an agreed period.
- Keep a list of anything staff report, and review it daily for the first weeks.
- Reconnect the other systems. If HHAeXchange data fed the old system, it needs to feed the new one. See how to connect your systems to HHAeXchange.
- Keep the final export and the migration log with your records.
- Close the old system properly: confirm in writing what the vendor does with your data.
Who does what
| Person | Their part |
|---|---|
| Agency owner of the project | Decides what moves and what each field means; signs off the result |
| Nurses | Check real records in the rehearsal and after the switch |
| Compliance lead | Retention, access during the move, closing the old system |
| Developer | Mapping document, move scripts, counts, fixes, the migration log |
| Old vendor | Export and continued access until you are done |
Where to start
Start with the list of what the old system holds and the decision about what moves. Both can be done before you have chosen the new system. If you would like us to look at what you have, book a free 30-minute review, or see what we build for home care agencies.
Frequently asked questions
How long does it take to move patient records to a new system?
It depends on how many records there are, how clean they are and how different the two systems are. The move itself is quick. Most of the time goes on mapping fields, cleaning data and checking the result, so plan for those.
Should we move every record or only active patients?
Decide this first. Many agencies move active patients in full and keep discharged patients in a read-only archive. Your record-retention obligations decide how long that archive must be kept, so confirm them with your compliance lead.
How do we know nothing was lost?
Count and compare. The number of patients, assessments, orders and documents should match on both sides, and nurses should open a sample of records in the new system and compare them with the old one, field by field.
Can staff keep working during the move?
Yes, if you plan the switch. Agree a short freeze on changes in the old system, move the final data, check it, then open the new system. Keep the old one read-only for a period so staff can look things up.
What happens to scanned documents and signatures?
They need their own plan. Files have to be moved, attached to the right patient and visit, and opened to confirm they are readable. Signed documents should be kept exactly as signed.
Who should be in charge of the migration?
One named person at the agency who knows the clinical work, usually a director of nursing or operations lead, working with the developer. Decisions about what a field means cannot be left to the technical team.