EHR

A patient chart looks like a document because hospitals make it look that way. There are notes, medication lists, lab panels, procedure codes, imaging references, adverse events, survival outcomes, and enough timestamps to make a database administrator feel briefly useful. So it is tempting to treat the electronic health record as a very long piece of text: serialize the events, train a model to predict the next token, extract an embedding, and hope that clinical meaning emerges somewhere inside the transformer fog. ...

A hospital does not buy “intelligence.” It buys a workflow. That distinction sounds obvious until an AI vendor arrives with a model that has billions of parameters, a clinical pretraining story, and the gentle implication that smaller models are now museum pieces. In the ICU, however, the useful question is not whether the model can talk like a doctor. It is whether it can detect tomorrow’s clinical deterioration from messy notes better than simpler systems that cost less, run faster, and attract fewer infrastructure headaches. ...

Hospitals do not run on clean datasets. They run on discharge notes, lab panels, repeated admissions, missing context, and the occasional clinical abbreviation that looks like it escaped from a tax form. That is the awkward reality behind chronic-disease prediction. The patient record is not just text. It is not just lab values. It is not just a sequence of visits. It is all three, with timing doing much of the quiet work. A patient returning after 42 days does not mean the same thing as a patient returning after 420 days, even when the diagnosis code looks identical. Healthcare operations already know this. Many AI models, bless their expensive little hearts, still behave as if they do not. ...