The Local Pharmacy Is a Hospice Care Team Member. Your Technology Should Treat It That Way.

A patient enters hospice on a Tuesday afternoon. The admission paperwork moves through the office. The first prescriptions go out by the end of the day. The hospice nurse, the medical director, and the case manager are new to the patient. The pharmacist on the corner of Main Street is not. He has been filling her thyroid medication for the better part of fifteen years.

Hospice doesn't replace the relationships a patient already has. Their primary care physician is still their primary care physician. Their pharmacist is still their pharmacist. Hospice arrives on top of those relationships and adds a clinical team, a plan of care, and a new layer of medications: a comfort kit on day one, additional symptom management as the disease progresses, sometimes daily adjustments. The pharmacy that has been filling this patient's blood pressure medication for a decade is now also filling her morphine, her lorazepam, and the first comfort kit her daughter has ever held in her hands. The pharmacist is one of the few constants in the medication picture.

By any plain-language definition of the words, that pharmacist is a member of the patient's care team. In most hospice software, he is a fax number.

On the care team whether the org chart says so or not

Hospice talks about the care team in clinical terms. The physician, the nurse, the chaplain, the social worker, the aide. The list is intentional and protected, because the team is what makes hospice hospice. The people on that list are not the only ones the patient and family interact with during the dying journey, and they are not always the ones the family already trusts.

The local pharmacist often is. He has filled this patient's medications for years. He knows the daughter by name. When the first hospice prescriptions arrive, they land on a patient profile he has known for a decade. The next time the daughter walks in, she is picking up the first comfort kit. The pharmacist is the one walking her through what each medication is for and how to use it.

Some of this work is clinical. Most of it is human. All of it is care team work, whether the hospice's org chart acknowledges it or not.

It is not who manages the pharmacy relationship, it is how

The pharmacy relationship has to be managed by someone. At most hospices, the PBM does it. At some hospices, an internal clinical leader does it. Either way, the practical work falls to whoever has the tools: the visibility into claims, the formulary configuration, the contact with the pharmacy network. That arrangement is not inherently a problem.

It becomes a problem when the tools fall short of the work.

A pharmacy technician sits on hold with a PBM for forty-five minutes to ask a question on behalf of a hospice patient. When they finally reach someone, they are told the PBM will follow up with the hospice and get back to them. The follow-up arrives the next day, or it doesn't arrive at all. When the claim finally processes, the pharmacy sees what it earned on the prescription: eighty-three cents. An hour of staff time, eighty-three cents in margin. That math doesn't work for the pharmacy. Over time, it doesn't work for the hospice either, because pharmacies that cannot make hospice scripts pencil out begin accepting them with less enthusiasm. Some stop accepting them at all.

Local pharmacies often go above and beyond for hospice patients. They deliver kits on Sunday afternoons. They call back when something seems off. They take questions at the counter that aren't theirs to answer. The hospice staff is doing the same kind of work on its side. The tools that connect them should be valuing both halves of that effort, not adding to it.

None of this is intentional. It is what happens when the tools fall short and both sides absorb the difference.

A hospice that decides to manage the relationship internally can land in the same place, with different mechanics. If the tools the hospice has are limited to what its PBM exposes, the hospice's ability to be a good partner is limited in the same shape. The pharmacy hears the same hold music, just with a different logo on it.

A hospice can want to be a great partner and still be a frustrating one to work with, because the tools determine what is possible.

Reactive software hands the friction to the pharmacy

There is a second, quieter reason the local pharmacy ends up at arm's length. The software the hospice and the pharmacy share is mostly designed to handle what has already happened, not to prevent what is about to.

A prescription goes out. The claim rejects at the pharmacy counter. The pharmacist now has a problem he didn't create. The family in front of him expects an answer. The hospice nurse who wrote the script is in the field. The PBM may or may not pick up. So the pharmacist makes the calls. He explains the situation to the family, again. He fields the next family's call about the same kind of thing. Multiply this by the hospice patients on his roster and the rejection rate any hospice runs, and the local pharmacist is now spending real hours of his week as the rejection-handling layer for a workflow he did not design.

None of that labor is about the medication. It is administrative bloat that shouldn't exist in 2026, paid for in staff time by both sides.

The hospice end of the friction looks different but costs the same. Office staff field calls from pharmacies, PBMs, and family members about prescriptions that didn't go through. Team leads chase prior authorizations after the fact. Nurses get pulled from patients to answer questions that wouldn't have come up if the pharmacy hadn't received a rejection. The cumulative effect is the most reliable burnout pattern in hospice pharmacy administration, and it does as much damage at the nursing station as it does at the pharmacy counter.

A pharmacy that never has to call

The simplest way to know whether your pharmacy relationships are working is to ask the pharmacies. If they say they almost never have to call your hospice, the relationship is working. If they say they spend hours a week trying to reach someone, the relationship is wearing down whether you can see it or not.

The goal of pharmacy administration done well is not better hold music. It is fewer reasons to be on hold in the first place.

When the information clinicians need is surfaced inside the prescribing workflow before an order is placed, prescriptions arrive at the pharmacy in a state the pharmacy can act on. The claim processes. The medication leaves the counter on the first attempt. The family does not wait. The pharmacist does not have a problem to solve on behalf of a hospice nurse he cannot reach. He has a script, a patient, and a brief moment of being useful to a family that is going through some of the worst weeks of their lives.

That outcome matters as much to the pharmacy's economics as to the hospice's. A low-margin generic is workable for the pharmacy if filling it doesn't cost half an hour of administrative cleanup. Lower administrative overhead means pharmacies are more willing to fill the cheap medications, which means the hospice's drug spend stays where it should be. Both sides come out ahead, and neither is paying for the other.

This is what it looks like when the company managing the pharmacy benefit is set up to make the pharmacy network succeed. Service levels run in both directions. Compensation reflects the work the pharmacy is actually doing, and volume is earned rather than assumed. The administrative environment stays calm. The central commitment is that the pharmacy almost never has to pick up the phone.

What to verify

Hospice executives don't usually have day-to-day visibility into the pharmacy side of the relationship. That isn't a failing; the work happens at the counter and on the phone, not in the C-suite. The pharmacy isn't going to volunteer the complaint. The questions worth asking aren't subtle.

The pharmacist on Main Street is doing care team work either way. The question is whether your pharmacy workflows are making it easier or harder.