Why Senior Housing & Care Got Stuck on Best-of-Breed
Every senior housing & care operator runs 8–12 vendors. None of them planned to. The fragmented stack is not a strategy — it is the accumulated residue of forty years of platforms that each entered the category from somewhere else and never quite met in the middle.
The origin map
Each major platform in this category was founded with a different starting entity. That starting entity shaped the schema, and the schema shaped everything after it.
The three founding mistakes (in hindsight)
1. Clinical-first platforms made the resident a patient. SNF reimbursement (MDS, PDPM, RUGs) was the gravitational center of the early platforms, so the schema was built around an encounter and a payer. Independent Living residents — who don’t have encounters in the SNF sense — became second-class citizens of a clinical record.
2. Real estate platforms made the resident a tenant. Yardi’s unit/lease/GL model is excellent for multifamily. It is structurally wrong for senior housing & care, where care intensity, payer mix, and acuity transitions matter more than lease terms. The clinical record gets bolted onto a tenancy model that can’t see it.
3. Workforce platforms made the shift an island. Scheduling, time, and agency platforms scaled by solving one painful workflow well — without owning census, acuity, or payroll. The result: workload thresholds and moral-injury signals live in tools that cannot see the resident.
Why unified is now inevitable
The operator’s data model — Resident, Care Plan, Ledger, Shift, Employee, Property, Entity, Audit Event — can finally be the spine of the platform instead of the integration layer. That is the architectural thesis behind SeniorCRE’s Operating Infrastructure Spec .
So what now?
For operators, the answer is not nostalgia for the old stack. The renewal calendar is a migration calendar. For each vendor coming up for renewal in the next 12 months, the question is no longer “which best-of-breed do we re-sign?” — it is “does this still belong outside the operator’s data model?” The answer, for almost every line, is no.
Frequently asked questions
- Why is senior housing & care software so fragmented?
- Because no incumbent platform started from the operator’s data model. PCC and MatrixCare grew out of SNF clinical reporting (MDS), Yardi out of real estate accounting, Eldermark out of AL community operations, and workforce/CRM tools out of horizontal SaaS. Each platform’s schema reflects its origin, not the operator’s reality. Integration became the only way to assemble the whole picture.
- Is best-of-breed a deliberate strategy?
- Almost never. It is the accumulated residue of acquisitions, EHR loyalty, well-meant pilots, and vendor M&A that left adjacent capabilities on different data models. Operators inherit best-of-breed; they rarely choose it.
- Why didn’t one incumbent just build a governed operating record?
- The cloud, multi-tenant Postgres, multi-layer tenant isolation, durable event streams, and AI tooling required to run a unified senior care OS economically only became viable in the last 3–5 years. Earlier incumbents would have had to rebuild on top of architectures that did not exist when they were founded.
- What makes unified inevitable now?
- The combination of regulatory consolidation (CMS MDS 3.0, QM Engine 2026), private-equity demand for portfolio-level reporting, and the maturation of cloud-native architecture make a single operator-centric data model the lowest-cost path. The Fragmentation Tax stops being defensible once it is named.
https://seniorcre.com/why-senior-living-best-of-breed