Minnesota EIDBI medical-necessity and authorization changes take effect September 1, 2026. The DHS implementation notice requires providers to connect assessed functional and developmental needs, objective clinical evidence, daily-life impact, goals, service intensity, coordination, and ongoing need across the CMDE, ITP, and authorization request. Practices should update evidence flow while keeping individualized clinical judgment and payer decisions separate.

Minnesota EIDBI medical necessity authorization changes September 2026

The Minnesota EIDBI medical necessity authorization changes September 2026 expect each request to show how functional and developmental needs affect daily life, participation, communication, learning, adaptive skills, and safety. The evidence should connect assessment findings to goals and the requested service configuration. Avoid a generic diagnosis paragraph or copied intensity recommendation. A qualified professional should explain the person-specific reasoning and uncertainty within scope.

Use objective evidence with context

Objective evidence can include appropriately selected assessment results, direct observation, defined opportunities, progress data, health or access information, and relevant records. Preserve the measure, date, setting, respondent or observer, denominator, supports, limitations, and interpretation. One score cannot decide medical necessity or intensity on its own, and administrative staff should not transform a template calculation into a clinical conclusion.

Align the CMDE and ITP without erasing authorship

Use the current CMDE Medical Necessity Summary and EIDBI ITP and Progress Monitoring form required for the service date and request. Map the CMDE finding, functional impact, selected goal, service, role, intensity, monitoring plan, and review point. Preserve who authored each clinical decision. Software may flag a mismatch or blank field; it should not rewrite clinical content to obtain authorization.

Build the request as a chain of evidence instead of a stack of forms. Each conclusion should point to its source observation, measure, record, client or family report, and author. Every requested service should point to the need and goal it addresses, while every goal should have an observable review method. When sources disagree, retain the disagreement and route interpretation to the qualified professional. A synchronized template that hides conflicting evidence is less useful than a transparent record.

Explain intensity as a testable recommendation

State the service, frequency, duration, setting, modality, qualified roles, caregiver work when applicable, ordinary supports, and why that configuration fits the assessed needs. Include the review date and evidence that would support increasing, decreasing, changing, or ending the recommendation. Count school, other care, travel, rest, play, family commitments, and communication access when evaluating feasibility.

Document coordination and nonduplication

DHS requires coordination with schools, waiver services, case managers, and other providers to show how EIDBI complements other supports and prevents duplication. Record the other service, purpose, schedule, contact attempt, information available, consent or disclosure route when required, and resulting division of work. Lack of a response should remain visible; it should not be converted into a claim that no overlap exists.

Use the minimum information needed for the coordination purpose. Verify who may authorize a disclosure and whether the client can participate directly. Offer interpreters, AAC, accessible formats, and time to review what will be shared. Separate permission to request information, receipt of another provider's record, and permission to disclose information back; one event does not automatically establish the others.

Track authorization as a lifecycle

Name the request state precisely: preparing, submitted, received, incomplete, pending clinical review, approved in full, approved in part, denied, withdrawn, expired, or under appeal. Preserve the submission artifact, receipt identifier, requested and approved services, units, dates, provider roles, conditions, notice, and next deadline. A portal screen or fax confirmation proves a transmission event only; it does not prove that the request was complete or approved.

If the decision differs from the recommendation, retain both. The payer owns the coverage decision, the qualified clinician owns the clinical recommendation, and the person or authorized representative owns their choices and appeal participation. Scheduling should use the approved service-date configuration and actual provider capacity while any dispute proceeds through the applicable route.

Support continued need with current evidence

For continued eligibility or intensity, compare the defined starting point, current functioning, progress, barriers, adverse effects, client and family input, implementation quality, and remaining need. Progress alone does not automatically require discharge, and limited progress does not automatically justify more hours. The qualified clinical role explains what the evidence supports; the state or payer decides the authorization request under its rules.

Match comparison windows before claiming change. State the dates, settings, opportunities, supports, missing observations, treatment integrity, and measure version for each period. Keep small samples and major context changes visible. Progress data can inform a recommendation, but they cannot by themselves establish that a service caused the change or predict the result of a new intensity.

A fictional September request cohort

Nia's Minnesota assessment team locks 24 authorization files due after September 1. Nineteen connect functional impact, objective evidence, CMDE finding, ITP goal, requested intensity, coordination, continued-need rationale, author, and current form. Evidence completeness is 19 of 24, or 79.2%. Five remain held for focused correction. The measure does not establish medical necessity, authorization, clinical benefit, or payment.

Use a focused release checklist

Before submission, verify the member, request period, current form version, qualified author, functional and developmental needs, daily-life impacts, objective evidence, strengths and preferences, goals, requested service and intensity, coordination, nonduplication, progress or continued need, consent and assent when applicable, accessibility, signatures, attachments, submission route, and response deadline. Keep the July legislative changes in a separate control layer.

Related resources

Sources