A few recent healthcare announcements caught my attention because they look like separate stories at first.
- Brook.ai and Highgate are focused on AI-driven infrastructure for chronic care between visits.
- Tuesday Health is expanding palliative care through a Humana partnership.
- Quantum Health and CirrusMD are combining navigation with virtual care.
- HRS acquired Rimidi, bringing deeper EHR workflow integration and CGM data into remote patient monitoring.
But they all point to the same underlying shift:
Healthcare is moving toward continuous care—and continuous care is not a feature you bolt on. It’s an operating model you build.
“Continuous care” is what everyone wants. It’s also what breaks the fastest.
In chronic care and serious illness, the gap is rarely clinical knowledge. We know what good care looks like.
The gap is that most care delivery systems are still designed around episodic moments:
- An office visit
- A discharge
- A new diagnosis
- A crisis
Everything else—the stuff that determines whether someone stabilizes or deteriorates—happens in the in-between.
So when organizations say they’re extending care “beyond the clinic,” what they’re really saying is: we’re trying to redesign the in-between.That’s hard.
And it’s why “continuous care” initiatives tend to fail in predictable ways:
- More data, more alerts, more dashboards… but no capacity to act
- New outreach workflows… but no clarity on ownership or escalation
- Virtual programs… that create extra documentation burden instead of removing it
- Impressive pilots… that don’t survive scale
What these announcements are really buying: the ability to execute in the in-between
Look at the language in these releases and deals. They keep coming back to the same promises:
- Earlier intervention
- Proactive symptom management
- Reduced administrative burden
- 24/7 access
- Longitudinal support
- Fewer avoidable hospital/ED visits
- Integration into existing environments and workflows
That’s not a tech spec. That’s an operating spec.
It’s also a tacit admission: the bottleneck isn’t sensing. It’s responding.
Remote monitoring, chat-first access, CGM streams, risk prediction—none of it matters unless a real care team can translate signals into actions at the right time.
The real product is the care loop
If you want to evaluate a “continuous care” strategy, ignore the branding and ask: Do they have a credible care loop?
A care loop has to answer, end-to-end:
- How do we know something changed? RPM vitals, CGM data, symptom surveys, chat-based outreach, caregiver reports
- How do we decide what it means? Triage logic, clinical protocols, decision support, clinician judgment
- Who acts, and how fast? Interdisciplinary teams, coverage model, routing, SLAs
- What happens when it’s ambiguous? Device error vs real deterioration, non-response, conflicting signals
- How does it land in the system of record? EHR workflow integration, documentation patterns that reduce rework
This is why acquisitions like HRS + Rimidi matter. Rimidi isn’t just “more features.” It’s deeper ambulatory workflow integration and cardiometabolic specificity (including CGM), which is exactly what you need if you’re trying to run a serious longitudinal program without drowning clinicians in noise.
And it’s why the navigation + virtual care combination (Quantum + CirrusMD) matters: it’s an attempt to connect member intent (navigation moment) with clinical action (physician access) quickly enough to change the downstream cost curve.
Plans and employers are becoming the distribution channel for “continuous care”
The Tuesday Health + Humana partnership is another strong signal: payers are increasingly willing to scale programs that can credibly reduce avoidable utilization while improving experience—especially for high-need populations.
That’s good news for access and coordination. It also raises the bar on measurement and operational discipline, because in payer-distributed models:
- Outcomes need to be provable
- Handoffs with the member’s existing clinicians have to work
- The “24/7” promise has to hold under load
- The program can’t collapse into yet another disconnected experience
My take: continuous care will be won by teams who treat ops as product
The winners in this category won’t just have the best AI or the best UI.
They’ll be the teams who can:
- Design workflows that survive scale
- Reduce admin burden instead of relocating it
- Make exceptions explicit and safe
- Integrate into the messy reality of clinical practice
- And keep the human connection intact for patients who are overwhelmed, not “engagement-optimized”
Because continuous care is not a new feature set.It’s a commitment to building a system that shows up, reliably, in the in-between.