Table of Contents
CMS has lifted the enrollment suspension it imposed on Provider Partners Health Plans’ Maryland institutional special needs plan after the insurer corrected network deficiencies, resolving the Provider Partners Maryland I-SNP suspension roughly ten weeks after it was first imposed.
What Triggered the Provider Partners Maryland I-SNP Suspension
The agency suspended enrollment into the plan in late May after Provider Partners lost all contracted long-term care facilities in its network and then disenrolled 29 members from the program without their consent. This combination, a complete network collapse followed by involuntary member disenrollment, represented a serious compliance failure for a plan type specifically designed to serve institutionalized individuals requiring long-term care.
Why Losing All Network Facilities Is Especially Serious for an I-SNP
Institutional special needs plans are built around serving Medicare beneficiaries who reside in or require the level of care provided by long-term care facilities, meaning a complete loss of contracted facilities effectively left the plan without the core infrastructure needed to serve its intended population.
How Provider Partners Resolved the I-SNP Suspension
In an Aug. 6 letter, CMS said the insurer showed it now has at least one contracted long-term care facility serving institutionalized individuals for each county in the plan’s service area. This county-by-county coverage standard gave CMS a clear, verifiable benchmark for determining whether Provider Partners had sufficiently rebuilt its network before lifting the suspension.
What CMS Warned Going Forward
CMS warned that any future compliance failures could lead to sanctions, monetary penalties or termination of the company’s MA contract. This explicit warning signals that CMS intends to monitor Provider Partners closely following this episode, rather than treating the network restoration as closing the matter entirely.
The Scale of Provider Partners’ Broader Operations
Provider Partners has 9,000 members and also operates I-SNPs in Illinois, Missouri, Ohio, North Carolina, Pennsylvania and Texas. This multi-state footprint means the Maryland network failure, while resolved, occurred within a broader operation spanning seven states, raising questions about whether similar network adequacy risks could exist in the company’s other markets.
Why This Multi-State Context Matters
Given that Provider Partners operates institutional special needs plans across six additional states beyond Maryland, CMS’s heightened scrutiny following this suspension may extend beyond the specific Maryland market to the company’s broader compliance practices nationally.
What This Provider Partners Maryland I-SNP Suspension Resolution Means Going Forward
With the suspension now lifted and CMS’s explicit warning about future compliance failures on record, Provider Partners will need to maintain its restored network across every county in its Maryland service area to avoid renewed enforcement action. Given the severity of the original violation, losing all network facilities and involuntarily disenrolling members, this case may serve as a reference point for how CMS handles similar network adequacy failures at other institutional special needs plans nationally.
What to Watch Going Forward
As Provider Partners resumes normal enrollment operations in Maryland, industry observers will likely watch whether CMS extends similar scrutiny to the company’s I-SNP operations in Illinois, Missouri, Ohio, North Carolina, Pennsylvania, and Texas, given the multi-state nature of its business. Given CMS’s stated willingness to pursue sanctions, monetary penalties, or contract termination for future violations, this Provider Partners Maryland I-SNP suspension resolution may also signal a broader tightening of federal oversight over institutional special needs plans’ network adequacy requirements industrywide.
For more healthcare industry updates, insights and news, visit DistilINFO. Click here to subscribe to stay informed.
