Seventy-one percent of U.S. hospitals had predictive AI integrated into their electronic health records by 2024, according to the ONC's Hospital Trends data brief. That adoption rate is moving faster than the regulatory framework covering it, and the evidence base underneath it is thinner than the deployment pace suggests. A recent analysis in Nature Medicine raised the core question: can evidence generation keep pace with AI adoption in clinical settings? The answer matters for any sponsor running a trial that touches an AI-assisted workflow, any CRO validating data from an AI-augmented EHR, and any regulatory team preparing a submission that includes real-world evidence.
The evidence gap no one is budgeting for
A randomized study of more than 9,600 patients across 16 primary care clinics in Kenya tested this assumption at scale. Clinicians using "AI Consult," a generative AI support tool integrated into an electronic medical record, showed improved quality of decision-making. Short-term patient outcomes did not significantly change. That gap between what AI changes at the point of care and what it changes in measured patient results is where evidence generation breaks down for sponsors.
If an AI decision support tool modifies clinician behavior during a trial without producing a detectable signal in the primary endpoint, that is a confounder the protocol likely did not anticipate. If the same tool is embedded in the site's EHR and feeding into the eClinical stack, source data verification has a new variable the monitoring plan was not designed to interrogate. The tool is live, the trial is running, and the evidentiary framework for what the AI actually changed is still being written.
FDA guidance is structural, not prescriptive
In December 2024, the FDA published final guidance titled "Marketing Submission Recommendations for a Predetermined Change Control Plan for Artificial Intelligence-Enabled Device Software Functions," updated in August 2025. The guidance addresses lifecycle management of AI/ML-enabled device software functions. It does not address with operational specificity how a sponsor or site should document, flag, or account for AI decision support modifications occurring in the clinical environment during an active trial. That interpretive gap is the operational problem sponsors are now inheriting.
Who gets caught in the crossfire
Oncology and cardiology sponsors running multi-site trials at academic medical centers face the most immediate exposure. These institutions have the highest AI adoption rates, the most complex EHR integrations, and the greatest likelihood that an FDA-cleared AI decision support tool is operating in the background of a site visit. Aidoc received FDA 510(k) clearance for its CARE AI foundation model, a triage solution that operates across radiology and clinical decision workflows. When that system is running at a site, it is influencing the clinical judgment that generates source data. Most monitoring plans do not account for it.
Decentralized and hybrid trial designs are exposed from a different angle. When a patient interacts with an AI-assisted telehealth platform, an AI-augmented ePRO tool, or an AI-powered symptom checker between site visits, the behavioral and clinical data flowing back to the EDC is already shaped by an upstream AI layer. Regulatory compliance specialists at ELIQUENT Life Sciences have documented AI tools being used for protocol deviation assessment, data cleaning, and risk signal identification in active trials. Each of those applications touches the audit trail an inspector will walk through.
The counterintuitive reality: sponsors who believe AI decision support is only a commercialization problem, something to manage after approval, will find it embedded in their Phase 3 data packages. Adoption at the site level does not wait for the sponsor's validation timeline.
The operational directive
Clinical operations leaders overseeing multi-site trials at institutions using AI-integrated EHR systems need a new section in their site feasibility questionnaire. Before randomization begins, three questions need documented answers at every site: which AI decision support tools are active in the clinical workflow, whether any of those tools interact with the data fields feeding the EDC, and what change control processes the site has if those tools are updated mid-trial. The FDA's Predetermined Change Control Plan guidance establishes that AI/ML-enabled software functions are expected to have managed modification pathways. Sites should be held to an equivalent standard of disclosure. If they cannot answer these questions, treat it as a protocol deviation risk category, not a vendor relationship issue.
For sponsors relying on real-world evidence generated in AI-augmented clinical environments, the pre-registration requirement the FDA has articulated for RWE credibility becomes more load-bearing. The study design must account for AI tool use at data collection sites as a potential effect modifier, or the resulting evidence will not survive a serious methodological challenge at the advisory committee level. Professionals working in regulatory affairs may find structured training on these evolving requirements useful - AI Regulatory Compliance Courses cover the shifting FDA landscape around AI-enabled tools.
Watch the comment period for any follow-on FDA guidance addressing AI in clinical trial operations specifically. The August 2025 update to the Predetermined Change Control Plan guidance touched AI/ML device functions but left the clinical trial intersection largely unaddressed. The agency's AI/ML-based Software as a Medical Device Action Plan, first published in January 2021, identified post-market surveillance and adverse event reporting for AI tools as an open action item. Five years later, that action item has not produced trial-specific operational guidance. The next draft that lands in the Federal Register on this topic will carry immediate protocol implications for any sponsor running trials at AI-heavy institutions, and the window to shape it through public comment will be short.
Why this matters for healthcare professionals
If you work in clinical operations, data management, or regulatory affairs at a healthcare organization, the practical takeaway is direct: your site questionnaires, monitoring plans, and audit preparation materials need to account for AI tools that are already live in your clinical environment. The FDA guidance addresses device software lifecycle management but leaves the active-trial intersection open. That means the burden falls on sponsors and sites to document which AI systems are running, what data they touch, and how they change over time. For those working in billing and compliance roles where AI-augmented workflows are becoming standard, Healthcare Billing Training addresses the operational side of AI integration in clinical settings. The evidence gap between AI adoption and AI validation is not theoretical - it is now a routine part of running a trial at any major medical center.
Your membership also unlocks:
