Ohio Level One, SELF, and IO Waivers for Autistic Children

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Ask the Ohio county board for eligibility and a three-waiver comparison

Ohio DODD's waiver directory describes Level One, SELF, and Individual Options. Save county-board intake, DD eligibility, waiting-list assessment, immediate or current-need findings, Medicaid application, DD level of care, waiver comparison, offer, acceptance, person-centered plan, budget, service authorizations, provider contacts, and notices.

Separate the six decisions in the state file

CMS's Section 1915(c) overview explains that states define target groups, institutional level of care, enrollment limits, person-centered plans, and services within approved waivers. For Ohio, create separate rows for program eligibility, institutional level of care, Medicaid financial eligibility, list or slot status, service-plan authorization, and provider availability. When the child route uses State Plan, 1915(i), 1915(k), or another authority instead, name it accurately. Add the decision maker, evidence, date, notice, next action, and next date to each row.

Build an application packet that can survive handoffs

Index the signed Ohio application, proof of identity and residence, representative authority when applicable, diagnostic evaluations, developmental history, adaptive and functional assessments, medical records, selected school records, current services, unmet needs, safety information, caregiver circumstances, and requested releases. Keep an original and a submitted copy. The delivery log should show recipient, channel, date, page count, confirmation, and missing-item response. Mark expiration dates and newer evidence so an old packet does not silently control a present decision.

Preserve Ohio immediate and current need findings

Ohio's waiting-list rule establishes county-board lists and due process. Record every assessed need, evidence, category, review date, service gap, alternative offered, waiver required, capacity decision, and notice. A county can identify a need but still dispute that a waiver is required. Keep the need finding and waiver-necessity evidence separately appealable.

Turn eligibility into an implementable support plan

After Ohio Level One, SELF, and IO waiver system eligibility, selection, or authorization, ask who owns assessment, person-centered planning, budget or cost limits, service authorization, health and safety planning, and provider selection. For each support, record the need, goal, service definition, frequency, units, setting, responsible role, start date, backup, and review date. Give the child and family accessible choices and a way to disagree. An approved service remains incomplete until a willing qualified provider, workable schedule, and first delivered service are confirmed.

Keep DD services separate from ABA, school, and insurance

Ohio Level One SELF and IO waivers for autistic children can intersect with Medicaid State Plan services, EPSDT, Medicaid or private-plan ABA, an IEP, health care, and community programs. Each system applies its own criteria, notice, and appeal route. A clinician may supply relevant assessment and treatment evidence within scope. The clinician does not decide state DD eligibility, Medicaid finance, school eligibility, list priority, or funding. Ask every payer or agency to identify the exact requested service and authority before accepting a coordination or payer-of-last-resort explanation.

Test the child's actual week and provider access

Place proposed Ohio supports on a real weekly calendar with school, ABA, health care, transportation, sleep, meals, siblings, caregiver work, and recovery time. Verify access in each setting. Include AAC, speech, sign, gesture, mobility, sensory needs, feeding, toileting, medication, allergy, seizure or other health plans, interpreters, and backup communication as relevant. Ask how providers respond to assent, refusal, pain, fatigue, distress, a request to pause, or a changed priority. Count authorized and delivered hours separately.

Control records, consent, and representation

List the person who can apply, receive protected information, consent to services, sign the plan, and appeal for the child under the applicable Ohio rules. These roles may differ. Keep releases narrow enough to identify sender, recipient, records, purpose, and expiration. Give the child information in an accessible form and include the child's preferences and communication in planning. A representative's signature should not erase direct child feedback, family disagreement, or the need to document who made each decision.

Use current July 2026 waiver administration and assessment rules

Ohio's July 2026 administration rule governs current IO and Level One operation, and CMS's waiver list shows current approval dates. Verify SELF separately. Do not merge services or budget rules among the three waivers. Record assessment tool, effective rule, approved amount, self-directed authority, provider model, and any exception.

Build the adverse-notice and appeal packet before a deadline runs

CMS eligibility policy states that Medicaid applicants and beneficiaries must have a fair-hearing opportunity after a denial, allegedly erroneous action, or failure to act with reasonable promptness. The operative Ohio notice supplies the issue, authority, effective date, appeal recipient, deadline, continuation rules, and required form. Date-stamp receipt. Preserve the application, evidence, decision, plan, service history, communications, requested remedy, and proof of timely delivery. Use state disability or Medicaid legal help for advice about the individual case.

Use current supports while the longer path remains open

Maintain Ohio Medicaid State Plan and EPSDT services, health-plan ABA, school, county-board non-waiver support, Family Support Services, respite, OhioRISE when applicable, and community programs. After an offer, verify the waiver matches actual intensity, complete the person-centered plan and budget, identify qualified providers, build backup coverage, and confirm first delivery.

A fictional Ohio control file

Ari's family tracks 24 Ohio controls. Eighteen have dated proof, producing 18 of 24, or 75.0% completeness. County eligibility and current-need findings are complete. Waiver necessity, offer, budget, provider, backup, and first service remain open.

Questions for the next state-system call

Has the county board decided DD eligibility? What immediate or current needs were found? Why is a waiver required? Which of Level One, SELF, or IO fits? Are Medicaid and level of care complete? Which budget, self-direction option, provider, and notice control?

Close every control with evidence

Before the next Ohio call, confirm the exact program, current effective rule, application receipt, eligibility standard, diagnostic and functional evidence, level-of-care status when applicable, financial status, list or slot status, update duty, assigned worker, plan assessment, requested services, authorization, provider, schedule, first-service date, backup route, consent, representative authority, notice, appeal deadline, and interim supports. Give each unresolved item one owner and one next date. Show the numerator beside its denominator and recheck the child's newest written notice.