The care the hospital assembled during an admission — conditions, medications, open obligations, wound care protocols — doesn't disappear when the patient walks out. And for home care agencies whose patients self-provision the record from home, Saliux Care stands alone on the same FHIR spine. Either path. One coordination layer. In real time.
What the hospital assembled during the admission — care routines, medication schedule, discharge lab baselines, wound care protocols — arrives at the home care agency as a fax. The coordinator rebuilds from scratch. That gap is where continuity breaks.
The coordinator is on one system. The visiting nurse has verbal instructions. The family calls to ask what happened on today's visit. The patient re-enters their medications into a third app. Everyone is working on the same patient from disconnected pictures.
Readmission penalties are real and preventable. The clinical trajectory in the weeks after discharge — missed routines, worsening observations, adherence gaps — is the signal. It only exists if someone is reading from the same record in real time.
The coordinator opens a new patient's record and finds not a blank intake form, but the care picture the discharging hospital assembled: active conditions with body-anchored locations, current medications alongside their discharge lab baselines, wound care protocols with scheduled intervals, activity restrictions, follow-up obligations. The coordinator's job is to review and confirm the translation from hospital discharge obligations to home care routines — not to rebuild from scratch.
The roster view shows every patient on service with real-time completion status: which routines are current, which are approaching, which are overdue. The agency compliance dashboard surfaces aggregate completion rates, provider performance, and physician order flags — derived live from the shared patient records. When a care plan state needs to change, the AI layer surfaces the suggestion for the coordinator to confirm or reject. No state change without a human confirmation event.
The visiting provider sees their full day's schedule and, on selecting a patient, a care queue showing exactly what is due for this visit — ordered routines with body-anchored locations, temporal status (current, due soon, overdue), and completion logging. Wound care on the right lower leg. Vital signs. Medication administration. Each routine has a scheduled interval, a body location, and a clear completion action.
When the nurse logs a completed routine, the coordinator's roster reflects it and the patient's own view shows what was just done — simultaneously. The PWA works offline: completions log locally when signal is unavailable and sync when the connection restores. One act by the provider propagates to every actor on the record — not through a notification system, but through the record itself.
A family member receives an invitation link from the agency. No download required. No account to create. The portal opens to show the last completed care routines in plain language — medical terminology suppressed — the upcoming visit, whether medications are on track, and an alert if anything is overdue.
The adult daughter in another state doesn't wonder. She doesn't call the agency. She sees what was done for her mother this morning, what's coming this afternoon, and whether anything requires her attention. Read-only at the data layer: no editing paths exist anywhere in the family portal. Access scope is set by the coordinator and the patient, adjustable at any time.
Saliux Care doesn't maintain its own patient database. It reads from the patient-owned FHIR record — activated by a VPI hospital at discharge, or by the patient self-provisioning from home via SMART on FHIR — and writes completed care events, observations, and visit logs back to that same record. The starting point is the record itself, not a handoff document. Hospital-built admission context, self-aggregated provider history, or whatever the patient brings.
When a visiting nurse logs a completed wound care routine, the coordinator's dashboard updates and the patient's own app reflects the completed care act — simultaneously, in real time. When the patient self-logs a blood pressure reading, the care team sees it before the next visit. When a physician modifies a home care order, it appears in the coordinator's care plan without a phone call or fax.
Hospital path: at discharge, VPI writes the patient's active care state — conditions, medications, open obligations, medication-lab pairs — to the patient's FHIR record. Self path: the patient connects existing providers from home via SMART on FHIR. Either path activates the same record. Saliux Care reads from there.
Hospital discharge obligations are reviewed one by one — transferred as-is, translated to home care equivalents, or flagged for coordinator action. Clinical attribution from the hospital record is preserved through translation.
Coordinator, visiting nurse, family, and patient are all operating on the same record at the same moment. Each completed act writes back. Every actor's view updates in real time.
When care ends, the agency's access ends. The patient's record remains — held by the patient, available to any provider they next authorize, independent of institutional boundaries.
Skilled nursing visits, wound care, medication management, and therapy in the patient's home — coordinated in real time against the same record the hospital built.
Long-duration care relationships with stable patient populations. Census-based coordination, compliance reporting, and care plan management without rebuilding records on intake.
Complex, high-touch care requiring close coordination between staff, family, and medical oversight. The family portal keeps family members present without burdening the care team with calls.
Interdisciplinary teams — nurses, physicians, chaplains, social workers, family caregivers — each with the right scope of access and a shared view of where the patient is in their care arc.
Post-acute recovery in a facility setting — shift-change handoffs, care protocol compliance, and discharge planning toward home are active daily workflows requiring real-time record access.
Any post-acute setting where a coordinator manages obligations, providers execute routines, and a patient-owned record carries the arc.
The patient's health record belongs to the patient. Architecturally. Saliux operates the record infrastructure but has no rights to the data — the record is patient-owned, patient-controlled, and portable. Saliux Care does not maintain its own patient database; it reads from and writes to the patient's FHIR record under patient-granted authorization, scoped to what the patient has chosen to share, revocable at any time. Institutions retain their own medical records — Saliux does not touch those. What the patient controls is their own record, and the record travels with them to every care relationship that follows.
This is not a privacy statement. It is the architecture. The patient is the record holder — structurally, not philosophically. Care providers are authorized readers and writers on a record they do not own. This is what makes the record portable across care settings without inter-institutional data transfers, and what makes the post-acute arc possible on a single source of truth rather than a chain of disconnected handoffs.
Whole-body clinical visualization at the acute point of care. Standalone in any FHIR-compliant hospital. When deployed alongside Saliux Health, VPI also writes a discharge bundle to the patient-owned record.
Explore VPICoordinator Hub, Provider PWA, and Family Portal — three surfaces reading from and writing to the patient-owned record, in real time, across the full post-acute arc.
You are hereThe patient's own view of their FHIR record — body map, care obligations, activity feed, and access management. The record is theirs. Provisioned where they receive care.
Explore Saliux HealthSaliux Care is in active development. We're seeking post-acute partners for early access — agencies and facilities who want to shape how this works in practice before it ships.