One identity
A single account, resolved on the server on every request. Sign-in happens at your identity provider; Sapphire never sees a password.
Most operators buy a tool per problem and inherit a seam per tool. Sapphire is a modular monolith: the applications below are separate products to the people using them, and one governed system underneath.
Four things every application inherits from the platform underneath it — and the reason a report in one module can trust a figure from another.
A single account, resolved on the server on every request. Sign-in happens at your identity provider; Sapphire never sees a password.
Every record belongs to a facility. Your facility scope travels with you across every module, and it is enforced at the data boundary.
Role and grant decide what you can reach. Knowing a URL is not access, and a mistake in a screen does not become a leak.
What was read, changed and approved is recorded once, across the suite — not per application in four different formats.
Build status is reported as it is. A module marked In build or Planned is not available to you today, and saying otherwise would be the first thing this platform is designed not to do.
Everything between admitting a resident and collecting the money — eligibility, claims, statements, payables and the agreements underneath them.
Resident financial records, eligibility and Medicaid pipeline, aged A/R and claim follow-up in one place.
Private-pay statements, payment capture and collections activity, tied back to the resident ledger.
Accounts payable from invoice capture through extraction, coding and approval.
Payer and vendor agreements with their rates, obligations and compliance dates kept attached to the contract.
The operational side of care — who is in the building, who is coming, and the clinical workflows that drive both.
Referral-to-admit tracking, live bed board and payer-fit screening for incoming residents.
Wound tracking and the resident clinical record that supports it.
Long-term-care analytics: PBJ reporting, Five-Star position, P&L cascade and a submission scrubber.
The daily morning operational report, assembled from the rest of the suite instead of by hand.
The people and the buildings — scheduling and labor cost on one side, work orders and purchasing on the other.
Schedules, projected HPPD, and the agency and overtime controls that keep labor cost in view before it lands.
Work orders, asset registry and preventive-maintenance schedules across the portfolio.
Order guides, requisition-to-PO flow and spend analytics against them.
Visitor and vendor sign-in, screening and badging at the front desk.
The corporate view — cash, ledgers and the rollup that lets an owner see every facility on the same basis.
Bank aggregation, reconciliation and a rolling 13-week cash position.
Portfolio financial rollup that reads from the operating modules rather than a re-keyed spreadsheet.
Cost intelligence for the platform itself — what the suite burns against what it replaces.
Resident trust-account management, with the balance history a survey will ask for.
Evidence, policy and oversight — the layer that makes the rest of it defensible when someone asks.
Compliance document control and audit readiness, with version history that survives a survey.
Policies and procedures every staff member can actually find.
The curated knowledge base that grounds suite AI, so answers cite something real.
Internal help desk and ticketing for the people running the buildings.
Identity, the facility spine, roles, the module registry and the audit trail over all of it.
We walk through the synthetic preview with your facility mix, payer mix and the reports you actually run today.