Microsoft’s diagnostic AI clears a hard benchmark—not the clinic
MAI-DxO reached 83% accuracy on complex published cases and 80% on an emergency-department benchmark by asking questions and ordering tests in sequence. The peer-reviewed result is substantial, but it is not evidence of safe autonomous diagnosis in real patients.

The story
Microsoft researchers have published a peer-reviewed evaluation of MAI-DxO, an artificial-intelligence system designed to work through a diagnosis sequentially instead of receiving a complete case summary at once. In tests reported in Science on October 22, the orchestrated system substantially outscored generalist physicians on two simulated benchmarks. The result is a notable advance in how diagnostic AI is evaluated, but it does not show that the system is ready to diagnose patients independently.
The researchers built the Sequential Diagnosis Benchmark, or SDBench, to resemble the information-gathering part of clinical work. A participant begins with a short presentation, then asks for history, examination findings or tests. A gatekeeper reveals information only when requested. Performance is judged by the eventual diagnosis, the path taken to reach it and the estimated cost of the work-up. That is more demanding than the multiple-choice medical exams on which many language models now score highly.
MAI-DxO adds an orchestration layer around a frontier language model. Simulated clinical roles propose possible diagnoses, challenge the leading explanation and select the next question or test. The orchestrator repeatedly updates the working differential as evidence arrives. Its purpose is not to create new laboratory data or examine a patient; it manages reasoning over information supplied through the benchmark’s text interface.
On 304 diagnostically difficult clinicopathological cases published by The New England Journal of Medicine, Microsoft reports that MAI-DxO achieved 83% accuracy. Generalist physicians reached 22% without outside resources and 36% when allowed to use textbooks and the internet. On 325 validation and test cases derived from MIMIC-IV emergency-department admissions, the orchestrator scored about 80%, compared with a reported 47% average for physicians. The system also produced lower estimated work-up costs in several configurations.
Those comparisons need careful framing. The NEJM cases are deliberately unusual teaching cases with known final diagnoses, not a representative stream of primary-care complaints. The MIMIC cases are retrospective records converted into text encounters. Neither benchmark captures every clinical signal: how a patient looks, the reliability of a history, a changing bedside condition, communication barriers, incomplete records or the operational consequences of a mistaken test order.
The evaluation also does not establish improved patient outcomes. Diagnostic accuracy is one component of care, alongside treatment selection, explanation, consent, follow-up and accountability. Estimated test prices are not the same as real resource use, and an apparently efficient work-up can still be unsafe if it omits a rare but urgent possibility. A system intended for clinical use would need prospective evidence, monitoring for subgroup differences and a defined route for clinicians to override or audit its recommendations.
Microsoft says the next phase will move into hospital settings through a collaboration with Beth Israel Deaconess Medical Center in Boston. The planned prospective study would let patients interact with the system and compare its performance with physicians’ independent assessments. Details such as enrollment criteria, endpoints, the system’s exact role and how adverse recommendations will be handled will determine whether that project tests clinical usefulness rather than simply reproducing another benchmark.
INNOVOX analysis: SDBench may be as consequential as the model result. Requiring an AI agent to choose its next piece of evidence exposes behaviors that a one-shot question hides—premature closure, excessive testing, anchoring and poor stopping decisions. An open benchmark can help researchers compare orchestration methods. But because Microsoft’s team created both the benchmark and MAI-DxO, independent evaluation on unseen institutions and prospectively collected cases is essential before treating its advantage as general.
What to watch now is the transition from simulation to accountable clinical support. Strong evidence would include a preregistered trial, transparent error categories, results across common as well as rare conditions, demographic performance, comparison with specialist teams and analysis of whether clinicians become more accurate when they use the system. Until then, the defensible conclusion is narrow: MAI-DxO performed impressively on controlled sequential-diagnosis tasks, not that it has replaced the judgment or responsibilities of a doctor.
INNOVOX analysis
The important contribution is not another model score but a more realistic evaluation loop: the system must decide what evidence to request, when to stop and how to balance information against estimated cost. Yet the same benchmark and orchestration stack were built by the researchers, so independent replication, prospective trials and safety analysis will matter more than the headline comparison with physicians.
What to watch
Watch for the prospective Beth Israel study’s protocol, preregistered endpoints, patient-selection criteria and failure analysis; independent replication on other hospitals’ data; performance across demographic groups and common ambiguous presentations; test-ordering safety; and a clearly defined human-oversight and regulatory pathway.
