Humana Healthy Horizons Ohio ABA Provider Guide

This Humana Healthy Horizons Ohio ABA provider guide focuses on the Medicaid plan's participation process, authorization and claims tools, and an announced October 2026 ABA coding change. It explains what the public instructions establish and where your practice needs a case-specific answer. The goal is to help an owner prepare the administrative work without confusing a portal selection, clinical approval or participation agreement with permission to bill every proposed service.

There is a dated ABA change worth planning for now

Humana's May 1, 2026 coding notice announces an October 1, 2026 transition to the listed nationally recognized ABA codes. As of August 30, you still have time to clarify how the October 1 change applies. Earlier service dates need their own applicable instructions; the announcement doesn't authorize rewriting those claims.

An owner can begin by finding out who in the practice reviews payer changes and who translates an approved interpretation into billing-system configuration. Those may be different people.

The clinical team also needs to be involved when a change affects how services are described. A rushed update made by someone who only sees the billing screen can create a mismatch between the record of care and the transaction the practice submits.

The provider-type paragraph needs to stay attached to the notice

The notice specifically discusses Community Behavioral Health Centers identified as Ohio Department of Medicaid (ODM) provider type 84. It also rejects using the named community psychiatric supportive treatment (CPST) and therapeutic behavioral services (TBS) alternatives as substitutes for ABA billing. That context matters when assessing how the change applies to your organization; it should not be reduced to a general announcement that any provider can now bill any ABA code.

Your actual enrollment, contracted arrangement and the professional roles involved still need review. A group might have the technical ability to select a code while lacking confirmation that its particular arrangement supports using it. Selecting a code also doesn't establish that a clinician is permitted to perform the service. Qualified coding and clinical reviewers should establish what accurately represents the care, and the plan should clarify the applicable participation and payment requirements.

A September approval spanning October deserves a specific question

Consider a fictional practice with a service authorization that starts in September and continues into October. Staff see the new coding notice and wonder whether the existing request, agreement or system setup needs to change. The notice does not answer every transition question for that case, and the effective date alone cannot supply the missing instruction.

A useful inquiry describes the actual authorization period and provider arrangement, then asks how the announced change affects subsequent submissions. Written clarification can be retained with the relevant administrative record. Until that answer is available, the office should avoid inventing a carryover rule or assuming an old approval automatically supports a different coding arrangement. The clinician remains responsible for the recommended care; an administrative transition should not quietly change the treatment plan.

Why the single-case-agreement wording needs clarification

Humana's ABA notice says ABA requires medical-necessity review and a single-case agreement, then describes an SCA process beginning when nonparticipating providers submit authorization requests through Availity. Read together, those sentences leave a scope question for practices with different participation arrangements. This guide does not resolve it by declaring every in-network case exempt or every arrangement identical.

The practical question is direct: which authorization and agreement requirements apply to this organization, provider and member? An SCA request is not the agreement itself. Any applicable terms, effective period and service scope need confirmation through the proper process. You can bring both sentences to Provider Services and ask how they apply to your case. That gives the representative the context behind your question.

Joining Humana is separate from resolving one case

A single member's service needs and a practice's wider network relationship are related, but different. Humana's network application page directs Ohio medical, Medicaid and behavioral-health providers to its online application route. That route is a way to express and document the request, not proof that the plan is offering the terms your business needs.

An owner should be ready to explain the organization's services, locations and proposed clinical staffing. Existing work with another Humana product or another state may provide experience, but does not establish this Ohio Medicaid relationship. The Ohio Medicaid FAQ points participation questions to 877-856-5707. The conversation can help identify the appropriate application and confirmation process. Dental and vision enrollment instructions on nearby resource pages should not be repurposed as ABA instructions simply because they also say Ohio Medicaid.

PNM data can explain a problem that looks like a Humana problem

Humana's Ohio provider-file guidance says it cannot accept changes inconsistent with the Provider Network Management (PNM) data shared through the Provider Master File. It distinguishes information maintained there from supplemental details an MCO may collect. That distinction can save an office from repeatedly sending a correction to the wrong place.

For example, imagine that a fictional rendering provider's address remains outdated in the state data while a practice sends the new address only to a plan representative. If the mismatch persists, the answer may be to correct the applicable source record and confirm its downstream handling, not to keep forwarding the same message.

The follow-up record can show what was submitted, where and when. It should not mark the problem resolved merely because an email was sent. The owner needs to know whether the relevant data now agree before relying on the change for upcoming work.

The authorization dropdown is not the claims dropdown

Humana's Ohio authorization page makes a specific distinction: authorization users choose Humana or Humana Behavioral Health in Availity, while Ohio Medicaid claims use Humana Healthy Horizons for Ohio Medicaid with payer ID 61103. Its traditional 61101 claims identifier should not be substituted. The page continues to direct authorization work through Availity pending a future state-system transition; it does not give this guide a launch date for that transition.

This is exactly the kind of detail that can disappear in verbal training. Two colleagues may both be working in Availity and assume they should make the same selection. A practice reference is more useful when it names the task and product next to the instruction. Your team still needs appropriate account access and current verification; a public navigation description is not a test of the practice's actual portal setup.

A short practice walkthrough can uncover access gaps

Before a real submission is due, authorized staff can walk through where the relevant functions appear and how their assigned roles work. That does not require inventing a patient, submitting test care or sharing logins. The purpose is to establish that the people expected to handle the work can reach the right tools and know where to ask for help.

Humana's Ohio documents and resources page lists Availity technical support separately from Provider Relations. A login or account-permission problem is different from a question about whether a proposed service meets plan requirements. Recognizing that difference helps the caller reach the appropriate support team. It also prevents the owner from mistaking an inaccessible screen for a clinical denial or a network decision when the underlying problem is simply access.

The published authorization list is a reference, not an approval

The accessible Ohio prior-authorization list carries a July 1, 2025 effective date and December 12, 2025 revision. Its behavioral-health table includes ABA codes 97151–97158, 0362T and 0373T. That date is worth keeping with your copy so staff can compare it with later notices.

The list helps identify a requirement to investigate. It does not determine a child's eligibility, approve an individualized treatment recommendation or establish that a particular provider can bill. Your team should check for superseding instructions and obtain the applicable current policy before use. The resource library identifies the Ohio manual and other tools, but this guide has not audited every page of that manual. Where the documents seem inconsistent, the unresolved point should be put to the plan and the appropriate professional reviewer.

What administrators can check without changing clinical judgment

An authorization employee can do a great deal to improve a submission without writing clinical content. They can establish that identifiers match, locate the requested attachments, confirm that the service dates are consistent and connect a response with the correct clinician. Those checks help the clinician's actual recommendation reach the reviewer clearly.

The boundary is equally important when information is missing. If a form asks for a clinical finding the record does not contain, the office should not fill the gap with plausible language. The qualified clinician can determine what information is available and whether further assessment or clarification is needed. A complete-looking packet is not an improvement if it obscures uncertainty. Owners can support accuracy by allowing time for that exchange rather than treating every returned question as a clerical failure.

Coverage changes deserve attention before the next visit

A family's circumstances can change while an authorization is still on file. The practice needs current member and program information for the relevant service dates, including any OhioRISE involvement. This article does not assign all ABA claims to an MCO or to OhioRISE based solely on a program name.

When something changes, a designated person can coordinate the payer questions and keep the family informed. The conversation should explain what the office is checking and who will contact them next. It should not ask a caregiver to choose between conflicting payer instructions or treat the administrative uncertainty as evidence about the child's clinical needs. Continuity concerns and clinical urgency require professional evaluation through the appropriate channels. That work can happen alongside the coverage inquiry without the two becoming confused.

An approval and a payable claim still need to agree

After service, the claim needs to accurately describe what occurred under the applicable provider arrangement and billing rules. An authorization number does not compensate for an incorrect member identifier, mismatched service date or unsupported coding choice. Those differences can be invisible in an owner's summary report until balances begin accumulating.

A practical review follows the submitted claim, acknowledgment and payer response. If a transaction never arrived, the team investigates its transmission. If it was adjudicated, the response can be compared with the actual submission, authorization and confirmed terms. This is more informative than calling every unpaid item a denial. The Ohio Medicaid FAQ and current resources can help staff locate the relevant process, while the actual notice governs the case-specific review. No general article can promise that correcting one field will produce payment.

The first October claims should be reviewed with the whole story

If the announced coding transition applies to your practice, the first affected claims deserve a deliberate check after the requirements have been confirmed. A changed system label might look correct while the service record, agreement or transaction still reflects something different. The useful review follows that relationship all the way through instead of looking only at whether software accepted the entry.

This can be a small, focused review by authorized staff rather than an owner personally reopening every chart. The clinical reviewer addresses the service description, the coding specialist examines the transaction and the billing team tracks the response. Any correction should preserve an accurate history and follow the approved process. Earlier claims should not be altered to imitate a later arrangement, and an administrative denial should not automatically become a charge to the family. Member liability requires its own careful review.

Making the payer relationship less dependent on memory

A small practice does not need a huge internal manual to handle this work thoughtfully. A dated reference file and clear follow-up responsibilities can go a long way. The broader Ohio Medicaid enrollment and authorization workflow can help you place Humana's requirements alongside the state work. Those habits become especially valuable when a notice changes or an experienced employee is away.

For an owner, the immediate priority may be obtaining an answer about the SCA language or confirming the October transition for the actual organization. Once that is settled, the office can translate it into clear instructions and a realistic family update. Growth is easier to evaluate when payer work is understandable, but neither a larger caseload nor a better-organized process guarantees collections. Confirmed terms, qualified clinical capacity and the practice's own operating evidence remain the foundation for business decisions.