The value of a baseline you don't know you need yet.

This is a personal account of one person's experience tracking health data through a health event. It is not medical advice, and it does not describe what any app or device can do for you. Individual experiences vary.

A few days after the unusual reading, I went through a full cardiac work-up: ECG, treadmill stress test, 24-hour Holter monitoring, and a cardiac ultrasound.

The most informative turned out to be the ultrasound.

It revealed a set of structural characteristics — mild left ventricular enlargement, an enlarged left atrium, and a mitral valve prolapse — that weren't causing immediate problems but were worth knowing about. No diagnosis of arrhythmia at this stage. No urgent intervention required.

What it established was something less dramatic but more useful: a baseline.

In engineering terms, this is the difference between event-level analysis and system-level understanding. The wearable had produced a signal. The investigation revealed the underlying structure that gave that signal context.

At the time, it felt like a dead end. The tests came back, the findings were explained, and life continued entirely normally. Work, sport, travel — nothing changed. For several years, nothing suggested that the structural findings were relevant in any active sense.

But they were documented. And when the situation changed later, having that baseline made it possible to understand what had shifted and by how much. Without it, the later picture would have been much harder to interpret.

The value of establishing a baseline is rarely obvious at the time. It becomes obvious later, when you need to assess change and have nothing to measure against.