Journal article
Machine learning in medicine: should the pursuit of enhanced interpretability be abandoned?
- Abstract:
- We argue why interpretability should have primacy alongside empiricism for several reasons: first, if machine learning (ML) models are beginning to render some of the high-risk healthcare decisions instead of clinicians, these models pose a novel medicolegal and ethical frontier that is incompletely addressed by current methods of appraising medical interventions like pharmacological therapies; second, a number of judicial precedents underpinning medical liability and negligence are compromised when 'autonomous' ML recommendations are considered to be en par with human instruction in specific contexts; third, explainable algorithms may be more amenable to the ascertainment and minimisation of biases, with repercussions for racial equity as well as scientific reproducibility and generalisability. We conclude with some reasons for the ineludible importance of interpretability, such as the establishment of trust, in overcoming perhaps the most difficult challenge ML will face in a high-stakes environment like healthcare: professional and public acceptance.
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Access Document
- Files:
-
-
(Preview, Version of record, pdf, 196.9KB, Terms of use)
-
- Publisher copy:
- 10.1136/medethics-2020-107102
Authors
- Publisher:
- BMJ Publishing Group
- Journal:
- Journal of Medical Ethics More from this journal
- Volume:
- 48
- Issue:
- 9
- Pages:
- 581-585
- Publication date:
- 2021-05-18
- DOI:
- EISSN:
-
1473-4257
- ISSN:
-
0306-6800
- Language:
-
English
- Keywords:
- Pubs id:
-
1181489
- Local pid:
-
pubs:1181489
- Source identifiers:
-
W3161904859
- Deposit date:
-
2026-03-24
- ARK identifier:
This ORA record was generated from metadata provided by an external service. It has not been edited by the ORA Team.
Terms of use
- Copyright date:
- 2021
- Licence:
- CC Attribution (CC BY)
If you are the owner of this record, you can report an update to it here: Report update to this record