When I started as a front-desk coordinator at a cardiac outpatient unit, I kept a notebook of every question I had to ask twice. A few months in, I turned it into a short guide for the next person who would sit in my chair. This article is that guide in question-and-answer form, with the same honest gaps. It covers how a cardiac hospital visit is organised from an administrative point of view, and how writing it down helped me understand it. It is strictly informational: nothing here is medical advice, no treatment is being rated, and each hospital runs its own procedures.
Why write a guide after only a few months?
Because that is when you still remember being lost. Someone with ten years in the job cannot recall which acronym baffled them on day two. I could, and my confusion was fresh enough to be useful. Explaining the process to a newcomer also showed me which parts I had only half understood, so the guide did as much for me as it did for the reader.
What is the first thing a new coordinator should learn about a visit?
The order of events. A visit is a chain: someone books, someone confirms, the patient arrives, details are checked, the person is directed to the right area, and afterwards follow-up is arranged. When I tried to write that chain down, I found I could not say who owned the step between “arrives” and “directed”. Once I asked, I learned it was a shared handover with a specific checkpoint, and I added it to my notes with the name of the role, not the name of a person.
What should I do when I do not know the answer?
Say so, and find the right person. This is the single most important line in my guide. In a hospital setting, a confident wrong answer to a patient’s family can cause worry or confusion, and clinical questions belong to clinical staff. My notebook had a page titled “Questions that are not mine to answer”, and writing it made the boundary clear to me. If you are curious how a hospital explains some of its own areas to families, the guide on how cardiac intensive care guidelines are shared with patients and families is a good example of that kind of plain explanation.
How do I explain preparation without giving advice?
By pointing to the hospital’s own instructions rather than adding my own. My guide separates “what the hospital asks patients to bring or do”, which I can describe, from “what anyone should do for their health”, which I cannot. For general context on the patient side of this, there is a helpful article on what a patient might do ahead of a cardiology appointment. I read it to check that my guide used the same plain tone, not to copy its content.
Another small habit paid off: I wrote each answer twice, once as I would say it to a colleague and once as I would say it to a worried relative at the desk. The two versions differ more than you would expect. The colleague version can be brisk and full of shorthand, while the relative version must be gentle, short and clear about what I cannot answer. Practising both on paper made me noticeably calmer at the desk, and it exposed a few answers where I had been relying on tone rather than facts.
What did writing it down teach me?
Three things stood out.
- I used internal shorthand without noticing. Words like “walk-in slot” and “records pull” meant nothing to a newcomer, so I replaced them with short sentences.
- I had mixed up two different checks that sounded alike. Writing both out side by side made the difference obvious.
- I had never learned what happened to a request after it left my desk. Asking about it connected me with colleagues I had barely spoken to.
Is it worth showing the guide to a supervisor?
Yes, and early. My first version contained two statements that were outdated, and my supervisor caught both in minutes. I now date each page and invite corrections. A guide like this is a record of one person’s understanding, and it should defer to official policy every time there is a conflict.
What if the process has changed since I wrote it?
Then the guide needs updating, and that is a feature rather than a failure. I keep a short “last checked” line at the top and ask each new starter to flag anything that no longer matches what they see. In my experience, new colleagues are the best auditors because they are comparing the page with reality for the first time.
Where can I share what I have learned more widely?
Internally, first. For general, non-confidential lessons, such as how to explain a new skill or how to write a clear handover, some people publish on a blog. MyBlogPad is a network of blogs that sign in through Google, with each blog on its own subdomain and room for several contributors per blog. Never include patient details or anything your employer treats as internal, and check your workplace’s rules before posting.
How do virtual visits fit in?
They add steps rather than remove them. My guide has a short section on how remote appointments are arranged, drawing on the hospital’s own descriptions. If you want a patient-facing overview, the overview of remote cardiology support for patients sets out the idea in everyday terms, and again, my job is to describe the process, not to judge whether a particular form of care suits a particular person.
What would I tell a new colleague on day one?
- Keep a notebook of every question you ask twice.
- Write the answers in plain words within a week.
- Separate what you can describe from what is not yours to answer.
- Show it to someone senior for corrections.
- Date it, and pass it on to the next person.
Final thought
The guide I wrote was never meant to be impressive. It was meant to save the next person a few weeks of the confusion I went through. Every time I added a line, I understood my own job slightly better, which is the quiet reward of teaching what you have just learned. If you have joined a team recently, try writing your own, even if only for yourself. You will quickly find the places where your understanding has gaps, and those places are exactly where to ask your colleagues for help.