Request a Demo
Ziva Health›AI Agents›Care Agent›Transitions of care
Care Agent workflow

Discharged today.
Followed through, well past day 30.

When a patient leaves the hospital, ED or a skilled nursing facility, the Care Agent runs your organization's transition protocol. It checks in, confirms medications and follow-up, watches for concerning symptoms and brings your team only the exceptions.

Text check-ins · liveDocument summaries · liveVoice calls · coming soonHospital event feeds · coming soonConfigurable protocols · coming soon
Request a demoHow it runs →
Trigger
Hospital, ED or SNF discharge
1Discharge detected
2Workflow starts
3Isabella checks in
4Answers evaluated
5Exceptions escalated
6Follow-ups continue
Owned by the Care Agent
Ziva handles the routine steps. Your team is brought in only for exceptions.
How it runs

Step by step,
and who handles each one.

Care AgentContinuous IntelligenceCare teamEventPatient
1
Event
Discharge detectedThe hospital, health system or SNF discharges the patient. Ziva learns about it through a hospital event data partner (coming soon) or when the facility's discharge summary arrives.
2
Intelligence
Workflow startsContinuous Intelligence recognizes the event and starts the organization's transition workflow.
3
Care Agent
Documents checkedDischarge summary, medication list, instructions and orders are read and summarized. Anything missing is flagged.
4
Care Agent
Isabella checks inHow are you feeling? Medications obtained and taken? Instructions understood? Follow-up booked? Any concerning symptoms?
5
Intelligence
Answers evaluatedRoutine answers keep the workflow going. A possible problem is marked Needs Review. A serious concern is High Priority.
6
Care team
Exceptions escalatedThe right care team member gets the reason, the context and a suggested step.
7
Care Agent
Follow-ups continueOn the days your protocol sets, such as Day 1, 3, 7, 14 and 30, then hands off into ongoing care.
One patient, start to finish

Maria L.*, 72 · heart failure

An example of how this workflow runs, and how often a person actually needs to step in.

*Stories are inspired by real patient experiences and health patterns observed in care. Names, images, quotes, and certain details have been changed or combined to protect privacy. Individual experiences and outcomes may vary. Your organization sets the protocol and escalation rules.

Tue 4pm
EventMercy Hospital discharges Maria after a 4-day admission
Tue 5pm
Care AgentDischarge summary & medication list summarized
Referral information missing, flagged to coordinator.
Day 1
Care AgentIsabella checks in
"Were you able to pick up your new medications?" → "Not the new one. The pharmacy needs approval."
Day 1
IntelligenceNew HF medication not started
Needs review Sent to care coordinator with context
Day 2
Care teamCoordinator submits prior authorization
The only staff touchpoint so far.
Day 2
Care AgentApproval in · Isabella reminds Maria
"Your new medication is approved and ready at the pharmacy. Can you pick it up today?" → "Yes, my daughter is getting it this afternoon."
Day 3
Care AgentFollows up: medication started · follow-up visit confirmed
Every step is written to Maria’s record: barrier, coordinator action, approval, pickup.
Day 7
Care AgentSymptom check-in
"Any swelling or shortness of breath?" → "Ankles a little puffy since yesterday."
Day 7
IntelligencePossible fluid retention in HF patient
High priority Escalated to nurse today with weight trend
Day 30
Care AgentTransition complete · handed off to ongoing care
Medications, visit and symptoms confirmed and documented. The same Care Agent keeps checking in every month, with no end date.
Post-discharge check-ins

Any transition, your protocol.

The same workflow runs after a hospital stay, an ED visit, a skilled nursing discharge or another transition. Your organization sets the schedule and the questions. Ziva doesn't hard-code a clinical schedule.

Day 1
Check-in
Feeling, meds, instructions
Day 3
Meds
Obtained? Taking them?
Day 7
Symptoms
Follow-up booked?
Day 14
Visit
Attended?
Day 30
Hand off
Into ongoing care

Example schedule only. How documents fit into transitions →

Exceptions

When Ziva brings in a person.

Routine answers keep the workflow moving. These situations are evaluated by Continuous Intelligence and sent to the right person with context.

High priority
Serious symptoms reported

For example, chest pain, worsening breathlessness or rapid weight gain. Escalated to the right clinician right away.

Needs review
Medication not obtained or not taken

Cost, insurance, pharmacy or confusion. Sent to the coordinator with what the patient said.

Needs review
No follow-up appointment

Flagged for scheduling help before the window closes.

Needs review
Missing discharge information

A summary, medication list or referral wasn't received.

Needs review
Patient unreachable

Escalated after the number of attempts your protocol allows.

Clinical observation
Mild or unclear concern

Ziva asks for a repeat reading or an earlier check-in and re-evaluates.

Your protocol

Your organization decides.
Ziva follows it.

Clinical judgment, thresholds and escalation rules stay with your team.

Check-in daysQuestions askedChannels & retry rulesEscalation contacts by roleWhat counts as urgentWhich transitions trigger it

Give your care team
fewer things to chase.

Show us how your team handles transitions of care today. We'll show you how the Care Agent would run it.

Request a demoExplore Ziva Agents →