One Operator-Controlled Operating Record.Across the entire senior housing & care stack.

The industry has been told for two decades that senior housing & care requires 8–12 systems wired together — an EHR for clinical, a PMS for real estate, a CRM for move-ins, a scheduler for staff, a portal for families, an accounting connector for finance, and a BI tool for the board. Each may remain authoritative within its domain. The harder problem appears when legitimate systems disagree and a consequential decision requires one applicable definition.

SeniorCRE is built on a different first principle: the entities that exist in a senior housing & care operation are knowable, finite, and shared across every workflow. A resident is the same resident in clinical, billing, and family communication. A shift is the same shift in scheduling, payroll, and agency spend. A property is the same property in operations and in the REIT covenant. If those entities are knowable, the operator can govern their definitions, source authority, exceptions, effective periods, and lineage without surrendering control to a vendor-created version of truth.

CANONICAL · ENTITIES

The eight canonical entities

SeniorCRE-native functions use a governed schema for these eight entities. Retained systems keep their source records; the operating record preserves their context and applies operator-declared authority when they disagree.

• Resident — one chart across IL, AL, Memory Care, and Skilled Nursing. Acuity transitions do not create a new record.
• Care Plan — one plan, versioned, with full pull-forward context into MDS 3.0, ADLs, and eMAR.
• Ledger — one general ledger per entity, with PDPM, Medicaid, and private-pay reconciled at posting, not at close.
• Shift — one shift record powers scheduling, time, agency spend, and the moral-injury workload thresholds.
• Employee — one identity across HRIS, RBAC, license tracking, and audit log.
• Property — one property across operations, leases, capex, and investor rollups.
• Entity — Holding Co → Operator → Region → Property → Unit, with cascading permissions and rollups computed in the database.
• Audit Event — append-only, immutable, queryable for survey and SOC 2 evidence.

ARCHITECTURE · AS · MOAT

Why the architecture is the moat

Vendor changes can create mapping, reconciliation, and migration work. An Operator-Controlled Operating Record makes the governing definitions, authority rules, exceptions, and lineage portable: the operator controls the record and its export. Vendor change remains a procurement decision rather than an unrecorded change in enterprise meaning.

Cross-functional decisions depend on data that lives in multiple legitimate systems. Connecting or matching those records supplies context; it does not establish authority. The operator declares which definition and source govern each decision, and the operating record preserves the alternate valid value and authority lineage.

GOVERNANCE · IN · SCHEMA

Governance is part of the architecture, not bolted on

multi-layer tenant isolation is enabled on every public table. Access is mediated by server-side access helpers functions tied to the authenticated session and the operator hierarchy. A role enum gates every mutation. Tenant isolation is enforced at the database layer, not the application layer — meaning a bug in application code cannot leak data across operators. The immutable audit log is append-only at the schema level and is the evidence base for state survey and SOC 2 future assurance reporting. SeniorCRE does not claim SOC 2 certification or its own SOC 2 report.