Most of consumer software is a race to feel instant. Health is one of the few places where that instinct should be resisted, and where the honest thing is often to take longer and say why.
What the time is spent on
Reading a clinical document properly is not a single step. The page has to be read as an image, which is rarely a clean scan. The values have to be separated from the ranges beside them. The document has to be identified for what it is, because a prescription and a blood panel are different objects. And then the explanation has to be produced in the language the person asked in.
Each of those can be made faster by being made shallower. The visible result of doing so is an answer that arrives sooner and is wrong in ways the reader cannot detect.
The part that is genuinely unacceptable
Taking a moment is fine. Taking a moment and showing nothing is not. A screen that sits blank while something happens invisibly is where people decide a product is broken and close it — and in our own testing that is exactly what happened before we fixed it.
So the wait is explicit. The system shows that it is working, and the thing that indicates progress is honest about what stage it has reached.
Where we do optimise hard
- Everything that is not the reading. Opening the app, moving between screens, returning to a document you have already read.
- Answers that are already known. Re-reading a report you have read before should not cost you the wait, or the credit, a second time.
- The first useful thing on screen. Partial understanding early beats a complete answer that arrives all at once at the end.
Fast where speed is free. Careful where it is not.
This article explains how our technology works. It is health information, not medical advice.