To configure Montana Medicaid ABA telehealth exception controls, obtain approval on the current ABA Telehealth Exception Request before delivering the remote service. Document why telehealth is medically necessary, the member characteristics that support it, clinical appropriateness, provider licensure and enrollment, locations, modality, authorization, and monitoring. Face-to-face care remains preferred, and the exception should match the exact member, professional, period, and service plan.

Define a Montana telehealth release

Havelock treats telehealth as a service-date configuration. One row identifies the member, program or plan, service, billing and rendering providers, supervisor when applicable, both physical locations, modality, authorization, clinical decision, access supports, platform, note, claim rule, and emergency plan. Any controlling change creates a new version.

Read the current Montana Medicaid ABA authority

Montana Medicaid's ABA services page links current manuals, fee schedules, forms, and the Telehealth Exception Request. The current exception form requires advance approval and asks for the specific reason, medical necessity, member characteristics, BCBA identity, NPI, license, start date, safety, technology, privacy, caregivers, outcome monitoring, and in-person plan.

Separate program coverage from payer routing

The ABA manual controls service, provider, medical-necessity, authorization, and billing requirements. Montana's post-emergency notice says the ABA telehealth exception continued after May 2023, with face-to-face delivery preferred and telehealth substituted when clinically appropriate. Havelock verifies that the current form and manual still govern each service date.

Keep a source decision log

Havelock records the source title, publisher, URL, publication and effective dates, checked date, service and provider scope, supersession state, question answered, and unresolved question. A later bulletin can replace one paragraph without replacing the whole manual. The log shows the exact rule used for each session and claim.

Use one release gate for every required fact

Havelock requires current member eligibility and service plan; approved telehealth exception matching member, BCBA, period and service; qualified, licensed and enrolled provider; clinical rationale and outcome-monitoring plan; both locations; synchronous platform when required; choice; consent and assent when applicable; access; underlying ABA authorization; complete note; claim setup; and in-person fallback and emergency plan. A failed gate holds the session or claim at the affected point. The register shows its source, owner, checked time, effective period, exception route, and next action. Clinical, legal, payer, technical, and claim facts retain separate owners and evidence.

Keep clinical decisions with qualified clinicians

Havelock routes case-specific modality, risk, treatment, supervision, and clinical-fit decisions to an appropriately qualified clinician. Operations verifies evidence, coordinates scheduling, and surfaces conflicts. Software checks fields and deadlines. A payer coverage action remains distinct from the treating clinician's recommendation.

Verify both locations for every encounter

Havelock asks for the member's physical location at check-in and records the practitioner's physical location from the responsible professional. Those facts drive licensure, payer, emergency, privacy, and place-of-service analysis. Profiles and prior visits serve as reference data rather than the current encounter record.

Preserve choice, consent, assent, and communication

Havelock gives the person an understandable modality choice when the governing source allows it and records required consent from the legally authorized person. Assent is monitored when applicable. Speech, AAC, sign, gesture, writing, interpreters, captions, and other effective forms remain available. The person has an accessible way to request a pause or another supported setting.

Decide whether remote delivery fits

A qualified clinician reviews purpose, response forms, observation needs, prompting, caregiver role, safety, privacy, environment, technology, fatigue, and alternatives. Havelock identifies which components need direct observation or in-person care and when to switch. Staffing pressure, distance, or payer approval supplies no clinical-fit conclusion.

Build technical and emergency readiness

Havelock tests the approved platform, audio, video when required, device power, bandwidth, camera view, communication system, backup contact, privacy, and outage route. The record names the person's physical location, local emergency contact, responsible adult when applicable, nearest response route, and stop condition. Staff pause when connection quality prevents safe or meaningful care.

Match authorization and documentation

Havelock compares the authorized service, provider, setting, modality, dates, units, and conditions with the planned encounter. The note records actual locations, modality, start and stop time when required, participants, accessible communication, interventions, responses, interruptions, supervision, and clinically relevant outcome. The record describes the delivered session.

Release the claim from completed evidence

Havelock derives code, units, modifier, place of service, rendering and billing identities, location, authorization reference, and payer route from verified records and current instructions. A telehealth flag supplies one field, while completed source evidence supports the configuration. Claim acceptance, adjudication, remittance, and payment remain later states.

Work through Havelock's fictional cohort

Havelock locks 18 fictional Billings sessions. Ten initially contain a current approved exception, provider and license evidence, clinical rationale, both locations, technology, access, authorization, monitoring, note, claim setup, and fallback. One begins before approval, one uses another BCBA's exception, one exception expired, two lack medical-necessity detail, one note omits location, and two lack a workable in-person plan. Six repair. Two remain held. The example is synthetic. It tests release and denominator logic and establishes no coverage, authorization, clinical, legal, privacy, licensure, claim, or payment conclusion for a real person or practice.

Calculate Havelock's measures

Montana ABA telehealth readiness is 10 of 18, or 55.6%. Sixteen sessions reach release or accountable hold, or 16 of 18, or 88.9%. Report holds by coverage, authority, location, choice, consent, assent, access, clinical fit, technology, authorization, documentation, claim, and emergency reason. Preserve counts beside percentages and age every unresolved item from its defined start event. Every failed or pending item remains visible in its declared cohort.

Address the main Montana failure mode

The exception is member, professional, service, and time specific. Havelock blocks copied approvals and links every session to the approved request version. A submitted request, historical approval, general telehealth policy, or fee-schedule row cannot substitute for current advance approval.

Test Havelock's controls

Havelock tests initial request, renewal, preapproval date, expired exception, different BCBA, changed service, medical-necessity rationale, in-person fallback, outcome monitoring, location change, outage, and claim rejection. Each scenario records the starting facts, expected action, source, observed result, owner, correction, retest, and disposition. A successful connection proves technical access for that test. Coverage, clinical fit, authorization, documentation, and payment need their own acceptance evidence.

Run independent acceptance

Havelock gives an independent reviewer the locked cohort, sources, locations, provider records, authorizations, clinical decisions, access plans, consent and assent evidence, platform results, notes, claims, and payer responses. The reviewer reproduces one release and one hold. A changed cohort, hidden failure, unsupported rule, or unexplained calculation fails acceptance.

Maintain the Montana Medicaid ABA telehealth exception and claim register

Havelock reviews sources monthly and after program, plan, law, rule, manual, code, modifier, place-of-service, form, platform, authorization, contract, or contact changes. Each source keeps an owner, effective and checked dates, scope, supersession state, and next review. This Montana page remains draft and noindex until every named expert review finishes.

Related resources

Sources