The Data Your Team Needs Is Already in Your System. They Just Can't See It.

A family tells their hospice nurse that a medication is running low. The refill request goes in, the family waits, and three days later nothing has arrived. At the Thursday visit, the family asks the only person in front of them: where is it? The nurse has no way to know. She cannot see when the refill was sent, whether the pharmacy processed it, or whether the claim rejected. So the game of telephone starts: calls to the office, a portal check, hold time with the benefit manager, a call to the pharmacy. At the end of the chain, the answer finally surfaces. The claim rejected days ago because it needed a prior authorization from the hospice, and nobody at the hospice knew. The answer existed from the moment of the rejection, inside systems the hospice already pays for. The refill sat dropped while a patient ran low on medication and a family lost a little more confidence in the people caring for them.

The same afternoon, a clinical manager is preparing for interdisciplinary group. One patient's medication list has grown to fourteen lines, and the team needs to talk about which medications are still serving comfort and which are left over from a hospitalization in March. That conversation would be informed by what each medication costs, when each was last filled, and which ones the family has quietly stopped picking up. All of it is knowable. The claims and fill history hold every answer. What the manager carries into the meeting is a medication list printed from the chart and her memory of last month's vendor report.

Upstairs, an administrator is answering a question from the board about pharmacy spend. The monthly report from her vendor arrived as a PDF three weeks ago, built on data that is now closer to seven weeks old. She will answer a June question with April numbers, because April numbers are what she can see.

Three people, three decisions, one pattern. Nothing in these scenes is missing data. The hospice generated every one of these answers itself, in the ordinary course of operating. The data is there. The team just can't see it.

Captured is not the same as visible

Hospice pharmacy produces operational data at a remarkable rate. Every order placed, every claim processed, every fill dispensed, every rejection returned, every price applied, every prior authorization opened and resolved. Each event is recorded the moment it happens, because the systems that process these transactions cannot function without recording them. Capture has never been the problem.

The problem is where the data goes after it is captured. Claims history sits in a benefit portal designed for the specialists who manage claims. Dispense records sit at the pharmacy. Pricing sits inside a contract. Authorization status sits in whichever queue is holding it this week. The people making daily clinical and operational decisions, the nurse in the field, the manager walking into IDG, the coordinator triaging the morning, were never the intended audience for any of those systems. So the data is technically retrievable and practically invisible.

What fills the gap is the telephone. The nurse calls the office because she cannot see a fill status. The office calls the pharmacy because they cannot see it either. The pharmacy reads it off a screen, and the answer travels back through two more people before it reaches the kitchen table where the question was asked. Everyone in that chain did their job correctly, inside a process that should not need to exist.

And the person standing at the end of it is the nurse. She absorbs the family's frustration on the hospice's behalf, and she gets no help from the systems she is supposed to be able to trust. Burnout in hospice rarely comes from the hard parts of the work. It comes from the preventable ones.

A monthly report describes decisions you already made

The standard answer to this gap has been reporting. The vendor compiles the month, formats the summary, and sends it over. Reports have a real place, trends matter, and a hospice should absolutely know its cost per patient day. But a report is a look backward. By the time spend appears in a monthly summary, the prescriptions that drove it have been written, filled, and billed. Reviewing it is archaeology, useful for understanding what happened, useless for changing it.

The decisions, meanwhile, happen in the present tense. The medication review is today. The recertification visit is today. The family at the counter is waiting today. A team working from last month's report is making this week's decisions on a delay, and the delay is structural, no amount of diligence on the team's part closes it.

This is the difference between a reactive posture and a proactive one. Reactive answers arrive after the claim, in the portal, in the report, in the phone call that follows the problem. Proactive answers surface before the decision, in the workflow where the decision is being made.

What surfacing actually looks like

Surfacing is a design choice, and it is more specific than "better dashboards." It means deciding that the data belongs where the team already works, shaped for the decision being made there.

The fill status belongs inside the patient record, on the screen the nurse already has open at the bedside, so "did this medication make it home" is a glance instead of a phone tree. The cost and fill picture belongs in front of the clinical manager during medication review and recertification, current as of this morning, so the conversation about a fourteen-line regimen is grounded in what is actually happening at the pharmacy. The open rejections and authorizations belong in a worklist the coordinator sees first thing, each one carrying the diagnosis and context needed to resolve it, so the morning starts with the work instead of a sweep of portals to find the work. The spend picture belongs to the administrator as a living number, so the board's question gets this week's answer.

And the effect lands where families can feel it. When the people writing and reviewing orders can see coverage, price, and history at the moment of decision, the prescriptions that leave the building are clean, the claims process cleanly at the counter, and the medication is ready when the family arrives.

There is a reason this blog is called Illuminations. The defining problem of hospice pharmacy data is not collection. It is darkness. The answers a hospice team needs are already being generated, recorded, and stored by the systems the hospice already pays for. The work that remains is bringing those answers into the light, at the place and moment where someone on the team is deciding what happens next.

Hospice teams do not need more data. They need to see the data they already have while it can still inform the decision in front of them. That is the difference between a system that records what happened and one that illuminates what is happening.