Downtime: the paper kit and the catch-up protocol

The first ten minutes: switch, don't wait

The moment the EHR stops responding, stop troubleshooting and start the paper protocol: log the exact time service stopped, tell the front desk to switch to the paper schedule, and keep seeing patients. HIPAA's Security Rule expects a documented contingency plan for precisely this moment — a data backup plan, an emergency-mode operating plan, and a way to keep functioning while electronic systems are unavailable 1Ref 1HHS Office for Civil Rights (2026).Summary of the HIPAA Security Rule.That the Security Rule requires scalable administrative, physical, and technical safeguards anchored in a risk analysis, which is the basis for expecting a documented contingency plan for outages..

A few things matter more than they seem to in the first ten minutes:

• Write down the start time somewhere durable — a wall calendar, a notebook, your phone. You will need it later to reconcile the chart.
• Don't try to diagnose the outage yourself past a quick check (is it your internet, or the vendor's). That call belongs to support, not to the ten minutes you have between patients.
• Keep the day moving. A downtime protocol only works if it assumes the day continues — patients still arrive, prescriptions still get requested, calls still come in.

Building the paper downtime kit before you need it

A downtime kit assembled during the crisis arrives too late to help; build it before you need it. Stock printed structured downtime forms that mirror your usual note fields, a current patient roster with medication and allergy snapshots, blank prescription paper if you prescribe, and a one-page script telling the front desk what to say to callers and how to triage same-day requests.

The kit is basic EHR operations hygiene, not a luxury item for a bigger practice — a solo clinician has no colleague to borrow a form from when the terminal freezes.

Charting during downtime: what a valid paper note needs

A downtime note is not a placeholder to clean up later — it is the legal record of that encounter until it is transcribed, so it needs everything an electronic note needs: the date, start and stop times, the reason for the visit, your assessment and plan, and your signature, written in real time rather than reconstructed from memory afterward.

Resist the temptation to write shorthand you'll "expand later." Later is exactly when the details are gone. If a paper note references material that lives in the chart — a prior problem list entry, a standing medication regimen — note that you reviewed it rather than trying to reproduce it from memory on paper.

The catch-up protocol once the system returns

Treat the system's return as its own workflow rather than something squeezed between patients: scan or transcribe every paper note the same business day, attach the original scan to the chart, and work oldest first so nothing ages past the point you can recall it accurately. Information-blocking rules treat you as an ongoing duty-bearer for making electronic health information available without unreasonable delay, so a backlog that lingers for days reads as delayed access, not outage recovery 2Ref 2Office of the National Coordinator / ASTP (2026).Information Blocking.That clinicians are actors under the information-blocking rule with an ongoing duty not to interfere with access to electronic health information, which frames why a lingering downtime backlog carries its own risk..

• Scan first, transcribe second. The image preserves the original even if your transcription is imperfect.
• Work oldest-first. The visit from this morning is easier to recall accurately than the one from three days ago.
• Route as you go. A paper note that mentions a referral or a lab order needs to land in the same in-basket for one workflow you'd use for anything else that arrived electronically — don't let it sit in a separate "downtime" pile indefinitely.

If your downtime overlapped with a stack of faxes or mailed records, the same catch-up discipline applies to the inbound pile as to your own notes: scan, index, route, and don't let two backlogs merge into one unmanageable one.

Signatures and authentication on backdated entries

Medicare requires every service to be authenticated by a handwritten or electronic signature, and a downtime note transcribed later is no exception: sign and date the paper original at the time you write it, then apply your normal electronic signature when you enter it into the chart, recording the true date of service separately from the date of entry 3Ref 3Centers for Medicare & Medicaid Services (2023).Complying with Medicare Signature Requirements.That Medicare requires authentication by handwritten or electronic signature and that attestation can cure a missing signature, supporting the signature discipline for backdated downtime entries..

If a signature is somehow missing when a note is reviewed later, an attestation statement can cure it — but that is a fallback, not a plan. Sign the paper original in the moment; don't rely on being able to reconstruct and attest to it months later during an audit.

Picking a vendor and contract that shrink your downtime risk

How often your EHR goes down, and how fast support responds when it does, is a contract term you can negotiate before signing — not a surprise you discover afterward. ONC's EHR contracting guide flags uptime commitments, support-response times, and data-access terms as exactly the clauses a solo practice tends to skip past and regret later 4Ref 4Office of the National Coordinator (2016).EHR Contracts Untangled: Selecting Wisely, Negotiating Terms, and Understanding the Fine Print.ONC's guidance that uptime, support-response, and data-access terms are contract clauses to negotiate before signing, supporting the vendor-selection discussion of downtime risk..

If you're mid-search on a replacement system, the ehr migration is where those questions belong, not an afterthought once you've already signed. And if your current vendor has sent you a sunset notice, your downtime math changes entirely — the outage risk that matters most is the one at the end of the contract, not the one in the middle of it. When support is slow to respond during an active outage, escalation through the right channel is a skill worth having ready before you need it.

When downtime becomes a security event

Not every downtime looks like routine downtime in the first hour — ransomware, a failing server, or a vendor-side breach can present identically, so treat any unplanned outage as a possible security incident until you've ruled that out. The Security Rule's risk-analysis obligation does not pause during an outage, and a free tool sized for small practices exists so a solo clinician can complete one without a consultant 5Ref 5Office of the National Coordinator / ASTP (2026).Security Risk Assessment Tool.That a free ONC/OCR risk-assessment tool sized for small practices exists, supporting the claim that a solo clinician can evaluate a downtime event as a possible security incident without a consultant..

If you lean on an answering service or a backup scheduling vendor to get through an outage, confirm a signed business associate agreement covers them before you hand over patient information — a stopgap vendor is still a business associate 6Ref 6HHS Office for Civil Rights (2026).Business Associates.That any vendor creating, receiving, maintaining, or transmitting PHI on the practice's behalf is a business associate requiring a BAA, supporting the caution about stopgap vendors used during downtime.. A downtime plan that only covers the EHR and ignores every vendor you route around it is an incomplete plan.