Guides11 articles · 6 topics
Honest guides to tracking symptoms.
Short, sourced answers to the questions people actually search: how to keep a record, when a pattern means something, how to describe where it hurts, how to make an appointment count. Written to be read on a bad day, and to be quoted correctly.
How these guides are written. The answer comes first, in two or three sentences. Detail follows under the questions you would ask next. Every guide lists its sources, names its author and, once one has read it, its clinical reviewer, and carries its last-updated date. None of them diagnoses, predicts or treats anything: they describe how to keep a good record and how to read it without fooling yourself.
01Tracking symptoms well
3 guides
How do you keep a record that is worth the effort on a bad day?
- How do you keep a symptom diary that actually helps? Keep it fast, fixed and in the moment. Decide on two or three measures per symptom (for example intensity on a 0–10 scale, duration, and where), log at the time rather than from memory at night, and keep going for at least four weeks before you expect it to tell you anything. A diary that takes thirty seconds and gets filled in beats a thorough one that gets abandoned.
- How do you rate pain on a 0 to 10 scale consistently? Tie the numbers to function, not to feeling. Decide once what a 3, a 6 and a 9 mean for you in terms of what you can still do (“notice it”, “have to stop”, “cannot do anything else”), rate the pain at the moment you log rather than the whole day, and never change the anchors mid-record. Consistency across months matters more than whether your 6 equals someone else’s 6.
- What should you write down about a symptom? Record five things: when it started and ended, how bad it was on a fixed scale, where it was, what it felt like in a word or two, and the plain facts around it such as sleep, medication or cycle day. Leave out interpretation. “Headache 6/10, left temple, 14:00 to 17:30, after 5 h sleep” is worth more than a paragraph about why you think it happened.
02Patterns and triggers
2 guides
When does a run of entries actually mean something?
- How long do you need to track before a pattern means anything? About a month for counts and averages, and closer to two months before a link between a symptom and something else (sleep, weather, a food) deserves much trust. Shorter records are dominated by day-to-day noise and by the sheer number of things that could be compared. Until then, treat anything that looks like a pattern as a hypothesis to keep watching, not a finding.
- Is a trigger the same as a cause? No. In a symptom record, a “trigger” is something that tends to happen before or alongside a symptom. That is an association. A cause is a claim that changing the one thing would change the other, which a diary cannot prove on its own. Some famous triggers turn out to be early symptoms in disguise, some are coincidences that repeat, and a few are real. Treat each as a hypothesis, and be most suspicious of the ones that feel obvious.
03Where it hurts
1 guide
How do you describe a location so it survives the telling?
04Doctor visits
2 guides
How do you turn a record into a better appointment?
- How do you prepare for a doctor’s appointment about a chronic symptom? Prepare three things: a one-page summary of the record (how often, how bad, where, since when, what you tried), the single question you most need answered, and a list of everything you take. Lead with the question, hand over the summary, and before you leave repeat back what happens next. A tired memory is worst at exactly the facts an appointment runs on, so write them down.
- What does a doctor want to see in a symptom report? Counts over a defined period: how many days, how bad on average and at worst, where, when it started and how it has changed, what else was going on, and what you tried with what effect. One page, numbers first, charts only where they add something. Long narratives, screenshots of every entry and confident claims about causes slow a short appointment down.
05Privacy and your data
2 guides
What happens to health data in an app, and how can you tell?
- Is a symptom tracker app private? How can you tell? Not by default. Most symptom and period trackers are consumer apps, not medical providers, so laws like HIPAA do not apply to them, and many send data to their own servers and to analytics or advertising partners. You can tell in ten minutes: check whether it needs an account, whether it has a server at all, what its App Store privacy label lists, whether the policy names third-party SDKs, and whether you can export and delete everything. An app that keeps data only on your device has the fewest ways to go wrong.
- What happens to your Apple Health data when an app reads it? Apple Health is a database on your iPhone, not a cloud service, and an app can read from it only after you grant access for each category. Once it has read, the data is the app’s to handle under its own privacy policy, within Apple’s rules: it may not be sold, used for advertising or passed to data brokers. So the question to ask is not “is Health safe?” but “what does this app do with what it read?” You can review and revoke every permission in Settings.
06Bad days and accessibility
1 guide