Keep Therapy Sessions Moving During Atlanta EHR Outages
When the internet or EHR goes down, keep the session moving only within a documented downtime process: confirm what is unavailable, use an approved method to record essential session information, protect those records, and reconcile them into the EHR after service returns. Assign decision owners and test the workflow before an outage, not while families and staff are waiting.
In This Article
- What should our clinic do first when the EHR or internet stops working?
- Can therapy continue if staff cannot document in the EHR?
- How do we keep downtime records private and secure?
- How should we restore the EHR workflow and reconcile session notes?
- How can an Atlanta therapy clinic prepare before the next outage?
- Frequently Asked Questions
What should our clinic do first when the EHR or internet stops working?

“John brought the right knowledge to my issue and resolved it in about a reasonable amount of time. I walked away confident the problem was actually fixed.”
Start by identifying the boundary of the outage. Is one tablet disconnected, is the clinic network unavailable, or can staff reach the internet but not the EHR? Check another approved device or connection and confirm whether the EHR vendor has reported a service issue. Avoid repeated sign-ins or improvised workarounds that could create duplicate entries or expose patient information.
Give staff one clear status update and name the person coordinating the response. That person should record when the interruption began, which locations or workflows are affected, and who has been contacted. A clinic director or designated supervisor can then make the operational call about whether a session can proceed under the clinic's approved downtime procedure.
For a multi-site practice across Metro Atlanta, make sure a local issue at one clinic does not get confused with a system-wide outage. Staff at another site may have different connectivity or access. Confirm the status separately rather than assuming every location is affected in the same way.
Three outage conditions to plan for: device or Wi-Fi trouble, clinic internet loss, and EHR service unavailability.
Takeaway: Identify what has failed before choosing a workaround.
Can therapy continue if staff cannot document in the EHR?
That depends on the clinic's clinical, operational, payer, and documentation requirements. The technology plan cannot decide whether a particular service should proceed. Define in advance who has authority to make that call, what information staff must capture, and what circumstances require pausing or changing the schedule.
Prepare a downtime form or other clinic-approved record that captures only the information needed to reconstruct the session and complete required documentation. Specify which fields are essential, who completes the record, and where it is stored. Do not assume that a blank paper form, personal device, or consumer note-taking app is an acceptable substitute.
Staff should be able to distinguish a temporary working record from the final EHR entry. Mark the record as created during downtime, include the session date and relevant identifiers using clinic policy, and note any follow-up still required. Avoid creating a second record in the EHR until the designated person has checked whether a partial or delayed entry already exists.
For ABA teams, the procedure should address what an RBT does if a tablet disconnects during a session, including how to preserve the session details and notify a supervisor. The process should work for clinic-based sessions and any approved in-home workflow. It should not depend on an individual staff member remembering an unwritten exception.
Takeaway: A downtime record is a controlled bridge to the official record, not a replacement for it.
How do we keep downtime records private and secure?
Decide before an outage whether the approved fallback is paper, a managed offline function, or another clinic-authorized method. Set access limits, storage rules, and a handoff process. If paper is authorized, keep forms under staff control and place completed records in a designated secure location. If an offline digital method is approved, document which devices and accounts may be used.
Do not send patient information through personal email, consumer messaging, or an unapproved cloud account just because the usual system is unavailable. A fallback should preserve access controls and the minimum-necessary approach as far as the approved workflow requires. If staff are unsure whether a method is permitted, the escalation instructions should tell them whom to contact rather than inviting improvisation.
HIPAA requirements do not change because an outage happens in Atlanta. A practice should review its downtime process against its own HIPAA Privacy Rule and Security Rule responsibilities, contracts, and risk analysis. Georgia breach-notification obligations may also apply if protected personal information is compromised; confirm applicability and deadlines with qualified counsel.
Limit temporary records to the period they are needed, then reconcile, retain, or securely dispose of them under the clinic's records policy. The owner should document what happened to each record, not simply assume it was scanned or entered later.
Takeaway: Make the fallback method part of the privacy and security process.
How should we restore the EHR workflow and reconcile session notes?
When connectivity or the EHR returns, do not treat the green status light as proof that every task is complete. Confirm that the affected users can reach the right system, verify whether delayed entries or synchronization are pending, and check for duplicate or incomplete records. If the EHR vendor provides recovery instructions, follow the applicable guidance and keep the clinic's process owner informed.
Assign reconciliation to a defined role. That person should compare the downtime records with the EHR, enter or complete the required information through the approved workflow, and mark each item as reconciled. A second review may be appropriate under the clinic's own policy for certain records. Keep the original temporary record protected until the required reconciliation and retention steps are complete.
Track operational items beyond the note itself. A disruption may affect scheduling, authorizations, secure messaging, or coordination with a referral partner. Record which work was delayed and who owns the follow-up, without putting unnecessary patient information in general outage communications.
A customer review offers a modest example of why clear ownership and follow-through matter. Madhav Naik, in professional services, said John brought the right knowledge to his issue, resolved it in about a reasonable amount of time, and left him confident the problem was actually fixed. That is a review of a technology issue, not a claim about EHR recovery, but the principle applies: close the loop and make the outcome clear.
For a broader look at testing connectivity failover before a carrier problem, see the Built, Wired & Secured article on validating network failover. A secondary connection should be evaluated against the actual clinic workflow, not assumed to work because equipment reports that it is available.
Takeaway: Recovery is complete when records and follow-up work are reconciled, not merely when service returns.
How can an Atlanta therapy clinic prepare before the next outage?
Write a short plan staff can use under pressure. Include the outage coordinator, clinical decision owner, IT or vendor contacts, approved documentation method, communication channel, and reconciliation owner. Record how to reach those people if the clinic internet is unavailable. For a practice with multiple sites, clarify whether each location follows the same process and how local status is reported.
- Map the dependencies for the workday, including internet service, Wi-Fi, staff devices, identity and sign-in, the EHR, and any connected scheduling or communication tools.
- Ask the EHR provider what offline functions, recovery steps, and support channels are available under your agreement. Keep vendor instructions with the clinic's downtime materials.
- Define the clinical and operational decision path. Technology staff can report system status, while authorized clinic leadership determines what service can continue.
- Walk through a realistic scenario with staff. For example, have a tablet lose Wi-Fi during a session and practice the notification, approved recordkeeping, and reconciliation steps.
- After a test or real outage, document what worked, what was unclear, and who will update the procedure. Recheck the plan when systems, staffing, or locations change.
Atlanta-area practices may operate from a single office or coordinate work across the Perimeter, North Fulton, Gwinnett, or other parts of Greater Atlanta. The useful planning question is not how many locations you have; it is whether the person at each location knows what to do and whom to contact when the normal workflow stops.
GDS Technology describes its approach as technology ownership rather than ticket-by-ticket support, and positions itself as one accountable partner across connected systems. For medical offices, IT support for medical offices should connect infrastructure and security decisions to the work staff need to complete. A clinic can also review HIPAA-focused IT compliance support, disaster recovery planning, and data backup and recovery services as related planning areas.
Takeaway: A useful plan gives every role a next step and gets exercised before it is needed.
A few questions to ask about your own setup:
- Can staff access the outage procedure without internet?
- Where are session notes recorded if the EHR is unavailable?
- Who decides when it is safe to resume normal workflows?
If you're weighing how your practice would handle an outage, you can get in touch with our team to talk through your setup and the questions you'd want answered.
Frequently Asked Questions
Should therapy sessions continue during an EHR outage?
That is a clinical and operational decision for authorized clinic leadership, based on the service, documentation requirements, available safeguards, and the clinic's approved downtime procedure. IT can confirm which systems are affected and explain recovery options, but it should not decide whether a particular session may proceed. Define the decision owner and escalation path in advance.
What should an RBT do if a tablet disconnects during a session?
Follow the clinic's approved downtime instructions: notify the designated supervisor, use only an authorized method to record required session information, and keep temporary records protected. Do not move patient details to personal email or an unapproved app. The clinic should specify how to identify the record, where it is stored, and who reconciles it when service returns.
Can staff use paper notes if the EHR is unavailable?
Only if the clinic has approved paper records as part of its downtime process. That process should define the required fields, who may access completed forms, where they are secured, and how information is reconciled with the EHR. Staff should not assume that paper is automatically an acceptable or complete substitute for the clinic's documentation requirements.
How do we know when EHR outage recovery is complete?
Confirm that affected users can access the required workflows, check for delayed or partial entries, and reconcile each temporary record according to clinic policy. Also assign follow-up for scheduling, authorizations, or communications that were interrupted. A restored login is one useful signal, but it does not by itself confirm that the records and operational work are complete.
Follow GDS Technology on Facebook, and subscribe on YouTube for new videos.