Solutions · Institutional Special Needs Plans
I-SNP Compliance: CMS Audit Readiness Without a Big-Plan Team
An I-SNP with a few thousand members faces the same SNPCC protocol, the same 15-business-day universe window, and the same CMS-10717 record layouts as a national carrier. The requirements do not scale down. The preparation has to.
The I-SNP Audit Reality
When CMS audits an I-SNP, SNPCC is in scope by definition, and it tests the things institutional care makes genuinely hard to document: health risk assessments completed on time for members who cannot always participate directly, individualized care plans that reflect what facility care teams actually do, and care transitions for a population where hospitalizations are frequent.
The structural challenge is that the evidence lives in more places than the compliance team controls. HRA and ICT documentation often sits partly in facility systems and partner EHRs. Claims, authorizations, and grievances flow through TPAs and PBMs, because most I-SNP operators delegate heavily. CMS does not distinguish: the plan owns every row of every universe, whoever generated it.
And the clocks are the same for everyone. Universes are due 15 business days from the engagement letter, the Models of Care and SNPCC Questionnaire in 5, and fieldwork documentation requests in 2. A three-person compliance team gets the same calendar as a plan with a compliance department of forty.
What CMS Tests, in I-SNP Terms
HRA timeliness at the universe level
Initial HRAs within 90 days of enrollment, annual HRAs within 365 days of the previous HRA, tested across every enrollee in the SNPE universe rather than a sample. For institutional members, outreach and completion often run through facility staff, and every attempt needs a documented date and method.
Care plans that operate, not just exist
ICPs with measurable outcomes and timeframes, evidence of enrollee or caregiver involvement, and implementation that can be verified through claims and case notes. Auditors trace whether the HRA-identified need became an intervention that actually happened.
Care transitions
Hospital admissions and discharges are routine events for an institutional population, which makes transition protocols one of the most exercised and most examined parts of an I-SNP's Model of Care: care team notification, ICP updates, and medication reconciliation after every transition.
MOC training evidence
ICT members and network providers, including facility-based providers, need documented Model of Care training. This is one of the most common gaps for operators whose provider relationships run through facility partners.
Everything else a sponsor owes
SNPCC is not the whole audit. Depending on scope, an I-SNP produces ODAG, CDAG, and FA universes too, mostly from delegate systems, plus the COA universe for the discussion-based CPE review. The CMS Program Audit guide covers the full picture.
Where Sevana Fits
Sevana Health builds compliance software exclusively for Medicare Advantage, and the platform is designed so a small team can run a big-plan readiness posture. Two pieces matter most for I-SNP operators:
- •The CMS Universe Scrubber validates SNPE and every other protocol universe against 1,600+ rules translated from the CMS-10717 record layouts, including HRA timeliness logic anchored to the previous HRA, before anything goes to CMS. Delegate files get the same treatment as internal data.
- •The Compliance Work Plan keeps the standing readiness work (scheduled universe validation, outreach documentation checks, MOC training currency) visible and owned, so the 5-day and 15-day windows arrive as execution, not discovery.
If you want to see the concept before talking to anyone, the free Universe Header Check tool validates your file headers against the current CMS spec in your browser. Your data never leaves your machine.
Frequently Asked Questions
What is an I-SNP?
An Institutional Special Needs Plan is a Medicare Advantage SNP that serves members who live in institutional settings, typically skilled nursing facilities, or who require an institutional level of care while living in the community (sometimes structured as an IE-SNP). I-SNPs commit to a CMS-approved Model of Care built around on-site and facility-coordinated care.
Does the SNPCC audit protocol apply to I-SNPs?
Yes. SNPCC (Special Needs Plans Care Coordination) applies to all three SNP types: D-SNP, C-SNP, and I-SNP. When CMS audits an I-SNP, SNPCC tests whether the plan is delivering on its Model of Care: timely health risk assessments, individualized care plans that operate in practice, interdisciplinary care team coordination, and care transition protocols.
What does an I-SNP submit in a CMS Program Audit?
For SNPCC: the SNPE (SNP Enrollees) universe within 15 business days of the engagement letter, plus the approved Models of Care and the SNPCC Questionnaire within 5 business days. Depending on audit scope, the plan also produces universes for the other applicable protocols, such as ODAG, CDAG, and FA, including data generated by TPAs, PBMs, and other delegates.
How should a small I-SNP compliance team prepare?
Treat readiness as a standing condition rather than a project: generate and validate the SNPE universe on a schedule, anchor annual HRA timeliness to the previous HRA rather than the enrollment date, document every outreach attempt with dates and methods, keep MOC training evidence current for ICT members and network providers, and test delegate data before CMS does. The submission windows do not scale down for small teams, so the work has to be done before the letter arrives.
Audit Readiness Sized for an I-SNP Team
See how the platform handles SNPE validation, delegate oversight, and the readiness calendar in a 30-minute walkthrough. We respond within one business day.