The Referral Approval the Patient Never Hears About

A referral approval is good news that usually goes undelivered. The authorization comes back, somebody files it, and the patient who has been waiting to find out whether they can be seen learns nothing. They wait a week, assume it was denied or forgotten, and either call to ask or give up. Both outcomes cost the practice something, and the second one costs more because it is silent.

Practices that have worked on referral communication almost always built it for the referring office first. That is the party that complains, so that is the party that gets the status update. The patient is the one with the most at stake and the least visibility, and in OB/GYN the waiting is rarely neutral. The referral usually attaches to something the patient is anxious about, on a timeline that may be moving whether or not the paperwork keeps up.

Most groups have a referral system and still leave the patient out

The tooling is not the missing piece, which is worth establishing before anyone proposes buying more of it.

An MGMA Stat poll found that more than three groups in four, 76%, manage referrals in either their EHR at 66% or referral management software at 10%, while about one in five, 21%, still track manually and 3% answered “other.” The poll drew 309 applicable responses.

Those systems record the referral and its authorization faithfully. What almost none of them do on their own is tell the patient anything, because outbound patient communication was never the job the software was bought to do.

So the status exists, it is accurate, and it is invisible to the person it concerns most. Closing that gap is a communication workflow sitting on top of data the practice already maintains.

An approval message has to carry the next step, not just the news

A notification that says the referral was approved and stops there generates a phone call, which defeats the purpose.

The useful version carries four things: that the authorization came through, what it covers, the authorization number where the practice’s process passes it along, and specifically what happens next. If the next step is that the practice will call to schedule, say so and say when. If the next step is that the patient books, give them the way to do it inside the message.

athenaOne supports this directly. Authorization details live on the patient’s referral records, and secure messages can be sent to the patient through the portal, so the notification can be generated from the record rather than retyped by someone reading it off a screen. Retyping is where authorization numbers acquire transposed digits.

Channel choice deserves a decision rather than a default. A portal message is appropriate for detail and creates a record the patient can return to. A patient who has never activated the portal needs a call or a text pointing them to it. Sending only to the portal and considering the job done is the most common way this workflow quietly fails.

Sensitivity is a design requirement here, not a nice touch

OB/GYN referrals attach to circumstances where an insensitively worded automated message does real damage, and the practice will hear about it.

A referral may relate to a pregnancy, to a pregnancy that is no longer ongoing, to fertility care, or to a service the patient has not discussed with anyone in their household. The same cheerful template that works for an orthopedic consult is wrong for all of these, and “approved” delivered without context can land as alarming rather than reassuring.

The controls that matter are practical. Keep the wording plain and avoid celebratory framing. Keep clinical detail out of the notification and point to the record rather than restating it. Respect that portal access may be shared in some households, which is a reason to keep the message minimal and let the patient open the detail themselves.

This is also a place to let the practice decide which referral categories get an automated notification at all. Some should simply generate a task for a staff member to make a human call. Deciding that list is a five-minute conversation with your clinical leadership and it prevents the one incident that would otherwise end the program.

One approval, several linked bookings

The complication specific to this practice type is that an approved referral rarely converts into a single appointment.

Obstetric care behaves like a dependency graph rather than a visit. There is intake, then interval visits at a defined cadence, then a shift in which class of provider the patient sees later in the pregnancy. Procedures can require a clearance visit beforehand. So a patient saying “book me an appointment” is often describing several linked bookings with ordering constraints between them.

Gestational thresholds make it harder, because they change which providers are bookable partway through. Practices commonly route new patients and symptom visits to nurse-midwives and advanced practice providers so physicians can concentrate on procedures and higher-risk patients past a certain point, and elsewhere the same rule appears as physician-only after a later threshold. Either way the set of bookable providers moves during the episode, which no static scheduling rule captures.

The automation’s job is to book what the rules allow and to recognize when a request needs more than one appointment, then hand the sequencing to staff where the practice wants a person deciding. It applies the practice’s thresholds; it does not evaluate the pregnancy. That distinction is the whole boundary, and it is what keeps this workflow administrative.

Plan for the reply before you send the message

Any outbound notification creates inbound volume, and a practice that sends approvals without deciding where the answers go has moved the bottleneck rather than removed it.

OB/GYN practices tend to be specific about this, and their rule is a good default. When a patient asks to speak to a doctor, ask what they need first. Anything the patient describes as urgent, and anything pregnancy-related, goes to the nursing team during hours or the on-call provider after hours. Everything else becomes an appointment offer or a message to the care team.

The important property of that rule is that it routes toward a clinician by default rather than trying to sort out how serious something is. The automation is not weighing anyone’s symptoms. It is applying a practice-written rule that sends whole categories of contact to clinical staff, and the categories were chosen by clinicians precisely so the automation never has to make that call.

Build the routing before the first notification goes out. The practices that get burned here are the ones that automated the outbound half, generated a wave of replies, and left them landing in a general inbox that gets read twice a day.

Key Takeaways

Build patient-facing referral notification, not just referrer-facing. The party with the most at stake usually has the least visibility.
Make the message carry the next step. Approval news with no instruction generates the phone call you were trying to avoid.
Generate notifications from the authorization record rather than retyping. Retyping is where authorization numbers get transposed.
Do not treat the portal as delivery. A patient who has never activated it needs a call or text pointing them there.
Write sensitively and keep clinical detail out. Let clinical leadership name which referral categories get a human call instead of an automated message.
Expect one approval to become several linked bookings. Obstetric care runs on ordering constraints and provider thresholds that shift during the episode.
Decide where replies route before the first message goes out. Route anything urgent or pregnancy-related to clinical staff by rule, so nothing is left to a judgment call.

Telling a patient their referral approval came through is a small message that closes a gap the practice did not know it had. It removes a category of inbound call, it stops patients from concluding they were forgotten, and in OB/GYN it lands during a stretch when hearing nothing is genuinely hard. Generated from the athenaOne referral record, delivered on a channel the patient actually uses, with the reply routed to the right people by a rule your clinicians wrote, it is one of the cheapest improvements available in referral intake.

Sources