An AI system that supplies information is performing a different role from one allowed to take a clinical action. The American Medical Association’s October framework asks how permission, evidence, oversight and responsibility should change as that role becomes more consequential.
It is a proposed governance framework, not an enacted system for licensing AI or proof that any named product is safe to operate autonomously. Its useful contribution is to make a broad label—agentic AI—less important than the actual function and authority being granted.
Start with the action, rather than the agent label
In a hypothetical appointment workflow, software might summarise a message, suggest an urgency category or change a booking without waiting for a person. These are illustrative functions, not a description of a verified deployment. They expose different questions about evidence and control, even if one supplier calls all three an “agent”.
The AMA’s accompanying page, dated 13 October, introduces governance for increasingly consequential clinical functions. The one-page original framework begins by defining the task, patient population, setting and intended use.
That specificity changes what needs explaining. A general benchmark result cannot, by itself, establish performance for every action in a real workflow. Nor does the ability to produce an answer establish permission to implement it.
Three governance questions that should stay separate
The AMA distinguishes regulation, the scope of clinical authority and liability. These categories address evidence and conditions of use, permitted action and oversight, and responsibility for decisions or failures.
Its use of “licensure” needs particular care. A footnote says the term concerns authorisation for an AI system to operate in a defined clinical capacity, rather than a licence to practise medicine. That is terminology within the proposal, not a statement that a new legal route already exists.
For readers assessing policy claims, the practical test is whether a statement describes a technical capability, a proposed permission or an actual jurisdiction-specific legal position. Those statements can sound similar while requiring different evidence.
Accountability follows more than the final click
The framework links accountability to authority, control, knowledge of risk and the ability to prevent or mitigate harm. It includes developers, organisations deploying systems, health systems, physicians, payers and other actors.
This helps explain why “a person remains in the loop” is incomplete as a workflow description. In the hypothetical booking example, one would still need to know what the person sees, which actions wait for review and what can be reversed. Those are questions raised by the allocation of authority; this article does not assess whether a particular installation’s controls are adequate.
The AMA also treats authority as something to reassess as performance, risk and technology change. Initial permission and continuing performance are therefore different stages of the proposal.
Evidence reporting and permission are different tools
The TRIPOD+AI reporting initiative addresses transparent accounts of prediction-model development, evaluation and updating. It is a reporting framework, not a licence to perform clinical work.
The distinction is useful: a clear study report can help others examine evidence, while leaving unanswered who can authorise a particular action or accept responsibility for its consequences. Conversely, a governance policy cannot supply missing clinical evaluation.
For NHS readers, the AMA document should also remain separate from England’s DCB clinical-safety responsibilities and DTAC buyer assessment. These have different jurisdictions and purposes. The new proposal does not replace those processes or establish compliance with them.
The most informative description of a clinical AI system is consequently a specific one: what it can do, which actions it is allowed to take, for which people and setting, on what evidence, and with whose responsibility. The agent label cannot supply those details.