On longitudinal intelligence and what’s missing from encounter-based medicine.
Every patient has a story. Not in the sentimental sense — in the clinical sense. A sequence of problems, interventions, responses, and adjustments that, taken together, explain why they are sitting in front of you today. That story exists somewhere in the chart. But the chart doesn’t tell it. It archives it. The physician has to do the telling, reconstructing continuity from fragments, visit after visit, patient after patient.
This is one of the most expensive inefficiencies in primary care. And almost no one talks about it.
The reconstruction tax
Before a physician can make a good decision about a patient they haven’t seen in six months, they need context. What medications did we try for the hypertension before landing on this one? What was the HbA1c trajectory over the last two years — improving, stable, drifting? Did the cardiologist ever weigh in on the chest pain from the spring?
All of that information exists in the chart. Retrieving it is another matter. The standard workflow is archaeology — opening prior notes in reverse chronological order, scanning for the relevant details, holding them in working memory while the next patient waits. A thorough chart review for a complex patient can take five to ten minutes. For a physician seeing twenty patients a day, that time simply does not exist. What happens instead is a partial reconstruction — good enough to proceed, but not the same as actually knowing.
The cognitive load this places on clinicians is real and largely invisible. It doesn’t show up in Press Ganey scores. It doesn’t appear in quality metrics. It lives in the gap between the care a physician intended to deliver and the care that was possible in the time available.
Why the encounter model creates this problem
The encounter-based record made sense when medicine was simpler. Each visit was a relatively self-contained event — a problem presented, examined, and addressed. The record documented what happened. Future visits referenced it if needed.
Chronic disease changed the calculus entirely. When a patient has hypertension, diabetes, CKD, and depression — each with its own medication history, lab trajectory, and specialist involvement — no single encounter is self-contained. Every visit is downstream of every prior visit. The clinical picture is inherently longitudinal, and a record organized by date is a poor container for longitudinal information.
The problem is not that the information isn’t there. It is that the structure of the record makes it expensive to retrieve. Encounter notes are optimized for documentation, not for synthesis. They capture what happened with high fidelity. They do not surface what matters now.
The physician as integration layer
In the absence of a system that synthesizes clinical history, the physician fills that role. This is so routine that it has become invisible — just part of what it means to know your patients. But it is work. It takes time, attention, and working memory that might otherwise go toward the patient in front of you.
There is also a reliability problem. Human synthesis is inconsistent. A physician who sees a patient regularly and carries that context in memory will practice differently than one covering for a colleague, seeing the patient fresh. Neither is failing — they are operating with different inputs. But the quality of care should not vary based on who happens to remember what.
A chart that synthesizes its own contents — that can present the arc of a problem across visits rather than requiring the physician to reconstruct it — would reduce that variance. It would also return to the physician something that the current system quietly takes away: the ability to be fully present in the visit, rather than partially occupied with remembering.
What longitudinal intelligence actually requires
Synthesizing a patient’s clinical history is not a search problem. It is a comprehension problem. The relevant information is scattered across dozens of notes, in inconsistent formats, mixed with irrelevant detail. Extracting the signal requires understanding clinical context — knowing that a medication listed in a plan three visits ago is worth tracking, that a lab value mentioned in passing is part of a meaningful trend, that an offhand note about side effects explains why a drug was later discontinued.
This is exactly the kind of pattern recognition that modern language models are genuinely good at. Not because they think like clinicians — they don’t — but because they can read across a large body of text and surface structure that would take a human significant time to reconstruct manually.
The output doesn’t need to replace the physician’s judgment. It needs to compress the time between opening a chart and having enough context to exercise that judgment well. A two-sentence summary of how a problem has evolved. A chronological list of every medication tried, with outcomes. The last three values for a key metric, with dates. Information that exists in the chart already, rendered in a form that takes thirty seconds to absorb instead of ten minutes to excavate.
Closing thought
The chart knows everything that was ever written into it. It knows almost nothing about your patient. Those are not the same thing. Medicine has spent decades improving the quality of what gets documented. It is time to spend some of that attention on what gets surfaced — on building records that don’t just archive a patient’s story, but tell it.