Book Appointment

Cancer Hospital Patient Coordination: The Mock Day That Worked

Healthcare IT

At one mid-sized cancer centre, the patient services group, which we will call the Ridgeway unit, carried a nagging headache they had never put a name to. Every Monday morning, new outpatients arrived with files in various states of completeness, and the coordinators spent the first two hours chasing paper. Lena, the team lead, decided to stop treating each Monday as a fresh emergency. Her plan was a cancer hospital patient coordination mock day: a full rehearsal of the administrative journey, with colleagues playing the roles of patients, so the gaps would show up while nothing was at stake. This is the story of how it went, and what any team or family can borrow.

Why a mock day, and why not just fix the forms

Lena’s first instinct had been to rewrite the intake forms. A colleague, Tomas, argued against it. “We would be guessing,” he said. “We only see the failures after real people walk into them.” He proposed rehearsing the whole flow once, start to finish, using a made-up file and a volunteer from the billing office as the patient. Nobody would be inconvenienced, and anything that went wrong could be fixed before it touched anyone.

Lena agreed on two conditions. The rehearsal had to cover only the administrative path: registration, document checks, appointment booking, payment questions and the walk between departments. Nothing clinical would be acted out. And every problem found would be written on a shared sheet with a name next to it, not discussed in the abstract.

Setting up the rehearsal

The team chose a quiet Thursday afternoon. They prepared three pretend files. One was complete and tidy. One had a missing referral letter. One had an insurance approval that named the wrong hospital location. Tomas played the patient’s relative and was told to ask the questions real relatives ask: where do we wait, who do we call if we are lost, and what happens if the scan report is on a phone and not on paper?

The coordinators were told to behave exactly as they would on a normal Monday, with no extra politeness and no hints. A stopwatch sat on the desk. Another colleague, Priya, was the observer and carried a clipboard with one instruction: write what happens, not what you think should happen.

What broke in the first twenty minutes

The first thing to fail was the simplest. The registration desk and the appointment desk each kept a separate list of required papers, and the two lists did not match. A patient could clear one desk and be turned away from the next. Nobody had noticed because no real patient had ever been asked to do both in one sitting in the exact same order.

The second failure was the phone. The pretend relative called the number printed on the appointment slip and reached a line that rang out. The slip had been printed from a template that still carried an old extension. In a real week, that would have cost a worried family a long wait on the pavement.

What broke later

By midafternoon the team had reached billing. The staff member there asked for an estimate letter, which the appointment desk never gave out. Another gap, found in minutes. By the end, the sheet listed eleven items. Lena was careful not to call any of them blame. “This is the cheapest list we will ever have,” she said.

The fixes were dull, which was the point

The repairs took less than a week. The two desks merged their document lists into one shared page. The appointment slip template got the right number and a second contact. A short “what to bring” sheet went into every confirmation message. Someone even stuck a floor-plan arrow near the lift after the walk-through revealed that the pretend relative had gone to the wrong wing twice.

None of these changes involved new software or a consultant. They involved a Thursday afternoon, three fake files and a clipboard. The next Monday, the coordinators reported that the first two hours of the morning were calm for the first time in months.

Lessons any team can take from the Ridgeway story

  • Rehearse the whole path, not one desk. Failures hide in the hand-offs between stations.
  • Use fake files with deliberate flaws. A perfect file proves nothing. A file with one wrong detail proves a lot.
  • Let an observer write, not fix. Fixing during the rehearsal hides the pattern.
  • Put names beside every finding. A list without owners decays.
  • Keep the scope non-clinical. The rehearsal tests paperwork, signage and phone lines, never treatment decisions.

For families: the same idea at kitchen-table scale

A big team is optional here. A family preparing for a first appointment can build a pretend file of their own. Lay out identity papers, referral letters, reports and insurance details, then ask a relative to read them as a skeptical desk clerk would. If you are weighing where to go, reading a discussion of why independent accreditation matters when looking at overseas centres can shape the questions you rehearse. And a list of suggested questions to bring after receiving a diagnosis makes a good addition to the folder. Any decision about care itself belongs with the treating doctors; the rehearsal is only about logistics.

A cook’s version of the same rule

Lena, who loves cooking, likes to point out that kitchens have always worked this way. A trial batch before a family gathering exposes the missing ingredient while there is still time to shop. People who enjoy that tradition might like Blendz, a worldwide collection of vanishing family dishes, uncommon produce and kitchen tales that readers are welcome to add to. The recipes there come from cooks who learned by repeating a dish quietly until it was right.

Running your own mock day: a plain schedule

  1. Pick a quiet slot. An hour or two when no real work is waiting.
  2. Prepare three files. One complete, one with a missing paper, one with a mismatched detail.
  3. Assign roles. A pretend patient, a pretend relative, the real staff, and one observer.
  4. Time every stage. Slow spots show up on a stopwatch before they show up in complaints.
  5. Debrief the same day. Write each finding on a shared sheet and give it a name and a deadline.
  6. Repeat after the fixes. A second short run proves the repairs worked.

When a mock day is not enough

Be honest about the limits. A rehearsal catches predictable friction, not every surprise. Real patients bring stress, unexpected questions and unusual cases, and some days will still be messy. But a team that has walked its own process once, with a stopwatch, handles those days differently. They know where the files live, which phone numbers work and who owns each step.

Lena still runs the exercise every few months, with new fake files and new volunteers. The sheet of findings gets shorter each time, which she takes as the real measure of success. Her closing note to the unit, pinned beside the clipboard, is blunt and practical: if a step has never been tried on a quiet afternoon, assume it will trip somebody on a busy morning.