Pricing
Pilot program · through October 15, 2026
The first ten hospices onboard as pilots — $500 integration, half the standard $1,000 deposit.
A limited pilot cohort at a reduced setup rate, working directly with our team as we build your EHR integration.
Fewer than 50 patients on census
Billed monthly
Independent agencies operating a single location, moving from sample-based internal audit to continuous review of the whole census.
50 – 150 patients on census
Billed monthly
Regional agencies with one or more branches, an accreditor to satisfy, and a QAPI program that needs to run from production data rather than spreadsheets.
150+ patients on census, or multi-state
From $2,500 / month · scoped to your organization
Multi-location organizations and health systems that need compliance posture rolled up across branches, with deployment scoped alongside your IT, compliance, and EHR vendor teams.
One-time $1,000 integration deposit covers the backend integration and API setup that connects Hospice Helper to your EHR. Separate from the monthly subscription — $500 for the first ten pilot agencies through October 15, 2026.
Census bands are a guide. If your agency sits at a boundary, or operates more than one location, we will place you on the tier that fits during the deployment conversation.
Included in every plan
The four modules, the Medicare audit tracker, the integrations that are available today, and the security posture behind them are part of every tier. Plans differ in scale, not in capability.
Every chart on the active census, reviewed continuously against citation-mapped audit checks.
HUV1, HUV2, and SFV windows tracked in your time zone; HQRP measure performance monitored continuously.
Annual evaluation, PIPs, and IDG attendance populated from the same findings surveyors will examine.
On-demand readiness reports scoped to ACHC, CHAP, TJC, or the state survey agency.
Tracker for TPE, ADR, SMRC, and UPIC notices with status workflow and due-date countdowns.
CSV/SFTP and FHIR R4 (SMART-on-FHIR, bulk export) available today; vendor integrations on the roadmap.
Encryption in transit and at rest, tenant isolation via row-level security, append-only audit log.
A BAA is executed with your agency before any production PHI is processed — no exceptions.
How pricing is determined
The contact form asks for your census and your EHR. With those, and the accreditor you answer to, we can scope the deployment and quote it in a single exchange.
Plans are sized by average daily census and the number of branches you operate — the same two inputs the contact form asks for.
Whether your EHR supports nightly CSV/SFTP export or a compliant FHIR R4 endpoint shapes onboarding effort, so it is scoped up front with your IT lead and vendor.
The BAA, the accreditor your readiness reports must satisfy, and any multi-location roll-ups are confirmed in the deployment conversation, and the final figure with them.
Questions
Anything not covered here is answered in the deployment conversation — including security questionnaires and the BAA template.
Next step
Tell us your census, your EHR, and your accreditor, and we will come back within one business day with a scoped deployment.
