Michigan Medicaid BHT provider enrollment in CHAMPS and PIHP network readiness requires separate applicant, relationship, and delivery-system decisions. Michigan requires providers serving Medicaid beneficiaries to be screened and enrolled in CHAMPS. The practice must choose the enrollment type supported by the real applicant, preserve the approved group or organization before linking rendering providers, and then satisfy the applicable PIHP or CMHSP contracting, roster, authorization, and reporting rules. An approved CHAMPS record does not by itself create a local network relationship or payable service configuration. Michigan provider enrollment CHAMPS overview

Map the applicant, relationship, and delivery system first

Create one row for the legal organization, one for each professional, one for every service location, and one for each PIHP, CMHSP, or other applicable Michigan delivery-system relationship. Preserve the legal name, Type 1 or Type 2 NPI, taxonomy, tax identity, professional license or credential, employer or group relationship, location, and intended rendering and billing roles.

Michigan says all providers who serve Medicaid beneficiaries must be screened and enrolled in CHAMPS, including providers that participate in Medicaid health-plan networks. Michigan CHAMPS enrollment requirement

Enrollment and network readiness remain distinct. A professional credential does not create CHAMPS approval. A CHAMPS approval does not establish a PIHP or CMHSP contract. A local contract does not automatically establish every rendering link, site, authorization, service code, or encounter configuration.

Administrative teams may gather documents and compare fields. Professional scope and supervision stay with clinical leadership, while authorized ownership or legal reviewers control disclosures. Contracting and billing leaders decide which supported network and transaction configurations may be used. Each readiness row should cite its source, checked date, effective date, and accountable owner.

Choose the CHAMPS enrollment type from the real role

Michigan's enrollment-type page distinguishes individual or sole proprietor, rendering or servicing, group, billing agent, facility or agency or organization, and atypical records. It also explains that Type 1 NPIs identify individuals and Type 2 NPIs identify organizations. Michigan CHAMPS enrollment types

An individual or sole proprietor may receive payment directly. A rendering or servicing provider works through an approved billing provider. A group is an organization of individual providers and uses a Type 2 NPI. A facility, agency, or organization is also an entity record with a Type 2 NPI. Those public definitions guide preparation, but the live application and applicant-specific state instruction control the choice.

Do not select group merely because several clinicians work together, or FAO merely because the entity calls itself an agency. Do not treat an internal job title as a taxonomy or CHAMPS specialty. When the provider type, specialty, subspecialty, or enrollment category is unclear, preserve the applicant facts and obtain written MDHHS guidance.

The category rationale belongs in the evidence file, along with who approved it and which current source was checked.

Approve the billing entity before linking rendering providers

Michigan's group guide says a group has a Type 2 NPI, rendering or servicing providers associate to it, and a new rendering enrollment cannot be completed until the group is approved in CHAMPS. Michigan group enrollment sequence The same sequencing principle applies when the live process requires an approved facility, agency, organization, or individual billing provider before an association.

The entity file should support legal and tax identity, Type 2 NPI, ownership and controlling interests, addresses, EFT, authorized signer, domain administrator, and the locations and professionals expected to associate. The professional file should support the Type 1 NPI when applicable, taxonomy, license or credential, employer, location, and intended rendering role.

Each association needs a dated relationship record with a start, end, submitter, state status, and supporting notice. Employment alone does not prove the CHAMPS link. A link to one group or site does not prove another.

If a group or FAO record is returned, do not start duplicate rendering applications to bypass the sequence. Resolve the underlying entity issue and preserve the original transaction.

Build a CHAMPS field-to-evidence index

Before opening the application, index the legal and DBA names, NPI, taxonomy, tax identity, ownership and managing interests, addresses, license or credential, group and location relationships, EFT, electronic-signature agreement, domain administrator, delegated users, and applicant-specific attachments. Each row should identify the source document, owner, verified date, expiration date, and system of record.

Michigan's provider enrollment page organizes the process into determining whether enrollment is required, selecting the enrollment type, registering with SIGMA when applicable, and creating MiLogin access for CHAMPS. Michigan enrollment preparation The CHAMPS overview identifies provider enrollment, updates, claims, payment, authorization, eligibility, and verification as separate system functions.

Names and addresses should agree across NPPES, tax, credential, bank, lease, and CHAMPS evidence. Resolve discrepancies with the authorized record owner rather than changing fields for convenience.

Identity, ownership, tax, credential, banking, and access materials require role-limited storage. Never share MiLogin or CHAMPS credentials. A tracker can show status without displaying protected values.

Submit, track, and preserve the state response

For every application or maintenance transaction, retain the applicant, enrollment type, NPI and taxonomy, specialty or subspecialty selected by the live process, relationships, locations, attachments, submitter, tracking number, date, returned questions, deadlines, and final notice. A saved application or confirmation page proves progress or receipt, not approval.

Michigan's determine-need page says providers must have approved CHAMPS enrollment to be reimbursed for covered services and directs applicants to verify whether an NPI is already enrolled. Michigan enrollment-need check A verification result is dated evidence; it does not replace the full approval or relationship record.

If the application is returned, preserve the exact reason and original answer. Correct only facts supported by current evidence. Do not create another NPI or entity, reuse another site's effective date, or backdate a license, group association, location, ownership, or EFT record.

After approval, compare the result with the intended configuration. Confirm the enrollment type, applicant, identifiers, relationships, locations, effective date, and limitations before scheduling or billing depends on it.

Separate CHAMPS approval from PIHP and CMHSP readiness

Michigan Medicaid behavioral health services operate through delivery-system relationships that may involve a PIHP or CMHSP. The exact contracting, credentialing, roster, authorization, and encounter path depends on the member, county, service, provider role, and current program arrangement. A general CHAMPS approval does not answer those local questions.

Keep a separate record for every intended network or contractual relationship. Link the intake request to the decision, executed terms, professional and site roster, directory evidence, portal access, authorization route, claim or encounter destination, effective date, recredentialing cycle, and termination terms. Do not infer that one region's instructions apply statewide.

The 2026 Medicaid policy bulletin page is the official index for current policy changes and should be checked for changes affecting provider enrollment or behavioral health operations. Michigan 2026 Medicaid policy bulletins A bulletin index is not applicant-specific approval.

When CHAMPS, a PIHP, and a CMHSP provide conflicting instructions, hold the affected configuration and request written clarification. Preserve which authority answered, for which product, role, site, and effective period.

Maintain associations, revalidation, and access

Calendar the professional license or credential, CHAMPS revalidation, legal entity registrations, ownership and controlling interests, NPI and taxonomy, locations, group or FAO associations, EFT, electronic signature, domain administrators, portal users, PIHP or CMHSP recredentialing, rosters, and directory checks. The live notice controls the actual due date.

Michigan's group page links current revalidation, application-tracking, controlling-interest, domain-administrator, and electronic-signature resources. Michigan group maintenance resources The FAO guide and rendering guide remain useful when those are the applicant's supported enrollment types.

When a professional leaves or a site closes, revoke access, end-date the relationship when instructed, preserve the prior dates, and identify open applications, authorizations, encounters, and claims. Do not delete historical evidence or silently overwrite a prior association.

Returned records, conflicting identifiers, expiring credentials, missing associations, location gaps, and roster differences belong in a dated exception queue with an owner, source, due date, evidence request, and disposition.

Run a Michigan configuration-level readiness review

A review of Michigan Medicaid BHT provider enrollment in CHAMPS and PIHP network readiness should end at the professional-entity-location-network level. Imagine a fictional Michigan organization with one approved group, two professionals, and two locations. One professional is linked to the group, the second application is returned, and the local network has activated only one site.

The organization holds the affected rows. It does not call the entire practice ready, assume employment creates the CHAMPS association, or copy the first site's network date to the second. Qualified clinicians make continuity and scope decisions for current members.

At a scheduled review, compare professional verifications, CHAMPS determinations, entity and relationship records, network agreements and rosters, authorizations, schedules, encounters, and claim exceptions. Record the outcome control by control instead of relying on a single readiness percentage.

The Finni provider-services overview describes administrative help with explicit limits. In Michigan, support may include organizing evidence, coordinating applications, tracking notices, comparing associations and network rosters, and surfacing exceptions. Finni cannot choose an unsupported enrollment type, approve CHAMPS or network participation, establish an effective date, decide clinical scope, authorize care, select unsupported billing data, or guarantee payment.

Related resources

Sources