UpDoc Gets First FDA Clearance for Agentic Clinical AI — What It Means for RCM

Autonomous AI that adjusts medications, orders labs, and documents in the EHR — without a scheduled visit — just received FDA clearance. The billing and coding infrastructure for what it creates doesn't fully exist yet.

$18M

Oversubscribed seed round — backed by Mayo Clinic, Eli Lilly, the American Diabetes Association, Cathay Innovation, Pear VC, Polaris Partners, and Section 32.

What UpDoc Actually Does

UpDoc announced today that it has received FDA clearance for the first Software as a Medical Device (SaMD) built on patient-facing large language models. The Palo Alto company simultaneously disclosed initial deployments at Cleveland Clinic, Allegheny Health Network, and UCSF Health.

The platform integrates directly with a health system's EHR and operates on behalf of a licensed clinician between patient appointments. The company's published example: a Type 2 diabetes patient whose blood glucose is drifting. UpDoc identifies the trend, initiates an insulin titration within physician-approved parameters, triggers a follow-up lab order, and documents the entire intervention in the EHR — without requiring the patient to schedule an appointment.

The key distinction from administrative AI is that the platform is performing clinical actions. Not scheduling, not eligibility checks, not prior auth submission. It is executing care. The clinician sets parameters; the AI executes within them.

The RCM Implication: New Billable Events at Scale

Autonomous between-visit care coordination is not a hypothetical billing scenario. The codes exist. The question is whether health systems have the infrastructure to capture them at the volume this platform would generate.

Relevant code categories for autonomous between-visit interventions:

  • Chronic Care Management (CCM) — 99490, 99491, 99439: Non-face-to-face care management for patients with two or more chronic conditions. Requires 20+ minutes of clinical staff time per calendar month and a documented care plan. AI-coordinated between-visit interventions would typically qualify. Reimbursement: ~$62–$130/month depending on time and complexity.
  • Remote Physiologic Monitoring (RPM) — 99453, 99454, 99457, 99458: Device-based monitoring with clinical review and treatment management. If UpDoc is triggering medication adjustments based on glucose readings, that's a billing-eligible event under RPM treatment management codes.
  • Principal Care Management (PCM) — 99424–99427: Single-condition chronic care management. Potentially the cleanest fit for a focused diabetic titration program.
  • Remote Therapeutic Monitoring (RTM) — 98975–98981: Covers non-physiologic data including medication adherence and functional status. Broader application for UpDoc's care coordination scenarios.

The challenge is documentation and attribution. Traditional CCM billing requires time-stamped documentation of the clinical interaction, a documented care plan, and provider attestation. When the clinical interaction is an AI agent executing an insulin titration at 2 AM, the billing team needs to know it happened, who owns the documentation, and whether the EHR entry constitutes a billable event under the relevant payer's policy.

Prior Auth Exposure

UpDoc's platform triggers lab orders autonomously. Lab orders — even within physician-approved parameters — are subject to prior authorization by many commercial payers, particularly for high-volume chronic disease management panels. The automation that eliminates the scheduling friction doesn't eliminate the PA requirement on the downstream lab order.

Health systems deploying UpDoc at scale need to understand their payer mix's PA requirements for the lab panels their UpDoc protocols will trigger, and ensure the platform either integrates with their PA workflow or routes flagged orders for human review before transmission.

⚠️ Watch: Payer Policy Lag on AI Documentation

Does a CCM billing note generated by an AI agent satisfy the attestation requirements of CMS and commercial payers? This is currently unresolved. Expect initial denials followed by policy clarification over the next 12–18 months as volume scales.

Investor Validation

The $18M seed included strategic investors whose involvement functions as market signals as much as capital. Mayo Clinic's participation implies clinical validation and a potential deployment pathway. Eli Lilly's involvement — as the manufacturer of the leading GLP-1 and insulin products — signals direct commercial interest in AI-assisted titration and adherence management at population scale. The American Diabetes Association as an investor is directionally the same signal.

What to Watch

  • Payer policy on AI-generated clinical documentation. CMS and commercial payers haven't issued guidance on AI-authored EHR notes as CCM/RPM documentation. The first audit cycle at a major deployment will force the question.
  • Coding guidance lag. CMS and AMA typically trail clinical practice by 18–24 months on new code categories. Interim billing under existing CCM/RPM/PCM codes is viable but imperfect.
  • Audit risk at scale. High-volume AI-generated CCM claims at Cleveland Clinic or UCSF will attract OIG attention. Health systems deploying this need a compliance framework before the revenue cycle team starts billing at volume.
  • Specialty expansion. The diabetes use case is the clearest. Oncology supportive care, cardiology titration, and behavioral health monitoring are the obvious adjacent categories — each with different coding complexity.

Bottom line

UpDoc's FDA clearance confirms regulators will approve patient-facing agentic AI for clinical use. The revenue opportunity from autonomous between-visit care is real — CCM, RPM, PCM codes exist and reimburse. But documentation standards, payer policies, and audit exposure haven't caught up to what the platform can generate at scale.

Source: UpDoc press release, June 25, 2026

Reaching RCM decision-makers? Advertise with RevCycleAI →