Catching it early: how a flag becomes a follow-up

The whole value of a check-in lives in one moment: the patient says something that matters, and the right person finds out in time. Everything else is in service of that moment being fast, accurate, and safe.

The patient's words come first

On a call four days after a knee replacement, a patient mentions that her calf feels tight and warm. She is not alarmed. She would probably not have called anyone about it. To a care team, though, that is a sentence worth stopping for.

Tend recognizes a concern, not a diagnosis

Tend is tuned to the concerns your protocols care about, mapped to what the patient went home from. It does not decide what the symptom is. It recognizes that the description matches something the care team asked to hear about, and it acts on that match.

• It notes the exact words the patient used.
• It marks the concern and why it was flagged.
• It writes a short, structured summary of the whole call.
• It routes the flag to the queue and channel your team chose.

A person decides what happens next

Tend never tells a patient they might have a clot. It tells a nurse that a patient described symptoms worth a call back, and it does so quickly.

Within minutes, a nurse sees the flag with the transcript and the summary attached. No retelling, no missing context. The nurse calls the patient back, and a problem that could have become an emergency becomes a phone call and a plan.

For truly urgent red flags, the design is different and deliberate: Tend surfaces the handoff immediately and, when appropriate, tells the patient to call 911. Speed and clear limits are not in tension. They are the same commitment to safety.