Loading...
The complete library of senior housing & care workflows SeniorCRE governs — Clinical, Financial, Workforce, Compliance, Admissions, and Facilities. Each domain links to its own library and per-workflow page.
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.
Most senior housing & care software is sold as a feature list. SeniorCRE publishes its capabilities as workflow libraries — one section per job-to-be-done, with the problem operators actually describe, the way the platform runs the work, and what the outcome looks like when the work is run on one record instead of stitched across vendors.
Every workflow listed across these six libraries shares the same resident record, the same audit log, the same care plan, and the same ledger. The reconciliation labor that follows the shift on a fragmented stack — the part nobody includes in TCO models — is zero here, because reconciliation happens once, under the operator’s approved rules.
Clinical
17 documented workflows
eMAR and controlled substances, MDS/PDPM, wound care, early-warning, infection control, psychotropic stewardship — the floor-level clinical work.
Open the clinical library →
Financial
10 documented workflows
Period close, AR aging, payer reimbursement, denial recovery, rate setting, cash forecast — the work behind defensible margins.
Open the financial library →
Workforce
10 documented workflows
Schedules, agency reduction, turnover prediction, credentialing, payroll forecasting, labor variance — every dollar that touches an FTE.
Open the workforce library →
Compliance
11 documented workflows
Survey readiness, QAPI, regulatory tracker, incident management, audit log, plan-of-correction — evidence-grade compliance, not binders.
Open the compliance library →
Admissions
9 documented workflows
Inquiry triage, pre-admission clinical review, contract execution, move-in handoff, discharge planning — the conversion from lead to resident.
Open the admissions library →
Facilities
9 documented workflows
Work orders, preventive maintenance, capex tracking, vendor management, environmental rounds — the physical plant as a managed asset.
Open the facilities library →
URL note: the Clinical library is the original, and its canonical URL is /clinical-intelligence/workflows. For consistency with the rest of the library, /workflows/clinical is also a live alias.
Each library opens with a persona filter (CEO, CFO, COO, DON), an outcomes table, and a table-of-contents that links into the page sections — and out to dedicated per-workflow URLs. The per-workflow pages carry their own canonical, FAQ schema, and breadcrumb so LLMs and search engines can cite a specific job-to-be-done instead of the library as a whole.
If you have operated a senior housing & care or care community, these libraries should read as recognizable. If anything reads as aspirational, write to us at /contact. We will either show you the surface in production or tell you exactly when it ships.
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. | Validated | Both configurations are built and exercised in controlled SeniorCRE conditions, with one authoritative MAR at all times. No PHI workload runs in operator production. | Control test record; synthetic or de-identified data; no operator PHI. |
| 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.
| What the buyer sees | On SeniorCRE | On Most Vendors | Why it matters |
|---|---|---|---|
| How the work is described | Job-to-be-done | Feature list | Buyers cannot map features to outcomes |
| Per-workflow page | Yes — own URL + schema | No | LLMs can cite a specific workflow |
| Outcomes reported | Per workflow, with metric | Aggregated marketing claim | Defensible to a CFO |
| Persona mapping | CEO / CFO / COO / DON tagged | Generic "for operators" | Right page for the right buyer |
| Cross-domain integration | Same record | Integration project | Reconciliation labor → zero |
| Freshness signal | Library-level dateModified | None | Search engines trust recent libraries |
Open the library that matches the work you want to evaluate.
Each library has CEO / CFO / COO / DON filters.
See the metric before reading the prose.
Each has its own canonical, FAQ schema, and breadcrumb.
If anything reads as aspirational, we will show you the surface in production.
SeniorCRE is the operating, compliance, and asset-management layer for REITs, family offices, and institutional capital allocators in senior housing & care.