Workflow

Deciding what to re-verify on a recall call, and what your chart already knows

Putting an established patient through the full new-patient intake wastes their time and yours. Asking nothing risks missing a change. This is how practices set the re-verification scope for recall calls, what triggers a deeper intake mid-call, and how a change reaches your staff.

How it pays back

Re-asking has a cost

Recall patients who are asked to recite information already in their chart experience the call as bureaucracy. Keeping the recall short is not only efficiency; it is the difference between a patient who answers the next call and one who does not.

Not asking has a different cost

A medication started since the last visit, or a new allergy, is exactly the kind of thing a shortened call can miss. The re-verification list exists so the brevity is deliberate rather than accidental.

The line is yours to draw

You define which fields get verified on a recall. Some practices add insurance changes or recent emergency visits; others keep it to medications and allergies. The workflow follows your protocols rather than a default.

Changes surface as changes

The summary distinguishes what was confirmed from what is new or different, so your staff read a short list of deltas instead of comparing a fresh intake against the old chart line by line.

New patient intake complete on call

Full medical history, allergies, medications, insurance captured

Established patient updates brief and focused

Current status verification without redundant questions

AI identifies patient status automatically

Routes to correct intake template

Escalation flagged for staff review

Changes in health or insurance escalate to your team

Frequently asked questions

How does the AI know whether a caller is new or established?

MedReception integrates with your EMR, so the AI checks your patient database before the call begins. New patients trigger the full intake; established patients trigger the brief update. A caller who is not in your system but refers to a recent visit can be flagged for escalation.

Which fields do practices usually re-verify on a recall?

Most verify current medications, allergies and the reason for the visit. Some also ask about insurance changes or recent emergency visits. You define the set, and it can differ by specialty or visit type.

What triggers a deeper intake mid-call for an established patient?

The AI asks whether anything is new or different since the last visit. If the patient reports new allergies, medications or diagnoses, it captures those in detail and flags them for your staff to review and file.

How do staff see what changed without re-reading everything?

The recall summary highlights what is new or different rather than restating the chart. Your team no longer digs through old records to work out which detail is current.

What if an established patient calls with a complex new problem?

The AI asks clarifying questions and captures the chief complaint. If the situation appears urgent or needs detailed history, it flags the call for escalation to your staff, who decide on routing and on how much intake the call warrants.

Related reading

Bring this to your practice

See how MedReception AI handles after-hours calls, scheduling, intake, and patient communication for medical practices like yours.

Want the numbers first? See plans and pricing