Loading...
SeniorCRE is the operator-controlled operating infrastructure for senior housing & care. Beneath the Operator-Controlled Operating Record sits Evidence & Provenance, layer 2: the sources, definitions, timing, lineage, and conflicts behind each operating fact. When systems disagree, the operator governs.
Institutional trust markers
Multi-community operators, REITs, private equity, lenders, and multi-state portfolios evaluate the same nine markers before they sign. Each one is documented, enforced in the platform, and reviewable in the Trust-by-Design procurement package.
HIPAA-safeguarded controls; no SOC 2 certification or report claimed. No completed independent penetration-test report claimed.
HIPAA-safeguarded controls today: encryption at rest and in transit, BAA execution, PHI segregation, and signed-URL access to PHI buckets.
Operator-controlled definitions, source authority, reconciliation, and lineage across clinical, financial, workforce, compliance, and capital surfaces. Multi-tenant with database-enforced isolation.
A documented ingestion path for operator-supplied clinical, property, and accounting exports. Named-vendor connectors are ROADMAP; no third-party integration is live in operator production today. AI reads only the fields the operator declared readable.
SOC 2 in progress (underlying AWS infrastructure maintains its own SOC 2 reports), MFA required, session timeout, concurrent-session limits, continuous automated vulnerability scanning.
Immutable, append-only logs with UTC-millisecond timestamps, full user/session context, and 7-year retention.
33-role RBAC hierarchy. Property-level tenant and role gates enforced at the API layer (Fastify + tRPC on AWS) with WorkOS-authenticated sessions and defense-in-depth checks in PostgreSQL.
Holding Co → Operator → Region → Property → Unit hierarchy. Portfolio rollups computed from the Operator-Controlled Operating Record at request time. Designed for multi-state, multi-payer, multi-entity ownership.
Full detail on each marker, evidence inventory, and the Trust-by-Design procurement package live on the Trust Center.
Status, stated plainly
This page describes architecture. The evidence card and occupancy example are illustrative, using synthetic data; they are not in operator production, and no figure on this page comes from an operator.
Don't just ask whether your data is governed. Ask who governs what it means.
The evidence beneath the operating record. SeniorCRE preserves the sources, definitions, timing, lineage, conflicts, and governing authority behind important operating facts. When systems disagree, it does not silently average, overwrite, or let AI choose the answer. It exposes the evidence, and the authorized operator determines what governs.
Who decides what governs.
Where governed facts live.
EHR, accounting, CRM, workforce, payroll — kept as they are. Each assertion stays historically true as an assertion.
Original assertion, source, definition, timestamp, and transformation history preserved. Evidence does not decide what governs.
Material disagreement exposed. Disagreement is not necessarily an error.
Who may decide, for which purpose, scope, and period.
The governing determination, authority, purpose, rationale, lineage, effective period, and supersession history.
Reasons from governed context. Model confidence never creates organizational authority.
Acts within explicit identity, authorization, policy, limits, and audit.
Right means right for the purpose, under the authority established by the operator. SeniorCRE establishes what is authorized to govern before SeniorCRE Intelligence reasons from it.
Know which numbers you can rely on.
Know what changed and why.
Know what deserves attention and what happens next.
The EHR says 91.7%. Accounting says 89.9%. Two systems, two honest answers, measuring different things. SeniorCRE does not average them or pick one. It shows both, the definition behind each, and why they differ — then the authorized operator sets which definition governs which decision. All figures here are illustrative.
Evidence card · example
GovernedSynthetic example, not evidence of a working operating record. Not in operator production.
Source received but not reconciled.
Multiple sources support the operating fact.
Material disagreement exists between systems.
An authorized operator has set the governing value or definition.
Evidence is older than the operator’s freshness threshold.
SeniorCRE does not decide business truth. It establishes and preserves the evidence; authorized operators decide what governs.
Intelligence does not establish authority. Intelligence operates within authority already established by the operator. Coherence before Intelligence.
The operator governs. SeniorCRE records what governs. Intelligence operates from there. Model confidence never creates organizational authority.
How do we create a consistent representation of the data?
Consolidating, matching, deduplicating and normalizing are real, valuable work.
Which assertion governs for a defined purpose, under whose authority, based on what evidence, and with what decision lineage?
SeniorCRE intends to prove the architecture against consequential operating disagreements, not by demonstrating software features. These are proof requirements, not additional architecture layers. Each proof must pass every step:
Candidate proof areas: census and occupancy; revenue and financial reconciliation; workforce and labor; CRM and move-ins; clinical and operational exceptions.
Status: planned proof. No proof under this standard has been completed in operator production, and no result is claimed.
Bring us one consequential operating disagreement. Request an Executive Briefing
licensed units (illustrative)
after units taken out of service (illustrative)
available to lease (illustrative)
configured for care (illustrative)
Each may be a legitimate source assertion. The question is not which number is wrong — it is which denominator governs for regulatory reporting, owner and lender reporting, staffing, or daily operations.
Illustrative figures for a hypothetical community. Not an operator, property, or measured result.
One governed fact can depend on another. When the denominator changes, everything computed from it carries that lineage. No causal relationship is claimed.
Once operating context is governed, SeniorCRE Intelligence can analyze accepted operating facts — not only contested ones.
This is inference from governed context. It is not a governing determination, and it creates no organizational authority.
Two legitimate sources give conflicting answers for the same purpose.
Govern it.
A definition or rule must be decided once, then applied consistently.
Define and configure it.
One system or person has not yet received newer information.
Surface and route it.
Two systems hold complementary information never joined.
Connect it.
The fact is accepted but still needs interpretation.
Analyze it.
A capability moves upward only when evidence supports the next level.
Never present architecture as production evidence.
Show me the evidence. Show me the disagreement. Show me who had authority. Show me why it governs.
Status as of September 29, 2026 (last modified 2026-09-29)
| Claim | Evidence step | What is true today | Proof to inspect |
|---|---|---|---|
| Operator and portfolio workspace foundation built (roles, hierarchy, entity tree). | Validated | Provisioning controls have been exercised repeatedly in controlled SeniorCRE conditions, including the operator onboarding wizard. Not yet performed for an operator in production; no standard duration is published. | Control test record; synthetic or de-identified data; no operator PHI. |
| Single-community acceptance boundary. | Architecture designed | A gate sequence derived from the migration and acceptance model. No community has gone live for an operator, so no observed duration exists. | Written deployment plan and acceptance-gate model. No execution record exists. |
| Portfolio-wide rollout acceptance across multi-community scope. | Architecture designed | A wave-cadence model from the deployment plan. Sequencing depends on community count, system count, data condition, source access, and operator authority decisions. Not a completed rollout. | Written deployment plan and acceptance-gate model. No execution record exists. |
| Connectors to PointClickCare®, MatrixCare®, Yardi®, and QuickBooks®. | Validated | Ingestion and normalization exercised against synthetic and de-identified extracts in controlled SeniorCRE conditions. No third-party integration is live in operator production. | Control test record; synthetic or de-identified data; no operator PHI. |
| Operator-Controlled Operating Record: source authority, reconciliation, field-level lineage. | Architecture designed | The Operator-Controlled Operating Record is designed and not yet implemented in any community. Authority rules, reconciliation, and field-level lineage are design intent; synthetic examples do not establish working governance. | Written deployment plan and acceptance-gate model. No execution record exists. |
| Clinical configuration: SeniorCRE as clinical system of record, or alongside an incumbent eMAR read one direction only. | Architecture designed | Designed, not built for operator use. SeniorCRE's native medication administration and eMAR are roadmap and not built; the read-only configuration alongside an incumbent eMAR depends on the Operator-Controlled Operating Record, which is designed and not yet implemented in any community. One authoritative medication record at all times is a design rule. | Written deployment plan and acceptance-gate model. No execution record exists. |
| Barcode-verified administration with an automated five-rights check at the point of medication pass. | Architecture designed | Not built. Corrected September 7, 2026: earlier pages, operator training guides, and generated answers described this control as running, which was false. Implementation boundary: four of the five medication scan surfaces open a camera preview with no decoder and match only a manually typed NDC; one mobile surface decodes frames through the browser-native BarcodeDetector API where the browser supports it (Chromium/Android; not iOS Safari, not most desktops) and compares the NDC alone. No decoding library is bundled, no surface verifies resident, dose, route, or time, and no scan result blocks an administration. The five rights are verified by the administering clinician, not by SeniorCRE. | Build-queue entry with scope and dependencies. No implementation exists. |
| Live write-back into operator payroll and scheduling systems. | Architecture designed | Specified and in the build queue. Read-side ingestion only today. | Build-queue entry with scope and dependencies. No implementation exists. |
| Implementation effort required from the operator. | Architecture designed | Deployment is staged, not effortless: platform access, source access, authority rules, reconciliation, security review, and any history migration are scoped work with operator-side effort. Any claim of zero implementation would be false. | Written deployment plan and acceptance-gate model. No execution record exists. |
Status and evidence class as of September 29, 2026. SeniorCRE has no operator-production deployment. Public timing is gate-based and operator-specific; no standard go-live duration is published. Maintained and reviewed by John Hauber, Founder, SeniorCRE, LLC. A medication-safety control was described on earlier pages as running when it was not; that correction is published in full at /medication-safety-claim.
SeniorCRE is the operating, compliance, and asset-management layer for REITs, family offices, and institutional capital allocators in senior housing & care.