How does SeniorCRE run PASRR Level I and coordinate Level II evaluations without delaying the admission?
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
Design target: fewer PASRR-related admission delays vs. operator baseline
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: Fax-based PASRR Level I form
Roadmap integration targets (not live): State PASRR portals · Hospital case management
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
Every Medicaid-funded NF admission requires a PASRR Level I; positives for serious mental illness or intellectual disability trigger a Level II evaluation that has to complete before admission. On a fragmented stack, the Level I is faxed, the Level II coordination is a phone tree, and the admission either delays or proceeds out of compliance.
How the platform is designed to run it
PASRR Level I generates from the pre-admission record with the disqualifying conditions clearly screened. Positives auto-route to the state’s Level II contact with the supporting documentation packet. The admission file shows PASRR status — Level I complete, Level II pending, Level II complete — so the admissions team can sequence move-in against the regulatory clock instead of around it.
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 hospital case manager calls about a Medicaid-funded SNF admission. The pre-admission intake captures the resident’s diagnoses and behavioral history; the PASRR Level I generates with the disqualifying conditions screened. The Level I is negative — admission proceeds Friday. On the next admission, a positive screen for serious mental illness auto-routes to the state’s Level II evaluator with the documentation packet; the admissions team sees the Level II clock running on the file and sequences the move-in for the day after the eval clears.
Design target
Design target: fewer PASRR-related admission delays vs. operator baseline. State-flagged PASRR non-compliance — a survey citation category — is designed to disappear as a finding because the workflow can prove the Level I was done and the Level II was coordinated.
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 integrated PASRR, the Level I is a faxed form, the Level II coordination is a phone tree, and the admissions team accepts the resident on a Friday only to find Monday that the Level II was never completed. The admission proceeds out of compliance, or it delays for a week while everyone scrambles. Either outcome shows up on the state survey list of frequent PASRR citations.
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 — Pre-Admission Screening and Resident Review (PASRR) policy
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 admissions 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
Admissions and CRM references
Admissions workflows on this page reflect the Pre-Admission Screening and Resident Review (PASRR) requirements, HIPAA marketing rules for referral sources, and CMS hospital discharge planning Conditions of Participation.
- Hospital Discharge Planning Conditions of Participation — Final Rule
CMS / Federal Register
Sets the discharge planning timelines and the patient-choice requirements that drive referral channel design.
- PASRR — Preadmission Screening and Resident Review
Medicaid.gov
Federal screen required before Medicaid-funded SNF admission; gates the workflow for serious mental illness and intellectual disability.
- HIPAA Marketing Rule (45 CFR 164.508(a)(3))
eCFR
Governs how referral relationships, sponsorships, and patient outreach can be structured without violating authorization rules.
- F-622 — Transfer and Discharge Requirements
CMS
The interpretive guidance for resident-initiated and facility-initiated discharges that bookend the admissions lifecycle.