When isolated events become a pattern.
Claes Parflo
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.
For several years after the initial investigation, nothing changed. Structural findings remained stable. Sport continued. There was no reason to think the situation was developing into anything significant.
Then, during a routine follow-up in late 2024, a 24-hour monitor detected abnormal rhythm patterns. Not a crisis — but enough to prompt the start of a medication to help stabilise heart rhythm.
A few months later, on 10 March 2025, a confirmed atrial fibrillation episode occurred. Emergency department, medication attempted, electrical cardioversion to restore normal rhythm. Procedure worked. Normal rhythm restored the same day.
That might have been the end of it. But the episodes returned. Then returned again. In total, around thirty episodes over the following year. Most were manageable with a pill-in-the-pocket medication strategy. Episode duration ranged from roughly one hour to fourteen hours.
The practical problem, more than the episodes themselves, was sleep. Waking up with an irregular heart rate and being unable to return to sleep — repeatedly, over many months — is a different kind of difficulty than any single acute event. It accumulates.
At some point it became clear that this was no longer a series of isolated events. It was a pattern. And patterns require a different response than events.
Cardiology has a phrase for this dynamic: "AF begets AF." Once a system starts drifting toward rhythm instability, future episodes become more likely rather than less. The situation had a trajectory, and the trajectory was not resolving on its own.
That recognition led directly to the next phase — and to a more deliberate approach to understanding what the data was actually showing.
From Signal to System