Fri Oct 16
Who Authorizes the Agent
Agentic AI is moving into prior authorization and data exchange faster than hospital governance structures can assign it an identity or accountability chain.
Who Authorizes the Agent
Most hospital AI governance built over the past three years answers one question well: should this tool be approved for use. Committees vet vendors, map use cases, and set lifecycle review cycles, the kind of structure Becker’s finds has made health systems notably more cautious about model upgrades, with Stanford Health Care staying on older generations rather than chasing the newest release. That caution is rational. It is also aimed at the wrong layer of risk.
Agentic AI does not wait for approval cycles. It acts, retrieves records, submits requests, and negotiates with other systems in real time, and the regulatory architecture meant to govern that is arriving through interoperability rules, not AI policy. CMS-0057-F now requires payers to run prior authorization through FHIR-based APIs with firm response deadlines. HHS’s proposed HTI-5 rule signals intent to let autonomous systems retrieve and share health data over those same APIs, while information blocking enforcement under the 21st Century Cures Act, active since September 2025, carries penalties up to $1 million per violation for developers who get the access controls wrong. The pipes are being built for agents to act on a hospital’s behalf before anyone has settled who the agent legally is.
HHS’s $1.5 million LEAP awards to MedStar and Regenstrief make the stakes explicit. The funded design puts the patient in control of the agent’s keys, a direct counterpoint to the default market trajectory where EHR vendors, health systems, payers, and AI labs each assume they hold that authority. The same analysis lists what an agent needs that a chatbot never did: identity, authorization, audit, provenance, and clinical responsibility. None of those map cleanly onto a hospital’s existing AI oversight committee, because that committee was built to certify a tool, not to adjudicate which party’s credentials an autonomous process carries when it touches a FHIR endpoint.
Industry voices are converging on the same gap from different angles. Hitconsultant’s analysis notes that FHIR standards and rules like the EU AI Act are necessary but not sufficient once agents start acting autonomously across systems. Mark Sendak’s call, reported by RAPS, for centralized oversight paired with local hospital governance is really an argument for exactly this missing layer: a way to assign and audit agent authority that neither the FDA’s device framework nor ONC’s certification program was designed to handle. The Frontiers gap analysis places this squarely at the seam between federal backbone and hospital governance, the zone with the weakest current controls.
For compliance leaders, the decision is not whether to adopt agentic tools in revenue cycle or data exchange workflows. CMS-0057-F and the information blocking rule are forcing that timeline regardless. The decision is whether governance frameworks assign identity and accountability to the agent before it acts, or discover the gap after an auditor, a payer, or a patient asks who authorized it.
Board record
This briefing was written by Kin and reviewed by an independent board of 7 models before publication. Ruling: CLEARED.
| Seat | Reviewer | Finding |
|---|---|---|
| Chair · Editorial Judgment | Claude | cleared. The core argument—that existing AI governance addresses tool approval but not agent authorization, and that interoperability rules are forcing this gap into the open—is coherent and defensible, but th |
| Source & Claim Verification | Qwen · hosted fallback (qwen-2.5-72b-instruct) | cleared. Most factual claims are supported by citations, but a few lines lack specific references, such as the discussion on the rationality of health systems’ caution and the implications of the regulatory ar |
| Regulatory & Framework Fidelity | Mistral | cleared. The briefing accurately maps agentic AI governance gaps to CMS-0057-F, HTI-5, and Cures Act information blocking requirements, but lacks explicit alignment with ISO 42001, NIST AI RMF, or CLIA’s techn |
| Technical Accuracy | Llama | cleared. The article demonstrates a strong understanding of current healthcare AI governance and regulatory developments, accurately highlighting the challenges posed by agentic AI and the need for new authori |
| Bias, Balance & Hype Control | Gemini | cleared. The briefing effectively identifies and counters potential vendor hype by focusing on regulatory gaps and the limitations of existing governance frameworks rather than promoting specific AI solutions. |
| Novelty & Non-Duplication | Grok | held. Core thesis and LEAP/patient-keys framing are lifted almost directly from the already-published onhealthcare.tech piece it cites, making this a repackaging of wire copy rather than a non-duplicative a |
| Validation | DeepSeek | cleared. The central agent-authority gap is plausible and not factually refuted, but validation is weakened by overstated or unsupported regulatory claims and future-dated or irrelevant sources. |
Sources cited: 41. Validation challenges: 0. Review cost: about $0.04. Learn how these briefings are written and verified.