Glaucoma Drop Refill and Side-Effect Call Handling

Establishes which pressure drop, which eye or eyes, and — the fact your glaucoma clinic most needs — whether the patient has already stopped taking it and for how long
Applies the administrative side of your refill policy, such as whether a pressure check is overdue or the last visit falls outside your window, and states what is outstanding without deciding the therapy
Tolerance complaints such as burning, persistent redness, lash or lid changes are captured in the caller's own words and routed; the AI never suggests stopping, switching, spacing or substituting a drop
Cost and coverage obstacles are recorded as the actual reason for the call, so staff address the barrier rather than transmitting another prescription to the same pharmacy
Instillation difficulty — a tremor, arthritic hands, a caregiver doing it, drops that keep missing — is flagged for the technician who can teach technique or discuss an aid
Each call is delivered as a structured task carrying drug, eye, days missed, stated obstacle, pharmacy and callback number, rather than a note saying the patient called about drops

How it pays back

A Stopped Glaucoma Drop Is Silent

Chronic open-angle glaucoma gives the patient nothing to feel, while the drop gives them something to feel every day. That combination makes quiet discontinuation common and self-reporting rare. When a patient does phone, the call is the only signal you get, and it should not be reduced to a refill ticket with no context.

The Refill Nurse Gets the Whole Request

Drug, strength, which eye, which pharmacy, how long they have been out, and whether a pressure check is overdue. Captured once, on the first call, in a fixed structure. No callback to ask which bottle, and no request ageing in a queue while the patient goes untreated.

Side Effects Route, They Are Never Triaged by Software

A patient describing burning or a red eye may be describing a tolerance issue, an allergy, or something unrelated. The AI does not attempt that distinction. It records what was said, applies your routing rule, and puts it in front of the clinician who can act, with nothing suggested to the patient in the meantime.

Elderly Callers, No Phone Tree

Glaucoma clinics run on long-term follow-up with an older population, often with reduced vision and hearing. Calls are answered immediately by something that speaks at the caller's pace, repeats and confirms detail, and does not require navigating a menu by memory.

Under 1 second to answer

No menu and no hold for patients managing a lifelong daily medication

Dozens of languages

Medication detail is captured in the language the patient is comfortable using

HIPAA BAA included

Medication and identifier data encrypted with AES-256 at rest and TLS in transit

Frequently asked questions

Does the AI approve refills or tell a patient the prescription was sent?

No. It never makes a clinical determination and never tells a patient a refill has been approved, denied or transmitted. It captures the request, states which administrative conditions your practice has set are outstanding, and routes it to the person who decides.

Can it tell a patient to stop a drop that is irritating their eye?

Never. Stopping a pressure-lowering drop is a clinical decision with consequences, and it sits entirely outside the AI's scope. The complaint is captured verbatim and routed on your rules, and the patient is told a member of your team will follow up.

What if the pharmacy substituted a generic or the cost changed?

It records what the patient was told and by whom, then routes to the staff member who handles that. It does not confirm equivalence, quote a price or predict coverage, because a wrong answer sends the patient back to the counter for nothing.

Does it know what the patient is currently prescribed?

Only where a direct interface to your system exists. Medication context is available through API or FHIR for supported systems, and custom integration is available elsewhere. Without that, it captures what the patient reports and flags the request as needing the chart checked. It does not read a medication list back as confirmation.

What if the caller says their vision has changed?

That leaves the medication path and follows the symptom rules your practice authored, including your urgent escalation branch if the description matches an item on your list. A medication call that turns into a symptom call should not stay in a refill queue.

Can it handle a family member calling about a parent's drops?

Yes, inside the disclosure policy you set. The relationship is established and recorded, and in glaucoma the family member is often the person actually administering the drops, which is captured as part of the handoff.

Handle Glaucoma Drop Refill and Tolerance Calls Properly