To configure KanCare Autism Waiver telehealth and plan controls, use the current Autism Waiver manual and the member's KanCare plan for the exact service and provider. Verify that remote delivery is expressly supported for that configuration, then confirm waiver eligibility, provider status, plan authorization, both locations, modality, clinical fit, documentation, and claim route. General telehealth guidance should not be extended into a waiver service without current evidence.
Define a Kansas telehealth release
Oriana treats telehealth as a dated service 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. A material change creates a new version.
Read the current KanCare Autism Waiver authority
The current Autism Waiver manual defines the waiver service, provider, documentation, authorization, and billing framework. The KMAP manual index identifies current manuals, while the provider home supplies notices and operational resources. Oriana checks all three for a later effective instruction.
Separate program coverage from payer routing
KanCare plan implementation can add credentialing, authorization, submission, and documentation requirements. When the current public source set does not clearly establish remote delivery for the exact waiver service and provider, Oriana requests written confirmation from the responsible program or plan and holds the session. General behavioral-health telehealth language stays outside the release gate.
Keep a source decision log
Oriana records publisher, title, URL, publication and effective dates, checked date, service and provider scope, supersession state, question answered, and unresolved question. A later bulletin may replace one rule while leaving other sections active. The log connects every released session and claim to the evidence actually used.
Use one release gate for every required fact
Oriana requires current waiver eligibility and plan; current Autism Waiver manual; written service-level telehealth support; approved and qualified provider; plan credentialing; PA; both locations; permitted modality; clinical fit; choice; consent and assent when applicable; access; complete note; claim fields and receiver; and emergency plan. A failed gate holds the session or claim at the point affected. The register shows its source, owner, checked time, effective period, exception route, and next action. Clinical, legal, payer, technical, and claim facts keep separate owners and evidence.
Keep clinical decisions with qualified clinicians
Oriana 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. The payer owns its coverage decision, while the treating clinician owns the recommendation within scope.
Verify both locations for every encounter
Oriana asks for the member's current physical location at check-in and records the practitioner's current physical location from the professional. Those facts drive licensure, payer, emergency, privacy, and place-of-service analysis. A profile, mailing address, device signal, or prior encounter provides reference data rather than current-location proof.
Preserve choice, consent, assent, and communication
Oriana explains the remote option in accessible language and records required consent from the person legally authorized to provide it. 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 pause, withdraw, or request 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. Oriana identifies components needing direct observation or in-person care and sets a switch condition. Staffing pressure, travel distance, or payer approval supplies no clinical-fit finding.
Build technical and emergency readiness
Oriana tests the approved platform, audio, video when required, power, bandwidth, camera view, communication system, backup contact, privacy, and outage route. The record names the person's 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
Oriana 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 note describes the delivered service.
Release the claim from completed evidence
Oriana 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 checkbox supplies one data point. Claim acceptance, clean-claim status, adjudication, remittance, and payment remain later states.
Work through Oriana's fictional cohort
Oriana locks 18 fictional Wichita waiver sessions across two plans. Ten initially contain current waiver evidence, written remote support, provider approval, plan status, PA, both locations, clinical decision, access, note, claim route, and response plan. Two rely on a general telehealth manual, one uses a state-plan rule for a waiver service, one provider approval expired, one PA names in-person care, two lack written service support, and two notes omit practitioner location. 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 Oriana's measures
KanCare Autism Waiver 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 Kansas failure mode
Waiver services, state-plan services, and general behavioral-health services can share everyday language while using different authorities. Oriana records waiver name, service, provider type, plan, manual version, authorization, and written telehealth decision. Similar labels never merge those configurations.
Test Oriana's controls
Oriana tests two KanCare plans, waiver eligibility, state-plan mismatch, general telehealth source, written program answer, expired provider approval, in-person PA, member relocation, failed platform, incomplete note, and claim rejection. Each scenario records starting facts, expected action, source, observed result, owner, correction, retest, and disposition. A successful connection establishes technical access for that test. Coverage, clinical fit, authorization, documentation, and payment need separate acceptance evidence.
Run independent acceptance
Oriana 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 KanCare Autism Waiver telehealth source and plan register
Oriana 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 Kansas page remains draft and noindex until every named expert review finishes.
Related resources
- Configure MaineCare Specialized RCS Telehealth Controls
- Configure Iowa Medicaid ABA Telehealth and MCO Controls
- Configure North Dakota Medicaid ABA Telehealth Controls
- Configure Hawaii Med-QUEST ABA Telehealth and Plan Controls