Ask a spine hospital’s international desk how they arrange a patient’s trip, and you will often hear, “Oh, Meena knows all that.” Meena knows which airport pickup is reliable, which documents families forget, and who to ring when a flight is late. When Meena takes leave, the knowledge goes with her. A patient travel coordination runbook fixes that, but plenty of teams put off writing one because of a handful of stubborn myths. Here are six of them, taken apart in plain language. Everything below concerns logistics and administration only; it says nothing about medical decisions, which belong to doctors and patients.
Myth 1: “Every patient’s trip is different, so you can’t write it down”
Details differ, but the skeleton rarely does. Someone enquires, a team confirms dates, documents are gathered, transport and a place to stay are arranged, the patient is greeted on arrival, and there is a return plan. A runbook captures that skeleton as a numbered routine and leaves room for notes where a trip departs from the norm. Think of it as the checklist an airline uses: flights differ, the pre-departure routine does not.
Myth 2: “A runbook means more paperwork”
It usually means less. Without a written routine, the same questions are asked in three emails and two phone calls because nobody is sure what has already been collected. With one, each coordinator ticks the same boxes in the same order, and a colleague picking up a half-finished case can see in thirty seconds where things stand. The paperwork is what you were already doing, written down once instead of remembered badly many times.
Myth 3: “Only the senior coordinator can be trusted with it”
That belief is what leaves a desk hanging by a thread: when only one person has the know-how, an illness, a resignation or a busy week stalls every case. Teams in the technology world learned this lesson with systems that only one engineer understood, and sites such as thedataops.org are full of writing about turning that kind of one-person knowledge into shared, repeatable practice. The same logic holds for a hospital desk: write the routine, let a newer colleague follow it, and ask the senior person to review rather than to do every job.
Myth 4: “Once it’s written, it’s finished”
A runbook that nobody edits quietly turns into a museum piece. Phone numbers change, a guesthouse closes, a visa office alters its opening hours. Assign an owner, put a review date on the first page, and add a line at the end of every trip debrief: “Did the runbook help, and what would we change?” Small edits made monthly beat a heroic rewrite every two years.
Myth 5: “It will make us sound robotic with patients and families”
A routine decides what gets done, not how warmly it is said. In fact, when staff are not scrambling to remember the next step, they have more attention for the person on the phone. Include a few sentence starters if it helps, such as how to confirm a date, how to explain what documents are needed, or how to say that a question will be passed to the clinical team. Then let people use their own voices.
Myth 6: “A runbook has to cover everything, including medical questions”
It should do the opposite. A good coordination runbook draws a firm line: logistics on this side, clinical matters on the other. It lists what the desk can help with, such as itinerary, documents the hospital asks to see, airport greeting, accommodation options and the name of the person a family meets on arrival, and it names who handles anything about symptoms, results or treatment. Keeping that boundary written down protects patients from well-meaning guesses at the front desk.
What the routine actually looks like
Here is a skeleton you can adapt for your own team.
- Intake. Record the patient’s name, contact preference, language, intended travel window and who is travelling with them.
- Document checklist. Send the standard list of papers the hospital requests ahead of time, and log what has arrived.
- Itinerary. Confirm arrival and departure dates, and note any changes the family reports.
- Local arrangements. Transfers, accommodation near the hospital, and a local contact number for the family.
- Arrival day. Who meets the family, where, and with which printed sheet of instructions.
- During the stay. A named point of contact for non-clinical questions, with their working hours.
- Departure and follow-up. Return arrangements, a courtesy message after travel, and the debrief note.
Borrow from existing reading, don’t repeat it
Your blog probably already answers some of the background families look for, and the runbook can point to those pages instead of having staff recite them. For instance, the desk can share the article on when persistent back trouble calls for a specialist hospital as general reading, and the piece comparing the range of back pain options discussed before surgery as background, with a reminder that any real decision is made with the treating team. Having those links inside the runbook means the answer is consistent and nobody has to improvise.
A quick test of your own runbook
- Could a colleague from another department run a trip tomorrow using only the page?
- Does every step have an owner and a time frame?
- Is there a clear sentence about what the desk does not discuss?
- Is there a date on the page and a name next to it?
If any answer is no, you have found the next edit. Start small: pick the trip type you handle most often, write the seven steps above in your own words, and use them on the next real case. By the third trip, the myths tend to dissolve. People find that a short, honest, regularly updated page is not a burden; it is the thing that lets the team take a day off without the whole desk holding its breath.
