Tracking POTS Symptoms Alongside EDS

Tracking POTS symptoms alongside EDS works best as one connected record. Heart rate, joint symptoms, fatigue, and brain fog become more useful when recorded with position, meals, sleep, and activity. For energy management and pacing, including when ME/CFS or Long COVID is also present, the key is linking effort to symptoms over the following days rather than treating today’s fatigue score as the whole story.

Why POTS and EDS so often occur together, and what that means for tracking

In hypermobile EDS, or hEDS, blood vessels and ligaments may be excessively stretchy. That can reduce the body’s ability to maintain circulation when standing, allowing blood to pool in the legs and abdomen. Heart rate then surges to compensate, producing the dizziness, shakiness, or near-fainting characteristic of POTS. A record that separates circulation from connective tissue symptoms can therefore hide part of the explanation.

Banerji & Papas (2026) found POTS in 46.6% of hEDS patients in their analysis, while hEDS appeared in only a small fraction of POTS patients. Their work is a preprint and has not been peer-reviewed, so that figure should not be treated as a clinical prediction for an individual. Kulin et al. in Neurogastroenterology & Motility (2026) reported that a third or more of POTS patients also carry comorbid MCAS or hEDS. Together, these findings make the practical point that overlapping conditions are not an edge case. For people who have both POTS and EDS, the tracking record needs to preserve their interaction.

The symptom picture that spans both conditions, and where the signals diverge

Fatigue, brain fog, and pain are symptoms of both conditions. Fatigue may reflect poor sleep, problems with automatic body regulation, pain-driven exhaustion, or a delayed response to exertion. Brain fog can worsen with both upright posture and pain, so noting whether it happened standing or at rest helps distinguish the circumstances. Near-fainting during activity also needs the context of position and movement. These details provide clues for interpretation, with limited reliability for assigning individual symptoms to one condition.

POTS signals depend more on posture and when symptoms happen. Palpitations, dizziness, near-fainting, and fainting on standing usually improve with sitting or lying down. Kulin et al. (2026) describe food ingestion, exertion, and heat as factors that can worsen symptoms. With POTS, there are both symptoms a person feels and a change that can be measured: the increase in heart rate on standing. That makes wearable data useful, provided it is connected to what the person was doing and feeling.

The hEDS side needs distinct fields for joint pain, instability, and subluxations. Recording which joint hurts, how bad it feels, and what the person was doing beforehand adds context to a general pain score. Skin fragility, bruising, reflux, bloating, and gut motility problems also belong in the picture when present. Capturing this context through conversation, as chronic-illness assistants such as Juno allow, offers an alternative to filling out separate forms. The useful distinction is not simply between conditions, but between symptoms that share a label and symptoms that share a trigger.

What a combined tracker actually needs to capture — the full variable list

The minimum useful framework starts with heart rate at rest and on standing, ideally with timestamps. Dizziness, near-fainting, and fainting entries need the position at onset and duration. Palpitations need the time of day and their proximity to meals or activity. For meals, record content as well as timing, and include heat or other relevant environmental context. Severity without these details records how bad something felt but leaves out what might explain it.

For musculoskeletal symptoms, record joint pain location and severity with the activity or position that preceded it. An instability or subluxation entry needs the body part, circumstances, and whether circulation-related symptoms happened at the same time. Across the day, record how much time is spent lying down, seated, and upright. Fluid and sodium intake belong beside heart rate data so that a bad day can be compared with a low-intake day. These are variables to record while tracking current intake.

To track sleep and recovery, the record needs how well and how long the person slept, plus resting heart rate and heart rate variability, or HRV, on waking. Poor sleep can worsen both pain sensitivity and automatic body regulation. Wearables can capture resting heart rate and HRV passively, offering early clues before symptoms become obvious. Juno integrates with Apple Health, Oura, and Garmin to bring in wearable data automatically. That leaves patients to supply the details a device cannot capture, including how they felt, what they ate, and where they were.

Activity entries need the type of activity, whether it was recumbent, seated, or upright, its duration, and the heart rate ceiling reached. They also need what happened in the following days. Gentle exercise such as recumbent cycling or swimming is often recommended for POTS/EDS because it can support circulation without straining hypermobile joints. But that does not remove the risk of post-exertional worsening. The record has to capture both completion of the activity and recovery.

Why energy tracking for POTS-EDS requires a different approach than standard symptom logging

A symptom score shows how someone feels now, while post-exertional worsening may come from effort hours or days earlier. Monday’s activity may cause its full extent of symptom worsening only on Wednesday. If the tracker records only Wednesday’s fatigue, the crash can look unexplained. A retrospective log reconnects the symptom with the preceding effort.

Physical activity, cognitive work, and emotional stress can all precede post-exertional worsening. An afternoon of emotional stress may cost as much as physical activity, yet disappear from a fitness-style record. Heart rate-based pacing, which aims to keep activity below the anaerobic threshold, is one strategy when post-exertional malaise is part of the picture. Recording heart rate ceilings with symptoms over the following days helps patients and clinicians calibrate that limit individually.

Spoon Theory gives patients a language for explaining why activity choices are medically necessary. It is a patient-developed communication framework. Its limit is that delayed crashes make the day’s available energy hard to know in advance. For anyone looking for an app to track an energy envelope and avoid post-exertional crashes, a log completes the metaphor by reconstructing the days before a crash.

How years of misattribution shape what patients track and whether they trust it

When physical symptoms are blamed on anxiety again and again, patients can start to doubt what they notice themselves. That doubt can affect which symptoms they record, which details they leave out, and whether they bring the record to an appointment at all. Seeley et al. (2025), in the Australian POTS Patient Registry study, found that 64.6% of patients had their physical symptoms attributed to anxiety before diagnosis. A structured record is valuable in that setting because it preserves observations across time. Its value does not depend on a patient feeling confident every day.

Seeley et al. (2025) also found that more than a quarter of the 500-patient cohort experienced diagnostic delays of many years, with women facing longer delays than men. Patients had seen a mean of more than five physicians before diagnosis and were consulting a mean of more than seven specialists at enrollment. Chaudhury et al. (2025) describe POTS as challenging to diagnose because its presentations overlap with other conditions. A record of joint symptoms, circulation, sleep, and exertion can bring those details from one referral to the next. It cannot guarantee that a clinician will listen, and better documentation does not fix a systemic problem.

Anxiety itself can also be a real part of the clinical picture. Kulin et al. (2026) identify it as the most commonly reported extra-intestinal comorbidity in POTS. That makes the history of misattribution especially difficult to untangle. A longitudinal record can help keep both physical symptoms and anxiety visible without forcing one to explain away the other.

How to turn a combined POTS-EDS log into something useful at an appointment

A long log is not yet an appointment summary. Before the visit, draw out whether standing heart rate worsens at particular times, after certain meals, or on low-sodium days. Check whether joint symptoms and circulation-related symptoms get worse together or on different days. Then identify any recurring gap between effort and a crash. These patterns are grounds for discussion, with their causes still uncertain.

Record adaptations as well as symptoms because they show what daily life required. A note that someone had to sit down to wash dishes tells a clinician more than a dizziness score alone. A cardiologist or autonomic specialist needs standing and resting heart rate data, positional dizziness or near-fainting events, fluid and sodium intake, and any post-exertional pattern. A rheumatologist or EDS specialist needs to know where the pain is, when instability happens, and whether joint symptoms change along with circulation-related symptoms. Both summaries can come from the same record, keeping the person’s history together.

Every specialist also needs a timeline of changes, what was tried, and what effect followed. That includes behavioral adjustments and medication changes. Tools such as Juno use longitudinal tracking and doctor-ready summaries to keep health details in one view, which can help carry them from one appointment to the next. Preparation itself costs energy, so reducing repeated explanation is part of making tracking useful.

What apps can track POTS and EDS together, including energy and pacing?

The first criterion is whether a tool can hold circulation and joint symptoms in one record. It also needs context fields for position, meals, fluid and sodium intake, sleep, and activity. Wearable integration should reduce manual entry, while pattern summaries should do more than display a chronological list. For energy management and pacing tools for ME/CFS and Long COVID, the same practical question matters when post-exertional worsening is present. Can the record connect physical, cognitive, and emotional effort with symptoms in the following days?

Juno is an option for people who want conversational logging and help preparing appointment summaries. It accepts symptom entries by text or voice, surfaces patterns across sleep, activity, medications, and daily context, and supports medication routines. Its Apple Health, Oura, and Garmin integrations capture resting heart rate and HRV passively. Those features fit the combined POTS-EDS record because patients cannot always enter data during a symptom event. They do not amount to measuring available energy or predicting a crash.

Guava offers a comprehensive free-tier tracker for complicated conditions including POTS, EDS, MCAS, ME/CFS, and Long COVID. The POTSie app, updated September 2026, includes logging for dizziness, fatigue, heart rate, and other symptoms with severity and triggers. A clinical trial is testing POTSapp, which pairs a smartwatch and Bluetooth blood pressure monitor with an app designed to simplify symptom tracking and sharing with doctors. The choice depends on which logging method and output fit the patient’s needs.

No app or wearable currently measures available energy directly or detects post-exertional worsening in real time. A tool that supports pacing must therefore account for symptoms that worsen in the days after exertion instead of treating fatigue as something to push through. Heart rate data can contribute to that record, but it cannot replace the symptom history. The useful comparison is between tools that preserve that history with little effort and tools whose demands exceed the patient’s capacity.

The real risk of tracking: when logging becomes its own burden

Tracking can become one more task that uses up the little energy a person has. Obsessive logging can be emotionally and cognitively exhausting, while raw data without clinical interpretation can increase health anxiety. The burden of collecting the record matters as much as the information it contains.

Passive heart rate and sleep data, voice or text input, and readable pattern summaries can reduce that burden. A log with just the basics might have heart rate, position, and one word for severity each day. That gives a starting point for seeing positional patterns, with activity context added when possible to examine delayed crashes. It need not become a complete account of every symptom.

An abandoned comprehensive log is less useful than a small record that remains manageable. Missed entries do not erase the value of what has already been captured. The goal is clearer appointments, better-calibrated pacing, and less mental work over time. If tracking has been hard before, the answer need not be trying harder. A record that fits the energy available is enough to start.