Key takeaways
- Referral and pre-authorisation paperwork moves through email, portals, trackers and phone calls across three or more parties.
- GeniOS links each insurer request and missing document to the booking that depends on it.
- The clinic operations manager gets one piece of intelligence with the referral, the gap and the next step.
- GeniOS works on the paperwork and follow-through only. Clinical decisions stay with clinicians.
The problem
A busy outpatient clinic runs on paperwork that moves between people who never sit in the same room. A referring practice sends a referral letter by email. The front desk logs it in a shared tracker and books a procedure slot. The billing team submits a pre-authorisation request to the insurer. The insurer replies, sometimes by email, sometimes in a portal, sometimes with a request for one more document.
Picture a Monday at a clinic group with three sites. The front desk handles 200 calls. The billing coordinator is working through last week's claims. On Friday an insurer emailed to say that the pre-authorisation for referral 4127 is on hold because the referral letter is missing a signature. The email went to a shared billing inbox. The tracker still says "submitted". The slot is booked for Thursday at 9:30 and is worth about $2,400 to the clinic.
Nobody sees the hold until Wednesday afternoon, when the front desk calls to confirm the appointment and the billing team checks the portal. There is no time to get a signed letter from the referring practice and a decision from the insurer. The slot is cancelled, the patient is rebooked weeks later, and the clinic carries an empty slot it could have filled.
Why it slips today
Each party does its own part. The gap is between them. Nobody owns the whole path from referral received to approval in hand, so a hold on one step does not reach the people who could fix it.
The shared tracker shows what someone last typed. It does not read the insurer's replies. The insurer portal shows status, but only to whoever logs in. The booking calendar shows the slot, but not whether the paperwork behind it is complete. And the referring practice does not know its letter was rejected unless someone calls.
| Where it lives | Who sees it | How it slips |
|---|---|---|
| Insurer request for a document | A shared billing inbox | Read late, or by someone who cannot act |
| Referral tracker | Front desk and billing | Says "submitted" long after a hold |
| Booking calendar | Front desk | No link to the paperwork behind a slot |
| Referring practice | Their own office | Never told its letter needs fixing |
The solution
GeniOS reads email, calendar, chat, documents and the business tools you already use, read-only to start. It keeps each referral tied to the paperwork and booking behind it, and surfaces:
- Bookings without approval. A booked slot close to its date where the insurer approval is not yet in hand.
- Insurer requests with no reply. A request for a document or detail that has not been answered.
- Referrals that went quiet. A referral received with no booking, no request and no next step after a set number of days.
- Paperwork completed. An item closed only on proof, such as the insurer's approval or the sent document.
Each piece names the referral by its reference, the gap, one owner and a date. It does not read or summarise clinical notes, and it never suggests a clinical decision. For work that falls between teams in any business, see Cross-Team Handoffs.
See it on the whiteboard
The board below follows one referral from a missed insurer email to an approval in hand before the booked slot.
A Thursday booking has no approval yet
How: get the signed letter from the referring practice and send it to the insurer today.
- Your tools
The insurer email, the front desk tracker and the booking calendar each hold one piece. GeniOS reads them where they are.
- GeniOS thinks
It links the hold to the Thursday booking and sees the tracker was never updated.
- Intelligence
The Clinic Operations Manager gets one item: send the signed letter to the insurer today.
- Delegated
The coordinator calls the practice, and she approves a Reply Drafter's insurer email before it goes.
- Goal moves
GeniOS sees the sent reply, then the approval, and moves the approvals goal.
How GeniOS thinks and plans
GeniOS connects the pieces as an experienced practice manager would. What happened: the insurer put the pre-authorisation for referral 4127 on hold because the letter is not signed. What is the pattern: the request reached a shared inbox, the tracker still says submitted, and nobody told the referring practice. Requests from this insurer have gone to the same inbox and waited before. What is the impact: a booked Thursday slot worth $2,400, and a patient who would wait weeks for another. Who owns it: the Clinic Operations Manager, because the fix needs the front desk, billing and the referring practice.
It checks this against the clinic's goals, which it forms from your own plans, board packs and management meetings. If a goal this quarter is to cut same-week cancellations, a booking three days out with no approval ranks high. GeniOS then picks one next step and a date. The insurer usually decides within a day of a complete file, so the signed letter has to reach them on Monday. The step is not "review all pending pre-authorisations". It is this letter, today.
How it delegates and gets it done
The owner answers with Delegate, Done, Later or Not relevant. The operations manager can delegate the call to the referring practice to the referral coordinator, and the covering reply to the insurer to a Reply Drafter agent that writes from the insurer's request. She reads the draft and approves it. Nothing goes to an insurer or a practice until a person says yes. This keeps people in charge, as described in human in the loop vs human on the loop.
The item closes only on proof: the sent reply with the signed letter, then the insurer's approval. If the approval has not arrived by Wednesday noon, the item comes back with time to move the slot to another patient instead of leaving it empty. When it closes, the goal moves, and GeniOS learns. If one insurer always asks for the same document, the next referral for that insurer is flagged before submission. Where approvals drive payments, Cash and Payment Obligations follows the money side.
How it reaches you
The intelligence arrives on its own in the GeniOS Mac app, from the menu bar, and in the web dashboard. The operations manager does not log into insurer portals one by one, compare the tracker with the booking calendar by hand, or wait for a weekly cancellations report.
What the team stops doing: chasing billing for status on Wednesday afternoon, analysing denial reports to guess which bookings are next, and deciding each morning which of 150 open referrals to check. People keep every decision, and clinicians keep every clinical one.
A worked example
The company, names, dates and numbers in this example are made up to explain the idea. It describes a three-site outpatient clinic group in Phoenix with 160 staff.
On Friday 7 November at 16:40, an insurer emails the clinic's shared billing inbox. The pre-authorisation request for referral 4127 is on hold because the referral letter from the referring practice is not signed. The tracker still says "submitted". The procedure is booked for Thursday 13 November at 9:30, a slot worth about $2,400 to the clinic.
On Monday at 8:15, Grace, the Clinic Operations Manager, receives one piece of intelligence. It names referral 4127, quotes the insurer's request, shows the Thursday booking and notes that the insurer usually decides within a day of a complete file. It suggests getting the signed letter from the referring practice and sending it to the insurer today.
Grace delegates the call to Tomás, the referral coordinator, who reaches the practice manager at 9:20. The signed letter arrives by email at 10:10. Grace delegates the covering reply to a Reply Drafter, checks that the right reference is on it and approves it. It goes out at 10:45. The insurer approves on Tuesday afternoon. GeniOS sees the approval, closes the item and moves the goal for approvals 48 hours before the slot. The Thursday appointment goes ahead, and the tracker is updated with the approval reference.
How to measure it
Track these month to month.
- Days from referral received to booking. How long a referral waits before the patient has a date.
- Bookings with approval 48 hours ahead. The share of booked slots with the insurer approval in hand two days before.
- Hours to answer an insurer request. How long a request for a document waits before a complete reply goes back.
- Slots lost to paperwork. Cancellations caused by a missing approval or document.
Where it applies
These are application areas we are exploring. They fit outpatient clinics, diagnostic centres, day surgery units and specialist practices that depend on referrals and insurer approvals. The work is administrative: documents, requests, bookings and follow-up. For why this needs more than a shared inbox, read why company intelligence is required.
- Domains: Administration, Operations, Finance
- Industries: Healthcare
- Roles: Managers, Executives
Questions about referral and pre-authorisation follow-through
Does GeniOS read patient records?
It is designed around the operational paperwork: referral references, insurer requests, bookings and the messages about them. Which sources it reads is your choice, and it does not make or suggest clinical decisions.
Does it submit requests to insurers?
No. An agent can draft a reply or covering note, but a person approves it before anything is sent, and submissions happen in your own process.
What if insurers reply in their portals?
Where portal updates reach email or a tool you connect, GeniOS reads them there. Where they do not, the team's tracker updates and messages still show the gap.
Why is this marked Exploring?
We are working through this area with early customers before calling it ready. If referrals and approvals cost your clinic slots, a call is the best way to see how it would fit.
Status
Exploring This is an application area we are exploring with early customers. We start read-only, on a small set of sources you choose, and shape the work with your team. Book a call and tell us how this work runs today.