What to Do When Technology Fails During Telehealth ABA

Identify the failure precisely

State whether the problem affects audio, video, captions, interpreter access, AAC, screen sharing, login, power, internet, device charging, privacy, or the platform itself. Note whether one participant or everyone is affected.

Avoid repeated random troubleshooting while the child waits. Use the agreed sequence and tell the clinician what the family can still see, hear, and communicate.

Protect communication and safety first

Keep the child's AAC or backup communication available. The ASHA AAC portal supports continuous access to AAC tools or devices.

Move away from an unsafe device, exposed cord, overheated battery, or lost-private-space situation. Keep water, bathroom access, mobility, and emergency help available. The responsible clinician decides whether clinical work can continue within scope after conditions are restored.

Use the approved backup route

The provider may use a reconnect, phone call, another approved platform, reschedule, or stop decision. Ask in advance which route applies to each failure and whether the backup supports the planned clinical activity.

HHS telehealth privacy and security guidance provides general tips. A convenient consumer app may still fall outside the provider's approved workflow.

Preserve accessibility during recovery

The joint HHS and DOJ telehealth nondiscrimination guidance discusses disability access and language assistance under the authorities it covers. A phone-only fallback may fail when the person needs captions, visual information, an interpreter, accessible controls, or another aid.

Ask whether the backup is effective for the child and family before proceeding. Record the access problem and owner when a repair requires later work.

Separate technical recovery from clinical completion

A reconnected screen shows technical availability. The team still needs the correct people, locations, privacy, communication, clinical information, time, and authority for the service.

Ask whether the visit was completed, shortened, converted, held, or rescheduled. Confirm how time and documentation are handled under the provider's and payer's current rules.

A fictional outage record

Eli's family is fictional. During eight telehealth visits, two have technology failures. One reconnects within five minutes with AAC and captions restored. One loses caption access and ends. Technical recovery is 1 of 2 events, or 50%.

The family reports both events and keeps the ended visit in the operational record. The ratio describes those two failures and cannot estimate future reliability or clinical quality.

Follow up on recurring problems

Track the failure type, duration, recovery route, access impact, visit outcome, and responsible owner. Repeated problems may require a different device, connection, platform, room, schedule, or care setting review.

When technology fails during telehealth ABA, ask for the final visit state and next step in writing. Keep technical support, clinical decisions, privacy review, scheduling, and payer questions routed to the correct owners.

Keep a one-minute failure card

Write the provider's support number, clinical contact, reconnect link, approved backup route, maximum retry time, privacy response, and stop condition on one card. Add the child's communication backup and the local emergency route. Store the card where the participating adult can reach it without searching through email.

Practice the sequence during a calm test: state the problem, protect communication, try the approved first step, contact the provider, and record the final visit status. Skip any practice step that would create distress, expose private information, or imitate an emergency.

Ask for a post-event answer

After an outage, ask whether clinical information was lost, whether the provider created a partial-session record, and whether the event requires a privacy, security, access, billing, or scheduling review. Confirm who owns each question.

For repeated failures, request a dated corrective plan and a test before the next visit. Compare platform, device, internet, access feature, room, and staff factors. Keep the family informed about the specific repair and the alternative if readiness remains incomplete.

Track failures by component

Use separate categories for home internet, provider platform, clinician connection, family device, power, login, captions, interpreter, AAC, camera, audio, and privacy. Record attempted fixes and the person who confirmed recovery. This prevents one broad “technology issue” label from hiding a recurring access failure or a provider-side outage. Review the oldest unresolved item before the next scheduled telehealth visit.

Ask the provider to tell the family when the incident is closed and what evidence supports closure. If the same component fails again, link the events and review whether the earlier repair held. Keep timestamps for detection, contact, recovery, and final visit disposition so the team can distinguish quick reconnection from a fully resolved access or privacy problem.

Follow a clear failure sequence

First protect immediate safety and communication. Then identify the failed component: power, internet, platform, login, sound, video, captioning, interpretation, device access, camera position, or provider connection. Record the time the failure began, what still works, and whether any sensitive information may have reached the wrong person.

Use the approved help or backup route and wait only for the agreed period. Avoid repeatedly sharing links, passwords, screenshots, or health information through unapproved channels. The family should know who can decide to continue by another method, pause, reschedule, or end the visit.

Decide whether another mode is appropriate

A phone call, audio-only connection, different platform, or later recording may change the service, privacy, accessibility, clinical usefulness, payer treatment, or documentation. Ask the qualified clinician whether the alternate mode can support the planned clinical work and operations whether it is approved and available. Verify payer or other requirements separately when applicable.

Keep the child's location, communication, privacy, and ability to stop in view. A backup that excludes AAC, captions, interpretation, visual information, or required caregiver support may restore a connection while making the service unusable. Record the final mode and which planned activities could not occur.

Protect information during troubleshooting

Use the provider's named support contact. Share the minimum information needed to identify the session and problem. Do not post meeting links or client details in public chats, personal accounts, or screenshots sent to unknown recipients. Confirm identity before allowing remote-control access or installing software.

If the failure may involve an unintended participant, exposed screen, misdirected file, or lost device, tell the provider's privacy or security contact promptly. Preserve facts and avoid deleting logs or messages unless the response owner directs it. The provider decides how the event is classified under its applicable rules.

Reconcile the session record and family account

Ask the provider to record actual connection times, service delivered, participants, interruptions, alternate mode, clinical decision, and follow-up. Keep technical status, clinical completion, attendance, authorization, claim submission, and payment as separate states. A visit can connect briefly without supporting the billed or planned service.

If the family receives a no-show, full-session, or fee record that conflicts with the event, request review with the outage evidence. Preserve the original and corrected versions. A rescheduled visit receives its own record and should not erase the failed event from reliability review.

Review recurring failures by component

For a defined period, count scheduled telehealth visits and mark each component failure, duration, child impact, access impact, recovery, and final outcome. Keep every scheduled visit in the denominator for an overall reliability rate. Use separate denominators when measuring caption, interpreter, or backup performance.

Repeated failures may call for a device, network, platform, training, scheduling, accessibility, or service-setting review. Bring clinical suitability to the clinician and technology patterns to the responsible operations or support team. End with a dated correction plan, owner, test, and decision about the next visit.

Work through an interrupted visit

At 3:12 p.m., a fictional telehealth visit loses audio while video remains. The child uses AAC on a separate device, and the caregiver can still reach the clinician through the approved support number. The family records the failure time, protects communication, and avoids moving to an unapproved personal video account. The clinician decides that the planned activity cannot continue without reliable audio and ends the service portion at 3:18.

Operations opens a technical case and tests the microphone after the clinical visit ends. The provider records six minutes of affected service, the actual end decision, the child's communication, and the follow-up. Billing, authorization, and any rescheduling are reviewed from the actual record rather than the platform's original 60-minute calendar block.

At the next visit, the corrected audio and backup are tested before service. The event remains in reliability reporting even though the problem was fixed. This example separates safe response, clinical completion, technical repair, documentation, and financial processing, which often occur on different timelines.

The family asks for the final disposition in ordinary language: what failed, what was corrected, whether information was exposed, how the clinical record describes the visit, and what will happen if the component fails again. It keeps the case number with the session date. Closing these questions helps the family prepare for the next visit without requiring access to the provider's internal technical details.

Store the one-minute failure card near the approved device and review it after any platform change. Remove obsolete phone numbers or links. A short card is useful only when the family can trust that its contacts and instructions are current.