All templates
HealthcareIT & DevOps

Healthcare Data Backup & Recovery Standard Operating Procedure Template

Free data backup and recovery SOP template for healthcare IT teams. Covers EHR backup schedules, HIPAA data retention, disaster recovery for patient records, and ePHI encryption.

March 12, 2026·8 steps·14-point checklist

Purpose

Define the backup, verification, retention, and disaster recovery procedures for all systems containing electronic protected health information (ePHI) in a healthcare facility. This SOP ensures EHR data, clinical images, lab results, and administrative records are backed up on schedule, encrypted per HIPAA Security Rule requirements, retained for the mandated 6-year minimum, and recoverable within defined timeframes when a disaster or system failure occurs.

Scope

Covers all systems that store or process ePHI: EHR databases (Epic, Cerner, athenahealth), PACS imaging archives, laboratory information systems (LIS), pharmacy systems, revenue cycle/billing systems, and clinical communication platforms. Also covers the backup of administrative systems that contain PHI (HRIS with employee health records, credentialing databases). Does not cover network equipment configurations or non-PHI business systems, which follow the general IT backup SOP.

Prerequisites

  • Backup infrastructure provisioned: on-site backup servers or appliances, off-site replication target, and cloud backup destination
  • HIPAA Security Risk Assessment completed, with backup and recovery risks identified and mitigated
  • Backup software configured with encryption (AES-256 minimum) for data at rest and in transit
  • Recovery Time Objective (RTO) and Recovery Point Objective (RPO) defined for each critical system
  • Off-site or cloud backup location at least 50 miles from the primary facility to protect against regional disasters

Roles & Responsibilities

IT Infrastructure Manager

  • Own the backup schedule, retention policies, and disaster recovery plan
  • Review daily backup job reports and escalate failures within 4 hours
  • Conduct quarterly disaster recovery drills and document results

Database Administrator

  • Configure and maintain EHR database backup jobs per the defined schedule
  • Monitor database replication to the disaster recovery site and verify sync status daily
  • Execute database restoration procedures during recovery drills and actual incidents

HIPAA Security Officer

  • Verify backup encryption meets HIPAA Security Rule requirements (45 CFR 164.312)
  • Audit backup access logs quarterly to ensure only authorized personnel can restore data
  • Confirm backup retention periods meet the 6-year HIPAA minimum

Procedure

Classify every system containing ePHI into one of three tiers based on clinical impact. Tier 1 (mission-critical): EHR databases, pharmacy systems — RPO of 15 minutes, RTO of 1 hour. These use real-time database replication plus hourly snapshots. Tier 2 (clinical support): PACS, LIS, billing — RPO of 1 hour, RTO of 4 hours. These use hourly incremental backups plus nightly full backups. Tier 3 (administrative): HRIS, credentialing — RPO of 24 hours, RTO of 24 hours. These use nightly full backups. Document the schedule in the CMDB.

  • aList every system that stores or processes ePHI
  • bAssign each system to Tier 1, 2, or 3 based on clinical impact
  • cDefine RPO and RTO for each tier
  • dConfigure backup jobs in the backup software to match the schedule
  • eDocument the backup schedule in the Configuration Management Database (CMDB)
  • fReview and update the schedule annually or after adding new clinical systems

Completion Checklist

0/14

Key Performance Indicators

Backup job success rate

99.5% or higher of scheduled backup jobs complete successfully

Restore test success rate

100% of monthly restore tests pass data integrity verification

Disaster recovery RTO achievement

Tier 1 systems restored within 1 hour during quarterly drills

Off-site replication lag

Under 1 hour for Tier 1 systems; under 4 hours for Tier 2 systems

Backup retention compliance

100% of ePHI backups retained for the full 6-year HIPAA minimum

Revision schedule: Annually, or immediately after changes to EHR systems, backup infrastructure, disaster recovery sites, HIPAA regulations, or after any data loss incident.

Why This Matters for Healthcare

Patient records are irreplaceable. A healthcare facility that loses EHR data loses medication histories, allergy records, lab trends, and clinical notes that directly inform treatment decisions. The HIPAA Security Rule requires covered entities to maintain retrievable exact copies of ePHI (45 CFR 164.308(a)(7)(ii)(A)) and to have a disaster recovery plan (45 CFR 164.308(a)(7)(ii)(B)). OCR enforcement actions have resulted in settlements exceeding $2 million for organizations that failed to maintain adequate backup procedures. Beyond HIPAA penalties, a data loss event that disrupts patient care triggers Joint Commission scrutiny, media attention, and loss of patient trust that takes years to rebuild.

Common Mistakes

  • ×Running backups on schedule but never testing restores — when you actually need the data, you discover the backup is corrupt or incomplete
  • ×Storing backup encryption keys on the same server as the backup data — if the server is compromised, the attacker has both the data and the key
  • ×Relying on a single backup location without off-site replication — a fire or flood at the facility destroys both the production data and the backup
  • ×Setting retention policies shorter than 6 years, which violates HIPAA documentation requirements
  • ×Using a cloud backup provider without a signed BAA — this makes the provider's access to ePHI an unauthorized disclosure under HIPAA

Healthcare-Specific Notes

Healthcare data backup must satisfy HIPAA Security Rule administrative safeguards (data backup plan, disaster recovery plan, emergency mode operation plan) and technical safeguards (encryption, access controls, audit logging). Epic databases typically use Oracle or InterSystems Cache — backup procedures must account for the specific database technology. Cerner uses Oracle databases with specific backup agent requirements. athenahealth is cloud-hosted, but the facility is still responsible for ensuring the vendor maintains adequate backups per the BAA terms. PACS imaging data is often the largest data volume in a healthcare facility — plan storage and bandwidth accordingly. For facilities in states with medical record retention laws exceeding 6 years (some states require 10+ years for certain records), the backup retention must match the longer requirement.

Frequently Asked Questions

Learn More About Data Backup & Recovery

For a deeper look at building onboarding documentation, see our complete guide.

Record It Once

Record your backup procedures with Glyde

Walk through your backup verification or disaster recovery drill once. Glyde captures every screen, configuration step, and validation check — then generates an SOP your IT team can follow for every backup cycle and recovery drill.

Try Glyde Free