You've had a rough week, so you open the heart-rate graph on your Apple Watch hoping it will explain what happened. Instead, you see a line that rises, drops, and rises again. You remember feeling dizzy after a shower, shaky while standing in the kitchen, and exhausted after a short walk, but the graph doesn't connect any of those moments to the numbers. It gives you data, not a story.
That's the central problem with heart rate trends. A watch can collect useful measurements, but a raw graph usually can't tell you whether a reading happened while you were asleep, seated, standing, exercising, recovering, dehydrated, or symptomatic. For POTS and dysautonomia, that context isn't a nice extra. It determines what the reading means.
When Your Watch Graph Stops Making Sense
The red line looks dramatic because it removes the details you need. A heart rate of 110 beats per minute might reflect a brisk walk, a stressful conversation, a shower, a postural change, or an autonomic episode. The number is identical, but the physiological question is different each time.
That's why many people with POTS feel overwhelmed during their first weeks of watch data. They've collected more information than ever, yet they still can't answer the questions a clinician needs answered: How often did the episodes occur? How long did they last? Did they begin after standing? Were symptoms present? Did the heart rate settle after rest?
The number needs a setting
Think of a watch reading as a sentence with missing words. “My heart rate rose” isn't enough. You need the surrounding verbs and circumstances: I stood up, I was walking, I had just eaten, I was asleep, or I felt lightheaded.
The same principle applies to resting heart rate. A measurement taken during sleep may differ from one taken during sedentary waking time. A 2025 longitudinal study of consumer-wearable data reported resting heart rates of 56±7 bpm during sedentary periods and 54±7 bpm during sleep, showing that a person's apparent baseline can shift with measurement context rather than disease alone. The study is described in research on context-aware resting-heart-rate interpretation.
Practical rule: Before asking whether a heart rate is abnormal, ask where, when, and during what activity it was measured.
The useful mental model isn't “my watch caught a high number.” It's “my watch recorded a possible episode under particular conditions.” From there, you can separate long-term baseline changes from short-term events, apply sensible exclusions, and create a record that a clinician can review.
What Heart Rate Trends Actually Mean
Heart rate trends have two layers. The first is your long-term baseline, the range your body usually occupies across weeks and months. The second is the short-term episode, a temporary rise or drop that stands out against that personal pattern.
A weather analogy helps. Your baseline is the climate of a place. It describes what usually happens across a season. An episode is a storm warning. It marks a distinct event that deserves attention because it differs from the surrounding conditions. One warm afternoon doesn't redefine the climate, just as one higher reading rarely defines your cardiovascular pattern.
Start with the baseline
A baseline isn't a universal “normal” number. A large longitudinal study from Norway's Tromsø Study followed 30,699 adults aged 30 to 89 across four survey waves from 1986 to 2007. Age-adjusted mean resting heart rate fell from 73.4 to 64.7 bpm in men and from 78.3 to 66.4 bpm in women, with the decline persisting across age groups and birth cohorts. The historical finding appears in the Tromsø Study report on population heart-rate trends.
That matters because a baseline reflects more than an individual's current fitness. Age, era, population context, sleep, illness, medication, and measurement conditions can all influence it. Longitudinal tracking is therefore more informative than comparing your number with somebody else's.
Then classify the episode
A useful trend record separates at least three contexts:
- Resting trends: Readings during sleep or quiet sedentary time, useful for following your personal background pattern.
- Orthostatic trends: Changes associated with moving from lying or sitting to standing, especially relevant to POTS and dysautonomia.
- Exertional trends: Changes during exercise, walking, or recovery, which shouldn't automatically be treated as orthostatic events.
A heart rate of 110 bpm during a workout is not equivalent to 110 bpm after standing still. Before interpreting any spike, label the activity state and posture as accurately as you can. A context-aware approach to health-trend analysis makes that distinction central rather than leaving it buried beneath a daily average.
Why POTS Detection Needs a 30+ bpm Rule
POTS detection becomes more useful when it follows a stated clinical criterion instead of a vague alert such as “your heart rate looks high.” The commonly used adult criterion is a sustained heart-rate increase of at least 30 beats per minute within 10 minutes of standing, without an orthostatic blood-pressure drop. For adolescents, the threshold is over 40 bpm.
This threshold isn't a claim that every qualifying episode proves POTS. Diagnosis still requires clinical assessment, consideration of symptoms, blood pressure, medications, other conditions, and appropriate testing. The value of the rule is that it gives patients and clinicians a repeatable way to identify which posture-linked events deserve review.
What the rise tells you
Suppose your resting or pre-standing heart rate is 68 bpm and your heart rate reaches 101 bpm after standing. That's a rise of 33 bpm. The important information isn't just the peak. It's the starting point, the size of the increase, how long it stays high, the posture trigger, and what you felt at the time.
A smaller rise may still matter if it's consistent and symptomatic. A larger or longer-lasting rise may provide a stronger reason for a clinician to investigate orthostatic intolerance, but the watch record can't establish the diagnosis by itself. The algorithm's job is narrower: identify and organize repeatable patterns for discussion.
| Population | Sustained HR Rise | Time Window | Posture Trigger |
|---|---|---|---|
| Adults | At least 30 bpm | Within 10 minutes of standing | Standing |
| Adolescents | Over 40 bpm | Within 10 minutes of standing | Standing |
The criterion becomes especially valuable when paired with exclusion rules. Exercise, cool-down, and recovery can produce legitimate heart-rate changes that resemble an episode. Removing those periods helps keep the episode count focused on events that may relate to posture or autonomic regulation.
Weekly reporting adds another layer. Instead of handing a clinician a collection of isolated spikes, you can show whether qualifying events recur at particular times, whether symptoms accompany them, and whether the pattern persists. That turns a subjective hunch into a reproducible observation, while still leaving diagnosis where it belongs, with a qualified healthcare professional.
Four Pitfalls of Reading Raw Watch Data
The native heart-rate graph is useful for viewing measurements, but it isn't a complete interpretation system. Raw watch data can mislead you when it lacks activity labels, posture information, symptom notes, or a long enough time window.
1. Workouts distort the background
Exercise raises heart rate by design. If workout periods and recovery windows remain mixed into a general average, the result may look like a change in resting behavior when it's really a change in activity.
Habit: Review resting patterns separately from exercise and recovery. Don't use a day containing unusual exertion to redefine your baseline.
2. A spike without symptoms is incomplete
A graph can show when the heart rate rose, but it usually can't tell you whether you felt dizzy, short of breath, weak, nauseated, foggy, or aware of strong palpitations. Without that information, you and your clinician can't easily distinguish a noticeable episode from an incidental measurement.
Habit: Add a brief note when an event occurs. Record what you felt, what you were doing, whether you had recently eaten or showered, and whether you'd taken medication or increased fluids.
3. Posture disappears from the graph
Seated readings may look ordinary while standing produces the change that matters. If the watch output doesn't preserve posture or a clear transition into standing, a POTS-relevant pattern can vanish inside a smooth-looking daily line.
Habit: Mark posture changes during episodes, especially when symptoms begin after standing. The timestamp matters because it lets a clinician compare the change with the surrounding heart-rate sequence.
4. Daily averages flatten the meaningful moments
A daily average can hide repeated short episodes, a prolonged morning rise, or a pattern that appears only after meals. It compresses a variable day into one number, which makes it easy to overlook distribution, peaks, duration, and recovery.
Habit: Look for recurrence and timing instead of chasing the highest isolated reading. A false-positive reduction framework is useful because it encourages you to ask which events should be excluded before counting them.
A clean-looking average can hide a difficult day. The pattern inside the average is where the clinical questions usually begin.
How Cardiogram Turns Episodes Into a Story
Cardiogram is designed to organize Apple Health heart-rate data around episodes, context, and reports. The important part isn't just the finished chart. It's the sequence of decisions that determines which measurements become part of the story.
Step 1, collect the background signal
The process begins with background heart-rate data from an existing Apple Watch. The app uses read-only HealthKit access, so it can analyze the available record without requiring another sensor or wearable. This creates the raw timeline needed to compare a possible event with the person's preceding baseline.
Step 2, identify a qualifying rise
The episode detector looks for a 30+ bpm increase within 5 minutes, then records the baseline, peak, sustained duration, and time of occurrence. This is a detection rule, not a diagnosis. It gives the user a consistent filter for finding events that may be relevant to orthostatic intolerance.
The detector also excludes workouts and recovery periods from episode counts. That matters because exercise-related increases are expected and shouldn't automatically inflate a list of suspected autonomic episodes.
Step 3, attach the missing context
A heart-rate event becomes more interpretable when the surrounding details travel with it. Users can link symptoms and possible triggers such as dizziness, palpitations, fatigue, brain fog, hydration, salt intake, sleep, and medications to individual episodes.
This doesn't turn a journal entry into proof of cause. It creates a timestamped record that lets you ask better questions. For example, you may notice that symptoms repeatedly appear after standing in the morning, after a shower, or when hydration has been poor.
Step 4, summarize the week
Weekly summaries gather episode frequency, duration, peak heart rate, timing, and symptom correlations. Heatmaps help show whether events cluster on particular days or periods rather than appearing randomly.
The weekly view also protects you from overreacting to one dramatic minute. A single high reading may be unimportant, while a recurring pattern with similar posture and symptoms deserves a conversation with your care team.
Step 5, prepare the appointment report
The exportable PDF states the detection criterion and presents timestamped episodes alongside trends and logged context. That format is easier to review during an appointment than a series of screenshots, because it shows the rule used to select events and the information attached to each one.
The purpose of a report isn't to diagnose yourself. It's to arrive with a clearer timeline than “sometimes my heart races.”
Cardiogram Compared to the Native Health App
The native Apple Health heart-rate view and Cardiogram serve different purposes. Apple Health provides access to the underlying measurements and a broad timeline. Cardiogram adds a layer for episode detection, exclusions, context logging, longitudinal summaries, and PDF reporting.
That difference matters for POTS conversations. A raw line graph can show that the heart rate changed. A structured report can help show whether the change met a stated rule, whether it happened outside exercise, and whether symptoms or posture were recorded at the same time.
| Capability | Apple Health | Cardiogram |
|---|---|---|
| Episode detection | Displays heart-rate measurements in a timeline | Detects 30+ bpm rises within 5 minutes and records episode details |
| Workout and recovery exclusions | Includes available heart-rate data without the described POTS-specific episode filter | Excludes workouts and recovery periods from episode counts |
| Symptom and trigger logging | Requires separate user notes or another tracking method | Links symptoms and triggers to detected episodes |
| Longitudinal review | Provides health history and available trend views | Adds weekly summaries, resting trends, and episode heatmaps |
| Clinician-ready output | Users may need to assemble screenshots or notes | Produces an exportable PDF with the stated detection criterion and episode context |
The distinction isn't that one view is useful and the other isn't. The native view is valuable when you need to inspect the original measurements. Cardiogram is designed for the next question, which is what those measurements mean when organized around potential episodes.
Its Apple Health integration uses existing watch data rather than requiring additional hardware. That can reduce friction during the first stage of monitoring, when the priority is building a consistent record instead of changing your entire routine.
A Weekly Routine That Actually Helps
A useful monitoring routine should be small enough to repeat. The aim isn't to study every minute of every day. It's to create a steady record that preserves context and gives your clinician something organized to evaluate.
Sunday evening, review the shape
Look at the weekly heatmap and episode feed. Notice recurring timing, duration, symptoms, and posture notes. Don't let one isolated outlier dominate the review, especially if it occurred during motion or came from a low-confidence measurement.
Monday morning, check the baseline
Review your resting pattern before interpreting the day's activity. If your heart rate is already high during quiet time, note it without assuming a cause. The question is whether the pattern persists and whether it appears in the same context on other days.
Mid-week, complete the missing tags
Open detected episodes and add the details you remember:
- Symptoms: Record dizziness, palpitations, fatigue, brain fog, or other sensations.
- Posture: Note whether you were lying down, seated, or standing.
- Triggers: Add information about meals, showers, hydration, salt intake, sleep, and medication.
- Activity: Confirm whether the event was ordinary movement, exercise, or recovery.
Friday, prepare the report
Export the weekly PDF if you have an appointment coming up. Bring the report, your timestamped symptom notes, and a short list of questions such as whether the pattern warrants orthostatic vital signs or further autonomic evaluation.
Recurring post-meal or post-shower episodes, or sustained morning tachycardia before standing, are more useful discussion points than a single surprising minute. Consistency beats intensity. Even a brief weekly review is more valuable than collecting a month of raw data and trying to reconstruct it later.
Practical Questions Before Your First Appointment
Privacy is a reasonable first question. Cardiogram's stated design processes data on device, uses read-only HealthKit access, and syncs through the user's iCloud account rather than relying on server-side storage. Review the app's current privacy information and permissions before enabling access, and export only what you choose to share.
Setup should be straightforward:
- Allow Apple Health access: Grant read-only permission for the heart-rate data you want analyzed.
- Enable notifications if desired: This allows phone alerts for detected events.
- Turn on symptom tags: Choose the symptoms and triggers you want available during review.
- Let the history populate: Existing Apple Watch data can provide an initial timeline, while ongoing wear creates a more useful longitudinal record.
Pricing uses a single membership with a 3-day free trial and an annual plan, and United States pricing may differ from local App Store pricing by region. Check the current in-app offer before subscribing, then confirm what the membership includes, particularly episode exports and clinician-ready PDF reports.
Before your first cardiology appointment, bring only the material that helps a clinician reason clearly:
- The PDF: Use the report that states the detection criterion and timestamps.
- A two-sentence symptom summary: Explain what you feel, when it happens, and whether standing appears to trigger it.
- Your medication list: Include prescribed medicines, over-the-counter products, and relevant supplements.
If POTS remains suspected, ask whether orthostatic evaluation or a head-up tilt-table test is appropriate. Don't rely on screenshots of raw watch graphs that lack posture, exclusions, symptom notes, and the 30+ bpm detection annotation. Your watch can help document a pattern, but your clinician must interpret it in the context of your history and examination.
Cardiogram organizes Apple Watch heart-rate data into context-aware episodes, weekly trends, and clinician-ready PDF summaries for POTS and dysautonomia conversations. Visit Cardiogram to review how the app can help you replace confusing graphs with a clearer timeline to discuss at your next appointment.
