The clinical AI safety gap is doubly structural: FDA enforcement discretion removes pre-deployment safety requirements while MAUDE's lack of AI-specific fields means post-market surveillance cannot detect AI-attributable harm
No point in the deployment lifecycle systematically evaluates AI safety for most clinical decision support tools
Claim
The clinical AI safety vacuum operates at both ends of the deployment lifecycle. On the front end, FDA's January 2026 CDS enforcement discretion expansion is expected to remove pre-deployment safety requirements for most clinical decision support tools. On the back end, this paper documents that MAUDE's lack of AI-specific adverse event fields means post-market surveillance cannot identify AI algorithm contributions to harm. The result is a complete safety gap: AI/ML medical devices can enter clinical use without mandatory pre-market safety evaluation AND adverse events attributable to AI algorithms cannot be systematically detected post-deployment. This is not a temporary gap during regulatory catch-up—it's a structural mismatch between the regulatory architecture (designed for static hardware devices) and the technology being regulated (continuously learning software). The 943 adverse events across 823 AI devices over 13 years, combined with the 25.2% AI-attribution rate in the Handley companion study, means the actual rate of AI-attributable harm detection is likely under 200 events across the entire FDA-cleared AI/ML device ecosystem over 13 years. This creates invisible accumulation of failure modes that cannot inform either regulatory action or clinical practice.
Supporting Evidence
Source: ARISE Network State of Clinical AI Report 2026
ARISE 2026 identifies 'risks from deskilling and automation bias remain underexamined in the published literature' and notes the 'transition from RCT evidence to real-world deployment evidence is the frontier challenge,' confirming systematic evidence gaps in post-deployment safety
Sources
1- Babic et al. 2025 (MAUDE analysis) + FDA CDS Guidance January 2026 (enforcement discretion expansion)
Connections
11Supports 4
- FDA MAUDE reports lack the structural capacity to identify AI contributions to adverse events because 34.5 percent of AI-device reports contain insufficient information to determine causality
- FDA's MAUDE database systematically under-detects AI-attributable harm because it has no mechanism for identifying AI algorithm contributions to adverse events
- Regulatory vacuum emerges when deregulation outpaces safety evidence accumulation creating institutional epistemic divergence between regulators and health authorities
- State clinical AI disclosure laws fill a federal regulatory gap created by FDA enforcement discretion expansion because California Colorado and Utah enacted patient notification requirements while FDA's January 2026 CDS guidance expanded enforcement discretion without adding disclosure mandates
Related 7
- clinical-ai-safety-gap-is-doubly-structural-with-no-pre-deployment-requirements-and-no-post-market-surveillance
- fda-maude-cannot-identify-ai-contributions-to-adverse-events-due-to-structural-reporting-gaps
- fda-maude-database-lacks-ai-specific-adverse-event-fields-creating-systematic-under-detection-of-ai-attributable-harm
- fda-2026-cds-enforcement-discretion-expands-to-single-recommendation-ai-without-defining-clinical-appropriateness
- regulatory-deregulation-occurring-during-active-harm-accumulation-not-after-safety-evidence
- healthcare AI regulation needs blank-sheet redesign because the FDA drug-and-device model built for static products cannot govern continuously learning software
- human-in-the-loop clinical AI degrades to worse-than-AI-alone because physicians both de-skill from reliance and introduce errors when overriding correct outputs