Referral Status Tracking: Closing the Loop for the Referrer

Referral status tracking is the capability referring offices ask about first and the one most specialty groups quietly do not have. A practice sends you a patient, hears nothing, and has no way to find out what happened without calling and asking a person to look it up. That call is a tax on both practices, and the office paying it is the one deciding where to send the next referral.

Inside your group the information exists. Somebody received the referral, somebody worked the authorization, somebody either booked the patient or did not. It is spread across a work queue, a fax inbox, an authorization record, and the schedule, and no single person is accountable for assembling it into an answer. So the default answer to “what happened to my patient” is a promise to check and call back, which frequently does not happen, because the person who promised it is answering the next call.

Having a system is not the same as closing the loop

Most groups have already bought the tooling, which is why this gap surprises people.

An MGMA Stat poll found that more than three medical groups out of four, 76%, manage patient referrals using either their EHR at 66% or referral management software at 10%. Only about one in five, 21%, still rely on manual tracking, with 3% answering “other.” The poll had 309 applicable responses.

So three quarters of groups have a system of record for referrals. The number that can tell a referring office the current status of a specific patient without a human going to look is much smaller, because tracking a referral internally and reporting on it outward are different jobs, and only the first one came with the software.

That is the actual gap. It is not a data problem, it is a communication problem sitting on top of data that is already there.

The referring office is asking three questions, not an open-ended one

The scope here is smaller than it first appears, which is what makes it automatable.

A referring office wants to know whether you received the referral, whether the patient has been booked and when, and whether the patient actually showed. That is the whole list. They are not asking for clinical detail, they are asking whether the handoff completed, because until it does the patient is still their responsibility and their problem.

Defining those three states precisely is most of the work. Received means the document landed and was matched to a patient. Scheduled means an appointment exists with a date. Completed or not completed is the visit outcome. Each has an unambiguous answer in your systems at any given moment.

Once the states are defined, the reporting becomes a routine outbound task rather than a research project. A status update on each open referral, sent to the office that made it, on a cadence, with no one having to remember. The offices that receive it stop calling, which is the second saving and usually the larger one.

The status lives in the referral authorization record

This is the athenaOne detail that makes status tracking practical rather than aspirational.

Referral authorizations are stored per patient as retrievable records, and they can be updated as the referral moves. That gives you a place where status genuinely lives, rather than being inferred from the presence of a document in one queue and an appointment in another. Reading the authorization record and the appointment together produces the three states without anyone assembling them by hand.

It also means the update path is a real one. When an authorization is obtained, when a number comes back from the payer, or when the referral is closed, the record can be updated so the next person to look, inside or outside the group, sees the same thing.

The discipline this requires is unglamorous and it is where most implementations actually succeed or fail. If your staff work referrals in a spreadsheet beside the EHR because the EHR workflow is awkward, the authorization records will be stale and any status you report will be wrong. Fixing that is a prerequisite, and it is worth doing regardless of whether anything gets automated.

Some referrals should not have come to you at all

Here is the complication that separates a real intake workflow from a status dashboard, and the sharpest version of it is a question worth putting to any vendor.

The question is this: if a referral arrives requesting a service this department does not provide, is the system able to recognize that the referral does not belong here, or does it just tell the referring office “we have a referral on file”? A status tracker that confidently reports “received” on a misdirected referral has made the problem worse, because everyone now believes the handoff is progressing.

The right behavior is administrative and it has a clear boundary. The automation can flag that the referral does not match the service lines this department handles and route it to staff for review. It does not decide what the patient clinically needs or where they should go instead. A person makes that call, and the referring office gets told promptly rather than three weeks later when someone notices the patient was never booked.

The same pattern applies to incomplete referrals. Where required labs or imaging are missing from what arrived, the useful action is an outbound call to the referring office to request them, before the patient is booked into a visit that cannot proceed.

This is a growth capability wearing an administrative uniform

Groups underinvest here because referral status looks like back-office hygiene, and it is worth naming what it actually is.

Referring offices send patients to the specialists who are easiest to refer to. Ease is not primarily about clinical reputation at the margin, because most referral decisions are between acceptable options. It is about whether the referral gets acknowledged, whether the patient gets seen in a reasonable time, and whether the referring office ever finds out what happened.

A group that closes the loop automatically is doing something its competitors are not, and the effect compounds, because referral relationships are habits. The practice that got a clean status update last month sends the next one without thinking about it.

Start by measuring the thing nobody measures: how many inbound referrals from your top referring offices resulted in a completed visit, and how long that took. Most multi-specialty groups have never produced that number, and it is usually less flattering and more actionable than anything in the monthly report.

Key Takeaways

Owning referral software is not closing the loop. MGMA polling puts 76% of groups on an EHR or referral tool, and reporting status outward is a separate job that did not come with it.
Define three states and stop there: received, scheduled, and whether the visit happened. That is the entire question a referring office is asking.
Keep status in the athenaOne referral authorization record rather than inferring it from a document queue plus the schedule.
Fix the shadow spreadsheet first. If staff work referrals outside the EHR, every status you report will be stale.
Flag misdirected referrals for staff review instead of reporting them as received. A confident wrong status is worse than no status.
Call the referring office for missing labs or imaging before booking a visit that cannot proceed.
Measure completed-visit rate and time-to-visit by referring office. Most groups have never seen that number, and it is where the growth argument lives.

Referral status tracking is not a dashboard project. It is the difference between being a group that referring offices have to chase and one they can rely on, and the information required to make that switch is already sitting in your athenaOne referral records. An AI team working those records can answer the three questions every referring office asks, on a cadence, without anyone remembering to. The referrals that follow are the return.

Sources