Health plans and self-managed plans · HAI
The visit happened. Everyone knows.
HAI builds the visit schedule, records each visit made by the professional and turns a visit that did not happen into a pending item with an owner. When the visit happens, the health plan and the accredited network look at the same record, as per the agreed design. When it does not, the team finds out in real time, while there is still time to cover it.
A 30-minute conversation about your operation, with a demo on fictitious data. No commitment.
Demo with fictitious data.
The problem
A visit that did not happen shows up too late
Hospital discharge depends on what happens at home. The planned home visit is what keeps the member cared for after discharge. When it fails, almost no one finds out in time.
For those receiving care
A paid visit that does not happen leaves the member without care and raises the risk of returning to hospital.
For those paying
In many operations, the failure only shows up weeks later, when the paperwork arrives. By then the visit can no longer be covered, only the bill discussed.
For those providing care
Paper records, filled in afterwards and sometimes incomplete. The health plan and the accredited provider end up arguing about what happened, instead of looking at the same visit.
The effect in each operation depends on the design and on the validation done with the health plan.
How it works
The same visit, seen by the health plan and the network
The HAI platform plans the schedule, records the visit made and opens the pending item when it does not happen. The record made at the visit is available to the health plan and the accredited network, as per the design agreed in each operation.
Demo with fictitious data.
Plan
HAI turns each member's planned visits into the day's schedule, with the provider and professional assigned.
Record on the spot
The app guides the professional through the visit and records who attended, where and at what time, plus the progress notes and checks the operation configures. Offline operation depends on version and implementation.
See the day
The Cockpit gathers the operation's day and separates the breaks, which are planned visits that did not happen. Each break becomes a pending item with an owner and a follow-up history. The detail shows where each number comes from.
Act in time
The pending item reaches the team, which handles the break with the accredited provider while there is still time to cover the visit. The system alerts; the clinical decision belongs to the professional.
Prove it
The visit record is already ready for audit, without waiting for paper. The trail supports checking and does not replace the analysis of whoever audits.
Care command center
HAI
Command Center
Within HAI, it is the coordination center for home care operations. It brings together the view of visits and organizes how teams receive requests, anticipate deviations and follow the care.
Demo with fictitious data.
- TrackWhat is planned, scheduled, under way or pending.
- CoordinateIdentifies who is responsible, records outcomes and follows referrals.
- CheckVerifies the result and supports the adjustments the care needs.
Internal teams and client teams. For the health plan, what each team sees follows the design agreed in each operation.
In one minute
Why a visit that does not happen costs so much
What changes by role
Each role sees what it needs, in the same visit
Four short summaries, one for each role in the decision. They apply to health plans and to self-managed plans. Open yours and share it with your team.
Health director
- The dashboard puts, for the home care of your network, the planned visit and the completed visit side by side.
- A break becomes a pending item with an owner and is handled with the provider in time to cover it, with the goal of reducing lack of care.
- Alerts based on the indicators your care team defines, sent to whoever the operation defines. The clinical decision always belongs to the professional.
Audit and regulation
- The app records the visit on the spot, instead of paper weeks later.
- Each visit arrives with who attended, where and at what time, plus the evidence the operation's profile and configuration define.
- The day view supports the audit. The trail supports checking; it is not a guarantee of the absence of errors.
Information technology
- Web platform, professional app and management portal.
- Role-based access, with authentication and separation between organizations. Integrations with the client's sources, preserving origin and identity, after a survey and validation in each operation.
- Health data treated as sensitive personal data, at the minimum necessary for the purpose. Privacy and security documentation on request.
Procurement and contracts
- Salvus provides the platform and the app. It does not hire professionals.
- The relationship with the accredited provider and with the health plan's network stays as it is.
- Scope, modules and roles agreed per operation before the start. Commercial terms handled in conversation.
What Salvus does and does not do
Clear limits from the first conversation
What Salvus does
Provides the platform and the app that build the schedule, record the visit, open the pending item when a visit does not happen and deliver the record to the audit, with scope per account.
It does not decide or prescribe
The system alerts. The clinical decision always belongs to the responsible professional.
It does not hire professionals
The relationship with the accredited provider and with the health plan's network stays as it is.
It does not replace your team
It supports coordination and makes information available in real time.
It is not the same in every operation
Modules, roles, processes and integrations vary. That is why the conversation starts from the design of your operation.
30-minute conversation
An objective conversation about your operation
Where the planned visit stops happening, how the information reaches the audit and what the demo would show with the design of your network.
We learn how you follow accredited providers' visits today.
We show the Cockpit, the Breaks and the Diary applied to your scenario.
If it makes sense, we agree on a demo with the design of your operation.
A case from the network
Home care case · large operation
Average days at home until readmission
After: 150 days
Before:
78 daysEarly readmission, within 30 days, in home hospitalization
After: 21.7%
Before:
26.3%−4.6 percentage points (lower is better)
Implementing care for a new patient dropped from 8 days to 33 hours. The information comes from the single record of each visit. The system alerts; the care decision belongs to the professional.
Source: large home care operation, records from the HAI platform and the client's management system, series from 2023 to 2026 (partial) for outcomes and 2022 to 2026 (partial) for implementation. Before-and-after comparison, with no attribution of cause.
Other cases we present in conversation, with the context, period and method of each, so that the comparison with your operation is honest.
One operation's result is not a promise for another.
Frequently asked questions
What we are usually asked
Does this work for self-managed plans?
Yes. The conversation is the same: how your organization follows accredited providers' visits today and what needs to reach the audit. The design of access, roles and network is agreed with your operation before any commitment.
Does the system decide or prescribe?
No. The system alerts. The clinical decision always belongs to the responsible professional.
Which indicators trigger alerts, and for whom?
They are the indicators defined by each operation's care team, and the alert goes to whoever the operation defines. The design is agreed at each implementation.
Does it work the same at every health plan?
No. Modules, roles, processes and integrations vary between organizations. That is why we propose a conversation and a demo with the design of your network.
Does this replace my team?
No. It supports coordination and makes information available in real time.
Does the health plan access the data directly?
It depends on the design agreed with the health plan and the provider. Access is by role. We confirm the scope in the conversation, before any commitment.
What happens when the app is offline?
Offline operation depends on the app version and the implementation. We confirm what applies to your operation in the technical conversation.
Which integrations exist?
We integrate the client's sources as agreed in each implementation, after a survey and validation. The list is not the same for every account and is confirmed in the technical conversation.
How much does it cost and how long is the implementation?
It depends on the design of the operation. We cover it in conversation, after understanding your scenario. We do not publish prices or timelines on this page.
Is there a case from a health plan like mine?
Cases are evolving and are presented in conversation, with context, period and method. Use the "Ask for a case in conversation" button.
Hosting, data region and data protection officer follow each client's policy.
Book 30 minutes
See your operation with every visit in view
In 30 minutes we learn how your operation follows visits today and show you HAI with fictitious data.
Prefer email? contato@salvus.me. Results depend on the design of each operation. Do not send health data by email or message.