Loading...
SeniorCRE is the operator-controlled operating infrastructure for senior housing & care.
Fragmentation is the antagonist; the operator governs what counts as truth.
WellSky is a long-term & post-acute clinical suite. SeniorCRE is the Operator-Controlled Operating Record above retained systems — clinical, CRM, financial, workforce, compliance, and capital governed by declared authority and lineage.
Product status. SeniorCRE capabilities on this page are classified as built, validated, or roadmap — not built. No operator-production use is claimed. No third-party integration is live in operator production today; Founding Operator deployment dates are not yet scheduled and remain to be determined. Statements about WellSky® describe publicly available product materials as of August 2026.
When systems disagree, the operator governs.
SeniorCRE is the Operator-Controlled Operating Record above the systems an operator runs — clinical, CRM, financial, workforce, compliance, and capital evidence governed by declared authority and lineage.
WellSky Long-Term Care is a clinical and post-acute software suite with EHR, eMAR, MDS, therapy, and CarePort referral-network coverage for SNF, LTC, and senior housing & care operators.
The right comparison is not feature-by-feature parity. It is what each platform was built to do.
Where each platform invests engineering and product depth.
| Capability | WellSky | SeniorCRE (pre-production) |
|---|---|---|
| Clinical EHR / eMAR / MDS | Mature long-term & post-acute clinical suite | SeniorCRE EHR/eMAR option plus governed resident evidence with validation-stage MDS/QM/M32 controls |
| Hospital / HIE / FHIR interoperability | CarePort & WellSky network integrations | HL7/FHIR ingestion framework designed to normalize hospital and EHR feeds into the Operator-Controlled Operating Record — ROADMAP: no third-party vendor integration is live in operator production as of September 8, 2026 |
| Therapy & rehab (PT/OT/SLP) | WellSky Rehabilitation suite | Therapy scheduling and progress evidence governed with clinical and ledger lineage |
| Care coordination & referrals | WellSky CarePort referral network | Admissions, referrals, and CRM evidence reconciled to governed resident identity |
| Sales CRM & lead-to-move-in | Partner CRM / add-ons | CRM evidence reconciled with clinical resident identity |
| Financials / ledger / period close | Partner GL / billing modules | GL, AR/AP, and period-close evidence under governed entity hierarchy |
| Property & CRE / asset management | Not advertised as a native capability in publicly available product materials as of September 8, 2026 | Built-in CRE + asset layer for owners, REITs, and lenders |
| Workforce / acuity / scheduling | Partner workforce | Acuity-weighted scheduling with 80% nurse-workload alert |
| AI predictive (falls, risk, NOI) | Analytics modules are advertised; predictive fall, risk, and NOI models are not advertised as a native capability in publicly available product materials as of September 8, 2026 | SeniorCRE Intelligence grounded via SCRE-DEX; governance first → intelligence second → execution last |
| Portfolio rollups at request time | Reports + BI across modules | Target-state rollups from governed records after accepted sources support them |
| Capital / REIT / lender intelligence | Not advertised as a native capability in publicly available product materials as of September 8, 2026 | Capital layer — tenant-scoped reads + immutable audit |
How to read this table. In the WellSky column, a check means the capability is advertised in publicly available product materials as of August 2026; an ✕ means it was not advertised as a native capability in those materials — not that the product cannot do it. In the SeniorCRE column, the dashed marker means built, validated, or roadmap — not built, as stated in the row: no operator-production use is claimed today. WellSky® is a trademark of WellSky Long-Term Care and is used nominatively for identification and comparison only; capabilities on both sides evolve.
DESIGN INTENT — architecture direction, not a built capability
Referral and admissions tooling answers a bounded question well: can and should this patient be admitted. The larger question sits above it — given everything the operator knows about this resident, this building, this workforce, this payer, this portfolio and this operator’s own rules, what is the right economic and clinical decision, and can the operator prove why it was made? That is the question a resident / patient economic and clinical journey record inside the Operator-Controlled Operating Record is designed to carry.
Before admission
Referral through authorization
During the stay
Admission through discharge
After the stay
Discharge through reimbursement outcome
“Should we accept this resident?” — as a governed decision
Not clinical eligibility and reimbursement alone, but clinical fit, staffing capacity, labor cost, payer economics, historical outcomes, current census, building capability, regulatory risk and expected margin — each traced to an authoritative source, with exceptions named rather than smoothed over.
Worked example — synthetic inputs, illustrative only
Recommended disposition: ACCEPT — with staffing exception flagged
A disposition is a recommendation with its exception named. The operator, not the model, accepts the resident — and the record retains who decided, on what inputs, at what time.
Governance first. Intelligence second. Execution last. When systems disagree, the operator governs.
Scope boundaries
WellSky and comparable referral, EHR, CRM, payroll and accounting systems remain contributing sources under this architecture. The record ingests them and reconciles what happened from referral through outcome and economics.
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. |
| 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.
Not necessarily. WellSky remains a strong long-term and post-acute clinical suite. SeniorCRE governs retained systems first and can replace selected domains only where the operator chooses that configuration.
WellSky Long-Term Care is a mature clinical and post-acute platform with strength in EHR, eMAR, MDS, therapy, and CarePort referral network coverage. It works well for operators whose primary problem is clinical depth and acute-to-post-acute care coordination.
SeniorCRE preserves resident identity, definitions, authority, reconciliation, and lineage across assessment, MDS, care plan, eMAR, vitals, ledger, and bed evidence while respecting whichever source the operator declares authoritative for each decision.
SeniorCRE’s capital layer is target-state: ownership, REITs, PE, and lenders receive governed evidence only after operator approval, scoped access, and acceptance gates.
No fixed duration is published. Production entry is gated by source access, security review, reconciliation, clinical safety where applicable, and operator acceptance.
SeniorCRE is built by senior housing operators, advisors, and capital-market professionals — because care performance, labor performance, compliance risk, and NOI are now one system.