Resident lifecycle record
The resident economic and clinical journey record
A resident economic and clinical journey record is one governed object, per resident, that preserves the full lifecycle from hospital referral to reimbursement outcome — what the operator knew at the moment of the accept-or-decline decision, what the stay consumed clinically and in labor, and what it actually produced. Because expectation and outcome are held in the same definitions with a named authoritative source per field, the variance between them becomes a governed record rather than an argument between reports.
- Canonical object
- One record per resident, referral through outcome
- Disciplines
- Definitions · Authority · Reconciliation · Lineage
- Authority chain
- EVIDENCE → DISAGREEMENT → AUTHORITY → OPERATOR-CONTROLLED OPERATING RECORD → INTELLIGENCE → EXECUTION
- Maturity
- DESIGN INTENT — architecture decided, not deployed
Evidence posture. The resident economic and clinical journey record is a DESIGN INTENT architecture: the canonical object, its authority rules and its lineage requirements are decided, and no part of it is deployed, integrated with a third-party system, or exercised on operator data. Every figure on these pages is a worked example on synthetic inputs, not a benchmark, forecast, or observed result. Last reviewed August 30, 2026.
The lifecycle being governed
Most operators hold each of these stages somewhere. Very few can traverse them as one record. The consequence is familiar: decisions made late, on numbers no one fully trusts.
- 01Hospital source
- 02Referral platform
- 03Clinical characteristics
- 04Operator rules
- 05Census & capability data
- 06Payer & reimbursement data
- 07Admission decision
- 08Authorization
- 09Admission
- 10Clinical course
- 11Labor consumed
- 12Length of stay
- 13Outcome
- 14Reimbursement
- 15Denial
- 16Readmission
What the record preserves
Referral through authorization
Before admission
What the operator knew, and could prove it knew, at the moment the accept-or-decline decision was made.
- · Referral source and referring hospital or platform
- · Clinical acuity and documented care requirements
- · Payer, plan and authorization posture
- · Estimated reimbursement under the applicable rate structure
- · Expected labor intensity by discipline and shift
- · Available service capability in the specific building
- · Acceptance rationale, including the operator policy applied
Admission through discharge
During the stay
The operating record of the stay itself, kept in the same definitions the pre-admission estimate used.
- · Census status and unit or bed assignment
- · Labor utilization: worked hours, agency hours, overtime
- · Clinical changes, assessments and acuity movement
- · Incidents, care requirements and interventions
- · Pharmacy and therapy utilization
- · Authorizations, continued-stay reviews and denials in flight
- · Length of stay to date against expected length of stay
Discharge through reimbursement outcome
After the stay
The closing of the loop: what actually happened, reconciled field-by-field against what was expected.
- · Actual reimbursement collected, net of adjustments
- · Actual labor cost attributable to the stay
- · Margin contribution under the operator’s own definition
- · Discharge disposition and hospital transfer, if any
- · Readmission within the operator’s measurement window
- · Clinical outcome as documented by the clinical authority
- · Denial and appeal history with lineage to the underlying documentation
What governance means here
| Discipline | Applied to the journey record |
|---|---|
| Definitions | One meaning for census, acuity, worked hours, authorized days, and margin contribution, applied identically before and after the stay. |
| Authority | A named authoritative source per field. Clinical authority stays clinical; financial authority stays financial; neither silently overwrites the other. |
| Reconciliation | Estimated reimbursement, expected labor and expected length of stay are reconciled against actuals — the variance is a governed record, not a report footnote. |
| Lineage | Every value carries its source system, capture time, and survivorship rule, so an accept or decline decision can be reconstructed months later. |
| Exceptions | Where a decision departs from operator policy or from capacity, the exception is named, attributed and retained rather than absorbed. |
The decision the record exists to serve
The highest-consequence moment in the lifecycle is a single question: should we accept this resident? Everything upstream is input to it, and everything downstream either confirms or contradicts it.
What this is not
- It is not a referral engine and does not seek feature parity with referral or admissions point solutions.
- It does not make employment, clinical or coverage determinations automatically.
- The operator may retain an EHR, CRM, payroll or accounting system, or assign selected system-of-record functions to SeniorCRE. Govern first. Replace only by choice.
- It does not publish operator data, customer names, or observed financial outcomes.
Frequently asked questions
What is a resident economic and clinical journey record?
It is a single governed record, per resident or patient, that preserves what the operator knew before admission, what happened during the stay, and what the stay actually produced clinically and financially — held in one set of definitions with a named authoritative source for every field.
How is this different from a referral or admissions tool?
A referral tool moves the referral. The journey record governs the decision and its consequences: the inputs the accept-or-decline decision used, the lineage of those inputs, and the reconciliation of expected reimbursement, labor and length of stay against actuals after discharge. SeniorCRE does not pursue referral-engine feature parity.
Does this require replacing our EHR, payroll or accounting system?
No. Govern first, replace only by choice. SeniorCRE clinical record surfaces are built; medication administration and eMAR remain roadmap — not built. It can run alongside an incumbent clinical system read in one direction, with the incumbent MAR authoritative.
Is this capability available today?
No. The resident economic and clinical journey record is DESIGN INTENT: the canonical object, authority rules and lineage requirements are decided, and it is not deployed, integrated with a third-party system, or exercised on operator data. Every figure published about it is a worked example on synthetic inputs.
Who has authority over clinical fields in the record?
Clinical authority remains clinical. The record carries clinical determinations from the clinical system of record and never derives, overrides, or infers them through financial logic.
Continue
- Canonical record: The operating record · One Operator-Controlled Operating Record
- Authority: Operator Authority Chain™ · Data integration
Coherence before Intelligence. When systems disagree, the operator governs.
Bring one contested admission decision
The useful version of this conversation is a referral you accepted or declined last quarter, and whether your systems can still reconstruct why.