Medicaid managed care enrollment, plan by plan: why each MCO is its own application

Why is each Medicaid MCO a separate enrollment?

Because the state and the plan are two different payers holding two different contracts. Medicaid managed care, in CMS’s words, delivers Medicaid benefits through contracted arrangements between state Medicaid agencies and managed care organizations that accept a set per member per month, or capitation, payment¹. The state enrolls you in the Medicaid program. Each MCO then decides whether you join its network, on its own paper, with its own credentialing file, provider ID and claims address.

Federal rule ties the two layers together without merging them. Under 42 CFR 438.602(b), the state must screen and enroll, and periodically revalidate, all network providers of its MCOs, PIHPs and PAHPs, and the rule adds that this does not require the network provider to render services to fee-for-service beneficiaries². State enrollment is a prerequisite for the plan contract, not a substitute for it.

Texas writes it as a sequence: providers must be enrolled in Texas Medicaid before they can be enrolled by an MCO or dental maintenance organization³. Pennsylvania says the other half out loud: enrollment in state Medicaid does not guarantee enrollment in individual MCO networks⁴. Put the two sentences together and you have the whole problem.

What order should you do them in?

State first, then the plans, in the order your patients are enrolled in them. The portal names change from state to state; the logic does not.

1. Identifiers. Confirm the Type 1 and Type 2 NPI, the taxonomy code the state expects for your provider type, and a current CAQH profile where the plans use it. An error here reappears in every application.
2. State Medicaid enrollment. Apply through the state’s provider system: TMHP in Texas³, PROMISe in Pennsylvania⁴, the Provider Network Management module in Ohio¹³, NCTracks in North Carolina⁷, IMPACT in Illinois⁹. Wait for the active date. Nothing downstream is reliable before it.
3. Pick the plans. Pull the plan mix from eligibility responses for your existing patients and apply to the plans that cover most of your panel first. Ohio’s FAQ answers the obvious question directly: providers are not required to contract with all Next Generation MCOs and can choose which ones⁶.
4. Credentialing. Where the state has centralized it, you go through one verification organization; where it has not, each plan runs its own. Texas requires every Medicaid MCO to use the Texas Association of Health Plans’ contracted credentialing verification organization³. North Carolina’s Provider Data Contractor obtains the primary-source-verified data, and the health plans rely on it to decide whether a provider meets their quality standard⁷.
5. Contracting and loading. Sign the participation agreement, then confirm the effective date, the plan’s provider ID, the payer ID for claims, and the ERA and EFT enrollment. Each is a separate step in most plan portals.
6. Verify before you bill. Check a real member’s eligibility to confirm which plan they are in. Ohio tells providers to check the Provider Network Management module before rendering services so that claims go to the correct MCO⁶.

The payer enrollment entry and the credentialing entry separate two words that plans use interchangeably and that are not the same thing.

How does the handoff differ by state?

The handoff from state enrollment to plan credentialing differs by state in three ways, shown for six states below: which system holds the Medicaid enrollment, whether the plans credential you one by one or through a shared route, and how many plans you may need to contract with.

What goes in the portal trail?

One row per plan, with the dates and numbers you will be asked for later. The trail is what lets you answer “we never received your application” with a confirmation number instead of a memory.

The 120-day rule makes the trail more than tidy. Under 438.602(b)(2), a plan may execute a network provider agreement while the state’s screening and enrollment is pending, for up to 120 days, but must terminate the provider on notice from the state that enrollment is denied or when the 120-day period expires without enrollment². If your state enrollment stalls, a plan contract signed on the strength of it has a clock running.

What happens to claims while plans are pending?

They are held against each plan’s own filing limit, and when they go, they go to the plan, not the state. Texas states the routing rule: claims for services administered by an MCO must be submitted to the client’s MCO³, and its managed care handbook gives 95 days from the date of service as the standard filing deadline³. Ohio routes every EDI claim, fee-for-service and managed care, through one EDI vendor, with the Fiscal Intermediary routing managed care claims onward⁶. Other states and plans set their own windows; the timely filing table lists the ones this site has verified.

The hold list needs a date column: the plan’s limit, counted from the date of service unless the plan’s manual says otherwise, and a review before it runs out. A held claim is still a claim with a deadline.

How do you keep the enrollments current?

Run two calendars: the state’s revalidation and each plan’s recredentialing. The federal rule requires states to periodically revalidate network providers², and plans recredential on their own schedules. North Carolina adds a warning worth copying everywhere: neither the health plans nor the Provider Data Contractor will contact providers to update credentialing information, so the provider has to keep its own NCTracks record current⁷. The revalidation entry covers the Medicare side, and the habit is the same here: a date on a calendar, an owner, and the portal trail updated when the work is done.