How does the platform reconcile internal QMs against the Five-Star refresh before CMS publishes the change?
Roadmap — not built
The platform does not yet ship a dedicated module for this workflow. The “How the platform is designed to run it” description below reflects designed-and-planned behavior, not currently shipping code. Outcome figures are modeled targets.
Design target · Expected outcome
Internal QMs match CASPER before refresh
Design target modeled from workflow design. No operator community has been measured, no approved Evidence Record supports it, and business outcomes remain contributory — figures are targets, not results. See Industry Findings for methodology.
Incumbents this workflow touches
Proposed in-platform scope: Quarterly Five-Star spreadsheet pulled from CASPER
Roadmap integration targets (not live): CASPER reports · CMS Care Compare · PointRight
The operator may retain existing systems or select SeniorCRE for defined functions. Alongside existing systems, this workflow would depend on approved source access, implementation and operator acceptance. Named vendor integrations are roadmap targets, not completed connections.
The problem
CMS refreshes Five-Star monthly. Many operators learn that their long-stay antipsychotic measure ticked up — or that a pressure-injury measure now triggers a star drop — when CMS publishes the new rating. The internal numbers and the CASPER report rarely agree, and the gap is hard to investigate after the fact.
How the platform is designed to run it
Long-stay and short-stay QMs compute internally from the same clinical record CMS will see. Each measure shows current rate, the trailing rolling window, the threshold for each star band, and the specific resident events driving the numerator. When an event would tip a measure across a star boundary, the dashboard flags it before the refresh. Reconciliation against CASPER becomes a check, not an investigation.
Proposed operating behavior, not a live deployment. Source access, implementation and operator acceptance must be established before this workflow can operate in a community.
On the shift (illustrative)
Illustrative example on synthetic data. Names, figures, and events are not from any operator community.
A Thursday afternoon the DON sees an alert: the long-stay falls-with-major-injury rate has crossed the threshold that would drop the QM star from 4 to 3 at the next refresh. The driver — three majors in 90 days, all on one unit, all after dinner — is on screen with the specific resident events. The community has a fall-reduction PIP open within 24 hours. The next CASPER report reflects the corrected pattern.
Design target
Five-Star surprises drop. When a QM is moving the wrong direction, the operator has the case-level detail to investigate within the building rather than the next CASPER cycle.
Design target only: not measured or validated in any community. Actual results require an operator baseline and pilot acceptance.
What goes wrong without it
Without internal QM reconciliation, the same star drop appears the morning after the CMS refresh. The leadership team learns from Care Compare. The PIP starts two months late. The investigation back to the three driving events takes a week because the case-level detail behind the CASPER number is not in front of the team.
Sources for baselines cited above
Industry benchmarks referenced in the problem statement or outcome come from these third parties. SeniorCRE figures are labeled with their evidence class — modeled from workflow design and benchmarks, not yet measured in a customer community.
- CMS — Nursing Home Care Compare Five-Star Quality Rating methodology
Centers for Medicare & Medicaid Services
Show me the evidence
Operators do not buy claims. They buy proof. If anything on this page reads as aspirational, ask us to walk you through exactly what is built, what is designed, and what is not yet in production in any community.
Where this connects in the platform
Every compliance workflow runs on the same record. These are the feature pages, head-to-head comparisons, and pillar articles that go deeper on the surfaces this workflow touches.
Feature surfaces
Compared head-to-head
Regulatory references
Compliance workflows on this page map directly to CMS Requirements of Participation, the State Operations Manual Appendix PP, and the QAPI at a Glance framework. Primary sources below.
- State Operations Manual, Appendix PP — Guidance to Surveyors for Long Term Care Facilities
CMS
Full F-Tag interpretive guidance used by state surveyors during the annual recertification survey.
- Requirements of Participation — Phase 3 Final Rule (42 CFR Part 483)
eCFR / CMS
The binding regulatory text. F-689 (accidents), F-684 (quality of care), F-880 (infection control) live here.
- QAPI at a Glance — A Step by Step Guide
CMS
The CMS-published framework for the five elements of QAPI used during the F-865 survey path.
- Five-Star Quality Rating System Technical Users' Guide
CMS
How survey, staffing, and quality measure stars are calculated — the math behind Care Compare ratings.