ABA practice telehealth requirements in Connecticut begin with a Connecticut-licensed behavior analyst acting within scope and the in-person standard. Section 19a-906 requires appropriate technology, access to history and records, the provider's license and contact information, an explanation of telehealth limits, documented consent, a primary-care record-sharing choice and HIPAA compliance. HUSKY payment is narrower: the code must appear on the current CMAP Telehealth Table and still meet enrollment, clinical, authorization and claim rules.

Ask where both people are before care begins

A Connecticut telehealth visit still happens in two physical places. Confirm the client's and clinician's live locations at the beginning of every encounter. A Hartford address in the chart does not establish that a family is home, and a clinician associated with a Connecticut office may be connecting from another jurisdiction.

Explain that the question protects everyone. Location affects licensure, payer enrollment, emergency routing and the authority that governs the service. If either answer is unexpected, pause the clinical work and route the facts to a qualified reviewer. Do not ask staff to make a multistate licensing decision from memory while the family waits.

Use an active Connecticut license as the ordinary route

Connecticut DPH licensing requirements tie behavior analyst licensure to current BCBA certification, while the practice act defines the regulated practice and licensure routes. Connecticut's 2026 telehealth statute recognizes title 20 licensees acting within professional scope. That makes the state license, not a video platform account, the starting point.

An earlier out-of-state registration pathway in section 19a-906 was expressly time-limited through June 30, 2025. Do not treat an old registration, temporary emergency arrangement or national credential as current 2026 authority. Maintain the Connecticut license, credential, role, employer, client assignment, supervision, payer enrollment and effective dates for every person who may render or direct remote care.

Meet the same professional standard through technology

Connecticut General Statutes 19a-906 requires the standard of care applicable to the profession and expected for in-person care, adjusted for the patient's age and presenting condition. It also requires access to or knowledge of the patient's medical history and health record, including primary-care information when known.

Translate that into a service-specific decision. Can the clinician see the relevant behavior and environment, communicate effectively, guide the caregiver and respond safely? A focused caregiver consultation may fit video, while a complex assessment may need views the family cannot reasonably provide. Record what information supported the decision and what limitation led to an in-person recommendation.

Give the family the required professional information

Section 19a-906 requires the telehealth provider to give the patient the provider's license number and contact information. This is more than footer text. Families should be able to identify who is responsible for care and how to reach the practice after a connection failure or a question about the plan.

Include the rendering professional's name, credential, Connecticut license number and a monitored contact route in the orientation and patient-facing materials. When a supervisor and technician both participate, explain their roles rather than presenting the screen name of the organization as the clinician. Keep the information current when assignments change.

Turn Connecticut consent into a real conversation

At the first telehealth interaction, the provider must explain treatment methods and the limitations of using the platform, obtain consent and document both notice and consent. A later revocation must also be documented. Consent may come from the patient or an authorized guardian, conservator or representative as applicable.

Discuss what the clinician intends to do, who may join, what the family may be asked to show or practice, privacy choices, technology limits, likely cost and the in-person alternative. Separate treatment consent, telehealth consent, information release and recording permission. A family can revoke telehealth participation without erasing prior valid care or waiving the practice's obligation to arrange appropriate continuity.

Ask the separate primary-care sharing question

Connecticut requires the provider at the initial telehealth interaction to ask whether the patient consents to disclosure of telehealth records to the primary-care provider. If the patient agrees, the records of telehealth interactions must be provided in a timely manner under the applicable record provisions.

Build this as its own decision rather than burying it inside a broad release. Record the answer, the named primary-care provider when known, the scope of consent and the transmission. If the family declines, do not treat that as refusal of telehealth. Clinical coordination may still be discussed through an appropriate, consented route.

Separate general modality permission from CMAP payment

The 2026 statute's definition can include synchronous interactions, store-and-forward and remote monitoring, and it no longer excludes audio-only telephone from the definition. That broad professional framework does not make every ABA activity or telephone call payable.

The CMAP Telehealth Information page states that only procedure codes on the current Telehealth Table may be paid remotely and that the table identifies when audio-video or specified audio-only service is allowed. Check the live table, service policy and date before scheduling and again before claim release. If the code is absent, CMAP says it is not eligible for telehealth payment.

Use the autism policy as a foundation, not a frozen answer

Connecticut's DSS autism-service policy addresses members under 21, medical necessity, behavioral assessment, individualized plans, provider enrollment, supervision, prior authorization, records and a general face-to-face expectation unless DSS specifically authorizes otherwise in writing. Some of that framework predates newer telehealth law and current CMAP tables.

Read the sources together. The underlying ASD policy defines the benefit and provider responsibilities; the live telehealth table and bulletins identify current remote payment routes. A newer general telehealth statute does not silently rewrite an older service limitation, and an older face-to-face sentence should not be used to ignore current written authorization. Preserve the date and hierarchy of each source.

Check coverage and cost before the visit

Section 19a-906 requires a provider to determine whether the patient has health coverage and whether the patient elects to use it or pay directly. Before care for someone paying directly in whole or in part, the provider must disclose the cost under the statute's terms.

Give families an understandable estimate and say what remains uncertain. Confirm HUSKY eligibility, managed benefit arrangements, authorization and other insurance rather than assuming a familiar plan is unchanged. Cost disclosure is not a promise of payer payment, and a family choosing self-pay does not waive licensure, clinical, privacy or record obligations.

Make modality failure a clinical decision

A supported video encounter can quickly become an ordinary phone call when bandwidth drops. The general statute may recognize audio-only telehealth, but CMAP service eligibility and the clinician's ability to perform the work remain separate. Do not let the calendar choose the fallback.

Decide whether a meaningful, permitted activity can continue, whether the call is nonbillable coordination or whether the service should be rescheduled. Record when the modality changed and what the clinician could still observe or accomplish. The claim must reflect the actual encounter and the current table, not the format that was planned.

Protect records and the surrounding workflow

Connecticut expressly requires telehealth services and related records to comply with HIPAA. HHS privacy guidance helps owners examine invitations, devices, chat, screen sharing, recordings, support tickets, exports, notes and claims, not just the encrypted video session. Confirm vendor terms, permissions, retention and incident response.

Ask who can hear at both locations and give the family time to adjust. Headphones, a different room, a shorter conversation or a reschedule may be appropriate. Document a material privacy limitation and the response without turning an ordinary household scene into unnecessary clinical detail.

Design remote care for effective participation

A technically connected visit may still exclude someone. Federal telehealth access guidance addresses effective communication, disability access and language assistance. Captions, interpreters, screen-reader support, visual schedules, sensory changes, simplified instructions, a larger device or slower pacing can be essential.

Ask about needs before the first appointment and test the real workflow. Explain the role of interpreters and support people and include them in consent and privacy planning. When the remote format cannot be made effective for the service, offer an appropriate alternative rather than treating the family's device or communication needs as noncompliance.

Keep supervision observable and within scope

Connecticut's practice act preserves the distinction between a licensed behavior analyst and an assistant working under supervision. The BACB Ethics Code adds certification-based expectations for competence, delegation, supervision, records and continuity. Remote presence does not expand anyone's scope.

Plan what the supervisor must observe, how feedback reaches the implementer and which client-specific risks require an in-person view. Distinguish clinical supervision, employer oversight and any separately billable service. Document the actual observation and direction. A supervisor's name in the platform participant list cannot stand in for evidence that meaningful supervision occurred.

Prepare a Connecticut continuity route

Before the encounter, confirm the client's location, callback number and responsible adult or support person expected when clinically appropriate. Know the local resources identified by the care plan. Decide what happens if the connection fails, privacy disappears, the participant leaves or risk exceeds what the clinician can assess.

Most disruptions need reconnection or a new appointment, not emergency dispatch. Still, families should know how to reach the practice and when an in-person option will be offered. Name who makes the clinical decision and who follows up. A generic 911 instruction is not a complete continuity plan.

Make the note and CMAP claim tell the same story

A useful record identifies the client, rendering professional and role, participants, both live locations, modality, consent and primary-care sharing decisions, purpose, clinical rationale, observations, material limitations, interventions and follow-up. It should also show access accommodations and any transition to in-person care.

Reconcile the claim with the live CMAP Telehealth Table, provider enrollment, authorization, code, rendering affiliation, modifier and place of service. The January 2026 CMAP bulletin tells providers to keep using the telehealth page and its current table. A correctly formatted claim cannot cure an absent code, unsupported professional, inadequate service or missing consent.

A fictional Connecticut case shows why the live table matters

Soundview Behavior Partners is fictional. A Connecticut LBA provides remote caregiver guidance using a code that appeared on an internal spreadsheet copied months earlier. The family consents, the visit is clinically useful and the note is complete. The billing team later discovers that the current CMAP Telehealth Table does not list that code for the date of service.

The practice stops future remote scheduling for the code, preserves the old table, live table, authorization, note and claim and asks qualified payer and compliance reviewers for a date-specific decision. It does not change the note or assume that good care guarantees payment. The review separates professional authority, clinical quality, benefit, code eligibility and claim facts.

Pilot a Connecticut workflow that families can follow

Begin with a narrow group of services supported by licensure, clinical review, authorization and the live payer table. Rehearse locations, license disclosure, consent, primary-care choice, coverage and cost, access, privacy, modality failure, in-person referral, notes and claims. Ask families what felt clear and what felt overly technical.

That is the practical answer to ABA practice telehealth requirements in Connecticut: the visit should be lawful, clinically useful, understandable and payable only when current written rules support it. Invite a Connecticut LBA, a DPH-aware adviser, current CMAP operations, family and clinical perspectives, privacy and accessibility specialists, an owner-operator and qualified counsel to review the page before publication, with every policy date in view.

Related resources

Sources