The hospice HOPE timepoints, explained
On October 1, 2025, the Hospice Outcomes & Patient Evaluation (HOPE) tool replaced the Hospice Item Set (HIS) as the standardized patient-assessment instrument for the Hospice Quality Reporting Program. HOPE is a bigger shift than HIS: instead of two data-collection points at admission and discharge, it adds in-person assessment visits during the stay and a symptom-driven follow-up. This guide walks through each timepoint and the places teams most often stumble.
This is a plain-language overview, not compliance advice. Always confirm current requirements and exact timing windows against the CMS HOPE Guidance Manual and your agency's policies.
The five HOPE timepoints
1. Admission
Completed at the start of care, the Admission assessment establishes the patient's baseline — including symptom impact, and the clinical and demographic information HOPE collects. Because several later timepoints and triggers key off what was documented here, the Admission record has to be both timely and complete.
2. HOPE Update Visit 1 (HUV1)
The first HOPE Update Visit is an in-person assessment during the early part of the stay (on or between days 6 and 15 of the hospice stay). This is new relative to HIS — the assessment schedule no longer jumps straight from admission to discharge, so agencies have to build these mid-stay visits into their scheduling and documentation routines.
3. HOPE Update Visit 2 (HUV2)
A second in-person HOPE Update Visit later in the first month of care (on or between days 16 and 30). As with HUV1, the challenge is operational as much as clinical: making sure the visit happens inside its window and that the documentation is captured while the clinician is still with the patient.
4. Symptom Follow-Up Visit (SFV)
This is the trigger that catches teams out. When a symptom is assessed at a moderate or severe level of impact — at Admission or at a HOPE Update Visit — an in-person Symptom Follow-Up Visit is required within two calendar days of that assessment. The follow-up has to be recognized, scheduled, and documented promptly, which is hard to do reliably from memory across a caseload.
5. Discharge
Completed when the patient is discharged from hospice care, capturing the end-of-care assessment information HOPE requires.
Where teams stumble
- Timing windows. HUV1, HUV2, and especially the Symptom Follow-Up Visit each have to happen inside a defined window. Missing one is a documentation and quality-reporting problem, not just a scheduling annoyance.
- Remembering the SFV trigger. A moderate-or-severe symptom at Admission or an update visit starts the follow-up clock. It's easy to miss when a clinician is documenting after a long day of visits.
- Consistency across clinicians. HOPE asks for structured, comparable answers. Free-text notes that don't map cleanly to the required items create rework downstream.
- Documenting at the point of care. The more time passes between the visit and the write-up, the more detail is lost — and HOPE asks for a lot of specific detail.
How MediScribe Flow fits
MediScribe Flow is a documentation workflow tool built to cover the HOPE timepoints. A clinician dictates the visit in the field; the app drafts a structured document for the relevant timepoint — Admission, HUV1, HUV2, Symptom Follow-Up, or Discharge — and shows the supporting evidence from the narrative next to each field so the clinician can confirm it. It also surfaces non-blocking reminders — for example, a note when a moderate or severe symptom is documented and a Symptom Follow-Up Visit may need to be considered.
Those reminders are prompts for the clinician to weigh, never automatic decisions. The practitioner reviews and is responsible for every field, and MediScribe Flow does not submit anything on its own. It is a documentation aid — not a coder, and not certified by CMS.