To configure Louisiana Medicaid ABA telehealth and MCO controls, identify the member's current health plan and the plan policy governing the exact ABA service. Verify provider role, synchronous audiovisual delivery, prior authorization, member and practitioner locations, clinical appropriateness, documentation, modifier 95, place of service 02 or 10, and claim receiver. Plan manuals can differ, so one MCO's rule cannot release another MCO's service.

Define a Louisiana telehealth release

Berengar 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 Louisiana Medicaid ABA authority

Louisiana Medicaid's services page routes providers to the state ABA manual, fee schedule, prior-authorization resources, and current health-plan information. The provider-manual page explains that service chapters supply provider qualifications, coverage, limitations, records, and reimbursement. Berengar records the state rule and plan implementation separately.

Separate program coverage from payer routing

The ABA FAQ routes members through their managed care organization, while the MCO resources page publishes current plan and state oversight material. Plan guidance may support family adaptive behavior treatment guidance or remote supervision under defined roles, synchronous audiovisual interaction, modifier 95, and POS 02 or 10. Berengar confirms those details in the responsible plan's current source before use.

Keep a source decision log

Berengar 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

Berengar requires current member and MCO; current state and plan service support; enrolled, credentialed and qualified provider; correct delivering and supervising roles; synchronous audiovisual modality; both physical locations; choice; consent and assent when applicable; clinical fit; PA; communication access; complete note; modifier 95; POS 02 or 10 based on member location; claim receiver; 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

Berengar 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

Berengar 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

Berengar 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. Berengar 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

Berengar 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

Berengar 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

Berengar 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 Berengar's fictional cohort

Berengar locks 22 fictional Baton Rouge sessions across three plans. Fourteen initially contain the state source, current plan rule, provider role, synchronous modality, both locations, clinical decision, PA, access, note, modifier, POS, receiver, and response plan. Two use another plan's manual, one is audio only, one uses POS 02 for a member at home, two PAs name in-person care, one note lacks practitioner location, and one supervisor relationship is stale. 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 Berengar's measures

Louisiana ABA telehealth readiness is 14 of 22, or 63.6%. Twenty sessions reach release or accountable hold, or 20 of 22, or 90.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 Louisiana failure mode

A plan manual supplies plan evidence rather than a statewide clinical or payment guarantee. Berengar stores plan, product, policy version, service, provider role, PA, modifier, POS, and receiver together. A plan migration or April 2026 plan-market change triggers reverification for every open authorization.

Test Berengar's controls

Berengar tests three MCOs, plan migration, family guidance, remote supervision, audio-only request, POS 02, POS 10, stale supervision, in-person PA, incomplete note, and wrong receiver. 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

Berengar 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 Louisiana ABA telehealth MCO and claim register

Berengar 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 Louisiana page remains draft and noindex until every named expert review finishes.

Related resources

Sources