AI should make care easier, not busier
Ahmad Alghazi on why the real opportunity for AI is not more answers, but less work between noticing a need and helping a person.
The next frontier is not another system that answers questions. It is a system that helps ensure important changes lead to appropriate care.
Healthcare does not stop when an appointment ends.
A patient starts a new medication. Their sleep changes. Walking becomes more difficult. A family member notices something unusual. A follow-up test remains incomplete.
These events may matter. Yet they do not necessarily become part of a timely clinical conversation.
Much of healthcare is organized around encounters: the consultation, the procedure, the admission, the discharge. People experience their health continuously, while the systems supporting them often receive information intermittently.
Artificial intelligence creates an opportunity to narrow that gap. But doing so will require a more ambitious goal than generating better summaries or adding a chatbot to every patient portal.
We should move from AI that assists individual encounters toward intelligence that supports continuity across them.
We can call this Care Continuity Intelligence.
Care Continuity Intelligence is a proposed approach to connecting a person’s evolving health information with their care plan, their care team, and the next appropriate action.
Its purpose is not to make an autonomous diagnosis or monitor every moment of someone’s life. Its purpose is to help answer five practical questions:
What has changed?
How does that change relate to this person’s history and goals?
Is the information reliable and sufficient?
Who is responsible for reviewing it?
What happened after the review?
The final question is what makes this concept different from another analytics dashboard.
A system can identify a possible concern without improving care. It can generate an alert without ensuring anyone has the authority, capacity, or context to respond.
Detection is not resolution. A recommendation is not a completed action.
Continuity requires a process that connects observation, interpretation, responsibility, response, and follow-up.
Consider a hypothetical patient recovering at home after a hospital admission.
Over several days, the patient reports greater fatigue. Their recorded activity declines. A scheduled follow-up has not yet taken place. They also mention that collecting a new prescription has been difficult.
Viewed separately, these observations may produce several disconnected tasks—or none at all.
Viewed together, they give the care team a more useful starting point.
A continuity-focused system could prepare a concise, source-linked account of what changed, identify missing information, and route a review to the appropriate team member under an agreed care protocol.
That review might reveal a clinical issue. It might reveal a transport problem, a misunderstanding, unreliable device readings, or a change that does not require intervention.
The system should not assume the answer.
Its value would be in helping the right person investigate, document a decision, and confirm whether the patient received the intended support.
That is a different ambition from predicting deterioration. It is about making care more responsive without pretending uncertainty has disappeared.
The technical foundation would be a living care context: a structured, time-aware representation of the information relevant to a person’s care.
This should not be a permanent summary that quietly becomes outdated. Nor should it be an unrestricted collection of every available data point.
It should distinguish between:
What the patient reported.
What a clinician observed.
What a device measured.
What has been confirmed.
What remains uncertain.
What the current care plan intends to achieve.
Dates, sources, permissions, and unresolved disagreements would be essential.
A medication mentioned in an old note should not automatically become a current medication. An absent measurement should not become a normal result. A model-generated interpretation should never acquire the status of a clinical fact simply because it appears in a polished paragraph.
The system would also need to preserve what conventional clinical summaries can overlook: the patient’s own priorities.
For one person, the most meaningful outcome may be walking independently. For another, it may be returning to work, sleeping comfortably, or managing treatment without overwhelming a family caregiver.
Continuity should connect clinical decisions to those goals—not reduce the person to a risk score.
The most consequential application of agentic AI in healthcare may be controlled coordination.
Within clearly defined permissions, an AI system could help prepare visit briefings, identify incomplete follow-up steps, draft questions for review, or check whether an agreed action has been acknowledged.
But the distinction between suggesting, authorizing, and executing an action must remain explicit.
Summarizing a patient’s check-in is not the same as changing their treatment. Reminding a coordinator about an incomplete referral is not the same as deciding that the referral is unnecessary.
Each action needs an appropriate level of oversight, a record of what occurred, and a clear route for correction.
A useful design principle is simple:
The more consequential the action, the stronger the evidence, authorization, and human accountability must be.
AI should make responsibility easier to exercise—not harder to locate.
There is an important risk in this vision.
A system designed to improve continuity could become intrusive, generate excessive alerts, or transfer more unpaid work to patients, families, and clinicians.
More data is not automatically better care.
Patients should understand what information is collected, why it is useful, who can access it, and whether someone is actually expected to review it. They should also know when a service is not monitored and must not mistake it for an emergency-response system.
Participation should not depend entirely on owning a wearable, using a smartphone confidently, or completing frequent questionnaires.
A credible model of continuity must support different levels of digital access and engagement. Otherwise, it risks making care more responsive for the most connected patients while leaving others further behind.
The goal is not maximum observation. It is sufficient, relevant information paired with an appropriate response.
Care Continuity Intelligence should be evaluated against outcomes that matter to patients and care teams.
Potential measures include:
Whether agreed follow-up steps are completed.
How long clinically relevant concerns wait for review.
Whether patients understand their next steps.
Whether coordination reduces or increases staff workload.
How often alerts are useful, unnecessary, or missed.
Whether benefits are distributed fairly across patient groups.
Clinical outcomes, safety, and costs would require careful prospective evaluation. Improvements should not be assumed from a successful demonstration or an accurate-looking summary.
A system that produces more messages but creates more work has not necessarily improved continuity.
A system that closes administrative tasks while overlooking patient concerns has not succeeded either.
This vision does not require replacing an entire health system at once.
A practical starting point could be a defined post-discharge pathway or a specific chronic-care program.
The first questions should be operational:
Which information is useful? Who reviews it? During what hours? What happens when a concern is unresolved? What can the technology do, and what must remain a clinical decision?
Only then should automation be introduced.
This approach creates something that can be tested: a defined population, a bounded workflow, explicit safeguards, and measurable outcomes.
It also exposes an essential truth. No AI model can compensate for a care process in which nobody owns the next step.
For CAN, Care Continuity Intelligence offers a direction for building connected care around people rather than isolated interactions.
Not another destination patients must visit.
Not another stream of alerts clinicians must manage.
A shared, permissioned understanding of what has changed, what matters, and what needs to happen next—with the patient’s goals and the care team’s judgment at its center.
This is a vision to develop and validate, not a claim that technology has already solved continuity.
The next era of healthcare AI should be judged by more than the quality of its answers.
It should be judged by whether people receive the right follow-through after those answers are given.