The Health Plan West Virginia ABA workflow deserves a closer look than a generic behavioral-health checklist. For an owner serving Medicaid members, the important questions include your practice's participation, the specific service being requested, the current Mountain Health Trust instructions and how MyPlan, THP's provider portal, fits into the work. This guide also helps with a question that can leave an otherwise organized office unsure what to do: a code missing from a general authorization spreadsheet is not, by itself, enough to clear an ABA visit to begin.

Joining THP as an organization differs from adding a practitioner

A growing practice can encounter two very different administrative projects that both get called “credentialing.” One is establishing a new organization's relationship with an insurer. Another is adding a professional to an organization that already participates. Knowing which project you have prevents the team from spending weeks following the wrong set of instructions.

The Health Plan's provider participation page makes that distinction explicit. An organization that is not contracted can submit a network request through the public form. An already contracted organization adding a practitioner is directed to the Credentialing Request Form in the secure provider portal. The page also explains that a full practice roster may be requested during contracting.

That is useful information for a BCBA planning to hire. The question isn't only whether the new person has the right professional qualifications. Your office also needs to know how that person will be recognized within the practice's payer arrangement, for the services and dates involved. A signed employment agreement and an insurer's accepted provider record answer different questions.

Imagine a practice that uses the public new-organization form each time a clinician joins. The owner may feel that the paperwork is complete because the form was submitted, while the actual practitioner-addition process hasn't started. A brief review of the existing contract and current portal instructions can redirect the work before anyone promises a start date to a family.

Generic forms can also be misleading when read too literally. A field about hospital privileges or prescribing belongs to a broader provider intake form; it does not establish that every ABA professional needs those qualifications. The practice should ask how its specific provider type is handled, rather than fill an irrelevant field with an unsupported answer.

During the contracting conversation, the owner has an opportunity to understand the practical agreement as well as the application requirements. Proposed service locations, the billing organization and the reimbursement terms should be clear enough to support a realistic plan. Interest in joining a network is not evidence that all of those details have been accepted.

Reading the Medicaid rules when the public pages seem to disagree

You can have three THP documents open and still be unsure which instruction applies. One describes outpatient behavioral health, another discusses Mountain Health Trust, and a spreadsheet lists procedure codes alongside several insurance products. Each resource is useful, but none should be read as if its shortest sentence settles every ABA question.

THP's July 2026 Mountain Health Trust chapter distinguishes Medicaid behavioral-health instructions from WVCHIP, and directs providers to its authorization list because plan and BMS requirements may differ. The chapter also contains broad clinic-based behavioral-health language. That general wording needs to be reconciled with the particular ABA service, provider arrangement and applicable state policy.

The authorization spreadsheet effective August 1, 2026 contains an important qualification. Its general missing-code rule is subject to exceptions, and its Medicaid notes preserve the controlling West Virginia document when coverage criteria conflict. At the August 30 review, individual ABA codes 97151 through 97158 were not listed. That absence should prompt a service-specific question, not an automatic “no authorization needed” entry in your scheduling system.

The state's ABA policy, section 519.23.6, describes authorization in advance of services and rejects backdating. Read alongside the plan materials, it is a reason to resolve the actual requirement before relying on a generic exemption. The practice should obtain current payer clarification when instructions appear inconsistent, without converting an administrative interpretation into a clinical coverage decision.

For example, a biller may search the spreadsheet for a familiar code, find no row and assume that an assessment can proceed. A more reliable discussion includes the member's product, the requested service and the specific passages that raised the question. The response should be retained in the appropriate record with its date and scope. An answer about a commercial plan should not quietly become the Medicaid rule for the entire clinic.

This is also why website labels need context. When reviewed, the public index still called the August 1 list “upcoming,” although that effective date had passed. The document's date and contents matter more than the heading alone. Your internal reference should identify the version consulted and direct staff to recheck changes, rather than preserve an old screenshot as permanent policy.

Families need not be drawn into that ambiguity. The office can explain that it is confirming the correct approval process and name the next follow-up. If a question involves the child's clinical needs or access to necessary care, the responsible clinician and appropriate plan support should be involved rather than leaving the family with an indefinite administrative hold.

Using MyPlan for work that another colleague can pick up

Once the requirement is clear, the submission process should be predictable. THP's prior-authorization page says that Mountain Health Trust requests must go through its provider portal under the change effective July 1, 2024; it does not accept routine fax or phone requests through that process. An old form saved on a shared drive may therefore be the wrong starting point even if it once worked.

An owner can ask the team to walk through a hypothetical request from preparation to response. That conversation often reveals a practical gap: the person who collects clinical documents may not know who submits them, or the person who submits may not receive the follow-up notification. The practice needs a workable handoff, not merely proof that someone has a portal login.

A response may approve dates or quantities that differ from the request. Your scheduler needs to see that difference, and the clinician needs a chance to address it before the office gives the family an inaccurate explanation. Administrative staff can flag a discrepancy and route it for review. They should not alter the treatment recommendation to make it fit the approval without the appropriate clinical decision.

Consider what happens when your usual coordinator is unexpectedly absent. Another authorized employee should be able to determine which request was submitted, whether more information is due and what the family was told. If all of that knowledge lives in a personal inbox, even a short absence can make a routine request difficult to recover.

Shared understanding does not require shared passwords. Access should be appropriate to the role, and patient documents should remain within the practice's approved systems. A brief status note can often carry the handoff without reproducing sensitive details in multiple places. The aim is enough context to continue the work safely, not a second unofficial chart.

A pending response also has implications for communication. Staff can say what is known and what is still being checked without promising approval. If a payer question remains unresolved, the next update should explain the progress made and the route being used. Repeating “we're waiting on insurance” gives a family little confidence that anyone understands the obstacle.

A claim needs a traceable path to its remittance

Your billing team may use a clearinghouse while your intake team spends most of its time in MyPlan. That division can work well, provided the practice can connect the services delivered to the claims submitted and the payer responses received. Otherwise, a rejection can sit in one system while an owner sees only a growing balance in another.

THP's claims guidance describes electronic vouchers, claim-status tools and EDI enrollment for practices that need to establish that connection. It distinguishes receipt of a claim from the service date. It also publishes filing and resubmission limits, so the office should track the relevant event rather than simply count days from the last time someone opened the balance.

Suppose a clearinghouse transmission is successful but a particular claim is rejected. The batch acknowledgement may reassure an inexperienced biller, yet the service itself has not reached the same stage. A useful investigation follows the individual claim and its response, then identifies whether the underlying information or the transmission needs correction.

The payer page also describes a separate cover sheet and timing requirements when documentation is faxed to support an electronic claim. That claims instruction should not be confused with the portal-only authorization process. Different transactions can legitimately use different channels. A practice reference that says only “THP no longer accepts fax” would erase the distinction and could send staff in the wrong direction.

An owner doesn't need to memorize every submission field to ask good questions. Which response shows that the claim was accepted? What amount was allowed? Why is the remaining balance unresolved? Was the issue corrected at its source, or will the same mistake appear on next week's claims? These questions help the biller explain the work in terms the whole practice can understand.

These details become especially useful when you're deciding whether to hire. Submitted charges, expected reimbursement and cash actually received are different figures; using the largest one can commit the practice to costs before you understand the uncertainty. A forecast should use the applicable agreement and actual payment experience, with unresolved claims identified separately. This is prudent management, not a promise that a particular insurer will pay on a fixed schedule.

Making a Medicaid reconsideration worth reviewing

A reconsideration should tell the payer what the practice believes is wrong and why. It is less useful when it merely resends the original claim without addressing the response. The owner can support the process by ensuring that someone has time to investigate the problem before choosing the next transaction.

THP's reconsideration and appeals page describes one provider reconsideration or appeal level for denied Medicaid claims. It gives the filing limit as the later of 180 days from the denial or 180 days from the service date. That is a provider claim rule, not a universal deadline for every member appeal or clinical review.

For instance, a claim may carry the wrong rendering information because a roster update never reached the practice system. Correcting the claim and establishing the provider record can be more relevant than arguing that the clinical service was necessary. A different case may involve an accurate claim and a disputed payment decision. The evidence and requested resolution should match that disagreement.

A reviewer shouldn't have to search a large attachment to discover why the practice disagrees. A clear account connects the claim and payer response to the information supporting the request. Clinical explanations remain the responsibility of the appropriate professional. Nobody should change an accurate service record solely to make a denial easier to contest.

Even a positive response may not mean the account is settled that day. The reconsideration outcome, adjusted claim and payment can appear at different times. Closing the task only when those records have been reconciled prevents the same issue from returning during the next financial review.

The family deserves protection from the confusion as well. A payer problem is not permission to transfer an unresolved balance to a parent. Financial-responsibility questions should be reviewed under the applicable agreement and member protections before anyone requests payment. Clear explanations and accurate records can preserve trust even when the administrative work takes longer than everyone hoped.

Related resources

Sources