I-SNP Operating Record: Enrollment, Coverage & Utilization
Institutional special needs plans put a plan cadence inside your building. See the record an I-SNP operator has to hold — enrollment reconciled to census, clinician coverage, transfer events, Model of Care evidence, and measure lineage — with primary CMS sources cited.
Key points
- If the plan can describe your building better than you can, you are a subcontractor in your own risk arrangement.
- Which residents are enrolled, effective when, disenrolled when, and how that reconciles to your census and level of care on the same date. Mid-month effective dates are where operator and plan counts diverge first.
- The clinical and census record supporting institutional or institutional-equivalent level of care for each enrollee, held with the assessment that established it and the date it was established.
- Care coordination activity, interdisciplinary team participation, individualized care plan review, and the dates each occurred — the operational proof behind the Model of Care elements the plan committed to CMS.
- NP, APRN, and physician time in the building by day, shift, and enrollee panel. Under an I-SNP, clinician presence is the intervention. It belongs in the same record as the population it serves.
- The event, the resident, the enrollment status at the moment of the event, the acting clinician, the disposition, and the return — dated at the point of care rather than reconstructed from a claims extract.
- Conditions documented, coded, and refreshed within the year, with the source note and author. Institutional risk scores are computed from data the plan submits, but the specificity originates in your EHR.
- Order changes, pharmacy interaction, and change-in-condition notes with timestamps, so an avoidable transfer can be reviewed as a sequence rather than argued as an impression.
Frequently asked questions
- Is SeniorCRE an I-SNP platform, a care-management tool, or a plan administration system?
- None of those. Plan administration, enrollment processing, and claims adjudication sit on the plan side. Care-management tooling is usually a workflow product inside a clinical system. SeniorCRE is the operator-controlled operating record above the systems you already run: it reconciles enrollment to census, holds utilization events at the point of care, keeps measure lineage intact, and puts labor and coverage in the same record as the attributed population. The record is governed where it lives, not where it is displayed.
- Do we replace PointClickCare® or MatrixCare® to run an I-SNP on this?
- No. Nurses keep charting where they chart, the MDS coordinator keeps the same workflow, and the biller keeps the RCM. SeniorCRE is designed for read-oriented extraction into an operator-controlled record. Named products are trademarks of their respective owners; SeniorCRE is not affiliated with, endorsed by, or sponsored by them.
- Will this reduce avoidable transfers or improve our shared-savings position?
- We do not make that claim and will not until an operator’s own data supports it under a stated methodology. Whether transfers fall depends on your clinical model, your clinician coverage, and your family communication — not on software. What the record does is make the inputs legible: the event on the day it happened, the coverage in place, the enrollment status, and the documentation lineage behind every number you and the plan will argue about.
- Can you connect to the plan, the TPA, or our care-management vendor today?
- No. No vendor, payor, plan, TPA, or HIE integration is live in operator production today, and no clinical data is transmitted to any external party today. The architecture is designed for governed, scoped disclosure — role boundaries, minimum-necessary field scoping, purpose recorded per disclosure, and an operator-readable audit trail — and connector scope is sequenced in the implementation plan.
- Does the operator or the plan own the clinical data in this arrangement?
- The operator owns its record. Our MSA, EULA, and Data Licensing Addendum prohibit monetization of de-identified resident data to third parties. The record is exportable in full on exit and keeps working if you disconnect us. Your obligations to the plan are governed by your agreement with the plan, which is exactly why you should be able to produce your own figures before you receive theirs.
- What is the security posture for PHI in an institutional plan arrangement?
- HIPAA-aligned controls with infrastructure SOC 2 inheritance. No SeniorCRE SOC 2 audit has been started; no auditor is engaged and no timeline is published. No independent penetration test has been completed. Encryption in transit and at rest, PostgreSQL row-level security enforced fail-closed under a non-owner role, signed-URL access for all PHI, and immutable audit logging on privileged functions. BAA-ready; operator BAA execution is a readiness gate.
https://seniorcre.com/value-based-care/i-snp