Somewhere between the front desk (which owns moments) and the clinical team (which owns encounters) sits a gap where patients get lost: the journey. The referral that stalls, the follow-up that never gets booked, the test result waiting on a callback, the surgical workup half-complete — all of it falls between seats, because no seat owned it. The patient coordinator is the role practices invented to own it, and in ophthalmology — where journeys are long, multi-visit, and clinically consequential — it has become one of the most valuable positions in the building. Or out of it.
The journey-ownership model
The coordinator's defining question isn't "what's happening today?" but "what's supposed to happen next for this patient — and is it scheduled?" The portfolio that follows: new-referral intake through first visit (entry, records, booking, the welcome call that sets expectations), diagnostic journeys (the glaucoma workup's fields-OCT-follow-up sequence booked as a chain, results communicated per protocol, the loop always closed), surgical journeys in partnership with the surgical coordinator (our cataract and surgical-coordinator guides map that division), and chronic-care continuity — the standing population of returning patients whose next visit should always exist in the schedule before the current one ends. One sentence captures the standard: no patient leaves the system's attention without a next step booked or a documented reason why not.
The daily workflows
Morning: the exceptions review — yesterday's no-shows recovered, results pending communication, referrals aging past the entry standard. Midday: the chains — new referrals processed, upcoming journeys checked for completeness (is the field test scheduled before the consult that needs it?), post-op sequences verified. Ongoing: the communication load — patient questions routed and resolved, referring-office updates sent, the "where am I in this process" calls that anxious patients deserve answered by someone who actually knows. Every workflow tracked, because coordination without tracking is vibes.
Boundaries and escalation
The coordinator communicates, schedules, and tracks; they do not advise clinically. The role's safety rests on the protocol architecture our triage guide describes: symptom reports escalate immediately, results are communicated per the doctor's disposition (never interpreted), and the coordinator's judgment calls are about logistics and urgency-routing, not medicine. Practices that write these boundaries down get a role that clinical staff trust; practices that leave them fuzzy get friction.
Office, remote, or both
Audit the portfolio above for location-dependence and the now-familiar answer emerges: nearly none of it requires the building. Referral processing, chain-checking, results-communication calls, recall of the chronically managed — all portable, all list-driven, all suited to the dedicated remote model whose economics and compliance architecture the rest of our series documents. Common configurations: smaller practices fold coordination into a broader remote assistant's portfolio; larger ones run a dedicated remote coordinator (or team) with an in-office counterpart for the walk-up moments. Either way, the design principle holds — the role is defined by ownership and follow-through, neither of which has an address.
Measuring the seat
The coordinator's value shows up in numbers practices usually don't instrument until the role exists: referral-to-appointment lag, no-show recovery rate, follow-up compliance for the managed-disease population, results-communication turnaround, and — the composite — the lost-to-follow-up rate across the practice's chronic panels. Every one of those numbers is a patient-experience number and a revenue number and a clinical-risk number simultaneously, which is the ultimate argument for the seat: coordination is the rare investment that pays all three currencies at once. The journey, it turns out, was always the product. Someone just has to own it.
.png)
.png)
.png)
