AI

LLMs Beat Clinical Fusion Models by Turning Patient Data into Plain Text

A new study shows that converting all patient data into natural language sequences lets off-the-shelf LLMs match or beat specialized clinical prediction systems across mortality, graft failure, and triage tasks.

Researchers led by Ajay Madhavan Ravichandran found that converting all patient data into a single natural language sequence and fine-tuning off-the-shelf LLMs matches or beats specialized multimodal clinical prediction systems across three tasks: in-hospital mortality, graft failure, and emergency triage. The approach outperformed a clinically deployed gradient boosting model for graft failure prediction and eliminates the need for custom fusion architectures. This suggests a simpler, more interoperable path for clinical AI that could reduce system complexity and deployment cycles in healthcare settings.

A team of researchers has demonstrated that large language models can outperform or match purpose-built clinical prediction systems simply by treating all patient data as plain text. The work, led by Ajay Madhavan Ravichandran and colleagues, tested this approach across three distinct medical tasks and found that a single serialization strategy eliminated the need for complex multimodal fusion architectures entirely.

The implications are significant for an industry that has spent years building intricate encoder pipelines to combine electronic health records, lab values, vital signs, and physician notes. If a pretrained language model can ingest everything as one narrative and still deliver superior results, the entire engineering playbook for clinical AI may need rewriting.

The Problem with Today's Clinical AI Stacks

Most hospital prediction systems today are bespoke constructions. Engineers pair separate encoders for structured data (blood pressure readings, creatinine levels, comorbidity codes) with text encoders for clinical narratives, then design learned fusion layers to merge the representations. Every new task, from predicting sepsis to estimating readmission risk, typically demands a new architecture. Retraining, validation, and deployment cycles stretch across months.

The research team asked a blunt question: what if the fusion step is unnecessary? Their answer was to serialize every data point, structured or unstructured, into a single natural language sequence and fine-tune a pretrained model end to end. No custom fusion modules. No modality-specific pipelines. Just text in, prediction out.

Three Clinical Tasks, One Unified Approach

The study evaluated this strategy on three clinically distinct benchmarks.

First, in-hospital mortality prediction on the widely used MIMIC-III dataset, which contains de-identified intensive care unit records from Beth Israel Deaconess Medical Center. Second, graft failure prediction using longitudinal data from a German transplant center, where the team compared their approach against a gradient boosting model currently deployed in actual clinical practice for post-transplant patient management. Third, emergency triage classification derived from ambulance records, a high-stakes setting where speed and accuracy directly affect patient outcomes.

Across all three, the serialized-text approach matched or exceeded established multimodal baselines. On graft failure specifically, it outperformed the clinically deployed gradient boosting system. The models tested spanned both encoder-based (ModernBERT) and decoder-based families (Llama 3.1, Gemma, DeepSeek-R1-Qwen, Qwen3), suggesting the result is not tied to a single architecture choice.

Why Simplification Matters in Healthcare

The healthcare technology sector has a well-documented tendency toward complexity. Vendors sell elaborate integration layers, hospitals maintain separate data warehouses for structured and unstructured information, and regulatory validation requirements multiply with every new component in the pipeline. A unified text-based approach collapses much of this infrastructure. One model. One input format. One validation cycle.

This also has practical implications for interoperability. Electronic health records vary enormously across institutions, but natural language is the one format every system already produces. Clinical notes, discharge summaries, and radiology reports are universal. Converting structured fields into text is trivial compared to building custom HL7 FHIR integrations for every new prediction task.

What This Means for the Broader AI Landscape

The finding adds to a growing body of evidence that language models are more capable generalist learners than their architecture labels suggest. The term "multimodal" has become a buzzword implying specialized vision encoders, audio processors, and cross-attention mechanisms. This study suggests that for many domains, "multimodal" may simply mean "good at understanding descriptions of multiple modalities."

That is not to say specialized architectures are dead. Image-heavy tasks like pathology slide analysis or retinal scan interpretation still benefit from vision transformers. But for the text-and-numbers world of clinical records, the overhead of custom fusion may no longer be justified.

Looking Ahead

The research team has not yet disclosed whether any health system plans to adopt the approach in production, though the comparison against an actively deployed graft failure model suggests the gap between research and deployment may be narrowing. The next critical step will be prospective validation: running these text-serialized models on live patient streams to confirm they maintain performance outside retrospective datasets.

Regulatory pathways also remain an open question. The FDA and equivalent bodies in Europe have frameworks for traditional machine learning models in healthcare, but the rapid evolution of LLM-based systems is forcing regulators to rethink what "locked algorithm" even means when the underlying model can be fine-tuned on new text with minimal re-engineering.

For now, the message to clinical AI teams is clear: before investing in another multimodal fusion pipeline, try describing your data in words and feeding it to a language model. The results may surprise you.