HIPAA Contingency Plan Template for Small Practices

At 7:10 a.m., the practice can reach its phones but not the EHR. The backup dashboard is green. Nobody knows who can request a restore, whether multifactor authentication depends on the unavailable network, or where today’s medication messages should wait.

The missing item is not another backup. It is an executable plan.

Takeaways

  • Name the data, applications, dependencies, and owners inside the recovery boundary.
  • Test restoration, not just backup completion.
  • Define a safe emergency mode for the clinical day.
  • Record gaps and retest after material change.

This outline supports planning. It does not establish HIPAA compliance, clinical downtime safety, or a recovery guarantee.

Draw a recovery boundary

Start with the electronic protected health information the practice creates, receives, maintains, or transmits. Then add the services needed to reach it.

RECOVERY BOUNDARY

Application or data set: __________________________________
Business and clinical owner: ______________________________
Hosting and backup owner: _________________________________
Identity, network, device, and power dependencies: ________
Last verified restore: ____________________________________
Downtime method and safe limit: ___________________________
Recovery priority and reason: _____________________________
Vendor escalation route: _________________________________

A backup that needs an unavailable identity provider is not yet a usable recovery path. A restored database without the attachments or audit history the practice relies on may be incomplete. Ask what is backed up, what is excluded, how versions are selected, and who can authorize each step.

Build the plan around three required jobs

HHS’s administrative-safeguards guidance describes the contingency-plan standard and its specifications. Translate the three required jobs into operations.

JobPractice decisionEvidence after a test
data backupwhat is copied, where, by whom, and how failure is noticedbackup event, exception, scope, retained version
disaster recoveryhow lost data and systems are restoredrequest, authorization, restore result, reconciliation
emergency modehow critical work continues while protections and systems are disruptedapproved downtime steps, role roster, controlled records

Testing and revision procedures and application-and-data criticality analysis are addressable specifications. “Addressable” does not mean optional by default. The practice evaluates what is reasonable and appropriate, implements an appropriate measure, or documents why an alternative meets the standard.

Make recovery order a clinical decision

A vendor may rank systems by infrastructure dependency. A practice also needs to rank patient-facing work. List the first few hours of a disrupted day: urgent messages, medication questions, results needing review, scheduled visits, referrals, billing, and routine filing. Assign a safe temporary route and a maximum tolerable delay through the practice’s clinical-governance process.

Do not invent universal recovery-time promises. Record the practice’s target, the basis for it, the vendor commitment if any, and the test result as separate fields. When those numbers disagree, the gap belongs in the risk register.

The EHR downtime plan provides a clinical-day worksheet. The HIPAA risk-assessment template helps connect recovery gaps to risk treatment.

Run a restore with invented data

Choose a test record that contains no patient information. Create it, confirm that the backup scope should include it, and have an authorized person request a restore into an approved test location. Record:

  1. who noticed and approved the request;
  2. the backup version selected;
  3. identity and network dependencies encountered;
  4. whether the restored content was complete and readable;
  5. how the test copy was secured and removed;
  6. every exception, owner, due date, and retest.

Then run a tabletop with the application unavailable. Staff should locate controlled downtime forms, reach the role roster, handle one urgent message, record one visit, and reconcile the invented records after service returns. Do not send a real patient message or alter a live chart during the exercise.

HHS’s ransomware fact sheet places contingency planning within the response to cyber disruption. NIST SP 800-34 Rev. 1 provides a broader seven-step planning method for federal information systems. It is useful planning reference material, not a statement that every NIST step is a HIPAA requirement for a small practice.

Keep one revision trail

TEST AND REVISION LOG

Scenario and date: ________________________________________
People and systems participating: _________________________
Restore or emergency-mode result: _________________________
Unmet dependency or unsafe ambiguity: _____________________
Interim control: __________________________________________
Permanent owner and due date: _____________________________
Retest evidence: __________________________________________
Plan version approved: ____________________________________

Patient Square is one part of a practice’s service map, not its contingency plan owner. Before adoption, ask which data can be exported, what support and recovery terms are documented, and how the selected deployment behaves when connected services are unavailable. Check the current US security page and agreement, then test the practice-owned workflow. A green vendor dashboard is a signal; witnessed recovery is evidence.

FAQ

Common questions

Which HIPAA contingency plan elements are required?

The HIPAA Security Rule's contingency-plan standard includes required data backup, disaster recovery, and emergency-mode operation plan specifications. Testing and revision procedures and applications-and-data criticality analysis are addressable specifications, which means the organization must assess and document how the standard is reasonably and appropriately met.

Is a cloud vendor's backup enough for HIPAA contingency planning?

No vendor statement completes the practice's plan. The practice still needs to understand scope, recovery roles, access dependencies, downtime work, communication, restore evidence, and the path back to controlled operations. Contract and service evidence should be tested against the practice's own risk analysis.

How often should a medical practice test its contingency plan?

HIPAA does not prescribe one universal annual interval for every contingency-plan test. Set a risk-based cadence and triggers such as a material system change, failed restore, vendor change, office move, or incident. Record the scenario, result, gaps, owners, and retest date.

Does a contingency plan replace a breach or incident-response plan?

No. Contingency planning focuses on availability and continuity under disruption. Incident response addresses detection, containment, evidence, assessment, communication, and recovery for an event. The plans should meet at named handoffs without collapsing into one vague document.

Sources

  1. HHS OCR: HIPAA Security Series, Administrative Safeguards.
  2. HHS OCR: Fact Sheet on Ransomware and HIPAA.
  3. NIST SP 800-34 Rev. 1: Contingency Planning Guide.