ABA practice telehealth requirements in Washington DC begin with the client's physical location, the professional's current District authority and clinical fit. District law preserves scope, standard of care, identity, consent, documentation, privacy and security. DC Medicaid's general guidance covers eligible providers and eligible services, but the reviewed materials do not publish a blanket ABA code list. Obtain current written service-code-role-plan approval, authorization and billing evidence before scheduling remote ABA.

Start with the person and place, not the platform

A family rarely experiences telehealth as a policy category; it experiences a visit that either fits daily life or creates another obstacle. Before offering the time, record where the client and professional will be physically located, who will render and bill, the intended activity, payer product and service date. A video link cannot answer authority, benefit eligibility, clinical fit or authorization.

Ask the family about privacy, communication access, technology, support people, safety and preference without making telehealth a condition of receiving care. The question is not whether ABA can occur on a screen in the abstract. It is whether this service, for this client, by this qualified person, from these locations, is permitted and useful today.

Apply the District telehealth law exactly

D.C. Code Section 3-1201.05 allows a health professional licensed, registered or certified under the chapter to provide telehealth within District scope and standard of care when not otherwise prohibited. It permits a relationship to be established remotely when consistent with competence and standard of care and keeps identity, documentation, informed consent, confidentiality, privacy and security rules in place.

Treat the section as a professional-practice framework, not payer coverage. Document the authority, competence and comparable in-person standard. Ask whether an initial in-person evaluation or other profession-specific requirement applies. A service that is legally possible may still be clinically unsuitable, excluded by a benefit or unsupported by an authorization.

Handle out-of-District practitioners cautiously

The telehealth statute generally bars a practitioner without District authority from serving a person physically in the District unless an existing relationship and the stated temporary-presence or 120-day condition applies, subject to subsection details and any compact. That is a narrow route, not a general way to build a remote ABA workforce.

Obtain qualified board and legal review for both physical locations. Track the existing relationship, client status, start and end dates and applicable professional authority. Do not use the 120-day language to onboard a new District family, erase a developing behavior-analyst license requirement or promise payer coverage.

Resolve behavior-analyst implementation first

D.C. Code Section 3-1207.71 creates behavior-analyst license eligibility, while the January 2026 Board minutes show implementing regulations still under review. The reviewed DC Health psychology page does not itself supply a current behavior-analyst application package.

Ask DC Health how the law is implemented for the exact professional before treating the person as District-authorized for telehealth. A BACB credential, submitted application or license in another state does not automatically answer the District question. Preserve the written response, date, facts and any later rule change.

Read Medicaid guidance as a two-part gate

DHCF's January 2023 guidance repeatedly ties reimbursement to eligible providers delivering eligible healthcare services. It requires program enrollment and applicable licensure and describes consent, sites, technology, records, confidentiality and claims. Its broad reference to behavioral healthcare does not identify ABA codes, roles or activities by name.

Require evidence for both halves of the gate. Confirm organization and renderer enrollment, affiliation and plan status. Then confirm that the exact ABA service, code, role, modality, location and date are covered and authorized. The reviewed general guidance does not support turning every Medicaid ABA service into telemedicine.

Keep the ASD benefit conditions in place

The DC Medicaid ASD State Plan supplement describes under-21 ASD screening, diagnosis, treatment planning and treatment including ABA, qualified practitioner classes and prior approval with supporting clinical material every six months. Remote delivery does not remove those ordinary benefit conditions.

Map who assesses, plans, supervises, renders and bills and what the current authorization approves. If a remote activity changes the clinical method, setting, caregiver role, observation or supervision, obtain qualified clinical and payer review. An authorization for ABA is not necessarily an authorization for a remote modality.

Get code-level and plan-level confirmation

DHCF's telemedicine page publishes the general guidance and transmittals, and Transmittal 26-01 says the new 2026 telemedicine E/M codes are not covered while Transmittal 23-11 remains in effect. That current reference reinforces the framework without supplying an ABA-specific code table.

Ask fee-for-service or the MCO in writing about the service code, modifier, place of service, rendering and billing provider types, member setting, authorization and effective date. Save the cited manual or response. A claims edit accepting a test line does not prove clinical coverage, and a prior paid claim does not establish current policy.

Obtain and document meaningful consent

The Medicaid guidance requires written or verbal consent for telemedicine in lieu of in-person care and explains how verbal consent is documented. The professional statute also keeps informed-consent law and standards applicable. Consent should tell the person what telehealth involves, foreseeable limits, privacy choices and alternatives.

Confirm who has legal authority to consent and how assent and participation will be respected. Revisit the choice when the service, platform, participants or setting changes. A checkbox should not hide that the family prefers in-person care, lacks a private room or needs language, disability or technology support.

Treat the member's setting as a clinical fact

DHCF's March 2023 clarification says “home or other settings” may include temporary lodging and certain places chosen for safe access and directs POS 10 for that clarified category. It also says providers must meet technology, consent and covered-service requirements.

That flexibility is not a recommendation to conduct ABA from a car or public park. Ask whether the setting supports privacy, observation, safety, client participation, emergency response and the intended intervention. Record the physical location accurately and develop an in-person or rescheduling option when the environment cannot support care.

Design the remote encounter around the clinical purpose

A caregiver consultation, supervisor observation, assessment component and direct technician service are not interchangeable simply because each can use video. Qualified clinicians should define what information must be observed, who needs to participate, what cannot be assessed remotely and what would trigger an in-person visit.

Avoid copying an office protocol onto a screen. Plan materials, camera position, communication, breaks, reinforcement, caregiver role and a safe ending. The BACB Ethics Code informs certification duties within scope but does not create District authority or payer eligibility. Document the clinical rationale rather than a convenience-only default.

Use technology that can support the service

The DHCF guidance describes two-way real-time communication, technical quality and exclusions for store-and-forward, remote monitoring and incomplete services. It expects technology appropriate to the standard of care and describes specific audio and video performance features. Those details matter when observation or interaction is clinically necessary.

Test the family's actual device and connection, accessibility, audio, camera range and backup contact before the first visit. Train staff on identity, privacy, platform use and interruption. If the connection prevents complete delivery, stop or adapt clinically and follow current documentation and billing rules. Time connected is not automatically a completed payable service.

Document and claim the encounter from current evidence

The Medicaid guidance requires records comparable to in-person care and retention for ten years or until audits are complete, whichever is longer. A useful note identifies participants, physical locations, consent, modality, clinical purpose, service delivered, response, limitations, interruption, support person and follow-up. Record what was actually observed and done rather than pasting a stock paragraph into every note.

The January 2023 guidance describes GT for video-audio, modifier 93 for audio-only and POS 10, 03 or 02 based on the member setting, including an originating-site NPI condition for POS 02. Those instructions apply only when the provider and service are eligible and the current plan has not issued a more specific rule. Reconcile location, renderer, code, units, modifier, POS, authorization and note before release; broad audio-only guidance does not make an ABA activity eligible.

Protect privacy and accessible communication

DHCF calls for a confidentiality compliance plan and encryption safeguards. District law keeps privacy and security standards in force, while HHS and DOJ access guidance addresses effective communication and nondiscrimination within federal scope. A secure platform alone cannot ensure a private, accessible encounter.

Verify identity and who is present, use the least necessary access, disable unneeded recording and plan for interpreters, captions, AAC and other accommodations. Let a family relocate or stop if privacy changes. Do not record for supervision or training unless the authority, consent, security, retention and payer implications are established separately.

Rehearse interruption and emergency fallback

Imagine Eastern Market Behavior Services, a fictional practice, proposes remote caregiver training for one Medicaid member. It obtains current written confirmation for the code, role, modality, authorization and plan, confirms District authority and consent and tests the family's chosen location. The first rehearsal includes a frozen video feed and an unexpected visitor.

The team pauses, confirms privacy, reconnects through the approved route and documents only the service actually completed. A separate rehearsal covers a client leaving view, a caregiver becoming unavailable and an urgent safety concern. This example teaches preparation; it does not establish that the code is covered or that any claim will pay.

Open only a supported remote lane

The practical answer to ABA practice telehealth requirements in Washington DC is an evidence chain for one person-location-service-role-payer-date combination. Professional authority, clinical fit, consent, benefit, code, authorization, technology, documentation, privacy, claim and fallback must all support the same remote encounter.

Before publication or reliance, obtain current review from DC Health, DHCF and the relevant plan, qualified healthcare, Medicaid, telehealth and privacy counsel, BCBA clinical and billing leaders, owner-operators, accessibility specialists and affected families. Recheck the policy whenever the Board issues behavior-analyst rules or a plan changes telehealth instructions. Uncertainty belongs in the decision record, not in a guessed claim.

Related resources

Sources