QuillwardHealth
Hospice operationsGuide

How to choose a hospice EHR with a demo script and vendor questions

A hospice EHR demo script built on Medicare rules, plus the HIPAA, data migration, contract and pricing questions to ask every vendor before you sign.

Short answer

Choose a hospice EHR built around the Medicare hospice benefit, and make every vendor run the same live scenarios: a readmission and a transfer-in, an NOE, HOPE visits with a symptom follow-up, an IDG review, a move to general inpatient care, a death with service intensity add-on visits, a live discharge with an NOTR, and an ADR packet. Then get a signed business associate agreement, a documented data export and return-of-data plan, and a written migration scope before you sign.

On this page
  1. Start with how the system models the benefit
  2. A demo script to send every vendor
  3. Security and privacy questions grounded in HIPAA
  4. Planning the data migration
  5. Contract and pricing questions to ask
  6. A quick checklist for comparing vendors
  7. Where Quillward fits
  8. Sources

Most hospice EHR demos look good for a simple reason: the vendor picks the patient. The admission is clean, the patient has never been on hospice before, nobody transfers in, and nobody dies on a weekend. Your real census looks nothing like that, and the gaps in a system show up in exactly the cases a scripted demo avoids.

The fix is simple. Write your own script, hand the same one to every vendor, and ask them to run it live with a clinician at the keyboard. What follows is a script you can use as is, with the Medicare rule behind each scenario so you can judge the answers, followed by the security, migration and contract questions that belong in the same evaluation.

Start with how the system models the benefit#

Many products began as home health or hospital software and added hospice later. Before you watch any screens, ask how the product stores an election, its benefit periods, prior hospice days, revocations and transfers. If those are notes or custom fields rather than real data the system calculates from, every deadline in this guide becomes something your staff tracks by hand. Our comparison of hospice and home health EHRs goes into why the difference matters.

A demo script to send every vendor#

Send the script a week ahead so the vendor can build test patients, and say plainly that you want to watch the work happen rather than see finished screens. The dates below come from one hypothetical patient whose election takes effect on Monday, November 2, 2026. Reuse them so every vendor is answering the same question.

1. A readmission with prior hospice days, and a transfer-in#

Ask them to admit two patients. The first used both 90-day periods at another hospice months ago, revoked, and now elects hospice with you. The second is changing hospices partway through a benefit period.

The rules: election periods run as two 90-day periods and then an unlimited number of 60-day periods, used in that order, and they can be elected at different times (42 CFR 418.21). So the first patient starts with you in a third benefit period, which lasts 60 days and needs a face-to-face encounter by a hospice physician or nurse practitioner no more than 30 calendar days before it begins (42 CFR 418.22(a)(4)). The Benefit Policy Manual, Chapter 9, section 20.1, allows a face-to-face within 2 days after admission when documented exceptional circumstances prevented an earlier one. Prior days also affect payment: the routine home care rate drops after day 60, and if a patient is readmitted within 60 days of a discharge, the day count continues rather than resetting (Claims Processing Manual, Chapter 11, section 30.2).

A transfer is different. A patient may change hospices once in each election period, and the change is not a revocation (42 CFR 418.30). The benefit period does not change, and the receiving hospice does not need its own face-to-face if it can verify the original hospice already did one (Benefit Policy Manual, Chapter 9, section 20.2.1). The admitting hospice submits a transfer notice (type of bill 81C or 82C) after the transfer, and its "from" date has to match the other hospice's "through" date (Claims Processing Manual, Chapter 11, section 20.1.3).

A good answer: the system asks for prior hospice history at intake, places the patient in the correct benefit period automatically, shows the face-to-face due date and the routine home care day count, and treats a transfer as a transfer, with no new benefit period and a transfer notice instead of a fresh election.

2. The election, the NOE and acceptance tracking#

Have them complete the election for the November 2 patient and produce the Notice of Election (NOE), the filing that tells Medicare the patient has elected hospice.

The rules: the NOE (type of bill 81A or 82A) must be filed and accepted by the Medicare Administrative Contractor within 5 calendar days after the admission date (Claims Processing Manual, Chapter 11, section 20.1.1). For our patient that means accepted by Saturday, November 7, because weekends count. An NOE returned for correction is not an accepted NOE. If it's late, Medicare doesn't pay for the days from admission until acceptance, and the hospice can't bill the patient for them. The election statement itself must include specific content under 42 CFR 418.24(b), and for elections on or after October 1, 2026, the FY 2027 final rule made the election statement addendum, which lists items, services and drugs the hospice won't cover, mandatory for every election. It must be provided within the first 5 days of the effective date (42 CFR 418.24(d)). Initial certifications can be signed up to 15 calendar days before the effective date, and if the written certification isn't in hand within 2 calendar days of the period starting, an oral one must be (42 CFR 418.22(a)).

A good answer: the election screen captures the effective date separately from the signature date, the addendum is part of the admission packet with its own due date, and the NOE shows a status you can trust (submitted, returned, accepted) with an alert well before day 5, not just a record that someone clicked send. Our post on the 5-day NOE rule walks through late-NOE exceptions.

3. A HOPE admission, then HUV1 with a moderate symptom#

HOPE (the Hospice Outcomes and Patient Evaluation tool) is the standardized assessment CMS uses for hospice quality reporting. Ask the nurse to complete the HOPE admission, then a first update visit (HUV1) where pain is recorded as having a moderate impact.

The rules, from the HOPE Guidance Manual v1.03, effective October 1, 2026: the admission record is due no later than 5 calendar days after the effective date of the election. HUV1 falls on days 6 through 15 and HUV2 on days 16 through 30, counting the election date as day 0. For our patient, HUV1 runs November 8 to 17 and HUV2 November 18 to December 2. When any symptom impact response is moderate or severe, a symptom follow-up visit, which must be a separate in-person visit, is expected within two calendar days. If HUV1 happens on Thursday, November 12, the follow-up is expected by Saturday, November 14. Hospices must submit at least 90 percent of HOPE records within the 30-day submission deadline.

A good answer: HOPE items sit inside the nurse's normal visit note instead of a separate form, the HUV windows appear on the schedule from day one, and the moderate response creates a follow-up visit task with a due date immediately. Ask what happens if the patient dies on day 4 (no HUV1 is required) and how the vendor tracks submission status for each record. More on the windows in our post on HOPE update visits.

4. An IDG meeting#

Ask them to prepare and run an interdisciplinary group (IDG) meeting for a handful of patients and update one plan of care.

The rules: the IDG, with the attending physician if there is one, must review and revise the plan of care as often as the patient's condition requires, and at least every 15 calendar days. The revised plan has to reflect the updated comprehensive assessment and the patient's progress toward the plan's goals (42 CFR 418.56(d)).

A good answer: the system knows each patient's next review date, builds the agenda from documentation since the last meeting, records who attended, and turns the discussion into plan-of-care changes that every discipline sees. A meeting note that sits beside an unchanged plan isn't a review.

5. A move to general inpatient care#

Ask them to move a home patient to general inpatient care (GIP) at a contracted hospital for uncontrolled pain, and back to routine home care five days later.

The rules: GIP is short-term inpatient care for pain control or symptom management that can't be handled in other settings (Benefit Policy Manual, Chapter 9, section 40.1.5). It can be provided in a hospice inpatient unit that meets the conditions of participation, or in a hospital or skilled nursing facility that meets specific staffing and patient-area standards (42 CFR 418.108(a)). On the claim, each level of care is a separate line under its own revenue code, 0656 for GIP, dated when that level began (Claims Processing Manual, Chapter 11, section 30.1). The inpatient rate is paid for the day of admission and each inpatient day except the day of a live discharge, which is paid at the home care rate (42 CFR 418.302(e)(5)).

A good answer: the level of care change is a dated event with its own documentation prompts for why inpatient care is needed, the contracted facility is recorded, the claim lines build themselves from those dates, and the system flags GIP days that lack daily documentation supporting the level.

6. A death with service intensity add-on visits#

Ask them to document an RN visit and a social worker visit on each of the last few days of a routine home care patient's life, then the death, then the final claim.

The rules: the service intensity add-on pays extra for direct care by an RN or social worker on routine home care days in the last 7 days of an election that ends in death, up to 4 hours a day (42 CFR 418.302(b)). Visits must be at least 15 minutes, and a social worker's phone calls don't count (Claims Processing Manual, Chapter 11, section 30.2.2). GIP days don't qualify, because the add-on applies only to routine home care.

A good answer: visit times are captured as real start and end times, the claim reports the qualifying visits correctly, phone contacts are kept separate, and the system can show you which of the last 7 days were routine home care. Ask the vendor to change one of those days to GIP and show what happens to the add-on.

7. A live discharge with an NOTR#

Ask them to discharge a patient who is no longer terminally ill.

The rules: before discharging, the hospice must get a written discharge order from the hospice medical director, a physician designee or the physician member of the IDG (the last two were added by the FY 2027 final rule, effective October 1, 2026), and should consult the attending physician (42 CFR 418.26(b)). The hospice files a Notice of Termination or Revocation (NOTR, type of bill 81B or 82B) that must be accepted within 5 calendar days after the discharge date, unless it has already filed the final claim; an NOTR is not used for transfers (Claims Processing Manual, Chapter 11, section 20.1.2). The patient loses the remaining days in that benefit period (Benefit Policy Manual, Chapter 9, section 20.2.3). The hospice must forward a discharge summary, and the clinical record if requested, to whoever takes over care (42 CFR 418.104(e)), and the HOPE discharge record is completed at the time of discharge. A revocation works differently: the patient signs it, and its effective date can't be earlier than the date it's made (42 CFR 418.28).

A good answer: the discharge workflow won't finish without the physician order, produces the NOTR with a due date, generates the discharge summary and HOPE discharge, and keeps revocation, live discharge and transfer as separate paths. See our post on hospice live discharge for the documentation side.

8. An ADR packet#

Ask them to assemble everything a reviewer would want for one month's claim, as if an additional documentation request (ADR) had just arrived.

The rules: providers generally have 45 calendar days to respond to an ADR from a Medicare contractor, and claims are denied if the documentation doesn't arrive in time (Program Integrity Manual, Chapter 3, section 3.2.3.2). The packet draws on the clinical record contents required by 42 CFR 418.104(a), including the election statement, certifications with the physician's brief narrative written for that patient rather than as boilerplate (42 CFR 418.22(b)), the plan of care, visit notes and orders.

A good answer: one person can build a complete, ordered, paginated PDF for a date range in minutes, including signed election forms, certifications, face-to-face attestations, IDG notes, orders and medication records, with signatures and dates visible. Ask how long it takes for a patient with 300 days of service. Our ADR response guide covers what reviewers look for.

Security and privacy questions grounded in HIPAA#

An EHR vendor that hosts your records is a business associate under HIPAA, and HHS lists EHR and cloud vendors among its examples. That gives you specific things to ask for, rather than a general promise that the product is secure.

Start with the business associate agreement. You may share protected health information with a vendor only after getting satisfactory written assurance that it will be safeguarded (45 CFR 164.502(e)), and the contract has required terms (45 CFR 164.504(e)). Read the vendor's agreement against that list instead of signing their standard paper unread. Ask for the list of subcontractors that touch your data, such as the hosting provider, because the vendor must hold each one to the same restrictions (45 CFR 164.504(e)(2)(ii)(D)).

On technical safeguards, the Security Rule requires access controls, including a unique identifier for each user and an emergency access procedure, plus audit controls that record and examine activity in systems holding patient information (45 CFR 164.312). Automatic logoff and encryption are "addressable," which HHS is clear does not mean optional. Useful questions:

  • Can every user have their own login, with roles that limit a volunteer or a biller to what they need?
  • Can you see who viewed or changed a specific patient's record, and when, without opening a support ticket?
  • How long are those audit logs kept, and can you export them?
  • What happens to field access and records if the vendor's system goes down?

Breach notification is next. A business associate must tell you about a breach of unsecured protected health information without unreasonable delay and no later than 60 calendar days after discovering it, and identify each affected person to the extent possible (45 CFR 164.410). HHS's sample contract language notes that the parties can agree to a shorter timeframe. Your own notices to patients depend on what the vendor tells you, so a shorter window in the contract is worth asking for.

Then ask about leaving. At termination, the vendor must return or destroy your protected health information if feasible and keep no copies; where that isn't feasible, the contract's protections continue for whatever it keeps (45 CFR 164.504(e)(2)(ii)(J)). Ask what format the return comes in, how long it takes, whether it costs extra, and how destruction is confirmed. Remember that you must keep clinical records for 6 years after a patient's death or discharge, or longer if state law requires (42 CFR 418.104(d)), so you need a usable export, not just a deletion certificate.

Information blocking rules may also apply, depending on the product. Under 45 CFR Part 171, a "health IT developer of certified health IT" is one of the actors that must not engage in practices likely to interfere with access, exchange or use of electronic health information. A developer counts only if it has at least one product module certified under the ONC Health IT Certification Program at the time of the practice (45 CFR 171.102). Not every hospice EHR is certified, so ask directly whether any part of the product is, and if so, whether its certification includes electronic health information export under 45 CFR 170.315(b)(10), which requires exporting a single patient's information and a full patient population in a computable format with published documentation. If the product isn't certified, these rules don't bind the vendor, and your contract is your only protection on data access.

Planning the data migration#

Ask each vendor for a written migration scope before you compare prices, because "we'll migrate your data" can mean anything from a full history to a spreadsheet of names. These are the pieces a hospice actually needs on day one:

  • Active patients with their election effective date, current benefit period number and start date, and any prior hospice days, so recertification and face-to-face dates calculate correctly.
  • Benefit period history, including transfers and revocations, because the routine home care day count and future period numbers depend on it.
  • Signed election statements, addenda, certifications and face-to-face attestations, as documents tied to the right patient and period.
  • Current medication profiles, with related and unrelated medications marked, plus allergies and active orders.
  • Plans of care and the most recent comprehensive assessment and IDG review date for each active patient.
  • HOPE records already submitted to CMS, and for each active patient, which visits in the current windows are still due.

Discharged and deceased patients are a separate decision. You still need their records for the retention period and for any ADR, so either migrate them in a readable form or keep read-only access to the old system for as long as you might need it.

Here is a cutover approach we'd suggest, offered as advice rather than a rule. Pick a cutover date early in a month so the last claim from the old system covers a full month. Freeze new admissions in the old system a few days before, then load active patients and check every one by hand: benefit period, next recertification, next IDG date and open HOPE windows. Run a mock month-end bill from the new system against a recent month you've already billed, and compare. Keep the old system read-only until all claims and NOEs filed from it have cleared. How long each of these steps takes depends on your census and the vendor, so ask for their plan in writing and test it against your own calendar.

Contract and pricing questions to ask#

These are suggestions, not legal advice, and a health care attorney should read the final agreement.

  • What is the pricing basis (per patient day, per user, per admission or flat), and what's included in it: billing, HOPE submission, e-prescribing, the clearinghouse, support, training?
  • What do implementation and migration cost, is that a fixed quote, and what happens if it runs over?
  • How much can prices rise at renewal, and is there a cap?
  • What is the minimum term, the notice period, and the termination right if the vendor misses its commitments?
  • What uptime does the vendor commit to, and what credit do you get if it falls short?
  • When CMS changes the rules each October, are updates included, and when will they ship?
  • What does the full data export at the end of the contract cost, and in what format does it come?
  • Who owns the data, and can the vendor use de-identified data from your records for its own purposes?

A quick checklist for comparing vendors#

Area Ask the vendor to show you
Admission Election, addendum and NOE with acceptance tracking, prior hospice days and transfers
Benefit periods Recertification and face-to-face due dates, including for readmitted patients
IDG A 15-day review schedule and agendas built from recent documentation
Quality HOPE admission, HUV1, HUV2, symptom follow-up and discharge inside the visit workflow
Field use Offline documentation on a tablet with no signal, and how sync conflicts resolve
Medications Related versus unrelated medications and comfort kits
Billing Claims by level of care, add-on visits, NOEs, NOTRs and aggregate cap monitoring
Cost report Exports of patient days, visits and statistics for Form CMS-1984-14
Audit readiness An ADR packet in minutes and a full access log
Security A signed BAA, subcontractor list, audit logs, MFA and breach notice terms
Migration A written scope and fixed quote for patients, history and documents

You can check the dates any vendor shows you against our hospice date calculator.

Where Quillward fits#

ChartWarden is built only for hospice and covers each row above. Keptware covers the cost report. Book a demo and bring your scenarios.

Sources

  1. 42 CFR Part 418: Hospice careecfr.gov
  2. 42 CFR 418.21: Duration of hospice care coverage, election periodsecfr.gov
  3. 42 CFR 418.22: Certification of terminal illnessecfr.gov
  4. 42 CFR 418.24: Election of hospice careecfr.gov
  5. 42 CFR 418.26: Discharge from hospice careecfr.gov
  6. 42 CFR 418.28: Revoking the election of hospice careecfr.gov
  7. 42 CFR 418.30: Change of the designated hospiceecfr.gov
  8. 42 CFR 418.56: Interdisciplinary group, care planning, and coordination of servicesecfr.gov
  9. 42 CFR 418.104: Clinical recordsecfr.gov
  10. 42 CFR 418.108: Short-term inpatient careecfr.gov
  11. 42 CFR 418.302: Payment procedures for hospice careecfr.gov
  12. FY 2027 Hospice Wage Index and Payment Rate Update final rule (Federal Register, August 3, 2026)federalregister.gov
  13. CMS Medicare Claims Processing Manual, Chapter 11: Processing Hospice Claimscms.gov
  14. CMS Medicare Benefit Policy Manual, Chapter 9: Coverage of Hospice Services Under Hospital Insurancecms.gov
  15. CMS Medicare Program Integrity Manual, Chapter 3 (additional documentation requests)cms.gov
  16. CMS HOPE Guidance Manual v1.03 (effective October 1, 2026)cms.gov
  17. 45 CFR 164.502: Uses and disclosures of protected health information, general rulesecfr.gov
  18. 45 CFR 164.504: Uses and disclosures, organizational requirements (business associate contracts)ecfr.gov
  19. 45 CFR 164.312: Technical safeguardsecfr.gov
  20. 45 CFR 164.410: Notification by a business associateecfr.gov
  21. HHS: Business Associate Contracts (sample provisions)hhs.gov
  22. HHS: Business Associateshhs.gov
  23. HHS: Summary of the HIPAA Security Rulehhs.gov
  24. HHS: Breach Notification Rulehhs.gov
  25. 45 CFR 171.102 and 171.103: Information blocking definitionsecfr.gov
  26. 45 CFR 170.315(b)(10): Electronic health information exportecfr.gov
  27. ONC: Information Blockinghealthit.gov

Quillward Health Team

Written by the Quillward Health team, who build hospice software alongside people who run a Medicare-certified hospice. Every regulatory fact is checked against CMS and federal sources. How we research and review.

General information, not legal or reimbursement advice. Confirm requirements with your MAC or counsel. Last reviewed October 12, 2026.

Put these deadlines on autopilot.

ChartWarden and Keptware track every date in this guide for each patient and each fiscal year.