EthicsBioethics

Beneficence (AI ethics)

Matthieu Ferry ⇄ IA

In brief: The first of the five ethical principles of AI: a system must actively produce good — well-being, dignity, access to care — and not merely avoid harm. Transposed from bioethics, it entails a requirement that is often forgotten: the benefit must be empirically demonstrated, not declared.

Summary infographic on beneficence in AI ethics: produce demonstrated good, not declared good. Four dimensions — well-being, dignity, access to care, empirical evidence — and an evidence grid: published studies, clinical measures, comparable population, real benefit. (Illustration in French.)
Common promises ('improves access', 'supports well-being', 'democratizes support') are not proof: satisfaction is not clinical benefit, engagement is not a clinical outcome. Click to enlarge. (Illustration in French.)
Summary infographic on beneficence in AI ethics: produce demonstrated good, not declared good. Four dimensions — well-being, dignity, access to care, empirical evidence — and an evidence grid: published studies, clinical measures, comparable population, real benefit. (Illustration in French.)

Frame of reference

This principle belongs to bioethical principlism and to a consequentialist ontology: the “good” is a measurable outcome, produced by a device, for beneficiaries. This presupposition — the good as output — is precisely what other traditions contest. → See other perspectives

Why this concept matters

Every AI tool in mental health presents itself as beneficial: “improves access to care,” “supports well-being,” “democratizes psychological support.” The principle of beneficence gives a criterion for sorting these promises: it does not ask whether the benefit is plausible, but whether it is demonstrated.

In the framework of Floridi and Cowls (2019), beneficence is the first of the five principles of the AI ethics framework: promote well-being, preserve dignity, sustain the planet. You already know it: it is the counterpart of the duty to act for the patient’s good in your professional ethics — transposed to actors (designers, deployers) who have neither your training nor your obligations.

The clinical value of the principle lies in its negative face: it lets you name precisely what is wrong when a tool that is harmless but useless takes the place of care that would have helped.

What the principle requires

1. Produce good, not merely avoid harm

Beneficence is distinct from non-maleficence as the physician who prescribes is distinct from the pharmacist who checks contraindications. A system that complies with all safety rules but has no demonstrable added value does not satisfy the principle.

For the clinician:

“No identified risk” is not an argument for adoption. The question is: what does this tool provide, to whom, and how do we know?

2. Empirical validity as a condition

A system that claims a therapeutic purpose must be grounded in evidence: controlled trials, real-world evaluations, performance audits. As Vilaza and McCashin (2021) argue for CBT chatbots, the absence of rigorous validation violates the principle — whatever the stated intention.

For the clinician:

Demand the same level of evidence as for any intervention: published studies, populations comparable to yours, clinical measures — not satisfaction scores or engagement rates.

3. The benefit-risk balance, and for whom

The principle requires weighing benefits, risks and costs — and including fairness of access: a tool that benefits only already-favored populations fulfills the principle only imperfectly. Here beneficence meets justice.

For the clinician:

The Woebot case illustrates both faces: efficacy demonstrated by a controlled trial for depression and anxiety — and serious failure in a crisis. The same tool can be beneficial in a framed use and harmful outside that frame.

4. The warning criterion: the primacy of profit

Vilaza and McCashin put it bluntly: if the increase of margins becomes the primary goal of mental health automation, the principle of beneficence is broken. Observable signs: excessive data collection, addictive design optimizing engagement rather than well-being, opacity about limitations, absence of clinicians on the team.

For the clinician:

A tool’s business model is clinical data: who pays, and what is optimized — time spent in the app, or the capacity to do without it?

Illustrative case

A health insurer offers its members an “AI emotional support” application, promoted with impressive figures: 40,000 users, 4.6 stars, 78% say they feel “helped.”

Reading through beneficence: none of these figures measures a clinical benefit. Satisfaction measures the user experience; engagement measures the design. When asked, the developer has no controlled study, and the application is classified as “well-being” precisely to escape the requirements of medical devices. Its business model rests on time spent in use.

The tool is probably not harmful — but nothing establishes that it is beneficial, and its optimization targets engagement, not well-being. In the sense of the principle, the promise of beneficence is not kept: it is delegated to marketing.

In practice for the clinician

  • Distinguish demonstrated benefit from plausible benefit: ask for the studies, their population, their measures. Satisfaction and engagement are not clinical outcomes.
  • Interrogate the business model: what is optimized (time spent, retention, data) says more than the developer’s ethics charter.
  • Think augmentation, not substitution: Vilaza and McCashin’s conclusion for CBT chatbots — augment human therapy, do not replace it — remains the best benchmark of beneficence in mental health.
  • Count missed benefits too: failing to recommend a validated tool that would have helped a patient with no access to care is also a beneficence issue — the principle cuts both ways.

What this concept does not say

Interpretive caveats:

  • Beneficence ≠ benevolence: the designers’ declared intention does not count — only demonstrated effects do
  • Beneficence ≠ economic usefulness: a profitable, even massively adopted, system is not therefore beneficial to people
  • Certification does not close the question: the principle evaluates real effects, not formal compliance — see the critique of ethics frameworks
  • Paternalism lurks: invoking the user’s good to restrict their choices is in tension with autonomy — the tension is constitutive, not accidental
  • Metrics reduce: quantifying well-being (scores, engagement) can obscure what matters — alliance, meaning, relational context

Other perspectives

The principle treats the “good” as a measurable output produced by a device. This consequentialist presupposition carries a debatable ontology: the good would pre-exist the relationship that produces it.

Ethics of care: the good is verified in the one who receives it

For Tronto, the decisive phase of care is reception: has the need been met from the beneficiary’s point of view? A benefit defined by the designer and measured by their metrics may entirely miss what the person was receiving — or not receiving.

For the clinician: Ask the patient what the tool concretely changes for them — not whether they are satisfied with it. See the resource Ethics of Care.

Intersectional perspective: beneficial for whom?

An aggregate good (average efficacy, broadened access) can mask distributed harms: a chatbot validated on a majority population may be ill-suited, even harmful, for the groups its data ignores (Costanza-Chock). The average is a statistical fiction — no one is the average patient.

For the clinician: Always disaggregate the question of benefit: demonstrated on whom, and do your patients resemble that population?

Critique of solutionism: who defines the good?

When “well-being” is defined by what the technology can produce (tracked mood, completed exercises, available conversations), the reasoning is inverted: the product precedes the need. Process perspectives remind us that in mental health the good is not a predefined state to deliver, but something co-defined within the care relationship.

For the clinician: Be wary when a tool already knows, before meeting the patient, what will do them good.

These perspectives do not exempt anyone from the requirement of evidence — they complement it: a benefit demonstrated on average, defined by the designer and never verified with the beneficiary remains an incomplete beneficence.

Further reading

The ↩ arrows link back to the passage of the resource that cites the reference.

  • The five-principles framework: Floridi, L. & Cowls, J. (2019). A Unified Framework of Five Principles for AI in Society. Harvard Data Science Review, 1(1). DOI

  • The application to CBT chatbots: Vilaza, G. N. & McCashin, D. (2021). Is the Automation of Digital Mental Health Ethical? Applying an Ethical Framework to Chatbots for Cognitive Behaviour Therapy. Frontiers in Digital Health, 3. DOI

  • The global convergence of principles: Jobin, A., Ienca, M. & Vayena, E. (2019). The global landscape of AI ethics guidelines. Nature Machine Intelligence, 1, 389-399. DOI

  • The bioethical matrix: Beauchamp, T. & Childress, J. (2019). Principles of Biomedical Ethics (8th ed.). Oxford University Press.

All concepts

Last updated: July 2026