Skip to content
Who is liable for AI mistakes

Who is liable for AI mistakes

Plus: The AMA's perspective on who should be liable when AI makes a bad decision, a look at the HTI-5 final rule, and a look at how AI can be used to dose medications.
• 7 min read •

The lead

Ruth’s take

This week, the American Medical Association pushed back on the idea that physicians should assume all liability for AI used in health care.

In an issue brief, the physician group, a major lobbying force in Washington, suggests that if doctors are going to be liable for damage incurred from AI recommendations, then they have to be put in a position where they can meaningfully assess the outputs. For example, if AI deprioritizes a patient during triage, a physician who only sees a list of patients should not be liable for not elevating a patient who needed priority.

The document also outlined a need to define expectations for reasonable reliance on AI tools. Essentially, the document suggests that regulators or industry groups need to outline the circumstances under which a physician can rely on AI without assuming full liability. If an AI tool has been authorized to complete a certain task, should a physician be able to trust that tool?

The paper also says that developers of AI tools should assume some liability for their products even after deployment and so should the deployers, ie. health systems. Without these liability agreements in place, AMA says that physicians should be able to refuse AI products presumably without having to worry about losing their jobs.

The organization says that clarifying liability should ensure patients have to have a path to accountability. Though patients have to be aware of when AI is being used.

The takeaway: As AI becomes more pervasive in medicine, discerning who is liable for harm is going to become even more pressing. As my conversation with Federation of State Medical Boards CEO Hank Chaudhry highlights, who gets in trouble when AI goes wrong is going to be a top issue to solve next year and developers are under pressure to take on some of that responsibility.

—Ruth

`

Upcoming Sessions

Live conversations with the people shaping healthcare.

View all →

Share this article

Spread the word