The patient liaison team at a mid-sized orthopaedic centre noticed a pattern in the calls it received about knee care. Families rarely phoned to dispute anything. They phoned because they could not read the estimate. One liaison, whom we will call Dev, started keeping a tally of the questions, and almost all of them boiled down to the same request: tell us what one unit of this covers. What follows is a story of how that team rebuilt its explanations around the cost per unit. The people and the centre are invented for illustration; the habits described are ordinary ones. Nothing here gives medical advice, quotes a price or judges any charge.
The first conversation
It began with a call from a woman arranging care for her mother’s knee. She had an estimate, a total at the foot, and a worried voice. Dev did what the team had always done: he repeated the total and offered to send the document again. The caller said politely that she did not need the document again, she needed to know what was in it. That sentence stayed with him. A total repeated slowly is still a total.
The team meeting
At the next team meeting, Dev described the call. A colleague, Ananya, said the same thing happened to her weekly. They agreed on an experiment: for one month, whenever a family called, they would not discuss the total first. They would ask which unit the family cared about most, and explain that. A day of stay, a consultation, a physiotherapy session, a named component of a package. Plain descriptions in everyday words, agreed in advance so every liaison said the same thing.
Building the unit descriptions
The team gathered a short list of units and wrote what each included and what it did not. They checked each description with the departments responsible, so that nobody would be promised something the ward could not deliver. They were careful about one thing: describing contents is not the same as guaranteeing a final amount. Where an element depended on how treatment progressed, the description said so in plain terms. Clinical questions, such as how many days a patient might stay, were passed to the treating doctors rather than answered by liaison staff.
What the families noticed
Within weeks, the tone of calls changed. Questions became specific: does a day include the physiotherapist’s visit? Is the follow-up review inside the package? Families who understood a unit began to write the answers on one sheet and share it with relatives. Arguments about “what we were told” faded because there was a single version. Dev noticed that fewer calls came back a second time with the same confusion, which gave the team more room for the calls that genuinely needed attention.
Where background reading helped
Several families asked for reading to help them understand the clinical side so that the lines on the estimate meant something. The team pointed them to the explainer on the way doctors assess knee problems and shape a plan, and to a gentler piece about everyday activities that can leave knees sore. The liaison staff never used these to steer anybody toward a decision. They were offered as context, so that the words on a statement, such as consultation or rehabilitation, did not feel foreign.
An idea borrowed from outside medicine
The idea did not originate with the team. Ananya’s brother works in software, and over dinner he had described how his employer once wrestled with a cloud invoice that no one could interpret. The engineers and the finance staff began splitting it by something tangible, such as each customer served, and the arguments turned useful. He had picked up the method, called FinOps, through FinOpsSchool, which runs FinOps courses and certification. Hospitals are not software firms, and Ananya was firm about that. Even so, the underlying move travelled well: name the piece, then ask what is inside it.
The team also learned to listen for the unit hiding inside a worry. When a caller said a statement felt heavy, the real concern was often a single repeating line, such as the daily charge, and naming it gave the conversation a place to land. Dev began to jot the likely unit next to each call note, which made handovers between liaisons smoother. A colleague returning from leave could read the note and continue where the last person stopped, with no need for the family to repeat the story from the beginning.
A difficult case
Not every call was easy. One family had misunderstood an item and was upset. Dev did not defend the statement or argue with the family. He asked which unit worried them, described what that unit included, and offered to arrange a conversation with the right department. The family did not leave delighted, but they left informed, and they said so. The team concluded that the method is not a remedy for every frustration. It is a way of making sure that, whatever the frustration, it is directed at the right question.
What the team learned
- Describe the unit before you discuss the total.
- Write descriptions with the departments that deliver the service.
- Separate what a unit covers from what the final amount will be.
- Hand clinical questions to clinicians, every time.
- Offer families a single shared page, not scattered phone notes.
What it did not change
The team was clear-eyed about limits. The method did not change a single clinical decision. It did not claim to say whether any amount was reasonable, and liaison staff were told never to express a view on that. It did not eliminate uncertainty, because some elements genuinely depend on how treatment develops. What it changed was the quality of the questions and the calm of the conversations around them, which turned out to be what families valued most.
A year on
When Dev reviewed the tally a year later, the most common opening line from callers had changed. It used to be, “I do not understand this estimate.” Now it was, “Could you explain what one day covers?” The second sentence is easier to answer and kinder to everyone involved. The team added its unit descriptions to the welcome pack handed to every new knee patient, and Ananya began a habit of ending calls by asking if the family wanted the explanation sent as a single page. Most said yes.
