Medicare's ACCESS Program: Payment Model Built for AI Agents, Details Inside

Medicare's ACCESS program (Advancing Chronic Care with Effective, Scalable Solutions) is a 10-year CMS pilot that pays for health outcomes, not activities. Traditional Medicare reimburses based on clinician time — no mechanism to pay for an AI agent that monitors patients between visits. ACCESS creates that mechanism. The first cohort of 150 participants goes live July 5, 2026.
How the Payment Model Works
Participating organizations receive predictable payments for managing qualifying conditions (diabetes, hypertension, chronic kidney disease, obesity, depression, anxiety). They earn the full amount only when patients meet measurable health goals: lower blood pressure, reduced pain, etc. This is a shift from fee-for-service to value-based care.
Pair Team's Implementation
Pair Team (raised ~$30M from Kleiner Perkins, ~850 clinical staff) deploys a voice AI agent called Flora as its primary patient interface. Flora handles intake, referrals, and check-ins. A peer-reviewed study in the Journal of General Internal Medicine showed Pair Team's model reduces avoidable ER visits by 50% and inpatient visits by 25%. The company claims one in four hospital visits and one in two ER visits don't happen when a patient is under their care.
Real Patient Interaction
A 67-year-old woman living out of her car, managing PTSD and congestive heart failure, spoke with Flora for over an hour. Hourlong conversations are now routine. Batlivala: "That's the companionship piece. And it turns out that is truly an intervention."
Who It's For
Developers building AI agents for regulated industries (healthcare, insurance) or working on voice-based patient engagement tools. The program's designers (Abe Sutton, Jacob Shiff) are former startup operators.
📖 Read the full source: HN AI Agents
👀 See Also

Exploring Clawra's Architecture and Social Autonomy Framework
David Im's Clawra experiments with a parallel world framework for AI companions, focusing on autonomy and local-first data privacy.

Claude Opus 4.6 effort=low parameter causes lazy agent behavior
When using effort=low with Claude Opus 4.6, agents made fewer tool calls, were less thorough in cross-referencing, and ignored parts of system prompts about web research. Switching to effort=medium resolved the issues.

OpenClaw 4.2 fixes pairing error and adds durable task flows
OpenClaw 4.2 patches a pairing error affecting users who updated around March 31st and introduces durable task flows that allow long-running tasks to survive gateway disconnections.

OpenClaw 2026.3.22 Update: Useful Features but Three Critical Issues Require Caution
The OpenClaw 2026.3.22 update introduces useful features like the /btw command, health monitor configurability, Telegram reply fix, and per-agent reasoning defaults, but three open issues (#53158, #53202, #53195) make it risky to deploy immediately without monitoring.