File Download

There are no files associated with this item.

  Links for fulltext
     (May Require Subscription)
Supplementary

Article: The need for a system view to regulate artificial intelligence/machine learning-based software as medical device

TitleThe need for a system view to regulate artificial intelligence/machine learning-based software as medical device
Authors
Issue Date2020
Citation
npj Digital Medicine, 2020, v. 3, n. 1, article no. 53 How to Cite?
AbstractArtificial intelligence (AI) and Machine learning (ML) systems in medicine are poised to significantly improve health care, for example, by offering earlier diagnoses of diseases or recommending optimally individualized treatment plans. However, the emergence of AI/ML in medicine also creates challenges, which regulators must pay attention to. Which medical AI/ML-based products should be reviewed by regulators? What evidence should be required to permit marketing for AI/ML-based software as a medical device (SaMD)? How can we ensure the safety and effectiveness of AI/ML-based SaMD that may change over time as they are applied to new data? The U.S. Food and Drug Administration (FDA), for example, has recently proposed a discussion paper to address some of these issues. But it misses an important point: we argue that regulators like the FDA need to widen their scope from evaluating medical AI/ML-based products to assessing systems. This shift in perspective—from a product view to a system view—is central to maximizing the safety and efficacy of AI/ML in health care, but it also poses significant challenges for agencies like the FDA who are used to regulating products, not systems. We offer several suggestions for regulators to make this challenging but important transition.
Persistent Identifierhttp://hdl.handle.net/10722/334666
ISI Accession Number ID

 

DC FieldValueLanguage
dc.contributor.authorGerke, Sara-
dc.contributor.authorBabic, Boris-
dc.contributor.authorEvgeniou, Theodoros-
dc.contributor.authorCohen, I. Glenn-
dc.date.accessioned2023-10-20T06:49:46Z-
dc.date.available2023-10-20T06:49:46Z-
dc.date.issued2020-
dc.identifier.citationnpj Digital Medicine, 2020, v. 3, n. 1, article no. 53-
dc.identifier.urihttp://hdl.handle.net/10722/334666-
dc.description.abstractArtificial intelligence (AI) and Machine learning (ML) systems in medicine are poised to significantly improve health care, for example, by offering earlier diagnoses of diseases or recommending optimally individualized treatment plans. However, the emergence of AI/ML in medicine also creates challenges, which regulators must pay attention to. Which medical AI/ML-based products should be reviewed by regulators? What evidence should be required to permit marketing for AI/ML-based software as a medical device (SaMD)? How can we ensure the safety and effectiveness of AI/ML-based SaMD that may change over time as they are applied to new data? The U.S. Food and Drug Administration (FDA), for example, has recently proposed a discussion paper to address some of these issues. But it misses an important point: we argue that regulators like the FDA need to widen their scope from evaluating medical AI/ML-based products to assessing systems. This shift in perspective—from a product view to a system view—is central to maximizing the safety and efficacy of AI/ML in health care, but it also poses significant challenges for agencies like the FDA who are used to regulating products, not systems. We offer several suggestions for regulators to make this challenging but important transition.-
dc.languageeng-
dc.relation.ispartofnpj Digital Medicine-
dc.titleThe need for a system view to regulate artificial intelligence/machine learning-based software as medical device-
dc.typeArticle-
dc.description.naturelink_to_subscribed_fulltext-
dc.identifier.doi10.1038/s41746-020-0262-2-
dc.identifier.scopuseid_2-s2.0-85087054864-
dc.identifier.volume3-
dc.identifier.issue1-
dc.identifier.spagearticle no. 53-
dc.identifier.epagearticle no. 53-
dc.identifier.eissn2398-6352-
dc.identifier.isiWOS:000524613600001-

Export via OAI-PMH Interface in XML Formats


OR


Export to Other Non-XML Formats