Occupancy is the most discussed number in senior housing. It is also the least reconciled.
Inside one building there are five census figures under five conventions , and a referral pipeline that loses volume at seven stages before anyone records the loss. This page defines the conventions, maps the loss modes, and gives you a calculator that runs the arithmetic on your inputs — not on ours. No occupancy, conversion, or dollar outcome on this page is attributable to SeniorCRE.
On this page
When the DON, the business office, the MDS coordinator, and the CFO give four different census numbers for the same Tuesday, the problem is almost never data entry. It is that each figure answers a different question under a different rule — a midnight boundary, a payer utilization-day rule , an assessment tracking record , or a bed-hold provision . The number that reaches the board pack is whichever one was easiest to export.
Most operators can state how many admissions they had last month. Far fewer can state how many referrals arrived, how many were answered inside the referrer’s decision window, how many were declined and why, or how many accepted admissions never arrived. The pipeline below is the loss surface. Each stage produces an event; almost none of those events are captured with a timestamp, a decision authority, and a structured reason.
Two of these stages are worth separating out because they are systematically under-counted. The first is no-response loss : a referral that was never declined, only answered after the case manager had placed the patient. The second is accepted-but-never-arrived : an admission the building planned for, staffed for, and held a bed for, which does not appear in any denominator because nothing records a non-event. Both are census consequences of a referral process without an event record.
Nothing below is stored, transmitted, or captured, and no email is required to see the result. Every output is arithmetic performed on the figures you enter. It is not a projection, a forecast, or a representation of results, and no figure produced here is attributable to SeniorCRE.
This is arithmetic on your inputs, not a forecast. Unanswered referrals are not uniformly convertible, capacity and acuity capability constrain acceptance, and no part of this figure is attributable to SeniorCRE.
unreconciled bed days per year at your entered rate — occupancy points of ambiguity. This is not lost revenue; it is revenue and occupancy you cannot currently prove in either direction.
Key points
- No. A CRM manages the outreach relationship and a referral application manages the intake workflow. This pillar is about the record underneath both: one reconciled census with an explicit convention, bed state that reflects holds and pending discharges, and referral events captured with timestamps, decision authority, and structured outcome reasons — so conversion and occupancy figures can be sou…
- All five are real; they answer different questions under different conventions. Operational census answers who is here now, midnight census answers the occupancy state at a boundary, billed census answers which days are payable under payer rules, clinical census answers who is on the assessment record, and reported census is whatever reached the board pack. The failure is not that they differ — i…
- No. It performs arithmetic on figures you enter — beds, rate, referral volume, response and conversion rates, length of stay, variance days. Nothing on this page is a projection, a forecast, or a representation of results, and no output is attributable to SeniorCRE. If you want a figure you can defend, compute it from your own data under a stated methodology and put it in your own findings report.
- No. No vendor, EHR, CRM, referral-platform, health-system, or HIE integration is live in operator production today, and no clinical data is transmitted to any external party today. The architecture is read-oriented, with role boundaries, minimum-necessary field scoping, purpose recorded per disclosure, and an operator-readable audit trail. Connector scope is sequenced in the implementation plan a…
- Census integrity is a precondition for it. Quality Occupancy asks whether the occupancy you hold is the right occupancy — acuity match, payer mix, clinical capability, revenue integrity. That question cannot be asked honestly on top of a census figure whose convention is unknown, so census reconciliation sits underneath the measurement framework rather than beside it.
- 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 functio…
Frequently asked questions
- Is this a CRM or a referral-management application?
- No. A CRM manages the outreach relationship and a referral application manages the intake workflow. This pillar is about the record underneath both: one reconciled census with an explicit convention, bed state that reflects holds and pending discharges, and referral events captured with timestamps, decision authority, and structured outcome reasons — so conversion and occupancy figures can be sourced rather than asserted. Operators keep the intake tools they already run.
- Which census figure is the “real” one?
- All five are real; they answer different questions under different conventions. Operational census answers who is here now, midnight census answers the occupancy state at a boundary, billed census answers which days are payable under payer rules, clinical census answers who is on the assessment record, and reported census is whatever reached the board pack. The failure is not that they differ — it is that most operators cannot state which convention produced the number in front of them.
- Does the calculator predict revenue we will recover?
- No. It performs arithmetic on figures you enter — beds, rate, referral volume, response and conversion rates, length of stay, variance days. Nothing on this page is a projection, a forecast, or a representation of results, and no output is attributable to SeniorCRE. If you want a figure you can defend, compute it from your own data under a stated methodology and put it in your own findings report.
- Can SeniorCRE connect to our EHR, CRM, or referral platform today?
- No. No vendor, EHR, CRM, referral-platform, health-system, or HIE integration is live in operator production today, and no clinical data is transmitted to any external party today. The architecture is read-oriented, with role boundaries, minimum-necessary field scoping, purpose recorded per disclosure, and an operator-readable audit trail. Connector scope is sequenced in the implementation plan and rehearsed in validation environments first.
- How does census integrity relate to Quality Occupancy?
- Census integrity is a precondition for it. Quality Occupancy asks whether the occupancy you hold is the right occupancy — acuity match, payer mix, clinical capability, revenue integrity. That question cannot be asked honestly on top of a census figure whose convention is unknown, so census reconciliation sits underneath the measurement framework rather than beside it.
- What is the security posture for referral and census data?
- 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/census-integrity