Skip to main content
DoneThat

AI Adoption GuideHealthcareFollowup

Medication adherence outreach agent

NLP-driven agent sends personalized reminders, answers medication questions, and escalates confirmed non-adherence to the care team.

Healthcare processAccessIntakeAssessDiagnoseTreatDischargeBillFollowup

By Don, DoneThat’s AI coach · updated

Every outreach names the signed instruction

The quality bar is an outreach message that cites the signed instruction. If the agent cannot name the drug, strength, route, frequency, and the clinician who signed, it does not send. A reminder without an order cite is the first failure mode. It sounds helpful, and it is not attributable to the regimen the clinic actually authorized.

Patients mix discharge bottles, samples, and leftover directions from an older visit. The agent is not there to invent a fill, guess a remaining quantity, or paper over a missing order. It repeats what was signed, asks whether the patient followed that text, and stops.

Inbox and chart products from Epic, Klara, Microsoft, and Oracle Health can carry the thread. The channel is not the source of truth. The signed instruction is. If the product can show an order but the clinic never captured a patient-facing instruction, do not send a reminder until a clinician signs one.

When the instruction was written at discharge, start from discharge medication reconciliation so the cite matches the list the patient left with, not an older clinic note that was never updated.

Load the instruction before the first message

Load the signed instruction before you compose anything. Pull the active order, or the signed after-visit instruction if that is what the clinic uses. Capture start date, any stop or hold parameters, and the identity of the signing clinician. If two instructions conflict, do not pick a winner. Queue the conflict for a pharmacist or prescriber. The agent does not reconcile competing directions on its own.

Map the instruction into the fields the reminder will quote: drug name as written, strength, form, route, schedule, and qualifying text such as with food, at bedtime, or hold if a stated parameter is met. Do not paraphrase those fields into friendlier language that changes meaning. If the clinic uses patient instruction personalization, personalize channel, language, and send time. Do not personalize the clinical content away from the signed text.

If the patient later asks whether a new over-the-counter product or a new prescription is compatible with this medicine, that question is not an adherence reply. Hand it to real-time drug interaction monitoring or to the pharmacist. The outreach agent answers questions already answered in the signed instruction: when to take, how many, with or without food, and whether a documented hold applies. It does not add new clinical advice.

Here is the one working example. A clinic visit signs amlodipine 5 mg by mouth once daily in the morning. The agent loads that line, the signing clinician, and the start date. It does not treat a retail fill history as proof the patient is taking the tablet, and it does not write a fill into the chart because a reminder went out.

Remind with a cite, then wait for a reply

Send a reminder that quotes the signed instruction, then wait. The message should read as a check against a specific order, not as a campaign blast. Name the drug and schedule. Name that this is the instruction signed at the last visit or at discharge. Ask one question: whether the patient took that dose as written, or whether they are holding for a reason the instruction already documents.

For the amlodipine line, that looks like: the clinic signed amlodipine 5 mg by mouth every morning; did you take this morning's dose as written? That is a cite plus a closed question. "Please remember your blood pressure medicines" is not.

Do not stack several medications into one vague note. If the patient has more than one signed instruction, send one cite per message or list each cite as its own line. Ambiguous reminders produce ambiguous replies, and ambiguous replies are not confirmed gaps.

After send, wait for a patient reply or for a documented proxy reply the clinic already accepts, such as a caregiver on file. Silence is not a clinical finding. Treating silence as non-adherence is the second failure mode. An unread inbox is not the same as a missed dose. You may send a bounded number of follow-ups that still cite the same instruction. You do not convert quiet into an alert for the care team.

If care plan adherence monitoring is already watching the broader plan, keep this agent scoped to the medication line. Do not let a missed appointment or an unsigned goal leak into a flag that the patient is not taking amlodipine.

Confirmed doses stay empty

When the patient confirms they took the dose as written, leave the outreach queue empty for that interval. Empty stays empty. Do not open a task, do not write a suspected miss, do not invent a fill rate, and do not file a pharmacy fill you did not see.

Confirmation is the patient's statement against the cited instruction, not a claim about the bottle. In the example, "I took this morning's amlodipine 5 mg" closes the reminder. "I picked it up" does not, unless the clinic's protocol treats pickup as a separate, labeled event. Pickup is not the same as taking the dose. If you need fill data, get it from the pharmacy record. Never have the agent invent a fill because the conversation felt successful.

If the patient confirms a hold that is already in the signed instruction, that is also a closed loop. It is not non-adherence. Escalate only if they report holding for a reason the instruction does not contain.

A confirmed "I took it" also does not authorize the agent to schedule the next three days as taken. Each interval needs its own confirmation or it stays unclaimed.

Escalate confirmed gaps; a clinician owns the regimen

Escalate when the patient or accepted proxy confirms they did not follow the cited instruction, or confirms they have no supply and are not taking it. The escalation should carry the cite, the patient's words, the time of the reply, and nothing inferred. "Patient states they have not taken amlodipine 5 mg daily for three days because the bottle is empty" is an escalation. A note that they are likely non-adherent is not. Do not attach a percentage. Do not guess remaining tablets.

A confirmed gap goes to the care team the clinic names for this workflow, typically the clinic pharmacist and the signing clinician or covering prescriber. The agent does not change the dose, stretch the interval, or suggest a 90-day supply. A clinician still owns the regimen. The pharmacist may call, may check the pharmacy fill history, may arrange a refill, or may bring a clinical hold to the prescriber.

If the patient asks to stop, split, or double the dose, that is a confirmed deviation plus a clinical question. Escalate both. Do not negotiate a new schedule in the thread.

The third failure mode is inventing a fill after a gap. It is tempting to complete the chart with a presumed pickup so the quality queue looks clean. Do not. If no fill is on file, the chart stays without a fill. If a fill is on file, cite the pharmacy record separately from the patient's taking-statement. Outreach quality is the cite plus an honest empty or an honest confirmed gap, not a tidy adherence score.

The regimen changes only when a clinician signs a new instruction. Until then, the agent repeats the current cite, leaves confirmed intervals empty, and hands confirmed misses to the team that can actually rewrite the order.

Is this worth automating for you?

Whether this pays back depends on how much time it takes your team today. Most teams estimate that from memory, and the estimate is usually wrong in one direction or the other.

DoneThat reconstructs where the time actually went, with no timers to forget, so you can measure the baseline before committing to a project and check the gain afterward.

Measure the baseline first