To configure Wisconsin Medicaid behavioral treatment telehealth controls, route the benefit through ForwardHealth fee-for-service even when the member belongs to a managed care organization. Verify current benefit and prior authorization rules, provider enrollment, service-level telehealth support, clinical fit, locations, accessibility, documentation, and billing. Managed care enrollment alone does not establish the behavioral treatment claim route.
Define a Wisconsin telehealth release
Sylvan treats telehealth as a service-date configuration. One row identifies the member, program or plan, service, billing and rendering providers, supervisor when applicable, member and practitioner locations, modality, authorization, clinical decision, access supports, platform, note, claim rule, and emergency plan. The row receives a new version when any controlling fact changes.
Read the current ForwardHealth behavioral treatment authority
ForwardHealth's current behavioral treatment benefit page says the benefit is carved out of managed care and handled fee-for-service, with prior authorization and claims submitted to ForwardHealth. Sylvan stores that routing fact with its checked date and still verifies member eligibility, provider enrollment, service authorization, and the actual service-date rule.
Separate program coverage from payer routing
The current prior-authorization criteria and provider-enrollment page define separate gates. The resource hub routes providers to benefit material. If the live sources do not state that the exact service, role, and modality may occur remotely, Sylvan obtains current written ForwardHealth support before scheduling or billing.
Use one release gate for every required fact
Sylvan requires current member eligibility; ForwardHealth fee-for-service route; enrolled provider and qualified staff; approved PA matching service, provider, location and modality; current telehealth support; both locations; choice; consent and assent when applicable; clinical fit; access; complete note; claim fields; and emergency plan. A failed gate holds the session or claim at the affected point. The register shows the source, owner, checked time, effective period, exception path, and next action. Clinical, legal, payer, technical, and claim facts retain separate owners and evidence.
Keep clinical decisions with qualified clinicians
Sylvan 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 can check fields and deadlines. A payer coverage action remains separate from the treating clinician's recommendation.
Verify location at every encounter
The member and practitioner locations can change between sessions. Sylvan 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
Sylvan 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 the session can work remotely
A qualified clinician reviews the purpose, response forms, observation needs, prompting, caregiver role, safety, privacy, environment, technology, fatigue, and alternatives. Sylvan 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
Sylvan 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 a connection failure prevents safe or meaningful care.
Match authorization and documentation
Sylvan compares the authorized service, provider, setting, modality, dates, units, and stated 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
Sylvan 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 the completed source record supplies the claim evidence. Claim acceptance, adjudication, remittance, and payment remain later states.
Work through Sylvan's fictional cohort
Sylvan locks 24 fictional Madison sessions for members who also have managed care enrollment. Sixteen initially contain the ForwardHealth carve-out route, provider status, current PA, service support, both locations, clinical decision, access plan, note, claim setup, and emergency route. Two are sent to the MCO, one lacks written telehealth support, two PAs name another setting, one provider affiliation is stale, one note lacks member location, and one backup communication path fails. 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 Sylvan's measures
Wisconsin behavioral treatment telehealth readiness is 16 of 24, or 66.7%. Twenty-two sessions reach release or accountable hold, or 22 of 24, or 91.7%. 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 Wisconsin failure mode
The carve-out can be overlooked when staff start from the member's health plan card. Sylvan makes ForwardHealth the explicit benefit receiver and treats plan enrollment, PA, provider enrollment, telehealth support, and claim acceptance as separate facts. Intake scripts explain the route without promising that ForwardHealth will authorize or pay the service.
Test Sylvan's controls
Sylvan tests managed-care member, ForwardHealth carve-out, current PA, setting mismatch, unsupported telehealth request, stale affiliation, changed member location, incomplete note, failed AAC backup, 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
Sylvan 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 ForwardHealth behavioral treatment telehealth and PA register
Sylvan 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 Wisconsin page remains draft and noindex until every named expert review finishes.
Related resources
- Configure Arizona AHCCCS ABA Telehealth and Coding Controls
- Configure West Virginia Medicaid ABA Telehealth and Claim Controls
- Configure California Medi-Cal BHT Telehealth and Plan Controls
- Configure Washington Apple Health ABA Telemedicine and Claim Controls