Palliative care is not early hospice, and software built for hospice does not fit it. The episode has no defined benefit period, the patient may be receiving active treatment at the same time, funding is mixed and often uncertain, and the clinical story runs over months with symptom trends that matter more than any single visit. This page sets out what an agency delivering community palliative care should look for.
Open-ended episodes break benefit-period logic
Hospice systems organise everything around election, benefit periods and recertification. Palliative care has none of that. A patient may be on your caseload for two years, come off it when their treatment succeeds and return later. A system that requires a certification cycle to exist will have empty required fields on every record, and empty required fields are how a clinical record quietly stops being trustworthy.
Symptom trends over time, not visit snapshots
The clinical value in palliative care is in the trend: pain scores, breathlessness, function and the effect of each change in medication over weeks. A system that stores each visit as an isolated note makes the trend invisible unless a clinician reads the whole chart. Ask to see a symptom charted across a caseload of months, and ask what happens when the assessment tool your team uses is not one the vendor ships.
Mixed and uncertain funding
Community palliative care is funded by a mix of health plan contracts, grants, charitable income and direct billing, and the mix changes. The system has to attribute time and visits to funders without forcing clinicians to think about it at the point of care. If cost attribution is a field on the visit note, your data will be wrong, because a nurse at a bedside is not the right person to answer a funding question.
Working alongside other teams
Palliative patients also have oncologists, primary care physicians, hospital teams and sometimes a hospice waiting downstream. The practical need is a shared, current summary the rest of the system can read: current medications, goals of care, escalation plan and who to call at three in the morning. Ask specifically how that summary is produced and shared, because it is the artefact other clinicians will judge you on.
Questions people ask about palliative care software
Can we run palliative care on our hospice system?
Many agencies do, and it works when the vendor supports a genuine non-hospice programme rather than a hospice record with the certification fields ignored. The test is whether an episode can exist with no benefit period at all.
How important is symptom scoring in the software?
Very, if you want to demonstrate outcomes to a health plan or a funder. A system that cannot chart your chosen instrument over time leaves you exporting to a spreadsheet, which is where most palliative outcome reporting still unfortunately lives.
Do we need medication reconciliation?
Yes. Palliative patients typically carry complex regimens changed by several prescribers, and reconciliation at each visit is core clinical work rather than an administrative extra. Make sure it is a workflow, not a text field.
What about patients who transition to hospice?
Ask how the transfer works if hospice is a different programme or a different agency: what carries over, what is re-entered, and whether the family answers the same questions twice. That handover is the point where families lose confidence.