
Decide what to migrate, what to archive, and what to test before shutting down an old EHR.
Your organization can deploy a new electronic health record system while years of patient history still sit in the old one. But before you shut down the old EHR, it’s best to confirm your records are actually discoverable.
Clinicians should be able to find the history they need, and the health information management staff can retrieve and release complete records without relying on the old application. But how do you ensure your new system has the information you need? You build those tests into your healthcare records management plan before setting a shutdown date.
Why Legacy EHR Decommissioning Matters
Keeping a legacy EHR running can mean paying for licenses, hosting, maintenance, and vendor support after the system stops serving day-to-day care. It also means your team has to maintain security on another system that houses protected health information (PHI).
A planned retirement of the old EHR can reduce those obligations while preserving access to the records you still need.
Where to Begin
Start with your records retention schedule. State law generally governs medical record retention. Your compliance team should also check applicable federal program requirements, contracts, and legal holds.
HIPAA requires safeguards for PHI while you maintain it, including through disposal. HIPAA’s separate six-year requirement for certain compliance documentation applies to that documentation. Patient charts follow the retention rules applicable to the records themselves.
What to Migrate and What to Archive
Migrate the data staff need in the new EHR to do their jobs.
A clinician may need current medications, allergies, active problems, and selected recent results in the normal chart workflow. Have clinical and operational owners define what must come over and verify that it appears where staff expect to find it.
Archive records you need to retain and retrieve after the old EHR closes.
These might include older encounter notes, billing records, signed forms, and historical reports. Preserve enough context to interpret them, including patient identifiers, encounter dates, authorship, and links to relevant attachments or images.
A patient may need both approaches. Their current medication list may belong in the new EHR, while notes from an older procedure can live in the archive. If a patient requests a history spanning both systems, staff should know where to look and how to assemble the response.
Best Practices for Legacy System Retirement
1. Inventory the EHR and Its Connected Systems
Map where clinical notes, results, scanned attachments, billing data, and diagnostic images actually live. Some items visible in the EHR may come from a separate imaging, lab, or document system.
Identify who owns each source, whether it will stay online, and what must be exported or linked for the historical record to remain usable.
Include paper charts and records subject to a hold.
2. Validate the Records Before Shutdown
Reconcile record counts by data type and investigate discrepancies. Then compare representative charts with the source, including older encounters, merged patient identifiers, amended notes, and records with attachments.
Open the attachments and test that reports and images still point to the right patient and encounter.
Have clinical, billing, and health information management staff test their own workflows and approve the results before IT retires the application.
3. Make the Archive Searchable and Control Access
Test whether authorized users can find a patient by identifier, narrow results by encounter date, and export a legible record. Set access by role and review audit logs. If you use document management software for scanned charts and other documents, verify how staff will find those files alongside structured EHR data and diagnostic images.
4. Test Release of Information From Start to Finish
Run a sample request for a patient whose records span the new EHR, the legacy archive, and paper files. Confirm that staff can verify the request, locate the relevant records, and deliver them in the appropriate format.
HIPAA’s right of access generally covers protected health information in a designated record set, including archived records. The federal rule generally requires covered entities to act within 30 calendar days, with a limited extension available under specified conditions.
If you use VitalChart release of information services, confirm how requests involving archived records will be routed and fulfilled before shutting down the source system.
5. Retire Hardware After the Records Are Accounted For
Once the archive and retrieval workflows are signed off, account for remaining copies on servers, drives, backup media, and vendor-hosted systems.
Check retention obligations and holds before authorizing disposal. Use an approved sanitization or destruction method appropriate for the media and document the outcome.
VRC provides hard drive destruction and IT asset disposition for equipment cleared for retirement.
Include Paper and Hybrid Medical Records
A historical patient record can span across several sources, including an electronic health record system, a scanned consent form, and a paper chart from an acquired practice, which can be a lot to consolidate. It’s best to decide which paper records to digitize based on how often staff need them, what they contain, and how long they must be retained.
If you use document conversion services, set indexing and image-quality requirements before scanning. Check that each scan is complete, readable, and associated with the correct patient. Review retention requirements and holds before releasing any originals for destruction.
Talk with VRC about the records work involved in your EHR retirement, from digitizing paper charts and organizing archived documents to supporting records requests and disposing of retired media.
Share this post
Resources
Latest Industry Insights
Stay informed with our expert perspectives on information management trends.
Get in Touch with Us.
See how we can help protect your records and documents throughout their life cycle.
