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 in progress.

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.

Claim correction · September 7, 2026

We published a medication-safety control that does not exist

Medication-safety correction (September 7, 2026): barcode scanning and automated five-rights verification are ROADMAP — not built. Earlier SeniorCRE pages, operator training guides, and generated answers described this control as running. That was incorrect and has been withdrawn from every surface. The five rights are verified by the administering clinician, not by SeniorCRE.

In short

The problem: SeniorCRE pages, operator training guides and generated answers stated that barcode scanning verifies the five rights at the point of medication administration. It does not, and no scan blocks an administration.
Who it’s for: Directors of nursing, clinical leaders, surveyors, and anyone who read an earlier SeniorCRE page or training guide describing barcode verification.
Why now: Clinical staff may have been told a system check exists. It does not, so the correction is published now rather than at the next content revision.
What you’d declare: You would be able to state, with a dated record, exactly which medication controls exist, which do not, and who verified that.
What to do next: Read what is actually built, the exact implementation boundary, and the gate that has to be met before this capability may be described again.

See the clinical capability status

What was published, and why it was wrong

What the system actually does today

Barcode-verified medication administration is not built. Four of the five medication scan surfaces open a camera preview with no decoder behind them and match only a manually typed NDC. One surface decodes camera frames through the browser-native BarcodeDetector API where the browser supports it and compares the decoded value to the ordered NDC; that check covers the NDC alone, not resident, dose, route, or time, and it blocks no administration. No five-rights check is performed by the system.

The implementation boundary, stated precisely

Implementation boundary (stated precisely so a reader who finds the working path does not doubt the rest): four of the five medication scan surfaces open a camera preview with no decoder behind them and match only a manually typed NDC. One surface does decode — the mobile medication administration screen (src/components/mobile/BarcodeScannerSheet.tsx) reads live camera frames through the browser-native BarcodeDetector API and compares the decoded value to the ordered NDC, flagging a mismatch. That API is available only on Chromium-based browsers, chiefly Android; it is not available on iOS Safari or on most desktop browser combinations, where the surface falls back to manual label verification. No decoding library is bundled. Even on the working path the check compares the NDC alone — not resident, dose, route, or time — and nothing the scanner returns blocks an administration. Barcode-verified administration and any automated five-rights check therefore remain ROADMAP - not built.

What is built in the medication surfaces

What is built: a scheduled medication pass with time-coded administration records, refusal and hold documentation, PRN follow-up prompts, controlled-substance shift counts with witness capture, and an immutable administration audit trail — built, not validated. None of it runs in operator production, and the medication surfaces have not passed pilot-readiness review.

The gate that would change this claim

The gate that would change this claim: a barcode reader that decodes NDC and resident identifiers, an order-matching check that blocks administration on a mismatch, a documented scanner-failure escalation path, clinician sign-off, and independent validation. Until all five exist, the capability stays ROADMAP on every surface. This is not five-rights verification.

What clinical staff must do

Verify the five rights yourself before every administration: right resident, right medication, right dose, right route, right time. SeniorCRE does not check them for you. Confirm the resident by two identifiers and read the label against the order on screen.

Medication-safety claim status

Status as of September 29, 2026 (last modified 2026-09-29)

SeniorCRE claim evidence step and proof class by claim, as of September 29, 2026
Claim	Evidence step	What is true today	Proof to inspect
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.

Architecture designed: Specified and in the build queue. No built capability exists to demonstrate.

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.

We published a medication-safety control that does not exist

What was published, and why it was wrong

What the system actually does today

The implementation boundary, stated precisely

What is built in the medication surfaces

The gate that would change this claim

Claim

Evidence step

What is true today

Proof to inspect

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.