Ask KJ · Healthcare cybersecurity
EHR Backup, Ransomware Recovery, and Clinical Downtime
Plan for a clinical outage and test restoration of records before relying on backups.

By Kimm C. King Jr. · Reviewed
Choose recovery targets around patient work
List the systems needed for scheduling, chart access, orders and referrals, medications or allergies where applicable, billing, and later record reconciliation. Agree how long critical work can run without each system and how much recent data could be lost. Document vendor recovery commitments and limitations.
Protect backups and test real restoration
Use separate access for backup administration and consider offline or immutable copies appropriate to the environment. Test the recovery of an EHR export, imaging and attachments, along with access and sequencing dependencies. Use test or approved controlled data and record whether clinical staff could use the restored information.
Run a downtime tabletop
Have staff simulate the loss of internet, the primary EHR, or single sign-on. Identify paper or approved offline workflows, call trees, access to critical records, and how to avoid duplicate entries. When the service returns, have designated staff reconcile the approved downtime records.
Keep evidence from the drill
Record the timestamp, systems, recovery gaps, responsible people, and next test date. An operational return to service and a privacy or breach determination have separate evidence needs.
My answers to related practice questions
Official sources
Apply this to your practice
Confirm requirements for your organization, services, and jurisdiction with your privacy or legal lead. Use fictional or approved de-identified examples when testing. Keep PHI out of public forms.
Find healthcare resources by state or city · All healthcare cybersecurity guides
Explore cybersecurity consulting · Read the website’s healthcare data notice