How should an AI patient assistant handle post-visit follow-up calls?
A practical workflow for approved follow-up messages, structured patient replies and safe handoff of clinical questions to staff.
The short answer
An AI patient assistant can handle a defined administrative follow-up after a visit. It can identify itself as AI, check that it has reached the right person, deliver the clinic's current approved message, record the patient's exact response and create a task for staff. It should not interpret symptoms, change care instructions or decide that recovery is normal.
Every call needs a visible outcome such as message delivered, no contact, patient declined, administrative request or clinical question handed to staff. Start only when the clinic has named the purpose, eligible visit types, timing, contact channel and owner. A broad question such as 'How are you?' is unsafe if the system has no approved action for the answer.
Separate administrative follow-up from clinical review
Administrative work can include confirming that a message arrived, offering an approved booking route, recording a preferred callback time or repeating a current general instruction. The workflow changes as soon as the patient reports a symptom, asks whether recovery is progressing correctly or wants advice about medicines, treatment or wound care.
At that point the assistant should preserve the patient's own words and use the clinic's human route. It must not label an answer normal or abnormal, assign urgency, diagnose a condition or reassure the patient because a particular phrase was not heard. If the patient states that there is an emergency, the system may play the clinic's approved emergency message, but it should not perform clinical triage.
Verify the person before revealing why the clinic called
Another person may answer an outbound call. Begin with a neutral introduction and explain that the call uses AI without naming a specialty, procedure or diagnosis. For EU deployments, the European Commission's Article 50 guidance says the transparency obligations for direct AI interaction apply from 2 August 2026. The identity check should match the sensitivity of the information and the action that follows.
If verification fails, do not confirm that a patient record or visit exists. Offer an official route back to the clinic. Voicemail and text messages need their own approved wording with minimal disclosure, taking account of the patient's contact preferences and the clinic's legal basis. A useful message can ask the patient to call back without revealing the reason on a shared device.
Use one approved and versioned follow-up protocol
Each protocol should state which visit type it covers, when contact may begin, the exact messages and questions, permitted clarifications, stop conditions, handoff team and alternative when that team is unavailable. Give it an owner, version, approval date, language set and withdrawal method. The call record should show which version was used.
Do not let the assistant assemble clinical advice from free text in the medical record or from a similar procedure. If the approved protocol is missing, expired or conflicts with the visit record, the assistant should stop and create a review task. A plausible answer is still the wrong answer when no authorised source supports it.
Capture the response without turning it into a clinical judgment
Use operational states that describe what happened, not what the response means medically. The record can show reached, identity confirmed, message delivered, patient asked for staff, question captured or handoff created. When free text is necessary, keep the patient's wording and separate it from system labels. If the answer remains unclear after a permitted clarification, send it to a person.
Collect only the details needed for that follow-up. A full recording or transcript should not be the default simply because the channel makes it possible. Decide in advance whether recording is needed, how people are informed, who can access the case and how long each part is retained. Health information belongs in a restricted workflow, not a broad reception queue.
Give every handoff an owner, deadline and acknowledgement
A useful handoff contains the verified patient or visit reference, the exact question or statement, call time, language, safe return channel, protocol version and any approved safety message that was played. The clinic sets the receiving team and response target under its own clinical policy. If nobody acknowledges the case, the system follows a pre-approved escalation path rather than silently waiting.
The assistant may track whether staff accepted, answered and closed the task. It cannot mark a clinical concern resolved merely because it entered a queue or because a message was sent. Closure needs a named human action and enough evidence for the clinic to understand what happened.
Test the failures patients will actually encounter
Acceptance tests should cover the wrong person answering, no answer, voicemail, an unsupported language, a dropped call, a duplicate campaign trigger, an unavailable source system, a revoked protocol, a new clinical question and an unavailable staff queue. Use test records and confirm that one follow-up cannot create two conflicting tasks.
Measure reach rate, successful delivery, patient opt-out, administrative completion, clinical handoffs, staff acknowledgement time, duplicate contacts, wrong-recipient near misses and reopened cases. A high call-completion rate says little if clinical questions sit unowned or patients receive repeated calls.
Keep clinical and sensitive decisions with authorised people
Authorised staff decide whether a symptom needs urgent review, what advice to give, whether medicines or treatment change, whether another appointment is needed and how safeguarding, consent, capacity or a complaint should be handled. The assistant should not infer risk from tone of voice, rank patients for care or close a concern on its own.
Clinical, operational and privacy owners should approve the workflow before launch. Pause it when testing or live monitoring finds disclosure to the wrong person, an outdated protocol, a dropped handoff or unapproved clinical advice. Restart only after the cause is understood and the affected cases have been reviewed.
FAQ
Can an AI patient assistant ask about symptoms after a visit?
Only within a question set that the clinic has approved after clinical, privacy and regulatory review. The assistant may record the patient's answer in their own words, but it should not interpret, score or diagnose it. A symptom, uncertainty about recovery or request for advice goes to an authorised person.
Can the assistant leave a voicemail or send a text message?
Yes, if the clinic has approved that channel and wording. Keep the message neutral, disclose as little as possible and use contact preferences already held by the clinic. Do not reveal a specialty, procedure or diagnosis on a shared device.
Does a post-visit AI call make the software a medical device?
Not automatically. Classification depends on the intended purpose and what the software does. If it provides information used for diagnostic or therapeutic decisions, the clinic and provider need a specific regulatory assessment under the applicable medical-device rules before deployment.
Sources and further reading
- European Commission: principles of the GDPR
- European Data Protection Board: Guidelines 02/2021 on virtual voice assistants
- World Health Organization: ethics and governance of artificial intelligence for health
- European Commission: MDCG 2019-11 rev.1 on qualification and classification of software
- European Commission: guidelines on AI Act Article 50 transparency obligations