SeniorCRE is the operator-controlled operating infrastructure for senior housing & care. It is designed to govern definitions, source authority, reconciliation, and lineage across the systems an operator already runs, and can carry selected system-of-record functions where the operator chooses. Govern first. Replace only by choice.

How is SeniorCRE different from PointClickCare?

PointClickCare is a clinical EHR. Operators can keep PointClickCare; SeniorCRE is designed to govern definitions and source authority above it. Where an operator chooses, SeniorCRE can assume selected system-of-record functions. Govern first. Replace only by choice.

How is SeniorCRE different from Yardi Senior Living Suite?

Yardi Senior Living Suite is a property-management and accounting system. Operators can keep Yardi Senior Living Suite; SeniorCRE is designed to govern definitions and source authority above it. Where an operator chooses, SeniorCRE can assume selected system-of-record functions. Govern first. Replace only by choice.

How is SeniorCRE different from MatrixCare or ALIS?

MatrixCare or ALIS is a clinical and community-management system. Operators can keep MatrixCare or ALIS; SeniorCRE is designed to govern definitions and source authority above it. Where an operator chooses, SeniorCRE can assume selected system-of-record functions. Govern first. Replace only by choice.

How does SeniorCRE approach HIPAA and security?

SeniorCRE signs Business Associate Agreements and is designed with the administrative, physical, and technical safeguards applicable to its role under HIPAA. SOC 2 attestation planned.

Who is SeniorCRE for?

Senior housing & care operators, REITs, and capital partners. Our operator beachhead is organizations running 10 to 40 communities; larger portfolios are served through a separate Strategic Enterprise engagement.

How much does SeniorCRE cost?

Pricing and implementation fees are set in the applicable order form.

How long does SeniorCRE take to implement?

Deployment is gate-based and operator-specific; SeniorCRE publishes no standard implementation duration.

Operator-controlled operating infrastructure for senior housing & care§ How operators start

Keep what works, connect the rest. One Operator-Controlled Operating Record above your existing systems.

There is one entry motion, because there is one condition almost every operator is actually in: you run an established EHR plus a patchwork of billing, scheduling and accounting systems, and you keep them.

Reporting, portfolio rollups and AI-readiness are consequences of that record rather than a cheaper door to it, so there is no separate visibility product to choose between.

Two exceptions exist for this motion — a greenfield community and an occupied community running on paper. Both are qualification outcomes reached in conversation and scoped under written approval. Neither is a segment you pick for yourself.

This page describes the first of two deployment models: governing the systems you already run. Operators who want SeniorCRE to carry the workflows directly — including EHR and eMAR — are on the second road. Compare both deployment models.

§ The plainest entry question

What did you spend on agency labor last month — and can you trace that number to acuity and rate capture from a single record?

Most operators can produce the invoice total and cannot reconcile it. Answer the three fields below and you have stated your own operating baseline — the same baseline we would otherwise establish on the first call.

The default motion

§ One door

Default — applies unless qualification says otherwise

Keep what works, connect the rest

The Operator-Controlled Operating Record above your existing systems.

Operators may retain PointClickCare, MatrixCare, ALIS, Yardi, payroll, accounting and scheduling systems. SeniorCRE is designed to establish the Operator-Controlled Operating Record above that stack — a reconciled record of care, labor, billing and compliance with defined ownership, lineage and audit trail. The operating record is not yet implemented in any community.

The condition it fits

Portfolios running an established EHR plus a patchwork of billing, scheduling and accounting tools
Operators whose teams should keep working in the systems they already know
Owners, REITs and capital partners who need consistent definitions across operators
Leadership that cannot currently answer census, agency and margin questions from the same record

What the record governs

One reconciled record per resident, care plan, ledger entry, shift, property and legal entity
Field-level ownership, lineage and audit trail — every number is traceable to its source system
Care assessment, billing detail, concession records, and labor and agency data reconciled against each other
Quality Occupancy Score computed from that reconciled record, not from a dashboard overlay
Portfolio rollups, board reporting and AI-readiness as consequences of the record

How we land beside your systems

This motion is designed to sit beside the retained EHR and connect agreed outside services. Named connectors and retained-system ingestion remain roadmap, not built; scope, access, implementation, validation and operator acceptance are prerequisites, not completed integrations.

Investment

Commercial terms for this motion are not published. Structure, rates, and implementation scope are provided under NDA in a written quote scoped to your portfolio. Exception motions are scoped separately.

Request an Executive Briefing Integration doctrine

Evidence status governs this page. Built means a capability exists; built means it has been exercised end to end against representative synthetic or de-identified data in a controlled SeniorCRE environment. Neither state establishes operator-production use or operator reliance. The Evidence Record governs the current date, boundary, definitions, and verification links.

What the record produces

§ Architecture first, measurement second

One Operator-Controlled Operating Record

Six canonical entities — Resident, Care Plan, Ledger, Shift, Property/Unit and Entity — carry declared ownership, role-scoped access, reconciliation state, and lineage. This is the architecture claim everything else nests under, and it is specific enough to be checked.

Read the model

Quality Occupancy Score

Occupancy is only worth what it costs to hold. The Score reconciles care assessment, billing detail, concession records, and labor and agency spend against each other — which is why it requires the record, and why no visibility overlay can produce it.

How it is measured

Fragmented Operating Truth — and its cost

Fragmented Operating Truth is the condition: the same question answered differently by each system. The Fragmentation Tax is the measured cost of that condition. The tax nests under the condition — it is not a second idea.

The Fragmentation Tax

Two exceptions — qualification outcomes, not entry points

§ Written approval required

These are named here for transparency, not for selection. A motion is never proposed before the operating reality is understood, and these two are approved separately because they carry different exposures. They are documented on this page so a buyer can see the gate — not step through it.

Exception · Greenfield · Gated

Greenfield — a community that does not exist yet

Condition · A community under construction or in pre-licensure, with no installed clinical system and no historical operating data to reconcile.

Primary risk · Construction and licensure timing risk. Certificate of occupancy, state survey readiness, and first move-in dates move independently of software readiness, and a slipped date changes the whole plan.

Distinct exposure

Construction schedule dependency
Licensure and initial-survey timing
No historical data to reconcile — and no fallback system if a date slips

Gate · Qualified in conversation, then scoped under written approval. It is not an entry point a buyer can select for themselves.

Exception · Paper turnaround · Gated

Paper turnaround — an occupied community running on paper

Condition · An occupied, licensed community with paper or near-paper clinical and operating process, where there is no installed system of record to sit above.

Primary risk · Clinical cutover risk in an occupied building. Medication administration, orders, assessments and incident reporting must remain continuous for residents receiving care during the transition.

Distinct exposure

Clinical continuity for residents currently under care
Change management with staff who have never used a clinical system
Survey exposure during and immediately after cutover

Gate · Requires written approval, a named clinical owner, and a documented cutover and rollback plan before any scoping begins. A parallel-run period and a declared authoritative-record date are required before any clinical data is treated as governed.

These two are the only exceptions currently approved for deployment. Both gates are owned separately: greenfield approval sits with the deployment owner carrying construction and licensure timing; paper turnaround approval requires a named clinical owner and a documented cutover and rollback plan.

Questions operators ask

§ FAQ

Start with your operating reality, not a menu

Bring last month's agency spend, your census, and the list of systems that produce them. We will tell you what an Operator-Controlled Operating Record above that stack would change — and whether an exception applies.

Request an Executive Briefing

Keep what works, connect the rest. One Operator-Controlled Operating Record above your existing systems.

Reporting, portfolio rollups and AI-readiness are consequences of that record rather than a cheaper door to it, so there is no separate visibility product to choose between.

Default — applies unless qualification says otherwise

Keep what works, connect the rest

The Operator-Controlled Operating Record above your existing systems.

The condition it fits

Portfolios running an established EHR plus a patchwork of billing, scheduling and accounting tools
Operators whose teams should keep working in the systems they already know
Owners, REITs and capital partners who need consistent definitions across operators
Leadership that cannot currently answer census, agency and margin questions from the same record

What the record governs

One reconciled record per resident, care plan, ledger entry, shift, property and legal entity
Field-level ownership, lineage and audit trail — every number is traceable to its source system
Care assessment, billing detail, concession records, and labor and agency data reconciled against each other
Quality Occupancy Score computed from that reconciled record, not from a dashboard overlay
Portfolio rollups, board reporting and AI-readiness as consequences of the record

How we land beside your systems

Investment

Request an Executive Briefing Integration doctrine

Keep what works, connect the rest. One Operator-Controlled Operating Record above your existing systems.

What did you spend on agency labor last month — and can you trace that number to acuity and rate capture from a single record?

The default motion

Keep what works, connect the rest

What the record produces

One Operator-Controlled Operating Record

Quality Occupancy Score

Fragmented Operating Truth — and its cost

Two exceptions — qualification outcomes, not entry points

Greenfield — a community that does not exist yet

Paper turnaround — an occupied community running on paper

Questions operators ask

Start with your operating reality, not a menu

The Senior Housing Journal, in your inbox

Keep what works, connect the rest. One Operator-Controlled Operating Record above your existing systems.

What did you spend on agency labor last month — and can you trace that number to acuity and rate capture from a single record?

The default motion

Keep what works, connect the rest

What the record produces

One Operator-Controlled Operating Record

Quality Occupancy Score

Fragmented Operating Truth — and its cost

Two exceptions — qualification outcomes, not entry points

Greenfield — a community that does not exist yet

Paper turnaround — an occupied community running on paper

Questions operators ask

Start with your operating reality, not a menu