Michigan Medicaid Mental Health Framework delay ABA guidance starts with the current MDHHS update: coverage-responsibility changes previously scheduled for October 1, 2026 are temporarily delayed. ABA teams should keep using the presently verified Medicaid health-plan, PIHP, and CMHSP routes, preserve source dates and reference numbers, and treat framework training or draft transition material as preparation until MDHHS publishes an operative replacement date.
The delay changes the implementation clock
MDHHS's live framework page announces the temporary delay and says broader page and document updates are coming. The same page still contains earlier October 2026 planning language. Record the delay banner as the current status, the older schedule as historical preparation material, and the checked date as August 20, 2026. A workflow should never select the older date simply because it appears deeper on the page.
Keep current BHT routing active
The state Medicaid manual portal remains the source for operative policy. Final letter L 24-78 describes behavioral health treatment, including ABA, through qualified providers in PIHP and CMHSP networks. MDHHS behavioral health access guidance assigns community behavioral-health access to the CMHSP and regional management to the PIHP. Verify the member's county, health plan, PIHP, CMHSP, provider network state, and authorization route before scheduling.
Freeze those facts in a current-state routing matrix. Give each row a member product, county, PIHP, CMHSP, qualified provider, authorization owner, notice and appeal route, claim destination, evidence date, and next recheck. A verified current route can remain active while future-state analysis continues. If two sources conflict, hold the affected change and ask the named authority for written direction.
Separate active work from readiness work
Active work includes current eligibility checks, county routing, clinical submissions, provider assignment, service authorization, notices, and appeals. Readiness work can include staff training, data-field mapping, referral testing, contract analysis, and a future cutover checklist. Label every readiness task with a dependency on a new MDHHS effective date. This prevents a practice from changing claims, referrals, or clinical handoffs early.
Build a controlled change register
Track each affected service, current owner, planned future owner, source URL, source date, contract dependency, system field, staff role, family communication, test evidence, release approver, and rollback path. Recheck the state page after each material notice and before any release. A health plan presentation, PIHP memo, or training deck can inform preparation while the current state authority controls the live route.
Assign each register item a state such as current, proposed, awaiting authority, ready to test, approved for release, or retired. Save the source that caused every state change. This history matters when an older authorization, claim correction, appeal, or continuity question crosses a later transition date.
Communicate the delay without creating a promise
Families and clinicians need a concise operational message: the current verified route remains in use, future ownership and timing are unsettled, and the team will share a source-backed change when one becomes operative. State which contact remains responsible today. Offer the message in the person's usable language and communication format, keep AAC available, and record who received it.
Use the minimum information needed for the communication. A general transition notice rarely needs a full clinical record. Member-specific routing, authorization, or appeal work should use the approved secure channel and the authority applicable to that action.
A fictional routing review
Ari's team locks 23 transition checkpoints across eligibility, county, PIHP, CMHSP, provider, authorization, notice, and system configuration. Eighteen have current evidence, so recorded readiness is 18 of 23, or 78.3%. The five future-state items remain holds tied to the missing operative date. This ratio measures documentation readiness. Approval, clinical fit, provider capacity, payment, and transition certainty require separate evidence.
The team also keeps all 23 checkpoints in its next review. Removing the five holds would turn the result into 18 of 18 and hide the central dependency. Each hold has an owner, the exact missing authority, the last checked date, and the event that will trigger another review.
Recheck on named events
Open the register when MDHHS announces a new effective date, publishes a final manual or bulletin change, identifies affected populations or services, or issues implementation instructions. Recheck after a PIHP, CMHSP, or health plan releases contract or provider guidance. A new date alone is insufficient for release when payer routing, open-case handling, data exchange, notices, or claims instructions remain unresolved.
Release criteria for the later transition
Require a current MDHHS authority, effective date, impacted population, service scope, payer and PIHP instructions, contract implementation, system tests, staff training, family notice, open-case reconciliation, and named cutover approval. Preserve both versions while older authorizations, claims, corrections, and appeals remain open. Use a complete, source-backed decision record as the launch signal; a calendar reminder carries no implementation evidence.
Related resources
- CMS 2026 Prior Authorization Timeframes and Denial Reasons for ABA Teams.
- North Carolina Medicaid CCP 8F ABA Changes: August 2026 Guide.
- CMS 2027 Prior Authorization API: ABA Readiness Guide.
- Massachusetts Standard ABA Prior Authorization Form: 2026 Workflow.
