Example output
Sample Migraine Pattern Report
This is what a Migraine Detective pattern report actually looks like. Thirty days of tracked context (sleep, food, hydration, hormones, stress, weather, attacks) turned into a structured analysis you can take to your clinician. The full PDF is embedded below.
What's inside: an attack timeline with co-occurring context, the pattern signals the system identified across the 30-day window, the layer breakdown (hormonal, histamine, vascular, threshold load), and a prioritized list of hypotheses worth investigating. Reports are generated automatically from your daily notes once you've tracked for at least three weeks.
The other honest outcome
When the answer is "no clear pattern yet"
Not every investigation finds a dominant pattern on the first pass. When the data doesn't support a conclusion, the report says so instead of inventing one. This is what that conclusion looks like:
Conclusion: no clear pattern yet
"Across this tracking window, no single layer rises consistently before your attacks. That is real information: it usually means the window is too short, a key data stream is missing (most often labs or cycle timing), or the driver lives in something not yet tracked. It does not mean nothing is going on."
"Recommended next step: continue tracking for two to three more weeks with sleep timing and hydration logged daily, and bring the Baseline Test List to your next appointment so the missing lab context can be filled in."
An investigation that can come up empty is the only kind worth trusting. If a report ever told everyone they had a pattern, it would be telling no one anything.