What Is Risk-Based Authentication and How Does It Fit Into a Fraud Detection Strategy?
Risk-based authentication scores every session in real time for smarter threat detection. Discover how RBA integrates...
Over $45 billion has flowed into healthcare AI since 2020. Healthcare software vendors have deployed tools across radiology, clinical decision support, and patient monitoring — yet fewer than 20% of those tools have been validated through prospective clinical trials. That gap is the first thing anyone evaluating these systems should understand.
The honest answer to whether AI works in medicine is: it depends almost entirely on which task, which patient population, and which study you’re reading. Peer-reviewed meta-analyses published through 2024 and 2025 tell a story that’s both more encouraging and more cautious than vendor marketing suggests. By the time you finish reading, you’ll know which clinical applications have cleared the evidentiary bar — and which haven’t come close.
Some applications of AI-driven healthcare software have genuine, replicable clinical evidence behind them. Not a lot — but enough to matter.
In radiology and ophthalmology, the evidence is compelling. Meta-analyses published in The Lancet Digital Health and JAMA Network Open have consistently shown AI systems matching or exceeding specialist sensitivity for specific screening tasks: diabetic retinopathy detection from fundus photographs, chest X-ray pathology flagging, and mammography triage.
Here’s the important caveat, though. Most of that performance data comes from curated, retrospective datasets — images collected from single institutions, often pre-selected for quality. When those same models get deployed into messy real-world environments with equipment variability, patient heterogeneity, and different image acquisition protocols, performance drops.
Sometimes substantially.
As of 2024, the FDA had cleared over 700 AI-based medical solutions in radiology alone. But clearance is not the same as clinical outcome evidence. These are distinct things, and conflating them is one of the most common mistakes health systems make when evaluating new healthcare software.
If a vendor shows you sensitivity and specificity benchmarks, ask what dataset those numbers came from. Single-site, retrospective data is a starting point — not a finish line.
Sepsis early-warning is the other domain where prospective evidence exists — though the picture is more complicated than advocates admit.
Some validated deterioration alert systems have shown statistically significant reductions in sepsis mortality in prospective trials. But the Epic Sepsis Model, one of the most widely deployed, was independently evaluated and found to generate false alerts for roughly 2 out of every 3 warnings it fires. Studies in NEJM Catalyst and Critical Care Medicine documented alert fatigue as a significant downstream consequence — clinical staff began ignoring alerts at higher rates, which partially negated the benefit.
The systems that do work share a common feature: workflow integration is part of the design, not an afterthought. An alert that fires into a vacuum is noise. An alert that routes to a specific person with a defined response protocol is a tool.
Beyond imaging and deterioration monitoring, the evidentiary ground gets thin fast. In some areas, it nearly disappears.
Large language models can pass the USMLE. That fact has appeared in more press releases, conference talks, and funding pitches than I can count. What it doesn’t demonstrate is that deploying an LLM as a clinical assistant improves patient outcomes.
Those are different claims.
As of early 2025, there are no published randomized controlled trials demonstrating that LLM-based medical solutions improve diagnostic accuracy or reduce clinical errors in real patient populations. Systematic reviews have flagged this absence repeatedly. The research that does exist measures surrogate endpoints: clinician satisfaction, time-to-decision, or model accuracy on test questions. These matter — but they’re not outcome data.
I’d argue the benchmark fixation has genuinely distorted the field. Passing a licensing exam tells you a model can retrieve and apply textbook knowledge. It says nothing about how that model performs under clinical ambiguity, with incomplete information, or in populations underrepresented in training data.
Vendor projections for AI-driven personalized treatment are among the most aggressively marketed claims in the sector. They also have the weakest evidence base.
Most studies in this space:
The FDA’s evolving regulatory framework for “adaptive” AI-based healthcare software — where the algorithm continues learning after deployment — signals that regulators are paying close attention to these gaps. If you’re evaluating any system marketed as continuously self-improving, that regulatory caution is worth factoring into your assessment.
Revenue cycle automation, prior authorization prediction, scheduling optimization — these are areas where AI has shown real operational efficiency gains. But operational efficiency and clinical impact are not the same metric. If your organization is evaluating healthcare software for operational use cases, that’s defensible. Just don’t let a vendor translate “reduced billing errors by 30%” into evidence that the system improves care.
Most clinicians and administrators were never trained to read AI research critically. Here’s what to look for.
Clinical evidence quality is a hierarchy, not a spectrum. A randomized controlled trial with patient outcome endpoints is the gold standard; a single-institution benchmark is the floor. Most healthcare AI research sits near that floor.
| Study Design | Evidence Quality | How Common in AI Research |
|---|---|---|
| Randomized controlled trial (RCT) | Highest | Rare — under 5% of published studies |
| Prospective observational | High | Uncommon |
| Retrospective validation | Moderate | Most common |
| Single-institution benchmark | Lowest | Extremely common |
When you see a study cited in a vendor pitch, the first question is: was this prospective or retrospective? The second: what endpoint did they actually measure?
CONSORT-AI and SPIRIT-AI are reporting guidelines developed specifically for AI clinical trials — they define what a well-designed study must disclose about data, methods, and subgroup performance. Studies that don’t follow them are harder to evaluate and often hiding design weaknesses. You don’t need to read the full guidelines — but knowing they exist gives you something concrete to ask: “Does your validation study follow CONSORT-AI reporting standards?”
Watch how the vendor responds.
When you’re reading a study or evaluating vendor evidence, these should give you pause:
Peer-reviewed studies have documented performance disparities across race, sex, and age in FDA-cleared dermatology AI tools, cardiac risk prediction models, and pulse oximetry algorithms. This isn’t speculative — the disparities exist because training datasets are not representative, and because many validation studies never report subgroup performance at all.
If your health system serves a diverse patient population, ask every vendor for subgroup-level performance data. If they can’t provide it, that’s an answer.
Knowing what the literature says only matters if it changes how you act.
The AMA and NHS both published updated guidance in 2024 recommending that health systems require independent validation studies — not just FDA clearance — before deploying AI medical solutions in clinical workflows. The case for local validation is particularly strong: a model trained on data from academic medical centers may perform differently in community hospitals with different patient demographics and documentation practices.
Requiring local validation isn’t obstruction. It’s due diligence.
Real-world performance monitoring needs to be built into procurement contracts, not treated as a post-launch consideration. Models drift. Patient populations change. Documentation practices evolve. A system that performed well at deployment can quietly degrade over 18 months without anyone noticing — unless you’re actively measuring.
When evaluating healthcare software, ask vendors specifically: what performance metrics does the system report on an ongoing basis, and who receives those reports? If the answer is vague, that’s worth pressing on.
Studies across multiple imaging and alert domains show that AI combined with clinician review outperforms either alone — but only when the clinician is genuinely engaged, not rubber-stamping outputs. Automation bias is well-documented: clinicians regularly over-defer to algorithmic recommendations even when their own judgment would have led to the correct call. Structural workflow design matters here. Override rates should be tracked. And clinicians should be able to push back on the system without administrative friction getting in the way.
Yes, but in specific, bounded contexts. Prospective trials have shown statistically significant mortality reductions for validated sepsis early-warning systems in certain implementations. AI screening tools for diabetic retinopathy have demonstrated early detection rates that translate to preserved vision in populations where specialist access is limited. These are real findings — they just don’t generalize automatically to other AI applications.
Ask for peer-reviewed publications — not white papers — that follow CONSORT-AI or SPIRIT-AI reporting standards. Check whether the validation was prospective or retrospective, whether subgroup performance is reported, and whether the study population resembles your own. FDA clearance is a regulatory milestone, not a clinical evidence standard, and the two should never be treated as equivalent.
Conflating proof of concept with proof of outcomes. A demo that impresses in a controlled environment, or a case study from a single flagship institution, is not evidence that the system will perform the same way in your context. The second-biggest mistake is deploying without a monitoring plan — which means you won’t know when performance degrades until something goes wrong.
In the domains where we have good data, yes — but the structure of that collaboration matters. AI augmenting a clinician who remains critically engaged outperforms AI alone or clinician alone in imaging triage and some alert contexts. The risk is automation bias, where the “human in the loop” becomes a formality rather than a genuine check.
The peer-reviewed record on healthcare AI is neither as promising as vendors suggest nor as bleak as skeptics claim. What it is, is precise. Diagnostic imaging tools and validated deterioration alerts have cleared a meaningful evidentiary bar. Generative AI clinical assistants, precision treatment optimization, and most operational AI claims have not — at least not yet, and not by the standards that clinical decision-making requires.
The question worth asking isn’t “does this AI work?” It’s: worked for whom, measured how, and validated by whom?
Start with something concrete: the next time a vendor presents clinical evidence, ask for the CONSORT-AI citation for their validation study. One question, asked consistently, will tell you more about a product than any demo ever will — and it’ll tell you something about the vendor, too.
Tell us about your product, platform, or business software requirement. We will suggest the right team structure, roadmap, and engagement model within 48 hours.