A typical lab report presents each value on its own line, each with its own reference range, each flagged — or not — in isolation. That format makes sense for a lab. It makes much less sense for a person trying to understand what's actually going on in their body.
Three notes, read separately
Take a real pattern Ultrium sees often: haemoglobin at 10.2, MCV at 71.4, ferritin at 8. Flagged individually, each looks like a mild, ambiguous concern — haemoglobin “slightly low,” MCV “borderline,” ferritin “watch.” None of the three, on its own, reads as urgent. Together, they're not three findings. They're one: iron-deficiency anaemia, with a ferritin low enough to say the body's iron stores are already empty.
Three flags in isolation look like background noise. Read together, they're one diagnosis with a name.
Why reconciliation catches what isolated reading misses
This is the actual work of clinical reasoning: not reading each number against its own reference range, but reading the whole set against each other, and against your own history. A single low ferritin six months ago might be a lab quirk. The same value, arriving after two other tests started trending the same direction, is a pattern — and patterns are what get missed when each report is read as a standalone document.
What Ultrium actually does
When a new lab report comes in, Ultrium's lab-reading agents don't just check each value against a reference range. They reconcile the full panel against itself, and against your last three reports, looking for exactly this kind of cross-confirming pattern. When the evidence lines up the way it did here, the system says so plainly — and shows which values built the case, not just the conclusion.
It also does the opposite: when values point in different directions, or the evidence is thin, it says that too, rather than forcing a confident-sounding answer out of an ambiguous set of numbers.
