The Doctor’s Shield: How a No-Licensure-for-AI Vote, a Six-Demand Vendor Liability Push, and an 81-Percent Adoption Rate Left Vendors Exposed and Courts Unpersuaded
On November 9, the American Medical Association’s House of Delegates voted that AI cannot be licensed as a physician, then adopted a six-part plan to move liability for defective clinical AI onto vendors and any organization that mandates their tools. With four in five physicians already using AI and a quarter reporting no training on it, the association is trying to write the liability rules before the courts do.
A Line Drawn in Orlando
At its Interim Meeting in Orlando on November 9, 2026, the American Medical Association (AMA) House of Delegates adopted policy drawing what the association called “a clear line between artificial intelligence as a tool to support healthcare and the practice of medicine”: AI can augment physicians and assist with clinical tasks, “but it cannot be granted physician licensure, professional titles or certification to practice medicine” [1]. The policy calls for AI-enabled technologies to be integrated into physician-led teams and used at the direction of the treating physician, and for the AMA to advocate model legislation that distinguishes the authorization of a medical technology from professional licensure while prohibiting nonhuman entities from holding titles reserved for physicians [1].
“AI can help physicians analyze information, identify patterns and support clinical decision-making, but patients deserve to know who is responsible for their care,” said AMA President Willie Underwood III, MD, MSc, MPH. “Physicians also need the authority, oversight and liability protections to make independent decisions when AI is part of the care team.” [1]
The distinction the AMA wants legislated is between a product’s clearance and a professional’s license. FDA authorization says a tool may be marketed; licensure says a person is accountable for judgment. The core logic of the AMA’s position is that blurring the two lets vendors borrow the authority of medicine without inheriting its obligations — patients hear “doctor,” but no licensed professional stands behind the output. A companion directive would also bar AI developers from using patients’ clinical data for proprietary or research purposes without explicit authorization [2].
Why Now: Adoption Is Outrunning the Rules
The push is not happening in a vacuum. The AMA’s 2026 Physician Survey on Augmented Intelligence found that 81 percent of physicians now use AI professionally — more than double the 38 percent rate in 2023 — with the average physician reporting 2.3 distinct use cases, up from 1.1 three years ago [3]. The most common uses are medical research summarization and clinical care documentation, and more than three-quarters of physicians now believe AI improves their ability to care for patients [3].
But the same survey shows the binding constraint. Clear liability frameworks “rank highest among regulatory actions essential to build physician trust and increase adoption of AI tools,” the AMA reported, alongside physician demands for data privacy (86 percent) and validated safety and efficacy (88 percent) [3]. Trade coverage of the survey data found roughly a third of physicians citing “clear liability frameworks” as the primary driver of adoption, and a quarter of physicians reporting they have received no AI training at all while 92 percent want more [4]. Eighty-eight percent of physicians told the AMA they are concerned about skill loss, particularly those with ten or fewer years in practice [3].
The AMA’s framing of the problem is that physicians are being asked to absorb risks the technology creates. Physicians are currently “being asked to become a safety net to protect against clinical AI failures,” meaning they “may be held accountable for risks that they cannot control and, ‘in some cases, may not even be able to identify,’” said Jennifer Goldsack, head of the AMA Center on Digital Health and AI [4]. The underlying mismatch: adoption is compounding while accountability rules are undefined — which is precisely the vacuum the new policy is designed to fill.
The Six Demands: Moving Liability Upstream
The operative fact behind the liability plan is scale. The FDA has authorized more than 1,450 AI-enabled medical devices as of December 2025, and the AMA argues that — “no different from say, from an inherent problem in an MRI machine” — physicians should not bear responsibility for defects in products they did not build, cannot inspect, and often cannot see through [2]. To that end, the House of Delegates directed the AMA to advocate six legislative demands [2]:
- Vendor liability for erroneous outputs. Federal and state legislation establishing that when a clinical AI product produces an erroneous output, and the physician used the product as intended while exercising appropriate clinical judgment, liability for patient harm rests with the AI vendor, manufacturer, or distributor — not a medical malpractice claim against the physician.
- Device-grade product liability. AI vendors held to the same product liability standards as manufacturers of any other medical device, including liability for design defects and for failing to provide adequate instructions or warnings.
- Insurance as a condition of marketing. Legislation requiring AI vendors and manufacturers to maintain product liability insurance adequate to cover claims arising from AI failures in clinical settings, tied to FDA marketing authorization.
- A ban on liability-shifting contracts. Legislation prohibiting contractual provisions — including end-user license agreements and vendor contracts — that attempt to shift liability for AI tool failures from the manufacturer to the physician or health system.
- Mandatory performance disclosure. Federal legislation requiring vendors to disclose known failure rates, limitations, and performance data for clinical AI products, including performance across different patient populations, so physicians can make informed decisions about the outputs they act on.
- The mandated-tool rule. When a health system, hospital, payer, or other entity mandates the use of a specific AI tool and that tool produces an error causing patient harm, the mandating entity and the vendor bear the liability — the physician who was required to use the tool and exercised appropriate clinical judgment is not liable [2][5].
Read together, the six demands share one allocation principle: liability follows control. Insurance requirements force vendors to price their own failure rates into their products; disclosure duties give physicians the information they would need to exercise the judgment the law expects of them; the anti-shifting rule prevents procurement contracts from quietly undoing what statute assigns; and the mandated-tool rule recognizes that when a system mandates a tool, the mandate — not the clinician holding it — is the decision that put the product in the room. The demands also extend to the machinery that judges physicians: the delegates called for physician-led oversight of any AI used in credentialing, privileging, peer review, and quality review, with full disclosure of the tool’s data sources, validation, limitations, and intended use [2].
The Framework Underneath: Duty Attached to Control
The November policy builds on a framework the AMA released in October 2026, in an issue brief titled “Liability for Clinical AI.” Its organizing principle is that “responsibility should reflect each party’s authority, access to information and ability to prevent or mitigate harm” [6]. Under that principle, four parties hold distinct duties: physicians are responsible for the clinical judgment they can meaningfully exercise; developers for the systems they build and the risks within their control; deployers — hospitals, health systems, and practices — for where and how AI is put to work; and patients must retain meaningful avenues for accountability and appropriate remedies when harm occurs [6].
Goldsack’s illustration of the principle is a case every clinician will recognize: if a physician builds a treatment plan on the recommendation of an AI clinical decision support tool, but the tool failed to account for critical data and the physician had no visibility into that error, the physician should not be held responsible for the resulting harm [4]. Disclaimers, in the AMA’s view, are “not strong enough safeguards” — the framework instead asks where the risk of harm lies, which stakeholder can prevent it, and what information that stakeholder needs [4]. “This [framework] is going to create the rubric by which every different stakeholder gets very clear on their responsibility to proactively implement best practices where they have the ability to mitigate risk,” Goldsack said [4].
The reason a framework is needed at all is structural. Traditional malpractice law assumes one licensed human holds all the relevant control over a patient’s care, which is what makes a single-defendant lawsuit coherent. When control fragments — a vendor designs the model, a hospital deploys it, a physician applies it — the old model either overcharges the physician, who lacks control over the defect, or under-deters the vendor, whom the injured patient cannot even see. The AMA’s answer is to re-attach legal duty to actual control, so that accountability and authority stay aligned as AI systems take on more autonomous clinical functions [6].
What the Malpractice Bar Says
The trial lawyers who will actually litigate these cases are not waiting for the AMA’s framework, and they see the problem differently. Medical malpractice attorney Rick Groffsky of Sommers Schwartz argues the technology is new but the legal principles are not: courts still expect clinicians to exercise independent medical judgment. “An AI tool is one more input to consider in that judgment, but it is not a replacement for it,” Groffsky said. “If a physician relies on a flawed recommendation without applying independent clinical judgment, the physician and the employing hospital will likely bear the responsibility” [7].
The documentation AI generates cuts both ways. “The defense that ‘the computer told me to’ does not hold up, because the law still expects independent judgment,” Groffsky noted — but when a clinician overrides a correct AI warning, “the documentation now works against them,” because there is a record that the system flagged the risk [7]. He expects future cases to involve multiple defendants, since a physician may rely too heavily on AI while “the hospital may have handed that physician an AI tool it never adequately vetted or properly trained staff to use” — and he expects vendors to face direct claims where “the flaw was baked into the product itself,” as when training data underrepresents particular patient populations and the model consistently misses conditions affecting those groups [7].
The courts are already arriving. A Florida lawsuit alleging that artificial intelligence contributed to a patient’s delayed cancer diagnosis is drawing fresh attention to the allocation question as AI moves deeper into diagnosis [7]. And Groffsky identifies what he calls perhaps the greatest long-term concern: automation bias. When software performs accurately most of the time, clinicians naturally become less skeptical, and the rare failures can be catastrophic. “The organizations most at risk are the ones that have deployed these tools widely but have not given clinicians clear guidance on when to rely on them and when to question them,” he said [7].
Where the AMA and the Courts Will Collide
The hinge in every one of the AMA’s demands is the phrase “appropriate clinical judgment.” The association wants physicians protected when errors are invisible to them; the malpractice bar observes that the electronic record now shows exactly what the tool recommended, what the clinician decided, and where the two diverged [4][7]. The collision point is the AMA’s demand for protection “against liability for choosing not to use an AI tool or follow an AI recommendation” [1] — a protection Groffsky’s analysis suggests courts will not extend to a clinician who dismisses a validated warning without documented reasoning, because both overreliance and underreliance on AI are expected to generate claims [7]. As certain diagnostic tools approach something resembling the standard of care, organizations choosing not to adopt them may face scrutiny comparable to ignoring any other established clinical practice [7].
There is also a second-order tension the policy exposes. The AMA wants liability to follow control — but physicians are the one party in the chain whose control cannot be measured directly; it is inferred from training, documentation, and behavior. Vendors’ control is embedded in the product, and a hospital’s control is embedded in its procurement and training decisions. Physician control lives only in the judgment call itself, which is why the AMA pairs its shield with information-forcing demands: the disclosure and training requirements are what make “appropriate clinical judgment” legally defensible at all [3][2]. “When we get this right,” Goldsack argued, patients harmed by AI “can seek compensation from the appropriate party,” and harm becomes less likely in the first place “because every stakeholder understands what they’re responsible for” [4].
What to Watch
For hospitals and health systems
The mandated-tool rule is the demand with the most immediate operational bite. Any system that requires clinicians to use a specific AI product would share liability with the vendor when that product fails — which means mandate decisions, and the documentation behind them, just became legal exposure decisions [2][5]. Systems should also expect pressure on the training gap, and should treat Groffsky’s advice as the operative standard: “Clinicians need real training on the tool’s limitations and failure modes, not just a software tutorial,” with governance and validation records built before deployment, not after [7].
For AI vendors
Every demand transfers cost onto the vendor side of the table: insurance requirements, failure-rate disclosure across patient populations, device-grade product liability, and a ban on the contract clauses that today shift those risks back to hospitals [2]. Provider groups including the AMA have separately told the FDA that developers — not providers — should be responsible for monitoring generative AI-enabled medical devices after they reach the market [4].
For policymakers
Watch state legislatures for the AMA’s model bills on licensure boundaries and vendor liability, and watch malpractice dockets for the cases that will define “independent judgment” in an AI-assisted exam room. The association’s stated goal is that clinical authority and accountability remain aligned as AI assumes increasingly autonomous functions [6] — but between now and then, the practical rule of thumb for every party in the chain is unchanged: control is the liability question, and the party that cannot document its control should not expect to keep its shield [7].
References
[1] American Medical Association — [ADVOCACY] “AMA: Artificial intelligence can augment physicians but don’t call it doctor.” Press release, November 10, 2026. (physician professional association)
[2] American Medical Association — [ADVOCACY] “Who can be licensed as a physician? Not AI.” Policy adopted at the 2026 AMA Interim Meeting, November 10, 2026. (physician professional association)
[3] American Medical Association — [ADVOCACY] “AMA: AI usage among doctors doubles as confidence in technology grows.” 2026 Physician Survey on Augmented Intelligence, 2026. (physician professional association)
[4] Vaidya, Anuja — [SECONDARY] “AI vendors, health systems join physicians in liability for clinical AI: AMA.” Healthcare Dive, November 2, 2026.
[5] Bruce, Giles — [SECONDARY] “AMA says AI can’t be licensed as a physician, pushes vendor liability.” Becker’s Hospital Review, November 10, 2026.
[6] American Medical Association, Center on Digital Health and AI — [ADVOCACY] “Liability for Clinical AI.” Issue brief, October 2026. (physician professional association)
[7] Siwicki, Bill — [SECONDARY] “AI misdiagnoses raise new liability questions for health systems.” Healthcare IT News, July 27, 2026.
AI automated and generated content. Human reviewed.


















