The chart has the history.The front desk has the rest.
A patient's trust in their doctor gets built one visit at a time, and no file can hand it to someone else. What's around that relationship is a different story: it's operational, it's learnable, and right now it lives in the heads of people who will eventually leave.
What walks out the door
None of this needs a medical licence. None of it is written down.
OakHive interviews them before they go. This is what comes back.
The patient who needs it explained twice
A medical assistant who's worked with the same doctor for years knows which patients need the same thing explained twice, slowly, before they'll agree to anything. The chart doesn't say so.
- What lands on you first
- The five things that need attention in week one.
- The patients who need it explained twice
- What was decided, and the reasoning behind it.
- Known risks & exceptions
- The one case that breaks the default process.
- Who to ask, and when
- Contacts for what isn't in this guide.
From the handover guide, written to whoever takes the role next.
The insurer that denies one code
A front-desk coordinator knows exactly which insurer denies a specific code unless it's submitted a certain way. The first the new coordinator hears of it is the denial.
- 01The five things that land on you first
- 02The insurer that denies one code, and what to send back
- 03The one exception that breaks the default process
- 04When to call, and when to escalate
Stop and ask
From the guided session that walks the role chapter by chapter.
The specialist's office that actually calls back
Referrals go out to several offices. One of them calls back the same day. Knowing which is the difference between a patient seen next week and a patient left waiting, and it's in nobody's system.
Which specialist's office actually calls back?
The one on the third floor, and only before 11. After that she left a message and chased it the next morning.
And who signed that off?
That wasn't covered in her interview, so I won't guess at it.
From the chat, answering after they have gone.
The prior authorisation that gets missed
The clinic usually finds out what the office manager knew the hard way: a missed prior authorisation, or a patient waiting longer than they should have been.
- 01What the role actually covered
- 02Prior authorisations that get missed
- 03Risks and gaps
- 04What wasn't covered
Offboarding checklist
From the manager's summary, ready before the last day.
Who to interview
The medical assistant who's worked with the same doctor for years. The front-desk coordinator. The office manager. Nobody with a medical licence has to be in the room.
The trust stays with the doctor. Everything around it stays with the practice.
Questions clinics ask
The role, not the patients: what they were responsible for, what breaks and how they fix it, the decisions they carried in their head, and who to call for what. Frustrations, opinions about colleagues and anything personal are not asked and don't appear in any document.
In Microsoft Azure's EU region, logically isolated per customer, with export and deletion on request and a data processing agreement in every contract. Access is closed by default and opened per person, and sensitive material stays with the manager and HR.
Whoever people go to instead of a document: the assistant who's worked with the same doctor for years, the front-desk coordinator, the office manager. Setup is their name and role, and the interview runs up to two hours.
Bring us the questionyour company keepsanswering twice.
Thirty minutes, no deck. You describe something your team has explained more than once, and we show you what OakHive does with it.
We are taking on a small number of companies at a time, so this is a conversation rather than a signup.