What is continuity-of-care automation?
Continuity-of-care automation is software that maintains contact with a patient across the gaps between clinical encounters — after a discharge, between appointments, across a chronic therapy. It runs the scheduled contact, captures structured answers, and escalates to a clinician on signal, so continuity stops depending on whether a human had time to call.
The word doing the work is "between". Care inside an encounter is well instrumented; care between encounters is mostly hope.
What problem is it solving?
Healthcare is organised around encounters — an admission, an appointment, a dispense. Each is documented, billed and observed. Between them, the patient is essentially unobserved, and most of what determines whether the care worked happens in that gap.
The gap is where medication is or is not taken, where a side-effect appears, where a refill is or is not collected, and where deterioration starts. None of it is visible until the patient makes contact again — and the patients least likely to make contact are frequently the ones you most need to hear from.
Continuity-of-care automation is the attempt to instrument that gap without staffing it, because staffing it at the required scale has never been economically possible for anyone.
Which handoffs does it cover?
The term gets used loosely, so it is worth being specific about which transitions are in scope.
Hospital to home
The largest and best-studied gap. The patient leaves with a prescription and a plan and becomes invisible until something goes wrong. The first 30 days is where medication failures surface.
Prescriber to pharmacy to patient
A prescription written is not a medication taken. Whether it was collected, understood and started is three separate facts, and none is routinely checked.
Across a chronic therapy
Months and years of a daily behaviour with no clinical contact between reviews. Adherence decays here in a pattern that is invisible from an appointment every six months.
Between care settings
Hospital to community, specialist to primary care, home care to clinic. Each handoff loses context, and the patient is the only one present at all of them — which is why asking the patient is often the highest-yield thing available.
How is it different from care coordination software?
Care coordination software is mostly for the coordinator. It manages a panel, tracks tasks, records outreach and surfaces a worklist. It makes a human more effective and it does not contact the patient — the coordinator does.
Continuity-of-care automation makes the contact. The distinction matters because the binding constraint is not that coordinators are disorganised; it is that there are not enough of them to call everyone. Better tooling for a coordinator does not fix a coverage problem that is arithmetic.
The two are complements rather than alternatives. Automation generates escalations, and escalations need somewhere to land — which is usually a coordinator, working in coordination software.
What should it deliberately not automate?
The clinical decision. Continuity automation is about maintaining contact and noticing signal. The moment a system decides whether a symptom matters, it has stopped automating continuity and started practising medicine — which in many jurisdictions makes it a regulated medical device, and rightly so.
The escalation threshold. A clinician sets what counts as signal. That is a clinical governance decision, and a vendor picking those thresholds for you is a vendor making clinical policy for your organisation.
The relationship, where the relationship is the intervention. For a small, complex panel where the patient tells a trusted person the truth, replacing that contact with automation removes the mechanism that was working.
Frequently asked
- What is continuity-of-care automation?
- Software that maintains contact with a patient across the gaps between clinical encounters — after a discharge, between appointments, across a chronic therapy. It runs the scheduled contact, captures structured answers, and escalates to a clinician on signal, so continuity stops depending on whether a human had time to call.
- How is continuity-of-care automation different from care coordination software?
- Care coordination software makes a coordinator more effective at managing a panel; the coordinator still makes the contact. Continuity automation makes the contact itself. The constraint is usually arithmetic rather than organisation — there are not enough coordinators to call everyone — so better tooling for a coordinator does not fix a coverage problem. In practice they are complements: automation generates escalations, and escalations land in coordination software.
- What should continuity-of-care automation not do?
- Make clinical decisions. Its job is maintaining contact and noticing signal; a clinician decides what the signal means and sets the escalation thresholds. A system that decides whether a symptom matters has stopped automating continuity and started practising medicine — which in many jurisdictions makes it a regulated medical device.