The aide often sees it first
A two-person transfer, a slip the patient asked not to make a fuss about. The hospice aide is not a core IDG member, so her observation reaches the IDG only if somebody deliberately puts it there.
Your nurses’, aides’ and social workers’ notes, assembled into a morning worklist, an IDG panel, a record of the meeting and the agency’s certification risk. Every finding opens onto the note or record behind it; what Hesovia cannot see is counted on the screen. What it prepares is handed to you as text, to paste into your EMR.
Every screen on this page is the working prototype, captured as it runs, on invented patients. It simulates a nightly EMR export; how your notes reach it is the first thing we settle with each pilot agency.
Open full size ↗
What you scan is Hesovia’s reading of each note, attributed to the discipline that wrote it. The note itself is one step away, verbatim: beneath the reading on IDG prep and in Open work, and in full on the chart.
A reading of a note is prefixed Hesovia reads and never set in a clinician’s type, so it cannot be quoted as hers.
Unknowns stay on the screen and in the count. A missing note is never shown as a pass.
Eligibility questions are routed to the certifying physician. Hesovia does not answer them.
Coverage shifts between visits and within each discipline, so one patient’s record is written by several nurses, aides and social workers. The case manager rebuilds the picture by hand, per patient, the night before IDG.
Clinical time should be spent interpreting the story, not hunting for it.
The operating principle behind HesoviaA two-person transfer, a slip the patient asked not to make a fuss about. The hospice aide is not a core IDG member, so her observation reaches the IDG only if somebody deliberately puts it there.
Two 90-day benefit periods, then unlimited 60-day periods. A plan-of-care review at least every 15 days. HOPE assessment windows counted from admission, or from the transfer date for a transfer-in. None of them waits for a vacancy to be filled.
A recertification narrative that cites none of the findings, or an unsigned attestation, is usually found under deadline pressure, not when it could still be fixed calmly.
These are the screens of the working demo, in the order a walkthrough takes them. The names, people and figures here are the ones you will see on the call.
Clinical surfaces for the patients on her team by default — IDG preparation, the meeting record and the census. She can widen to the whole census when covering, and that access is recorded. No revenue or agency-wide financial exposure.
The whole census, plus compliance and revenue exposure across the agency. The financial surfaces are limited to this role.
The navigation changes with the role. Dana’s sidebar has four entries; Elaine’s has five, and she lands on Compliance. Switch role keeps what the other role just did, and Reset demo clears it.
Sign-in answers the two questions every clinical buyer asks first. Choose a role: a case manager scoped to her team, or an administrator who sees the agency. The panel beside it states what the demo is and is not.
It runs entirely in this browser. No server, no account, no database, and nothing is transmitted anywhere — including anything you type during the demonstration.Sign-in · What this is
Open full size ↗Today opens on the patients whose charts changed: Changed since your last visit, declining first, each change attributed to the discipline that wrote it. Below it, Open work: paperwork, plan-of-care reviews, clinical follow-ups and questions for a physician, each an instruction to a named person, with a deadline where there is one.
Open full size ↗
Open full size ↗
Open full size ↗For each patient on the agenda, IDG prep puts what every discipline documented since the last meeting in one panel, ordered by clinical risk and then by what is time-critical to certify.
Each line you scan is Hesovia’s reading, labelled Hesovia reads and attributed to the discipline. View source notes opens what your clinicians wrote, in full.
A chart opens in Summary: what changed since the last IDG, team decisions waiting on the physician, and open tasks, each with an owner. Hospice criteria is the long view: every note, every measure, every provenance line. The summary is a filter over that page, not a summary written on top of it.
Open full size ↗
Open full size ↗
Open full size ↗Every patient on the team is reviewed, not only the six with changes, because the group’s documented review of each plan of care is what keeps its 15-day interval.
Open full size ↗Every plan of care must be reviewed at least every 15 days. That is arithmetic on two dates, so Hesovia checks it for the whole census.
The plan-of-care review interval is checked for every one of them — it is arithmetic on two dates, so it needs no documentation Hesovia cannot see.Census
Open full size ↗The administrator lands on this screen, Certification & billing risk. Money is sized in three categories: care already invoiced against a confirmed missing element, revenue that cannot be billed unless something is closed, and the charts Hesovia cannot confirm either way, the biggest figure on the screen. Every amount is a gross period value at a national rate, tied to no claim; it sizes the question and does not price a recoupment.
Open full size ↗
Open full size ↗A clean screen above means these were checked and passed. It does not mean the chart is clean. These are outside what Hesovia can see, and they remain yours.Compliance · What Hesovia is not checking
2026 is the first year HOPE submission timeliness is enforced.
HOPE rows sit in the same worklist, under their own filter: an Admission or HOPE Update Visit (HUV) window about to close, an in-person symptom follow-up visit due within two days of its screening.
Rows quote CMS’s own item names and labels and never describe the patient in Hesovia’s words. A transfer-in counts from its transfer date.
The administrator’s card counts records in their window. It gives no on-time rate: that needs CMS’s acceptance records, which the EMR does not hold.
Open full size ↗
Open full size ↗Hesovia never states a conclusion a clinician would have to defend. It shows what your team documented, says plainly what it cannot see, and routes clinical determinations to the physician who has to make them.
If write-back, or a check the demo does not make, is what would decide it for your agency, that is the conversation we want to have.
The demo shows the access model: a case manager scoped to her team, widening for coverage permitted and recorded, and money visible only to the administrator. The platform behind it is being built around isolation, traceability, least-privilege access and verifiable infrastructure controls from the beginning.
Security architecture supports a compliance program; it is not, by itself, a certification or guarantee of compliance.
Each role sees its own population by default, and every screen states which population it is showing.
Designed so clinical data stays within private network boundaries, with intentionally constrained routes.
Designed around short-lived identities instead of shared credentials, so every action keeps a human name.
Security records are designed to survive the workload systems they describe.
Building the system, one defensible decision at a time.
We document the architecture, tradeoffs, failed assumptions, and verification that shape Hesovia. It is a record of how the platform is being built—not a polished story written after the fact.
We walk hospice leaders and clinical teams through the demo on this page. Then we ask what would decide it for you: whether handing the IDG record over as text is acceptable at first, or write-back is required; what your EMR already reports; and what would make a pilot on your own extract worth running.
Book a walkthrough