How can an ABA practice join Michigan Medicaid BHT and submit ABA authorization? Identify the member's Prepaid Inpatient Health Plan and Community Mental Health Services Program route, satisfy the current Behavioral Health Treatment provider and professional requirements, and complete the local contracting, credentialing, and authorization process. Configure billing by the responsible entity. Keep proposed policies and delayed system transitions outside current release rules until approved and effective.

Map the operative program route first

Michigan's autism services page and resource library place Medicaid Behavioral Health Treatment within the specialty behavioral-health system. For an ABA practice, the member's PIHP and CMHSP relationship is operationally decisive because local access, provider participation, authorization, and claim routing can differ by region.

The 2026 Medicaid policy bulletin index distinguishes approved bulletins from proposals. A May 2026 BHT proposal remains future-state material until final approval and an effective date. Michigan's mental-health framework describes broader delivery-system planning. The planned October 2026 responsibility change was temporarily delayed when checked, so current PIHP and CMHSP workflows remain active until an authoritative implementation notice says otherwise.

Separate every readiness gate

Build Michigan rows by provider entity, clinician or technician role, location, PIHP, CMHSP, managed-care relationship when applicable, and service. Track professional authority, Medicaid and regional provider status, contract, credentialing, roster, portal, member eligibility, BHT clinical determination, authorization, claim receiver, source version, and revalidation. A statewide concept map cannot replace regional written evidence.

Use four operational states for each Michigan row: verified, pending, held, and expired. Store the source, scope, owner, effective date, last check, next action, and evidence link with the state. Software can surface omissions and contradictions. State agencies, plans, qualified clinicians, privacy or legal owners, and billing specialists retain decisions within their authority.

Build a source-backed enrollment file

Start with the member regions the practice genuinely intends to serve. For each region, obtain current provider onboarding instructions and preserve the organizational application, ownership, NPI and taxonomy, licenses or certifications, staff qualifications, supervision model, sites, screening, insurance, contract, credentialing, roster, approval, and effective date. Document which PIHP or CMHSP owns each step and how individual staff become eligible under the agreement.

42 CFR 455.410 requires state Medicaid agencies to screen enrolled providers and to enroll covered ordering or referring professionals. For managed care, 42 CFR 438.602(b) assigns states enrollment, screening, and periodic revalidation duties for network providers. A single pending-network-agreement period may reach 120 days under the federal managed-care provision, yet that period supplies neither a billing effective date nor a payment promise for a Michigan practice. The CMS NPI fact sheet draws another practical boundary: an NPI identifies an individual or organization. Licensure, credentialing, Medicaid enrollment, network status, authorization, and payment require their own evidence.

Use a build-ready configuration record

Assign every Michigan configuration a durable identifier. Keep one row per billing entity, rendering professional or role, location, payer or program, product, service, and submission route. Recommended fields include legal name, NPI, tax identifier where applicable, taxonomy, license or certification, state enrollment number, screening and revalidation dates, contract, credentialing, roster, directory result, portal role, authorization path, claim receiver, effective period, source version, and named owner. Link the evidence that supports each field and preserve a change history. Broad free-text status notes make contradictions hard to detect and age poorly.

Create three useful Michigan views from the same controlled data. A launch view lists incomplete enrollment, contract, roster, portal, and claim-test work. A client release view joins member eligibility, delivery route, provider and site, qualified clinical decision, authorization, scheduled service, dates, and units. A reconciliation view links the original claim, acknowledgments, adjudication, remittance, deposit, corrections, refunds, and recoupments. Restrict sensitive fields by role. When two sources conflict, hold the affected configuration, preserve both versions, and ask the responsible agency or plan for written clarification.

Configure authorization by member and route

At referral, verify Medicaid eligibility, county, PIHP and CMHSP, active provider relationship, and current BHT authorization route. Capture the qualified assessment, diagnosis and referral evidence under the operative source, individualized plan, requested service, provider and setting, dates and units, supervision, coordination, continued-stay data, receipt, questions, decision, and renewal. If responsibility transfers later, recheck provider participation and authorization before scheduling under the new route.

Release claims from verified evidence

Michigan claim release should join the responsible PIHP or CMHSP, provider and staff status, member eligibility, authorization, location, actual service and time, code and modifier, units, supervision, and completed record. Configure each receiver separately. Keep a proposed future rule from overwriting an operative regional edit. Reconcile rejection, adjudication, remittance, recoupment, and payment at claim level, with ownership assigned to the region or practice according to written evidence.

A fictional readiness review

A fictional Grand Rapids organization reviews 18 PIHP-CMHSP-provider rows. Twelve are ready. Two regional contracts remain unsigned, one staff roster lacks an effective date, one row applies the May proposal as current, one assumes the delayed transition already occurred, and one receiver has no claim test. Readiness is 12 of 18, or 66.7%.

The Michigan denominator is locked before the review begins. Applications, portal accounts, directory entries, approvals at other sites, and unrelated claim tests cannot remove a held row. Each exception receives a responsible owner, next action, due date, and the exact evidence needed for release.

Measure the workflow after launch

Review Michigan autism resources, policy bulletins, PIHP and CMHSP provider material, and framework transition notices monthly. Trigger immediate review after a county, region, staff, site, contract, bulletin, or transition-status change. Measure regional agreements effective over rows due, staff rosters confirmed over roles due, authorization decisions by target over requests due, and mature first claims adjudicated without resubmission over mature first claims. Segment all outcomes by PIHP and CMHSP.

Maintain a Michigan transition register even while a planned change is delayed. For each announced milestone, capture its official source, current status, dependent regional workflows, owner, decision date, and earliest affected service date. Review the register at every release meeting. Preparation work may continue in a test environment, while production routing stays tied to operative PIHP and CMHSP instructions until the responsible authority confirms implementation.

Go/no-go checks before the first covered service

  • The member's county, PIHP, and CMHSP route are verified for the service date.
  • The organization and staff have written regional authority and effective dates.
  • The authorization matches the provider, site, service, dates, and units.
  • Proposals and delayed transitions remain outside current system edits.
  • The configured receiver produced a traceable claim and remittance test.

A go decision in Michigan applies to the named configuration and service period. An expired approval, credential, roster, authorization, source, or claim control pauses new covered-service promises on that row. Existing clients move through qualified clinical, payer, and continuity review under the applicable rules.

Related resources

Sources