An ABA telehealth modality switch workflow decides whether one planned visit may move between in-person and telehealth. It verifies the client's and professional's locations, legal and professional authority, clinical appropriateness, consent, privacy, technology, communication access, emergency plan, payer route, staffing, and documentation. The original visit remains held or canceled until the replacement modality passes every applicable gate.
Record both proposed configurations
Keep the original date, service, provider, location, modality, duration, authorization state, and release evidence. Create a proposed replacement row with client and professional location, platform, participants, setting privacy, technology, access supports, emergency route, and requested effective time.
Use a side-by-side configuration record
A switch should expose every field that can change:
| Field | Original | Proposed |
|---|---|---|
| People and roles | Client, staff, supervisor | Reconfirmed participants |
| Location | Client and professional sites | Exact telehealth locations |
| Service | Type, duration, goals in scope | Same or qualified revision |
| Access | AAC, interpreter, sensory support | Tested remote implementation |
| Safety | Site plan and emergency route | Remote location and contact route |
| Payer | Product, authorization, provider, place | Current modality configuration |
| Technology | In-person tools | Platform, device, privacy, backup |
Preserve the original row even after the switch is approved.
Verify location and authority
Telehealth.HHS.gov cross-state licensing guidance says pathways vary by state and advises verifying the patient's location before the appointment. It offers general orientation rather than profession-specific authority. Check current law, board, entity, payer, and professional requirements for both locations.
Verify again at the encounter
Planned location and actual location can differ. Before service, obtain the person's current location through the approved workflow, confirm the professional's location and role, and check that the previously approved authority still applies. Record the emergency address or response information required by policy.
If the person connects from an unapproved jurisdiction or setting, follow the hold, safety, or rescheduling route. Do not ask staff to make an improvised legal determination during the visit. Keep current board, law, payer, and organizational escalation contacts available.
Confirm clinical fit and the person's choice
A qualified clinician decides whether telehealth fits the case and visit within scope. The BACB Ethics Code addresses competence, consent and assent when applicable, client involvement, confidentiality, risk, and documentation for covered behavior analysts.
State why the switch is being considered
Classify weather, facility issue, travel disruption, client request, staff request, exposure concern, continuity, clinical recommendation, or technical contingency. The reason helps identify the required route but does not determine the result. A convenience request still needs the complete configuration review.
Explain the proposed change in a form the person and family can use, including participants, privacy expectations, technology, location, choices, and what happens if the connection fails. Record consent and assent when applicable under the governing process and keep a practical way to pause or end the visit.
Test privacy, technology, and access
Telehealth.HHS.gov describes hybrid care as a mix of in-person and telehealth services and advises discussing which visits fit each route. DOJ effective-communication guidance and ASHA AAC guidance support usable communication and continued AAC access. Test captioning, interpreter, device, connection, backup, and emergency contact routes.
Define failure and fallback states
Use preflight passed, preflight failed, connected, degraded, interrupted, safely paused, converted to approved alternate route, rescheduled, or canceled. State the minimum conditions for service to start and continue. A connected screen does not establish privacy, communication access, clinical suitability, or adequate information for care.
Give staff a response for lost audio, missing video when required, failed captioning, unavailable AAC, privacy interruption, inability to verify location, and emergency concern. Preserve the person's communication method during troubleshooting. Record actual service time separately from connection time.
A fictional switch queue
Clearwater ABA reviews nine same-week modality-switch requests. Six clear location, authority, clinical, consent, privacy, technology, access, emergency, payer, and staffing gates. Two remain in-person, and one is canceled. Telehealth release yield is 6 of 9, or 66.7%; disposition completeness is 9 of 9.
Use both rates for different questions
The 6-of-9 rate answers how many requests became telehealth visits. The 9-of-9 result answers whether every request received a disposition. Neither shows whether the six visits were completed successfully or whether the in-person and canceled outcomes fit the person's needs.
After the visit window, report telehealth completed, interrupted, rescheduled, or canceled; actual service time; access failures; location exceptions; clinical follow-up; and charge holds. Keep the original nine requests as the cohort for switch-outcome reporting.
Reconcile after the visit
Update actual modality, location, participants, service time, technology issues, consent evidence, clinical note, staff time, authorization usage, charge, and claim hold. Track requests, release time, failed gates, completed visits, access problems, technical failures, emergency-plan gaps, and payer rejections.
Review recurring switches as a capacity signal
Segment requests by reason, site, service, staff role, client location, time band, platform, and failed gate. Repeated same-day switches can reveal fragile facility capacity, unrealistic travel, inaccessible technology, or a mismatch between advertised hybrid care and actual readiness. Investigate before assigning cause.
Audit a sample of approved and declined switches against source evidence and the person's experience. Use findings to improve preflight timing, device support, staff training, location verification, emergency planning, and published service promises.
Reconfirm the exact encounter at start time
Before service begins, verify the client's current physical location, the provider's location and authority as applicable, identity, consent or other required participation, privacy, technology, communication access, emergency plan, payer configuration, staff and supervision, and whether the clinical owner still considers the modality appropriate. A prior test or accepted offer cannot establish encounter-time facts.
If the connection fails, location changes, privacy is inadequate, the person cannot use the platform, or another gate becomes uncertain, follow the approved fallback. Options might include troubleshooting within a bounded time, holding, rescheduling, or changing modality only after the required review. Do not continue audio-only, move platforms, or convert to in-person simply because that path is technically available.
Owner modality-switch questions
- Are the original and proposed configurations recorded side by side without overwriting history?
- Did qualified roles verify location, authority, clinical fit, consent, payer, privacy, access, technology, and emergency readiness?
- Can the person choose among complete options through an accessible process?
- Are start-time verification and failure thresholds explicit?
- Do actual modality, duration, service, provider, location, documentation, and claim records reconcile?
- Do recurring switches reveal a capacity, transport, access, or operating problem needing separate action?
Scheduling coordinates the switch; it cannot supply authority or clinical appropriateness.
A start-time failure example
A family accepts a telehealth alternative after an in-person site closes, and every pre-visit gate clears. At start time, the client is in a different state than expected and the provider's authority for that location is not verified. The practice follows the hold and reschedule route, communicates the next step, and records the actual location and failed gate. It does not begin while someone searches for an answer.
In another visit, location and authority are valid but the AAC display cannot be seen reliably on the platform. The clinical and access owners determine that the configured encounter is not workable. The fallback preserves the person's communication tools and choice. Both failures remain evidence for future planning rather than being counted as successful switches because a video link opened.
Related resources
- ABA Schedule Publication and Freeze Calendar
- ABA School Calendar Synchronization Workflow
- ABA Client Availability Change Intake Workflow
- ABA Holiday and Planned Closure Scheduling Workflow
Sources
- Council of Autism Service Providers, Organizational Guidelines public overview
- Behavior Analyst Certification Board, Ethics Code for Behavior Analysts
- Telehealth.HHS.gov, Licensing Across State Lines
- Telehealth.HHS.gov, How Can I Use Hybrid Care?
- U.S. Department of Justice, ADA Requirements for Effective Communication
- American Speech-Language-Hearing Association, Augmentative and Alternative Communication (AAC)
