← All ideas IDEA-106 6.5 us health-companion developed

Walk into your pain specialist with a one-page record: what you tried, when it started working, when it stopped, and what side-effects hit — so the next 15 minutes are about what's next, not what you forgot.

Problem

Chronic-pain patients (fibromyalgia, MS, post-injury, neuropathy) cycle through dozens of medications over years and remember almost nothing accurately at 15-minute follow-up visits. Without a structured log of 'medication name + onset time + duration of relief + side-effects', the pain specialist re-tries failed regimens and patients lose months. Paper diaries collapse during flares; Excel spreadsheets are useless to bring to the clinic.

Audience

US adults 30-65 with chronic pain (fibromyalgia, arthritis, MS, post-injury, neuropathy), often working with a pain-management specialist or rheumatologist on multi-decade journeys, frustrated by 15-minute appointments where they can't summarize 6 months of trials

Reasoning

Source signals

SIG-20260426-us-health-companion-chronic-pain-medication-effectiveness-tracking: "measure how long each dose provides coverage"

What we ship

**Core features (MVP)**

**Pain score quick log**: tap → 0-10 intensity + location (body-map tap) + 5-second voice note. <20 seconds per entry.
**Medication trial log**: user enters their taken medications (NOT from a drug database — we do NOT suggest medications). Each intake — log with timestamp + dose. After 30/60/90 min — push "did it help? 0-10". User-reported effectiveness, never our assessment.
**Side-effect tracker**: checkboxes (drowsiness, nausea, headache, brain-fog, mood changes) — after each med entry.
**Trial summary report**: weekly — "med X over 14 doses: avg onset 47 min, avg duration 4.2h, avg effectiveness 6.3, side-effects in 9/14 doses". Pure statistics over user-supplied data.
**Auto context**: weather (barometric), sleep (Apple Health), activity level — overlaid on pain log.
**Specialist PDF (Pro)**: 1 click → 1-page PDF: medications tried (with onset/duration/effectiveness/side-effects each), pain trends over period, weather/sleep correlates. Ready for the appointment.
**Anti-features (critical)**: do NOT suggest "switch to X medication" (RD/MD territory), do NOT diagnose pain syndrome, do NOT make cure claims, do NOT integrate with pharmacy for refills (avoid PHI/HIPAA gray zone).

**Primary user flow**

1. Signup, pick: "fibromyalgia / arthritis / MS / post-injury / neuropathy / mixed". UI adapts.

2. 3-min onboarding: optional Apple Health pair, enter currently-taken medications manually (free text, not from drug DB).

3. Daily use: pain score log + voice note. Med intake → tap "took med X" → push 45 min later "did it help?".

4. Every 4-6 weeks — generate specialist PDF before follow-up visit.

5. Free: 30 days history + basic pain log. Pro $9.99/mo or $79/yr: unlimited history, medication trial reports, specialist PDF, weather/sleep correlates.

**What it looks like**

**Landing**: "Don't lose 6 months remembering what you tried." hero. Side-by-side: messy Notes app vs our PDF.
**Main app screen**: pain score timeline (last 14 days) with color scale; quick-add buttons (pain log / med taken / side effect).
**Specialist PDF**: top — pain timeline + weather overlay; middle — medication trial table (med / period tried / avg effectiveness / side-effect rate); bottom — current regimen.

**MVP build plan (11 days)**

Day 1-3: Postgres schema (pain_logs, medications, intakes, side_effects, weather_snapshots), FastAPI, Stripe.
Day 4-5: voice→structured-log Claude prompt (user-stated facts only, never recommendations).
Day 6-7: medication trial summary statistics (avg onset, duration, effectiveness — simple arithmetic).
Day 8-9: PDF generator (timeline + table, weather overlay).
Day 10: paywall, polish, audit copy for anti-prescription framing.
Day 11: landing, deploy, launch on r/ChronicPain / r/Fibromyalgia.

Reasoning

Pain from SIG-chronic-pain-medication-effectiveness-tracking is captured: pain specialists themselves say "patients who bring structured tracking data have more productive visits" — this isn't just a patient pain, it's a professional ask. Existing apps (Bearable, Manage My Pain, Palina, ChronicallyGina, PainClinics.com) are either general-tracking, or have weak medication-trial features, or overloaded UX. Our wedge: focused medication-trial log + onset/duration/effectiveness tracking + specialist PDF — not a diary or all-in-one, but specifically a visit-prep tool. Regulatory-safe: do NOT suggest "switch to X" (CRITICAL — would be FDA medication-advice territory), do NOT integrate with a drug DB (further from FDA), do NOT prescribe dose changes — we only collect what the user took and how they rated effectiveness. Lesson from IDEA-047: AI is used ONLY for voice note → structured user-stated fact conversion (med name, dose, effectiveness rating — user's own words, not AI assessment). No "based on your data, consider X" — that would be a red flag. The PDF is formatted rendering of user's own data, not interpretation. One specific design choice: medication name is a text input, we do NOT autocomplete from a drug database (slightly worse UX but removes FDA-relevant ambiguity about whether the app "knows" about specific drugs).

Quick competitive read

**Bearable** — general chronic-illness tracker, has medication tracking, but weak specialist PDF.
**Manage My Pain** — older player, dated UX, weak voice/AI.
**Palina (ClarityDTX)** — pain + sleep tracking, not focused on medication trials.
**ChronicallyGina** — community + lite tracking.
**PainClinics.com Excel templates** — DIY level, zero automation.
**CareClinic** — health journal, not pain-focused.
**White space**: medium. Focused medication-trial log + visit-prep PDF — nobody offers this as a core wedge. Most are general health journals. Score hint: competitive_pressure 5-6.

Initial pricing hypothesis

Free: 30 days history + basic pain log. Pro: $9.99/mo or $79/yr — unlimited history, medication trial reports, specialist PDF, weather/sleep correlates, body-map. WTP is high: pain-management specialists cost $200-400/visit, one saved month on a failed regimen pays back a year of Pro.

Distribution hypothesis

1) **r/ChronicPain (290K+) + r/Fibromyalgia (105K+) + r/MultipleSclerosis (75K+)** — solo-dev "Built this because I couldn't remember if amitriptyline worked at my last visit. One-page PDF, your pain specialist will thank you." Authenticity-driven.

2) **American Chronic Pain Association partnership** — outreach to ACPA for free 6-month Pro for members in exchange for newsletter mention.

3) **Pain-specialist clinic outreach** — 50 small private pain-management practices with free Pro for practice manager + patient flyer (waiting-room QR).

Source signals (2)

SIG-20260426-us-health-companion-chronic-pain-medication-effectiveness-tracking:
SIG-chronic-pain-medication-effectiveness-tracking

Score breakdown

market_size	6/10
pain_severity	6/10
build_feasibility	6/10
speed_to_revenue	7/10
regulatory_safety	5/10
competitive_pressure	9/10
recurring_revenue_fit	8/10

MVP stack

frontend	Cloudflare Pages + React + Tailwind
backend	Railway + FastAPI + Postgres
ai	Claude Sonnet 4.6 ONLY for converting voice notes into structured medication log entries (med name + dose + onset time + effectiveness 0-10 — user-provided facts, never recommendations)
payments	Stripe Subscriptions
storage	Postgres + R2 (PDF exports)
external_integrations	['Apple HealthKit (read-only sleep + activity if user opts in)', 'OpenWeather (pain often weather-correlated)', 'Stripe']

Estimated build: 11 days

Regulatory

soft_block

Blocks: D-006

SaMD-creep risk (D-006 soft) — well-mitigated by deliberate design choices. AI is used only for voice notes → structured medication log entries (med name + dose + onset time + effectiveness rating — user-stated facts only). Reasoning explicitly says "no 'switch to X medication' suggestions" (which would be FDA medication-advice territory) AND "do NOT integrate with drug DB" (deliberate UX-degradation to remove FDA-relevant ambiguity about whether the app "knows" about specific drugs). This is the strongest IDEA-047 lesson application in the batch — deliberate friction to stay clearly outside SaMD scope. Trial summary statistics (avg onset, duration, effectiveness, side-effects rate) are arithmetic over user-supplied data, not clinical assessment. Specialist PDF must remain "user-supplied medication trial log, formatted for clinician review", never "evidence that medication X failed" or "you should try Y" — same surface-area risk as IDEAs 099/101/105 PDFs. US regional advisory: HIPAA does NOT apply (B2C, no provider relationship). NO pharmacy integration / NO refill flow is a deliberate avoidance of HIPAA gray-zone (correct — pharmacy flows would invoke 42 CFR Part 2 substance-use-disorder data plus state pharmacy-board scrutiny). WA MHMDA: chronic-pain symptom data + medication-effectiveness data are "consumer health data" — opt-in consent + sale-prohibition default + consumer-rights mechanism. Controlled-substance angle: opioids are common in chronic pain — even though we don't integrate with drug DB, voice transcripts WILL contain mentions of Schedule II/III drugs (oxycodone, hydrocodone, gabapentin, tramadol). The data itself is sensitive but not regulated as PHI without provider context; however storage encryption + breach notification (FTC HBNR) become more important. For DEA-relevant misuse risk: copy must NEVER frame the app as helping users "find the right dose" or "manage opioid use" — that would invoke FDA + DEA scrutiny. Stay strictly in "log of what the patient took and how they rated it". BUILD RECOMMENDED with strict guardrails: (1) onboarding disclaimer "this app does not recommend, prescribe, or change medication doses — it logs what you took and how you rated it; only your prescriber can change a regimen"; (2) maintain deliberate non-integration with drug databases (text-input only); (3) WA MHMDA-compliant consent + medication-data opt-in; (4) audit copy for any "switch to X" or "consider Y" patterns before launch; (5) specialist PDF watermark "user-supplied medication trial log, not a clinical assessment"; (6) encrypted-at-rest storage + breach plan (FTC HBNR ready); (7) NO pharmacy refill flow (already in spec); (8) audit voice transcripts for opioid-use-misframing if any AI-generated summary is added later (currently only AI-extracted user-stated facts — keep that boundary).

Competitors (0)

No competitors profiled yet.