Under risk, the operator needs its own record — not the plan’s version of it.
Senior care is moving from billing a rate to owning a population. Medicare Advantage risk sharing, shared-savings arrangements, ACO and ACO REACH participation, Institutional Special Needs Plans (I-SNPs), bundled episodes and SNF VBP all ask the same underlying question: what happened to an attributed resident, when, under whose coverage, at what cost. That answer lives across the EHR, the plan portal, payroll, census and the ledger. SeniorCRE assembles it into one operator-controlled operating record, governed where it lives rather than where it is displayed.
Attribution and eligibility reconciliation
Plan rosters, attribution files and enrollment status arrive on the payor’s cadence, while census and level of care live in the operator’s systems. Reconciled by hand each month, an operator cannot state on a given day which residents are attributed, to which contract, at which risk tier. The operating record holds attribution next to census so the population under risk is knowable daily.
Utilization events at the point they happen
Transfers, emergency department visits, hospitalizations and returns are documented clinically and surface in claims data weeks later. A risk-bearing operator needs the event, the resident, the attributed contract and the acting clinician in one record on the day of the event rather than in a quarterly plan report.
Quality measure lineage
Star Ratings, MDS-derived quality measures and SNF VBP inputs are computed from documentation entered for a different purpose. Without lineage — which record, which field, which date, which source system produced the number — a disputed measure cannot be reconstructed. The record carries source authority on every figure.
I-SNP and clinician coverage economics
Under capitation, nurse practitioner and APRN time is the cost of the contract, not a line in the labor budget. Coverage hours, agency mix and acuity belong in the same record as the attributed population they serve, so coverage decisions can be evaluated against the population rather than against a budget.
Honest posture on outcomes and integration
SeniorCRE publishes no readmission, length-of-stay, utilization or savings figures attributable to the platform, and no per-bed or per-member dollar claims. Those are outcomes of an operator’s clinical program, computed from the operator’s own data under a stated methodology. No vendor or payor integration is live in operator production today, no payor feed is connected, and no clinical data is transmitted to any external party. Controls are shipped in main and exercised in SeniorCRE-operated validation environments.
Governed disclosure under risk contracts
Risk arrangements widen who sees clinical data: plan analytics teams, third-party administrators and care-management vendors. Each disclosure needs a scope, a purpose, a role boundary and an audit trail the operator can read. Row-level security is enforced fail-closed under a non-owner database role, PHI is reached only through signed URLs, and privileged functions write immutable audit logs. BAA-ready; operator BAA execution is a readiness gate.
Frequently asked questions
- Does SeniorCRE improve clinical outcomes or reduce readmissions?
- We do not make that claim, and we will not until an operator’s own data supports it under a stated methodology. What the record does is make the inputs to those measures legible: the utilization event on the day it happens, the attributed contract it belongs to, the coverage that was in place, and the documentation lineage behind every computed measure. Whether a program then improves an outcome depends on the operator’s clinical model, not on software.
- Are you a population health platform or a payor analytics tool?
- Neither. Population health and payor analytics tools sit on the plan side of the relationship and compute from claims. SeniorCRE sits on the operator side and governs the operating record where it lives — inside the operator’s clinical, labor, census, and financial systems — so the operator can enter a risk conversation with reconciled figures of its own rather than only receiving the plan’s.
- What does an I-SNP operator get that they do not have today?
- One record in which enrollment status, clinician coverage hours, transfers and ED events, acuity, and staffing sit together with the source system named on every figure. Today those live in the EHR, the plan portal, payroll, and a spreadsheet, and are reconciled monthly at best. The gap between the event and the report is where risk-contract performance is lost or contested.
- Can you exchange data with plans, TPAs, or care-management vendors?
- The architecture is designed for governed, scoped disclosure: role boundaries, minimum-necessary field scoping, purpose recorded per disclosure, and an audit trail the operator can read. No such exchange is live today, and no clinical data leaves the platform to any external party at present. Connector scope and validation-environment rehearsals are sequenced in the implementation plan.
- Do we have to replace PointClickCare® or MatrixCare® to run a risk contract on this?
- Replacement is not required. SeniorCRE is designed to sit above the EHR, payroll, and the ledger as the operator-controlled layer, using read-oriented extraction, and can assume selected system-of-record roles where the operator deliberately chooses that configuration. Clinicians keep documenting where they document. The record is governed where it lives, not where it is displayed. Named products are trademarks of their respective owners; SeniorCRE is not affiliated with, endorsed by, or sponsored by them.
- Who owns the clinical data in a risk arrangement?
- The operator does. The 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. That is what makes it operator-controlled: export without penalty, disconnect without data loss, and source authority visible on every figure.
- What is the security and compliance posture for PHI under these contracts?
- 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 logs on privileged functions. BAA-ready; operator BAA execution is a readiness gate. Full detail is in the security architecture brief.
https://seniorcre.com/value-based-care