Documenting during EHR or internet downtime: where an offline scribe fits
The EHR goes down at 10:40 on a Tuesday. Maybe it is planned maintenance that ran long, maybe the internet line is cut, maybe it is something worse. The waiting room doesn't empty. You still have to see patients, and you still have to document them.
Most clinics have a downtime binder. Fewer have thought about what happens to their AI scribe in the same hour. If the scribe is a cloud service, it goes down with the internet. If it runs inside the building, it keeps working. This article is about where an offline scribe fits into a downtime plan, and where it doesn't.
Downtime is a when, not an if
A 2023 paper from Sydney Local Health District on its EHR downtime procedures puts it plainly: "downtime events are inevitable and common." The authors list the usual causes: planned maintenance and upgrades, cyber-attacks, IT failures, power outages, and hardware or software faults (Lyon et al., Applied Clinical Informatics, 2023). It also cites a study in a Swedish emergency department where downtime was associated with a median increase in length of stay of 76 minutes.
Two recent events showed how wide an outage can spread when it starts outside the building. In February 2024, the cyberattack on Change Healthcare, which the American Hospital Association called "the most significant and consequential cyberattack on the U.S. health care system in American history," disrupted claims and eligibility checks across the country (AHA, March 2024). In July 2024, a faulty security software update from CrowdStrike disrupted digital services at at least 759 of the 2,232 US hospitals researchers were able to scan, according to a study in JAMA Network Open (JAMA Network Open, summarised by Fierce Healthcare).
Neither event was the clinic's fault. Both landed on clinics anyway.
What the rules already ask for
HIPAA's Security Rule requires a contingency plan: policies for responding to "an emergency or other occurrence (for example, fire, vandalism, system failure, and natural disaster) that damages systems that contain electronic protected health information." Within that, an emergency mode operation plan is required, and testing the plan is an addressable item (45 CFR 164.308(a)(7)).
The federal SAFER Guides go further for EHRs. The Contingency Planning guide covers "planned or unplanned EHR unavailability," meaning any time clinicians can't reach all or part of the record (ASTP/ONC, SAFER Guides). If you haven't read it, it is the best free checklist available for this problem.
Any AI scribe you depend on is now part of the system that contingency plan has to cover.
What happens to each kind of scribe
A cloud scribe
A cloud scribe sends the recording to a vendor's servers to be transcribed and written up. When your internet is down, it can't do that. Some apps keep the recording on the phone or laptop and process it later, which helps, but you finish the day without drafts. When the vendor has an outage, the same thing happens even though your internet is fine.
A scribe on the laptop
With ScribeMD Desktop in Local only mode, speech-to-text and note writing both run on the computer. It needs the internet once, to download the app and the models. After that it works fully offline. If the internet line is cut, nothing about the visit changes: the transcript appears as you talk, and the note is written when you stop.
A laptop on battery also survives a short power cut that takes down the network switch, which a server in the closet doesn't.
A scribe on a server in the building
Cortex is a box that sits on the clinic network. Exam rooms record to it over that network, and it writes the transcript, note and codes on site. An outage at your internet provider doesn't stop it. It does need the clinic's own network and power, so pair it with your existing plan for those.
What a scribe can't do during downtime
A scribe writes the note. It doesn't give you the chart. During an EHR outage you still won't see allergies, the medication list, recent labs or the last specialist letter unless your downtime plan provides a read-only copy. The SAFER Contingency Planning guide covers that, and it is a bigger patient-safety question than documentation.
A scribe also doesn't put the note into the EHR while the EHR is down. You end the outage with a stack of drafts that need to be reviewed, signed and entered. That is still far better than a stack of handwritten pages that need to be read, remembered and retyped, but it is work, and it needs an owner.
Adding the scribe to your downtime plan
- Write it down. Name the scribe in the contingency plan, with which kind it is and what it needs to keep working (internet, clinic network, power).
- Keep at least one offline-capable machine ready. A laptop with the models already downloaded and Local only tested. Models can't be downloaded during an internet outage.
- Decide the template. Downtime is not the moment to try a new note format. Use the template your clinicians already sign every day. SOAP, History and physical, and Progress note are built in.
- Label downtime drafts. Agree on a convention, such as starting the note title with the date and "downtime," so back-entry is easy to track.
- Assign back-entry. Decide who checks that every downtime draft was reviewed, signed and entered once the EHR is back, and by when.
- Test it. The Security Rule lists testing and revision of the contingency plan for a reason. Run one clinic session a year in downtime mode, scribe included.
The patient conversation doesn't change
Patients should know a tool is listening, whatever the network is doing. An offline scribe gives you a concrete answer to the usual question: the recording is transcribed on this computer, and it stays on this computer.
Where to start
If you are one clinician, download ScribeMD Desktop from the Local page. It is free for individual doctors and needs no account, so it costs nothing to keep ready as the downtime option even if you use something else day to day. If you run a clinic and want every exam room covered when the internet isn't, read our checklist for putting an AI server in your clinic and then look at Cortex.