Practice Academy / Security & continuity
When systems go down,
what keeps working?
A physician owner’s guide to responsibilities, dependencies, and recovery evidence.
General physician business education • Prepared November 15, 2026
Executive summary
Protecting information and maintaining safe operations are connected responsibilities. A secure product, a signed business associate agreement, or a successful backup job does not by itself prove that a practice can continue essential work during disruption. Start by identifying the systems and people that critical workflows depend on. Assign authority for technical response, clinical decisions, privacy assessment, and administrative coordination before an incident occurs. Then test approved continuity and restoration arrangements and record what remains unresolved. This lesson gives physician owners a way to ask better questions without pretending they should personally operate every security control. It is an educational framework, not a security certification, clinical downtime protocol, or assurance that a practice satisfies all applicable requirements.
Learning outcomes
- Distinguish confidentiality, integrity, and availability.
- Map a critical workflow’s dependencies and accountable roles.
- Ask for recovery evidence rather than relying on product or contract labels.
Where this fits: Build on vendor and technology handoffs. Apply this lesson when selecting systems, reviewing continuity plans, or changing a practice’s operating model.
A dependency map, not a product list
The EHR is only one part of the system.
Can the right person authenticate?
Can the practice reach the service?
Is the vendor system available?
Can authorized staff obtain the needed information?
Repeat this exercise for phones, results, prescribing, billing, payments, and other essential work. Record information flows and shared dependencies. Two applications may depend on the same identity service or connection, so two vendor names do not necessarily mean two independent recovery paths.
The HIPAA Security Rule applies to covered entities and business associates and protects electronic protected health information through administrative, physical, and technical safeguards (U.S. Department of Health and Human Services [HHS], 2026b). Do not assume that every business record is ePHI or that a nonclinical company can never have business associate responsibilities.
HHS’s risk-analysis guidance encompasses the ePHI an organization creates, receives, maintains, or transmits, not merely its EHR. It does not prescribe a single method that guarantees compliance (HHS, 2026a). A completed questionnaire should therefore prompt examination of scope and unresolved risks, not an automatic compliance claim.
Three different protections
Confidentiality: preventing unauthorized access or disclosure. Integrity: protecting information against unauthorized alteration or destruction. Availability: making information usable when an authorized person needs it (HHS, 2026b). A measure that addresses one dimension may leave another unresolved. HHS explains, for example, that a cloud provider maintaining ePHI can be a business associate even without the decryption key; encryption alone does not resolve all integrity, availability, or administrative risks (HHS, 2022).
Proposed operating model / Confirm actual assignments
Coordination is not technical incident response.
| Role | Responsibility to define |
|---|---|
| Physician owner and governance | Resources, accountable roles, priorities, and escalation arrangements |
| Security official and qualified security/IT operators | Assigned safeguards, monitoring, investigation, containment, and restoration within authorized scope |
| Clinical leadership | Safe care implications, clinical prioritization, and approved downtime procedures |
| Administrative coordinator | Inventory, vendor follow-up, exercise coordination, evidence, and unresolved-action tracking |
| Privacy and legal advisors | Applicable duties, facts, and notification decisions |
| Technology vendors | Contracted technical services, support, escalation, and relevant evidence |
MedCBO’s administrative coordination can help organize these responsibilities when included in the engagement. It does not replace the practice’s security official, qualified technical responders, clinical leadership, or legal advisors. Do not infer a security operations center, forensic response service, penetration-testing capability, or compliance guarantee from an administrative-support agreement.
NIST’s Cybersecurity Framework 2.0 provides an outcome-oriented structure for assessing, prioritizing, and communicating cybersecurity work. It does not prescribe one implementation for every outcome (Pascoe et al., 2024). Framework alignment can organize discussion; it is not legal sign-off.
Fictional case
The backup succeeded. The practice still cannot work.
The EHR is inaccessible. A vendor dashboard reports that last night’s backup job succeeded. Staff cannot determine how to access the approved downtime information or whom to contact for restoration. Pending results and orders need attention.
A successful job report is useful evidence about that job. It does not establish that restoration has been tested, that staff can use the recovered information, that all critical systems are covered, or that interrupted work will be reconciled.
Knowledge check: may administrative staff treat the backup status as permission to resume normal care?
No. Clinical leadership determines safe care implications. Qualified technical responders establish system status and recovery evidence. Administrative staff coordinate the approved process, communications, and outstanding work without substituting their judgment for those roles.
Ask for the next evidence
- Who is directing technical investigation and coordinating the relevant vendors?
- What approved downtime process applies to the affected workflow?
- Which information and services are available, incomplete, or unreliable?
- What restoration evidence exists, and who validates its scope?
- How will documentation, orders, results, and other interrupted work be reconciled?
- Who assesses privacy implications and any notification obligations?
An operational outage, security incident, and legally reportable breach are not interchangeable labels. Use the designated response process and qualified assessment rather than assuming every outage is a breach or every restored system is fully resolved.
Continuity is a maintained capability
Test, learn, and close the gaps.
HHS describes security-incident procedures and contingency planning that address backup, restoration, and protection of ePHI during emergency operations. Its summary also explains that “addressable” implementation specifications are not simply optional; the regulated entity must assess and document the appropriate treatment (HHS, 2026b). Review the current rule rather than treating proposed amendments as existing requirements.
A practical governance record should identify the exercise or review performed, its scope, evidence, gaps, accountable owners, and follow-up dates. Revisit the record after meaningful system, vendor, workforce, or operating changes. Avoid a universal restoration-time promise: the appropriate objectives depend on the practice’s risks, clinical requirements, system architecture, and resources.
An owner dashboard can show critical dependencies without tested recovery, unresolved high-priority risks, overdue access or vendor reviews, and unclosed exercise findings. Define the measures and their scope. A green score without evidence is not an assurance.
Next: assign vendor handoffs · understand MedCBO’s scope · Practice Academy.
References & source notes
U.S. Department of Health and Human Services. (2022, December 23). Guidance on HIPAA & cloud computing. HHS cloud guidance.
U.S. Department of Health and Human Services. (2026b, August 7). Summary of the HIPAA Security Rule. HHS summary.
U.S. Department of Health and Human Services. (2026a, August 12). Guidance on risk analysis. HHS guidance.
Pascoe, C., Quinn, S., & Scarfone, K. (2024). The NIST Cybersecurity Framework (CSF) 2.0 (NIST CSWP 29). National Institute of Standards and Technology. https://doi.org/10.6028/NIST.CSWP.29
Sources checked November 15, 2026. HHS dates above are the pages’ last-reviewed dates, not claims about original publication. The case, map, and responsibility table are educational synthesis, not empirical findings or a validated clinical protocol. Applicable duties depend on role, information, contracts, jurisdiction, and facts. No certification or compliance guarantee is made.