Eye care's chronic side — glaucoma, diabetic retinopathy, macular degeneration, severe dry eye — shares an inconvenient truth with the rest of chronic medicine: the disease is managed in the spaces between visits, but the practice is only staffed for the visits. Drops adhered to or abandoned, follow-ups kept or drifted, warning symptoms reported or ignored — the between-visit layer determines outcomes, and in most practices it's nobody's job. Virtual patient care coordination is the model that makes it somebody's: a remote team member running a designed calendar of touchpoints across the practice's chronic panels. Here's how it works.
The touchpoint calendar
The core artifact is a per-condition touchpoint design — what outreach happens, when, for whom. A representative pattern across eye care's chronic panels: new-treatment onboarding calls in the first weeks (where drop technique and tolerance problems surface, and where our glaucoma guide locates the highest-leverage adherence window); follow-up reminders tied to clinical intervals rather than generic recall; symptom check-ins for the conditions where early reporting changes outcomes — the AMD patient asked about distortion, the diabetic patient reminded what new floaters mean; and reactivation outreach for anyone drifting off their monitoring schedule, escalating per the tiered ladder our follow-up guides describe. Each condition's calendar is designed once, with the doctors, and then executed daily — which is the entire point.
The protocol boundary, drawn brightly
Coordination is not clinical care, and the model's safety lives in that line. The coordinator works from scripts and decision rules the clinical team wrote: what questions to ask, what answers are reassuring, and — crucially — what triggers immediate escalation. "Any new distortion on the Amsler grid → same-day clinical callback" is a rule a trained coordinator executes flawlessly precisely because it requires no judgment about retinas, only fidelity to the protocol. Everything clinical routes to clinical staff; everything logistical resolves at the coordination layer; and every touch is documented in the chart, building the longitudinal record of engagement that both care and risk management want. This is the same protocol-bounded architecture our triage and coordination guides describe — applied longitudinally.
Why remote fits this layer best
The between-visit layer has a defining operational property: it's all list-driven outbound work on a calendar — exactly what an interrupted front desk structurally cannot sustain and a dedicated remote coordinator structurally cannot avoid, since the calendar is their entire job. Add the scale economics: one remote coordinator can run the touchpoint calendars for a practice's full chronic panel — hundreds of patients — because the daily volume is calls and messages, not encounters. The compliance architecture is the standard stack from our HIPAA guides; the vetting bar adds empathy-on-the-phone and protocol discipline, both testable with scenarios.
What it measures and what it returns
The coordination layer produces numbers practices have never had: follow-up compliance rates by condition, lost-to-follow-up trending down, new-treatment adherence check completion, escalations caught (each one a symptom reported weeks earlier than it otherwise would have been). The revenue story is real — kept follow-ups are kept visits, and a managed panel is a retained panel — but the deeper return is the one that changes how a practice thinks of itself: the shift from a place patients visit to a system that keeps them. Eye care's chronic diseases are decades long. The practices that build the between-visit layer are the ones actually present for them — and it turns out presence, at scale, is a calendar with an owner.
.png)
.png)
.png)
