EHR Downtime Procedures for Nursing Homes: A Template You Can Adapt

It’s 2:40 a.m. and the EHR won’t load on any unit. The charge nurse on the second floor is an agency nurse on her third shift in your building. She knows the facility “has downtime procedures.” She doesn’t know where the binder is, who is supposed to call it, or whether the backup MAR printouts on the shared drive are from tonight or from last Tuesday.

That is the failure most nursing homes are set up for. They have downtime procedures in the sense that a policy exists somewhere. What they don’t have is a document a stranger could pick up at 2:40 a.m. and follow.

This post is a template for that document: what EHR downtime procedures for a nursing home should contain, section by section, with the decisions you need to fill in. If you want the IT triage side (is it PointClickCare or is it our building?), we cover that separately in our PointClickCare outage checklist.

The short answer

EHR downtime procedures for a nursing home are a written plan for continuing resident care and documentation when the electronic health record or eMAR is unavailable. A usable version answers seven questions:

  1. When is downtime declared, using a time threshold, not a judgment call?
  2. Who declares it on every shift, including nights and weekends?
  3. Where is the backup clinical data, such as eMAR backup reports, and how do you know it’s current?
  4. What paper forms are used, and where are they kept on each unit?
  5. Who gets notified: staff, IT, pharmacy, lab, administrator on call?
  6. How is paper documentation entered back into the EHR, and by whom?
  7. How is the event logged and reviewed so the next one goes better?

Everything below is a way to answer those seven questions for your building.

Why this has to be written down

Federal rules already expect it. The CMS emergency preparedness requirements for long-term care facilities, 42 CFR 483.73, require policies and procedures that include “a system of medical documentation that preserves resident information, protects confidentiality of resident information, and secures and maintains the availability of records.” The same section requires the emergency plan to be reviewed and updated at least annually, built on an all-hazards risk assessment, and tested with exercises at least twice a year.

An EHR outage is one of the most likely hazards on that risk assessment. A cyberattack, a carrier outage, a failed firewall or a vendor incident all end in the same place: nurses on paper. If the procedure for that lives only in the heads of your day-shift DON and one unit manager, it isn’t a system of documentation. It’s a hope.

For how this fits the rest of the emergency plan, see our guide to the IT pieces of the CMS emergency preparedness rule.

The template, section by section

1. Scope: which systems this covers

List every system whose loss sends staff to paper. For most skilled nursing facilities that’s the EHR and eMAR, and often a pharmacy ordering portal and lab results interface. Name each one, the vendor, and the vendor’s support number.

Fill in:

  • Systems covered: ______
  • Vendor support contacts (printed, not just saved in the EHR): ______
  • IT provider help desk and after-hours number: ______

2. Downtime levels and the trigger to go to paper

Write a time-based rule. “Use judgment” fails at night.

A published example from a long-term care system running PointClickCare, Health PEI’s PCC downtime procedures, uses three scenarios. An outage under two hours within one shift does not invoke downtime procedures; staff catch up before the shift ends. An outage over two hours invokes them, led by the on-shift RN supervisor. An outage that spans a shift change gets its own handling, because paper has to pass between shifts.

You don’t have to copy their two-hour number. Your DON and medical director should set the threshold around your med pass schedule. But you should copy the structure: a short outage, a long outage and an outage that crosses a shift change are three different events.

Fill in:

  • Level 1 (short, single shift): under ___ minutes. Action: ______
  • Level 2 (extended, single shift): over ___ minutes, or overlapping a scheduled med pass. Action: go to paper.
  • Level 3 (crosses a shift change): paper handoff rules: ______

3. Who declares downtime, on every shift

Name a role, not a person: “the RN supervisor on duty,” with a backup role if that person is on a unit. The Health PEI procedure has the nurse supervisor contact IT to confirm the system or network is down, then lead the response.

Then check the roster. If your night supervisor is regularly an agency nurse, your procedure has to work for an agency nurse. That means it can’t depend on knowing which closet the binder is in.

Fill in:

  • Declares downtime: __ (backup: ____)
  • Confirms with IT by calling: ______
  • Notifies administrator on call when: ______

4. Backup clinical data: where it is and how you know it’s current

This is the section where IT and clinical operations meet, and where most plans quietly fail.

PointClickCare offers an eMAR Backup process. In the Health PEI deployment, it creates “a paper image of electronic treatment records” covering seven days (three previous, the current day and three ahead). A designated laptop downloads a new file every hour. Their procedure requires that laptop to stay powered and be hard-wired to the internet. An IT business systems specialist audits it weekly to confirm it’s working. At the one-hour mark of an outage, the nurse supervisor begins printing and distributing the backup reports.

Three details in there are worth stealing:

  • The backup computer is designated and wired. A backup laptop on Wi-Fi, on a power strip under a desk, fails in exactly the outages you’re planning for: power, network and ransomware.
  • Someone checks it on a schedule. A backup that silently stopped downloading three weeks ago is worse than none, because staff will trust it.
  • Printing starts at a fixed time. Not when someone remembers.

Fill in:

  • Backup computer location(s): ______ On backup power? Y/N. Wired? Y/N.
  • Who verifies the newest backup file, and how often: ______
  • Printer it uses (also on backup power): ______
  • When printing starts: ______

Our free downtime readiness check walks through these items for your building.

5. The paper kit on every unit

List the forms and keep them where the work happens. Health PEI keeps a binder of PCC downtime forms on each household: a nurse progress note, a resident care flowsheet, a vital signs record and a neuro vital signs record, with resident labels attached before use. They also require at least 1,000 sheets of letter paper on hand at all times, a reminder that an extended outage runs on printed pages.

Fill in:

  • Forms in each unit’s kit: ______ (MAR/TAR printouts come from section 4)
  • Admission, discharge and transfer form for residents moving during downtime: ______
  • Kit location on each unit: __ Who restocks it after use: ____
  • Paper and toner reserve: ______

6. Communication during the outage

Staff on other units need to hear the same thing at the same time. Health PEI uses a fan-out call to every household at the start (“downtime procedures begin if this lasts two hours”) and a second call when paper documentation is in effect.

Don’t forget the people outside the building who depend on the EHR: your pharmacy, your lab, the hospital you transfer to, and on-call physicians. 42 CFR 483.73 also requires a method for sharing resident information and medical documentation with other providers to maintain continuity of care. Decide now how you’ll do that with the EHR down.

Fill in:

  • Internal notification method and script: ______
  • Outside parties to notify (pharmacy, lab, physicians, transfer hospital): ______
  • How resident information goes out with a transfer during downtime: ______

7. Recovery: getting paper back into the EHR

The outage isn’t over when the screen comes back. Decide in advance:

  • Who enters the paper documentation. Health PEI has the original documenter transcribe their own entries and does not recommend having someone else enter them.
  • Scan or transcribe. Health PEI says staff “must not scan the downtime record” and should transcribe it, then shred paper only after entry is complete and verified. For an outage that crossed a shift change, their procedure keeps the paper as part of the permanent record instead. Your health information and compliance leads should make this call, and write it down.
  • Medication reconciliation. Compare paper MARs and any new orders taken during downtime against the live record before the next med pass.
  • Timestamps. Entries made after the fact need the time care was actually given, entered carefully.

Fill in:

  • Who transcribes: __ Deadline: ____
  • Scan, transcribe, or keep paper as permanent record: ______
  • Who reconciles medications and orders: ______

8. Log it, review it, and count it

Record the start and end time, the cause, how long it took to go to paper and whether the backup reports worked. Health PEI requires the supervisor to report start and end times to a central office that logs every downtime.

Then hold a short review and fix what broke. That review matters for compliance too: 42 CFR 483.73 requires exercises at least twice a year, and a facility that has an actual emergency requiring activation of its emergency plan is exempt from its next required full-scale or facility-based functional exercise. Whether a given outage qualifies is a question for your emergency preparedness lead, but you can only make the case if the event was documented.

Fill in:

  • Downtime log kept by: ______
  • After-action review within ___ days, attended by: ______

Where these plans usually break

Having a template doesn’t make the plan work. These are the weak points worth testing first:

  • The plan assumes the person who wrote it is on duty. Run your next drill on nights or a weekend.
  • The contact list is stored in the system that’s down. Phone numbers for IT, PointClickCare support and your pharmacy belong on paper at every nurses’ station.
  • The backup computer shares the same failure. If it’s on the same network segment, the same domain login and the same power circuit as everything else, a ransomware attack or power loss takes it out too. Our post on how ransomware hits a nursing home shows how long “down” can last.
  • Nobody owns the restock. The kit gets used once and never refilled.
  • The procedure was never tested end to end. Printing the backup, using the forms and entering them back are three separate skills. A tabletop discussion doesn’t test any of them.

The IT side of downtime readiness

Clinical leaders own the decisions in this template. Your IT provider owns making them possible: a backup computer that is powered, wired and monitored, a second internet path that fails over on its own, Wi-Fi that reaches every med cart, and a recovery plan for when the outage is a cyberattack rather than a vendor blip. The same items show up in a HIPAA risk analysis, so it’s worth doing both together. See our HIPAA risk assessment for nursing homes and how we approach IT for skilled nursing facilities.

If you’d like a second set of eyes on your downtime procedures before your next drill, or before your next survey, talk to RDE Technologies. We can walk through the IT pieces behind each section of this template with you.

Frequently asked questions

How long should a nursing home wait before going to paper during an EHR outage?

Set a specific threshold in writing, tied to your med pass schedule, and let the supervisor on duty apply it without calling anyone. One published long-term care procedure uses two hours within a single shift. The right number for your building is a clinical decision for your DON and medical director.

Who should declare EHR downtime in a skilled nursing facility?

A role that exists on every shift, usually the RN supervisor on duty, with a named backup. The procedure should work for an agency nurse who has never seen it before.

Do CMS rules require EHR downtime procedures for nursing homes?

CMS doesn’t use the phrase “downtime procedures,” but 42 CFR 483.73 requires LTC facilities to have a system of medical documentation that preserves resident information and keeps records available during emergencies, an all-hazards risk assessment, annual plan review and twice-yearly exercises. Written EHR downtime procedures are a practical way to meet the documentation piece for an IT outage.

Should paper downtime records be scanned into the EHR?

Decide this in advance with your health information and compliance leads. Some long-term care systems require staff to transcribe paper entries into the EHR rather than scan them, and keep paper as the permanent record only in specific cases, such as an outage that crossed a shift change.

Can a real EHR outage count toward emergency preparedness exercises?

Under 42 CFR 483.73, an actual emergency that requires activation of the emergency plan exempts the facility from its next required full-scale or facility-based functional exercise. Document the event and your response either way, and confirm with your emergency preparedness lead whether it qualifies.

Share this article

Share on Facebook
Share on Twitter
Share on Linkdin
Share on Pinterest

Leave a comment

Find out what your IT really needs.

A free assessment of your network, backups and security, with a written report of what we found. No obligation.