Loading...
SeniorCRE is the operator-controlled operating infrastructure for senior housing & care.
Fragmentation is the antagonist; the operator governs what counts as truth.
What happens when both numbers are right? Mastering decides which value survives when records describe the same fact — and Skypoint ships that layer today. The authority layer above it decides which of several legitimate definitions governs a given decision. An operator needs both, and this page does not pretend they are the same purchase.
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 Skypoint describe publicly available product materials as of September 9, 2026.
When systems disagree, the operator governs.
SeniorCRE is the operator-controlled operating infrastructure for senior housing & care. It holds the operator's declaration of which legitimate definition and which source govern a particular consequential decision — and preserves the competing valid reading rather than electing one surviving value.
Skypoint runs a data and AI platform for senior housing, care and post-acute providers. Its current material describes skyMDM master data management across clinical, operational, financial, staffing, billing and CRM systems; a connect, clean, validate, enrich, map, match and merge pipeline; schema and terminology mapping into one unified ontology; operator-defined validation and configurable field-level survivorship rules including "most trusted source"; human review of ambiguous matches; field-level lineage with auditable and reversible merges; and a golden record described as the ground truth its AI agents run on, consumed by skyCommand, skyCare, skyInsights and skyAgent (publicly available product materials reviewed September 9, 2026).
The right comparison is not feature-by-feature parity. It is what each platform was built to do.
These are different questions, and the second one is not a feature of the first. Reviewed September 9, 2026.
Which value is correct?
Entity resolution, validation, schema and terminology mapping into one ontology, configurable field-level survivorship, human review of ambiguous matches, field-level lineage with reversible merges, and a master record that applications and agents can consume. This is real engineering and it is hard to do well. Skypoint publicly documents all of it, and if an operator does not have this layer, they should buy it.
Available today. Buyable today. Skypoint ships it and markets HITRUST r2 certification and HIPAA compliance alongside it (publicly available materials reviewed September 9, 2026). SeniorCRE treats this layer as shared category ground, not as a differentiator, and holds no equivalent third-party certification.
Which correct answer has authority here?
Not a data-quality case. Clinical or operational occupancy of 91.7% and revenue occupancy of 89.9% can both be correct. A survivorship rule that elects one of them globally does not clean the data; it destroys the meaning the other one carried, and the staffing decision and the covenant decision needed different ones. The authority layer is where the operator declares which definition governs which decision, keeps the competing valid reading, and records why that definition had authority when the decision was made.
Available today. Not buyable today, from us or, as far as we can document, from anyone. We have not identified public documentation — from Skypoint or another vendor in this category — describing authority that varies by decision rather than by mastered field, or two independently valid values preserved with neither elected as the survivor (reviewed September 9, 2026). SeniorCRE is building this layer and has exercised it only.
If the same resident exists three times under three spellings, no amount of declared authority produces a number worth governing. Identity resolution, validation and survivorship come first, and an operator who skips them is governing noise. This is why this page does not argue against master data management — it argues that mastering is the floor, not the ceiling.
A survivorship rule answers "which value is most trusted for this field." It is the wrong instrument for "which of two legitimate definitions the enterprise authorized for this decision," because the correct answer changes with the decision and both readings have to survive. Force that question through a survivorship rule and the operator gets one number, no record of the competing reading, and no way to reconstruct why it governed.
If an operator needs a platform now, the mastering layer is available now and we are not a candidate for it. What an operator can do now is stop treating the authority layer as something a vendor grants later: write it into the evaluation. Ask any vendor — including us — the four questions below, and require that definition authority stays with the operator rather than with whichever system produced the number.
An operator can keep the systems they run today and have SeniorCRE govern what those systems produce, or deploy SeniorCRE itself as the system of record for functions they choose, including its own EHR and eMAR. Domain authority belongs where it belongs. Decision authority belongs to the operator.
Skypoint has built one of the more sophisticated data-and-agent architectures in senior housing & care technology, and this page gives it full credit. Master data management is excellent architecture when several records represent the same underlying fact. The distinction begins where two values are both legitimate and merging them would destroy meaning.
Ground truth is not something a platform gets to declare. The operator declares the definition, assigns source authority, governs reconciliation, and preserves the decision with lineage.
Unifying, matching, merging, deduplicating, or remembering data improves context. It does not establish authority when legitimate systems disagree.
One person.
These records should normally be matched, mastered, and reconciled. One canonical representation is the right answer, and master data management is the right tool.
Both may be correct.
Neither is bad data. Neither should globally overwrite the other. The question is which definition the operator has authorized to govern the decision in front of them. Illustrative example; figures are not operator results.
WHEN SYSTEMS DISAGREE
|
IS ONE VALUE WRONG?
/ \
YES NO
| |
DATA QUALITY / MDM BOTH MAY BE VALID
| |
CORRECT / MASTER DEFINITION + AUTHORITY
RECORD |
DECISION CONTEXT
|
GOVERNED TRUTHStaffing
Clinical / operational occupancy
91.7%
Capital planning
Revenue occupancy
89.9%
No globally surviving value is required. Authority changes with the decision context, and both readings stay preserved with the definition that was in force.
A golden record answers
“What is the mastered value?”
An Operator-Controlled Operating Record answers
“Which valid definition governs this decision?”
| Dimension | Master data / golden record | Operator-Controlled Operating Record |
|---|---|---|
| Problem being solved | Multiple representations of the same entity or fact | Multiple legitimate definitions or authorities affecting a consequential decision |
| Typical action | Match, merge, deduplicate, standardize | Define, authorize, reconcile, adjudicate |
| Conflict handling | Determine which field value survives | Determine which valid meaning governs this decision |
| Authority | Field- or source-based survivorship and mastering rules | Definition + decision context + domain + source + effective period + operator policy |
| Result | Golden / master record | Governed truth for a defined operating purpose |
| Preservation | Source lineage and merge history | Competing valid facts, plus authority and decision lineage |
| AI role | Ground AI in clean, linked, mastered data | Ground AI in operator-authorized meaning for the decision being made |
| Execution | Provide clean context to downstream systems | Govern truth before recommendation, authorization, and permitted execution |
How to read this table. It contrasts two architectures, not two vendors. No column asserts that any named product lacks a capability. Master data management and operator-controlled operating governance answer different questions and can coexist in the same estate. SeniorCRE capability descriptions reflect built, validated, or roadmap — not built; no operator-production deployment has completed.
Data lineage tells you where a number came from. Authority lineage tells you why that number governed. Both matter; they are not the same record.
Source lineage
Where did the fact originate?
Transformation lineage
What happened to it technically — mapping, standardization, merge?
Authority lineage
Why did this definition and this source govern?
Decision lineage
Which decision relied on it, who authorized it, and what followed?
As AI agents become capable of acting directly across enterprise systems, the critical control point moves upstream. Before an agent acts, the enterprise must know not only where a fact came from, but whether that definition is authorized to govern the decision being made.
Govern the truth before you automate the decision. When systems disagree, the operator governs.
Domain authority belongs where it belongs. Decision authority belongs to the operator. Source precedence is not the same as decision authority.
Scope of authority
Skypoint now publicly describes skyComply as a system of record for legal, risk and compliance and as “one governed record” across resident and workforce risk. It also describes human-attested determinations, evidence-gated closure, field-level change history, policy-linked workflows and a governance layer spanning EHR and training environments. Those are substantive governance capabilities.
Publicly available materials reviewed September 12, 2026
The distinction is not governed versus ungoverned. The question is what is being governed.
Domain governance
Governing a defined process end to end
Real, valuable, and buyable today from vendors that have built it. An operator without this layer should acquire it.
Enterprise operating authority
Governing which meaning the enterprise relies upon
This column states what SeniorCRE is designed around. It is not a statement that another vendor cannot perform any capability listed here.
SeniorCRE is designed around the enterprise case in which independently authoritative systems may contain simultaneously valid facts and the operator must determine which definition governs a particular consequential decision.
The two layers coexist. A governed domain record and operator-controlled enterprise authority answer different questions, and a portfolio can reasonably run both.
Ask them of Skypoint, of any mastering vendor, and of us. Our answers are design intent in a validation environment; theirs may be a shipped product. Both answers are worth having in writing.
One more, and we lose it: ask for an independent third-party security certification. Skypoint publicly markets HITRUST r2; SeniorCRE holds no equivalent credential today and publishes no attestation. An operator’s compliance reviewer should score that against us.
A capability table would compare a shipped commercial product with a pre-production one and hand us marks on the rows where we have nothing in operator production. That is not a comparison; it is a graphic. Skypoint is a shipped commercial product; we are not. Skypoint is buyable today and holds an independently assessed HITRUST r2 certification. SeniorCRE is not buyable today, holds no equivalent certification, and everything described here as the authority layer is design intent built, not yet validated with synthetic or de-identified data. Where this page says a capability is not documented, it means only that we did not find public documentation of it in materials reviewed September 9, 2026 — never that the product lacks it.
Skypoint is a trademark of Skypoint Cloud Inc., used nominatively for identification only. Statements about Skypoint describe publicly available product materials as of September 9, 2026; capabilities on both sides evolve.
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.
Skypoint is a shipped commercial product; we are not. Skypoint also holds an independently assessed HITRUST r2 certification, which SeniorCRE does not. Everything described here as the authority layer is design intent built, not yet validated with synthetic or de-identified data. That asymmetry is why this page carries no capability scorecard: a table would hand us marks on precisely the rows where we have nothing in operator production. Reviewed September 9, 2026.
Skypoint has built one of the more sophisticated data-and-agent architectures in senior housing & care technology. Its current material publicly describes master data management across clinical, operational, financial, staffing, billing and CRM systems, configurable validation and field-level survivorship rules including "most trusted source", schema and terminology mapping into one unified ontology, human review of ambiguous records, field-level lineage with reversible merges, a golden record its applications and agents consume, a native conversational interface, and agents that operate third-party software. We give all of that full credit. The strategic question is therefore no longer whether data can be unified. The harder question is what happens when two different answers should not be unified because both are legitimate. Reviewed September 9, 2026.
Master data governance determines which value survives. Operating authority determines which valid meaning governs. A golden record is powerful when there should be one answer. An Operator-Controlled Operating Record is necessary when multiple answers are legitimate and the enterprise must determine which one governs a particular decision.
It is testable. Clinical or operational occupancy of 91.7% and revenue occupancy of 89.9% can both be correct. Neither is bad data. Merging them, or letting a survivorship rule elect one globally, destroys meaning: the staffing decision needs one definition and the capital-planning decision needs the other. The governed question is which definition the operator authorized for the decision in front of them, who approved that definition, which competing valid reading was preserved, and under which authority rule the determination was made. Figures are illustrative, not operator results.
No. If an operator needs the mastering layer now, it is available now and we are not a candidate for it. What an operator can do now is refuse to let the authority layer be settled implicitly by whichever system produced the number: put the four questions on this page into the evaluation, and require that definition authority stays with the operator. Reviewed September 9, 2026.
No, and any such claim would be inaccurate. Skypoint publicly documents field-level survivorship and master-record governance, lineage, semantic mapping, grounded AI and cross-system agents. SeniorCRE addresses the different case in which multiple values remain legitimate and authority depends on decision context. Where we say a capability is not documented, we mean exactly that: we have not identified public documentation of it in materials reviewed September 9, 2026, which is not evidence of absence in the product.
Pre-production. Decision-contextual authority, preserved competing facts, authority lineage and decision lineage are design intent, built with synthetic or de-identified data. No operator production deployment has completed, no third-party integration is live in operator production, and no operator outcome figures are published. Skypoint is a shipped commercial product; we are not.
Behind. Skypoint publicly markets HITRUST r2 certification and HIPAA compliance; SeniorCRE holds no independent third-party security certification today and publishes no attestation. Controls are documented and exercised internally, no PHI workload runs in operator production, and independent assessment is scheduled work rather than a credential we hold. Reviewed September 9, 2026.
Yes. Earlier pages, operator training guides and generated answers stated that barcode scanning verified the five rights at the point of medication administration. That control does not exist. The correction, the exact implementation boundary and the gate that would have to be met before the capability may be described again are published in full at /medication-safety-claim. It is recorded there, on its own page, rather than in this comparison.
No, and that is the operator’s election either way. An operator can keep the systems they run today and have SeniorCRE govern what those systems produce, or deploy SeniorCRE itself as the system of record for functions they choose, including its own EHR and eMAR. Domain authority belongs where it belongs. Decision authority belongs to the operator.
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.