Loading...
The operating record is designed and not yet implemented in any community. PIIEL, WRIE, LCIFS, and ALIRP — illustrative surfaces use synthetic or de-identified data. Zero external user logins. Human-in-the-loop on every clinical decision. Outcome figures shown on this page are industry benchmarks or internal validation-set estimates not measured in operator production.
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.
Four named AI systems are built with synthetic or de-identified data: PIIEL (physician intent intake), WRIE (workforce retention prediction), LCIFS (labor cost forecasting), and ALIRP (asset lifecycle and CapEx). Each draws from operational data already flowing through the platform — no additional data entry, no external user logins, human-in-the-loop on every clinical decision. A future operator validation is intended to scope one community, one workflow, and one operator-approved outcome metric; timing remains governed by acceptance gates. No outcome percentages are published on this page; outcome validation is not measured in operator production.
The build → validate → prove governing thesis.
Where the AI surfaces ladder into the clinical chart.
The substrate every AI surface writes to.
DALLAS, TX · AI BRIEF
Most senior housing & care AI is demoware — a vendor slide deck with vendor-reported ROI and a roadmap dated next year. SeniorCRE has built proprietary AI systems against the platform's operator-controlled authority model: PIIEL converts external physician orders into nurse-executable workflows; WRIE scores staff turnover risk from operational signals; LCIFS forecasts labor cost from census, scheduling, and acuity; ALIRP times capital asset replacement before failure. Every surface is human-in-the-loop and immutably audited. The outcome percentages on this page are industry benchmarks or internal validation-set estimates used to size opportunity — operator-validated pilot results are pending publication.
No external user — physician, pharmacist, vendor, or family member — ever logs into SeniorCRE.
Converts external physician orders (HL7, FHIR, PDF, verbal) into structured, nurse-executable workflows. Designed; illustrative surfaces use synthetic or de-identified data. The reduction figures below are industry-benchmark targets used to size opportunity — operator-validated pilot results are pending.
Machine-learning models score staff retention risk from behavioral operator-authorized signals in the designed workflow. Designed; illustrative surfaces use synthetic or de-identified data. Turnover-reduction figures are industry benchmarks — operator-validated results are not measured in operator production.
Integrates census, scheduling, overtime, and acuity to forecast labor cost and surface drift early. Designed; illustrative surfaces use synthetic or de-identified data. Accuracy and variance figures are internal validation-set estimates — operator pay-period validation is not measured in operator production.
Tracks capital assets from acquisition through depreciation to replacement, with predictive maintenance and CapEx forecasting. Designed; illustrative surfaces use synthetic or de-identified data. Failure-reduction and lifespan figures are industry benchmarks — operator-validated results are pending.
The constraint is deliberate. It collapses the PHI attack surface, removes credentialing overhead from the operator, and keeps the licensed clinician in the loop on every clinical decision. AI assists. People decide.
Evidence & Provenance
Because choosing the governing number is an act of authority, and authority belongs to the operator. SeniorCRE’s AI systems reason from the governed record and its evidence; they do not resolve conflicts between systems on their own.
The operator governs. SeniorCRE records what governs. The operating record is designed; it is not yet implemented in any community or in operator production.
See the evidence architectureGovernance first → intelligence second → execution last. The governing thesis behind every AI surface in the platform.
Co-pilot, never autopilot. Augments the clinician inside the chart — never replaces judgment.
Why senior housing & care needs an operator-controlled operating layer, not a bolt-on assistant.
granular role-based access, immutable audit logs, and the boundary between decision support and SaMD.
What ships now, what is in pilot, and the regulated capabilities we will not build.
Forecasting, workforce, and portfolio dashboards governed by operator-controlled authority.
How operational data becomes investment-grade signal for owners, REITs, and capital partners.
AI-assisted MDS reconciliation across SNF, AL, MC, and IL — under one payer-rule engine.
Passive sensing for fall risk, agitation, and high-acuity events — surfaced to staff, not families.
HL7, FHIR, PDF, and verbal orders into nurse-executable workflows. Built today; outcomes not measured in operator production.
Score staff turnover risk from 40+ behavioral signals. Built today; turnover-reduction figures are industry benchmarks.
Forecast labor and surface drift before it hits the P&L. Built today; accuracy figures are internal estimates.
Predictive maintenance, CapEx forecasting, and depreciation in one asset spine.
How agents and assistants ladder into operator workflows without external user logins.
How acquirers use AI through due diligence, underwriting, and close.
C3 operational intelligence surfacing portfolio risk and operational alpha.
Internally operated agents for intake, reconciliation, and operational triage.
In-product assistant with action-based query params and Gemini 2.5 Flash.
Operator-grade content drafts — never autonomous, always reviewed in-product.
WebRTC ambient dictation with ElevenLabs fallbacks across the clinical workflow.
Conversational query patterns operators and families use to find senior housing & care.
Indexed query set powering voice-optimized landing pages.
Pilot. Prove. Scale. Capability is built. Outcomes are validated in pilot, not in a deck.
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.
| Dimension | SeniorCRE | Hospital-AI vendor bolt-on | Pilot-stage point AI |
|---|---|---|---|
| Build status | 4 proprietary systems built | Pilots, decks, future roadmap | Single-workflow trial |
| External user logins | Zero — structured intake only | Physician portals + family logins | Varies by vendor |
| Acuity coverage | SNF · AL · MC · IL native | SNF-only or acute-care retrofit | Single setting |
| Audit trail | Immutable, append-only, signed | Best-effort logging | Often missing |
| ROI validation | Operator-baseline, day-60 threshold | Vendor-reported | Anecdotal |
| Data source | One Operator-Controlled Operating Record | Federated extracts | Per-vendor silos |
One community, one AI surface, one outcome metric. Real production data under NDA. Day-60 go / no-go threshold pre-agreed with the operator.
Expand to 3–5 communities with metric definitions held constant. Independent operator-baseline validation alongside override-rate reporting.
Portfolio rollout in phased waves. Same metric, same math. Quarterly model and prompt audit, versioned and signed.
Override rate per AI surface reported alongside outcome metric. Role-based access, tenant isolation, and audit-log integrity re-validated.
Human-in-the-loop on every clinical decision. No FDA SaMD-class diagnostic AI. No external user logins. Ever.
SeniorCRE is the operating, compliance, and asset-management layer for REITs, family offices, and institutional capital allocators in senior housing & care.
Modern agentic platforms increasingly control AI execution through identity, permissions, deterministic business rules, human approvals, validations, and audit trails. Those controls matter, they are becoming standard properties of enterprise software, and SeniorCRE claims none of them as an invention.
But they begin after another institutional question has been answered: what information is the enterprise authorized to rely upon? If two operating infrastructure contain different legitimate values, an agent can be perfectly authorized to execute while still acting on the wrong definition.
SeniorCRE governs the path from evidence to the Governing Record before SeniorCRE Intelligence and controlled execution apply.
Illustrative — not operator data
An AI agent authorized to update the capital forecast
System A
Operational occupancy — 91.7%
System B
Revenue occupancy — 89.9%
Both values are valid.
Only then: AI recommendation → decision → authorization → execution
Permission to execute does not establish authority over truth.
An agent can be authorized to act. The operator still determines what governs.
Definitions, source authority, reconciliation state, lineage, and human adjudication are built; external operator deployments have not yet begun. Enforcement of truth policy and action policy through a single agent gateway — including any MCP-exposed path — is architecture and design intent on the build roadmap, not a live capability.
The operator’s. A summary is only as trustworthy as the record it was handed: definitions, source authority, reconciliation state, and lineage declared by the operator in the governed operating record. When systems disagree and reconciliation has not been applied, the correct behavior is refusal, not selection — the model must not choose a convenient value in place of the operator’s authority.
Architecture & future state
SeniorCRE is building toward a governed multi-agent operating intelligence system for senior housing & care, designed to evolve into the control plane connecting the systems operators keep to the decisions people and AI are authorized to make.
Foundation
Operator-controlled operating infrastructure
Design intentRecord
Operator-Controlled Operating Record
Design intentIntelligence
Governed multi-agent operating intelligence system
RoadmapAuthority
Operator Authority Chain™
DoctrineFuture destination
Governed operating intelligence & control plane
RoadmapSolid steps show the designed sequence, not proven readiness. The Operator-Controlled Operating Record is designed and not yet implemented in any community. Dashed steps remain roadmap, not built. Clinical judgment, medication decisions, and care-plan changes stay with licensed humans.
Inheriting a user’s permissions is becoming a standard property of enterprise AI, as are confirmation gates and audit trails. Permission to act is not authority to determine what governs. AI should inherit not only user permissions, but operator-defined truth, source authority, and reconciliation state.
Epistemic authority — what the AI is allowed to believe
Definitions, source authority, reconciliation state, and lineage to origin. Governed before any decision is proposed, and governed across systems that are each independently authoritative.
Execution authority — what the AI is allowed to do
User and agent role, decision rights, required approvals, and execution permissions. Inherited permissions belong here — and they say nothing about which system’s fact governs.
The question an operator should put to any AI-enabled system: before the AI acts, can the operator determine which system’s fact governs when CRM, EHR, workforce, and finance disagree? Governing both layers in one place — the Operator-Controlled Operating Record — is what SeniorCRE is designed to do. Enforcement of the two policy layers as a single gateway is on the build roadmap; external operator deployments have not yet begun.
SeniorCRE is operator-controlled operating infrastructure for senior housing & care. AI in senior housing & care only earns trust when the operator governs the record it runs on. The governing rules, use classes, and data-handling posture are published rather than described.