Symptovue starts with active pain logging, then adds optional context and careful pattern summaries that can become low-risk experiments and better appointment conversations.
In the last 45 days, headache logs tended to be lower after yoga or mobility sessions. This is based on 6 sessions, so read it as a pattern to test, not proof of cause.
Capture where it hurts, intensity, timing, sensation, and what you tried without rebuilding the whole day from memory.
Planned sources include HealthKit, Mac work-session aggregates, and later platform-dependent phone and posture check-ins.
Insight cards show the time window, sample size, confidence, and competing explanations.
Turn a pattern into a low-risk behavior test, such as a short break habit or evening mobility routine.
Export an appointment-ready report with trends, body-map heat, interventions, goals, and questions.
No keystrokes, screenshots, URLs, window titles, clipboard, or screen content.
Optional context
The Mac companion is planned first because it can capture derived workday aggregates cleanly. Windows is fast-follow; phone context is platform-dependent; iPhone support is coarse daily bands rather than exact minutes.
Own-data visualization
The chart starts with committed pain, PROMIS, PSFS, and intervention entries. Premium overlays are aligned to the engine's lag and labeled as association only.
Bounded chart views
Body-map views use avatar regions, while adverse-reaction charts show intervals, sample size, and lag without turning an association into a trigger or safety verdict.
Avatar regions only; user photos and local photo references are excluded from synced and exported charts.
A negative pattern is not proof of safety. This chart never diagnoses an allergy or intolerance.
Experiment loop
Recovery charts show uncertainty bands around associations. Experiment views compare baseline and intervention windows as self-observation, not treatment proof.
Slower recovery after high-slouch days · CI +0.4 to +2.1 days · n=7 · lag 1 day
Association with uncertainty band; does not show treatment efficacy or predict future recovery.
Baseline/intervention observations only; does not prove treatment efficacy.
Exploration boundary
User-driven exploration is separated from findings, labeled as hypotheses, and moves forward only by seeding a self-experiment.
Not corrected for multiple comparisons. Exploration never bypasses the AnalyticsEngine gate or safety post-filter.
Seed a self-experimentAppointment-ready
Reports are planned to summarize trends, maps, interventions, activity context, user goals, and questions while keeping medical-scope language clear.
May 1 - June 14
Neck, right shoulder, tension-type head pain.
What should I test before the next visit?
Pre-launch waitlist
Join for product updates and research invitations. The first release is being built, and concept visuals are labeled until real screenshots exist.