There is a category of work in every practice that has no owner and no queue. Someone should check whether Mrs. Alvarez scheduled the specialist appointment. Someone should follow up on the lab that was ordered three weeks ago and never came back. Someone should call the patient who was told to return in six months and never did.
All of these are important. None of them are on anyone’s list.
Why open loops stay open
Practices are organized around what is happening today. The schedule drives the day, and the schedule contains patients who are coming in.
A patient with a pending referral is not on the schedule. A patient whose result has not returned is not on the schedule. A patient due for a recall who has not booked is not on the schedule.
So the work depends on someone noticing, and noticing depends on that person having capacity and being present. When they take a week off, the loops that were being held in their head simply stop being held.
The consequences range from a lost appointment to a delayed diagnosis, which is why this is worth more than an efficiency conversation.
The loops worth tracking
Referrals sent. Did the patient schedule, did they attend, did anything come back. Most practices send the referral and learn the outcome only if the patient mentions it.
Orders placed. Labs and imaging ordered but not resulted. There is usually no systematic view of what is outstanding and for how long.
Post-visit instructions. A patient told to return if something does not improve. Nobody checks whether it improved.
Unscheduled recalls. Due for a return visit, no appointment booked. Sitting in a recall list that gets worked when someone has time.
Prescriptions not filled. Increasingly visible through pharmacy data and rarely acted on.
Care plan drift. For chronic conditions, patients who were on a schedule and have fallen off it.
Each of these is a state that should have a deadline and an owner. In most practices they have neither.
What a tracking layer does
Nothing clinical. It watches for state and time.
An open item is created when a referral is placed, an order goes out, or a recall becomes due. It has an expected resolution window. If nothing changes by then, it surfaces.
Where the next step is logistical, the system can take it: a message asking whether the patient scheduled the specialist, a reminder that a lab is still outstanding, a prompt that they are due.
Where the next step needs judgment, it goes to a person with the context attached rather than as a task with no background.
The point is that the loop exists somewhere other than in a person’s memory, and that it makes noise when it stays open too long.
The boundary
Clinical interpretation stays with clinical staff, without exception. A system may ask whether a patient scheduled their appointment. It may not ask about symptoms and evaluate the answer.
Anything a patient says in response that sounds clinical needs to route to a person promptly. That escalation path is the most important part of the design, and it should be tested with realistic worst-case messages before going live.
The rest of the compliance picture is standard: protected health information, minimal detail in unsecured channels, access controls, audit logging, communication preferences honored.
What practices notice
The first visible change is usually referral completion. Practices that start tracking whether patients actually attended referrals typically find the completion rate lower than assumed, and that following up moves it substantially.
The second is recall performance becoming consistent rather than depending on how busy the month was.
The third is less measurable and matters. Staff stop carrying a mental list. The cognitive load of remembering what is outstanding across a panel of patients is real, and removing it changes how the day feels.
A place to start
Pick one loop. Referrals is usually the right one because the gap is easy to measure and the clinical stakes are clearest.
For one month, log every referral placed and check the outcome at four weeks. Scheduled, attended, nothing.
Whatever that number turns out to be is your baseline, and for most practices it is enough on its own to justify building the systematic version.
If your practice is holding open loops in people’s heads, get in touch. We build follow-up systems that work alongside the EHR with the clinical boundary respected.
Frequently asked questions
What follow-up can be automated safely?
Logistics and status: confirming a patient scheduled the referral, reminding about a pending order, checking whether they picked up a prescription, prompting an overdue recall. Anything clinical, including interpreting symptoms or results, stays with clinical staff.
How does this interact with the EHR?
It should read from it rather than duplicate it. The EHR holds the clinical record; the follow-up layer tracks whether the loop closed. Duplicating clinical data creates a reconciliation problem and a compliance surface nobody wants.
Do patients find automated follow-up impersonal?
Generally the opposite, provided it is specific and the path to a person is clear. Patients read follow-up as attentiveness. What they dislike is generic messaging that appears unrelated to their actual situation.