Continuity and transition of care when a provider exits

Two related but distinct obligations

The terms get used interchangeably, but they cover two different situations, and conflating them causes gaps.

Transition of care governs the member who is already undergoing an active course of treatment when they enroll in your plan, often with a provider who is out-of-network for you. The obligation is to let that treatment continue without abrupt interruption during a defined transition period, even across the network boundary.

Continuity of care governs the member who is stable inside your network when their provider leaves it. The provider's contract terminates, and the obligation is to keep the member's active treatment continuous, and to notify the member in time to act, rather than letting them discover the change when a claim denies. Both obligations exist to protect the same thing, an uninterrupted course of care, but they trigger on different events and require different operational responses.

The 90-day transition period

The Contract Year 2024 Medicare Advantage Final Rule set a firm floor for the transition-of-care situation. When a member who is in an active course of treatment enrolls in a coordinated-care Medicare Advantage plan, the plan must provide a transition period of at least 90 days during which the member can continue that course of treatment.

Two features of the rule have real operational teeth. First, during that 90-day window the plan may not require prior authorization for the active course of treatment. You cannot use a PA process to quietly stall care the rule says must continue. Second, the protection applies even when the treating provider is out-of-network with your plan. A new enrollee mid-treatment does not have to abandon their provider on day one because you never contracted them.

After the 90 days, the normal rules resume. The plan may reassess medical necessity and apply its ordinary in-network and out-of-network benefit design going forward. The transition period is a bridge to an orderly handoff, not a permanent out-of-network entitlement, and the work during those 90 days is to either bring the provider in-network or transition the member to an in-network provider without breaking the course of care.

Notification when a provider leaves the network

When a provider's participation contract terminates, CMS requires the plan to notify affected enrollees, and recent rulemaking has made those requirements more specific and more demanding. CMS amended the enrollee-notification provisions at 42 CFR 422.111(e) to set distinct requirements for no-cause and for-cause terminations, and to impose heightened, more stringent notice requirements when the terminating provider is a primary care or behavioral health provider.

The logic is that not all provider exits carry equal risk to members. Losing one specialist among many is disruptive; losing a member's primary care physician or their behavioral health clinician severs the relationship at the center of their care. CMS singled those categories out for stronger, more specific notice because the continuity stakes are highest there.

The operational point is that notification is a regulated deliverable with content and timing standards, not a courtesy letter. Members need enough advance notice to choose a new provider and, where they qualify, to request continuity of care before their current treatment is disrupted. A late or vague notice is both a member-harm event and a compliance finding.

The populations that need continuity most

Continuity protections exist for everyone, but the members who will be seriously harmed by a lapse are a specific, identifiable group. These are the members to find first when a provider exits, because for them a gap is not an inconvenience, it is a clinical event.

• Members in active cancer treatment, where an interruption in chemotherapy or radiation carries direct clinical risk
• Pregnant members, especially those in the second or third trimester, for whom switching obstetric providers late is destabilizing and sometimes unsafe
• Members with serious and complex chronic conditions under active management with a specific specialist
• Members recently discharged from a hospital or facility, or scheduled for imminent surgery, who are mid-transition already
• Members receiving ongoing behavioral health treatment, where the therapeutic relationship itself is part of the treatment and cannot be swapped without harm
• Members who are terminally ill or receiving end-of-life care, where continuity is a matter of dignity as well as clinical need

Operationalizing continuity so nothing falls through

The rules are only as good as the workflow behind them, and this is where plans stumble. A termination that lands in network operations as a roster edit, with no trigger to the clinical and member-communication teams, is a continuity failure waiting to happen. The fix is to treat every provider termination as an event that fans out into a defined, tracked process.

The moment a termination is known, identify the affected members, and inside that group flag the at-risk populations above, because those are the members who need proactive outreach, not just a standard letter. Generate the compliant notices with the right content and lead time, applying the heightened standard when the exiting provider is primary care or behavioral health. Stand up the continuity and transition mechanism so members with an active course of treatment can continue it, and so the 90-day protection is honored without a prior-authorization roadblock. Then assign, in-network, the members who need a new provider, and confirm the handoff actually happened rather than assuming it did.

• Trigger the workflow the instant a termination is confirmed, not when claims start denying
• Identify all affected members, then flag the at-risk subset for proactive, individualized outreach
• Issue compliant termination notices with correct content and lead time, using the heightened standard for primary care and behavioral health exits
• Honor the transition and continuity period, suppressing prior authorization on the protected course of treatment
• Reassign members to in-network providers and confirm the handoff, closing the loop rather than assuming it

How we approach it

We build continuity of care as an operational workflow, not a policy document that sits in a binder. That starts with wiring the trigger: a provider termination should automatically set off member identification, at-risk flagging, notice generation, and continuity setup, so nothing depends on someone remembering to act.

We also design for the predictable disruptions, because most terminations are not surprises. When you know a contract is at risk or a group is being acquired, the continuity plan should be ready before the exit, with the at-risk members already identified and the outreach staged. Done this way, a provider leaving the network becomes a managed transition instead of a scramble, your members stay protected through their treatment, and your notices and timelines hold up under the scrutiny CMS now applies to exactly these events.