Backup Requirements for Medical Offices in Idaho

HIPAA backups aren't optional and 'we sync to OneDrive' isn't a strategy. Here's what §164.308(a)(7) actually requires and how to build a defensible PHI backup.

Reviewed by Joey Garcia · CompTIA Security+ · USAF Veteran · February 27, 2026

Backup is one of those topics that puts people to sleep until they need a restore. At that point it's the only topic in the world.

For Idaho medical and dental offices, the stakes are higher than for most small businesses. Lose patient records and you don't just have a recovery problem; you may have a HIPAA reportable breach, possible state notification duties, and potentially an OCR investigation asking why you can't restore data you were required to safeguard.

Here's the part that catches most practices off guard: HIPAA actually prescribes what your backup program must include. And not in vague terms. It's in specific Security Rule language. You can read §164.308(a)(7) and §164.312 and walk away with a checklist. Most practices have never read either.

Let's fix that.

What HIPAA Actually Requires

The HIPAA Security Rule covers backup under the Administrative Safeguards section (§164.308(a)(7)), specifically the Contingency Plan standard. There are five implementation specifications under that standard: three required and two addressable.

§164.308(a)(7)(ii)(A): Data Backup Plan (Required)

"Establish and implement procedures to create and maintain retrievable exact copies of electronic protected health information."

Key words: retrievable , exact copies , electronic protected health information . You can't just have backups; you have to demonstrate you can pull data back when you need to, and that the copies are accurate.

§164.308(a)(7)(ii)(B): Disaster Recovery Plan (Required)

"Establish (and implement as needed) procedures to restore any loss of data."

This is the plan . It goes beyond "we have backups" to "here are the steps we'd follow to restore X system in Y time after a Z event."

§164.308(a)(7)(ii)(C): Emergency Mode Operation Plan (Required)

"Establish (and implement as needed) procedures to enable continuation of critical business processes for protection of the security of electronic protected health information while operating in emergency mode."

Translation: how do you keep operating safely while you're recovering? If your system is down for 48 hours, what's the safe way to handle patient care, check-ins, and PHI during the gap?

§164.308(a)(7)(ii)(D): Testing and Revision (Addressable)

"Implement procedures for periodic testing and revision of contingency plans."

Addressable doesn't mean optional. It means you implement it if reasonable, document why if you don't, and adjust based on practice size. For a typical small clinic, it's reasonable. Test your backups.

§164.308(a)(7)(ii)(E): Applications and Data Criticality Analysis (Addressable)

"Assess the relative criticality of specific applications and data in support of other contingency plan components."

Rank your systems. The practice management system and the imaging system are tier 1. The breakroom microwave timer is not.

That's the HIPAA backup framework in plain English. Now let's translate it into actual technology.

The 3-2-1 Backup Rule for Patient Information

The industry-standard rule for backup design is 3-2-1, and it applies cleanly to medical practices.

  • 3 copies of your data: the live system, plus two backups
  • 2 different media , for example a local backup appliance plus a cloud target
  • 1 offsite : at least one copy is physically separated from your office

For PHI specifically, you also need:

  • Encryption at rest on every copy. Both local and cloud backups must be encrypted. Unencrypted backups containing PHI are a breach waiting to happen if the backup media is lost or stolen.
  • Encryption in transit : when backups are transmitted to cloud or offsite locations, the transmission is encrypted (HTTPS, TLS).
  • Audit logging of backup and restore operations (who restored what, when). This supports the HIPAA audit-controls standard.

The cheap-and-dirty "we copy files to a USB drive overnight" approach fails on multiple counts: not encrypted, not offsite, not logged, not tested. It's not a HIPAA backup.

Immutable Backups and Ransomware-Resistant Storage

The most important evolution in backup design over the past five years is immutability : backup copies that cannot be encrypted, deleted, or altered by an attacker who has gained access to your network.

Why this matters: modern ransomware operators don't just encrypt the live system. They specifically hunt down your backups before triggering the encryption. They want to make sure you can't recover without paying. And they're good at it. Common targets include:

  • Veeam / Datto / BDR console: they log in with stolen admin credentials and delete the backups
  • Shadow copies on the local system, disabled by ransomware as a first step
  • Cloud sync targets like OneDrive or Google Drive: encrypted files sync to the cloud, replacing clean copies
  • Any backup target reachable from the compromised network

Immutable backups solve this by making backup copies write-once-read-many. Once written, they can't be changed or deleted for a defined retention period, even by an admin. Common implementations:

  • S3 Object Lock (AWS, or any S3-compatible storage) in Compliance mode
  • Azure Blob Storage with immutable policies
  • Datto immutable cloud (or similar from BDR vendors that support it)
  • Wasabi or Backblaze with object lock enabled
  • On-prem appliances with hardware-level immutability (Rubrik, Cohesity, modern Synology with snapshot retention)

The retention period should match your recovery objective. For a small clinic, 30-90 days of immutable history is typical. Long enough that even a slow-burn attack that's been hiding for a few weeks can be recovered from.

Restore Testing: The Most-Skipped Step

Untested backups are a hypothesis. Tested backups are a plan. Backups that have been silently broken for months are a common discovery in small practices.

A real restore test, for a medical practice, looks like:

  • Monthly file-level test: pick a random patient file, restore it to an alternate location, verify it opens and the contents are correct. 15 minutes of work, documents your backup is functioning.
  • Quarterly application-level test: restore the practice management database to a test environment. Verify it boots, the data is consistent, you can run a basic report. Half a day of work, proves you can recover the system , not just files.
  • Annual full-DR test: simulate a full outage. How long does it actually take to bring the whole environment back? Where are the bottlenecks? What's missing from the runbook? A day of work, often illuminating.

The test results get documented. Date, what was tested, what worked, what didn't, what was fixed. This documentation is your audit trail when HIPAA compliance gets reviewed, and it's your operational record when you're picking the next data backup solution .

Recovery Time Objective and Recovery Point Objective

Two numbers every practice should know about their backup setup:

Recovery Time Objective (RTO): how long can you be down before it materially hurts? For a typical medical office, the answer is usually 4-8 hours. After that, appointments cascade, patients reschedule, and the operational cost compounds.

Recovery Point Objective (RPO): how much data can you afford to lose? If your backup runs nightly and the ransomware hits at 3pm, you've lost a day of work (patient encounters, new records, billing entries). For most clinics, the RPO target is 1-4 hours. Continuous or hourly backups are the standard for tier-1 systems.

Many small clinics have a backup that might meet a 24-hour RPO and a 24-48 hour RTO. The OCR-acceptable defense for "we lost two days of patient data due to a ransomware incident" is much weaker than for "we lost two hours."

A modern BDR (backup and disaster recovery) appliance with continuous data protection can typically get small clinics to a 1-hour RPO and a 4-hour RTO for roughly $300-500/month in appliance and storage costs. The math against the cost of a longer outage is straightforward.

Where Small Practices Get It Wrong

A few common patterns in small practices:

  1. "We back up to OneDrive." OneDrive is sync, not backup. Files modified on the live system replicate to OneDrive within minutes, including ransomware-encrypted files. You can recover individual files from version history, but a full ransomware event will outpace OneDrive's protection.
  1. "The vendor handles our backups." Cloud-hosted PM systems (Dentrix Ascend, Open Dental Cloud, etc.) do backups on the back end, but the BAA usually limits the recovery options. Read your agreement. Often the vendor recovers the database; you're responsible for everything else (workstation files, scanned documents, email).
  1. "Our IT person handles it." Sometimes true, sometimes not. Get the specifics in writing: what's backed up, where, how often, how long retained, when last tested. If your IT person can't produce that documentation in 24 hours, you don't have a defensible backup program.
  1. "We have a backup drive in the closet." Local-only backups break the 3-2-1 rule (keep one copy offsite), and they fail in the most common disaster scenarios (fire, flood, theft of the whole office).
  1. "Our last restore test was…" (silence) . If you can't remember, the answer is too long ago.

What Good Looks Like

For a typical 5-15 person Boise medical or dental office, a defensible HIPAA-aligned backup looks like:

  • BDR appliance onsite running continuous-data-protection snapshots
  • Cloud replication to an immutable target (Datto Cloud, Wasabi with object lock, or similar)
  • Encryption at rest and in transit, with documented key management
  • Monthly file-level restore tests, documented
  • Quarterly application-level restore tests, documented
  • Annual full-DR tabletop, documented
  • Written contingency plan covering data backup, disaster recovery, and emergency operations
  • BAAs in place with the BDR vendor and the cloud storage provider

Total cost: typically $300-700/month for a small practice for the appliance lease and cloud storage, with managed support priced separately. Compared to the cost of an unrecoverable ransomware event, which can be six figures and an existential threat to the practice, it's cheap insurance.

For HIPAA-related IT services and a broader walkthrough of compliance, the medical IT services page covers the rest of the picture.

The Honest Take

The point of HIPAA's backup requirements isn't bureaucracy. Patient records matter, ransomware is real, and a small practice without recoverable backups is one incident away from losing the business.

The fix isn't expensive or exotic. It's just rarely set up correctly the first time, and almost never tested afterward. If your last restore test was "sometime last year" or "we've never done one," you don't actually know what you have.

If you're a Treasure Valley medical or dental office and you want to talk through your current backup setup (what's covered, what's not, what tests have been run, what gaps exist for HIPAA), request a free 15-minute call.

Let's Talk

A working backup is the difference between a bad afternoon and an ended business. Let's make sure yours actually works.

Request a Free 15-Minute Call →

About Joey Garcia

USAF Veteran CompTIA Security+ Boise, ID

Joey Garcia is the founder of Idaho Proper IT, a Boise-area technology company serving trades, professional offices, and other small businesses. He served in the U.S. Air Force at Mountain Home AFB, holds a CompTIA Security+ certification, and has worked in IT support and administration roles since 2022. Idaho Proper IT is intentionally personal: Joey does the work himself, without handing you to a junior technician you have never met.

📞 (208) 918-0636 Free IT health check →

Share this article:

Need Help With This? Let's Talk.

Talk directly with Joey about your business technology. Start with a free 15-minute IT review.