A

Polypharmacy Doctor Visit Question Generator

3.80

Derivation Chain

Step 1 Chronic disease polypharmacy management
→
Step 2 Drug interaction verification
→
Step 3 Not knowing what to ask the doctor after discovering interactions

Problem

Even when patients in their 50s+ are aware of potential drug interaction issues, they don't know how to ask their doctor 'Is this combination of medications safe?' During an average consultation of under 4 minutes, they don't know what information to present or in what order to help the doctor make a judgment. Most end up only saying 'I think I'm taking too many medications' and leave without any concrete action.

Solution

A web service where users input their current medication list and symptoms to (1) auto-generate a one-page 'My Medication Summary' (organized by hospital and active ingredient), (2) output 3-5 'items that need verification for this combination' categorized by medical specialty, and (3) provide a memo template for recording doctor's responses after the consultation.

Target: Ages 55-65, taking 7+ medications, chronic disease patients who struggle with doctor-patient communication during visits
Revenue Model: Question generation and medication summary are Free. Consultation record history management (6+ months) at 1,500 KRW/month (~$1.10/month). Pharmacist/nurse pre-consultation referral.
Ecosystem Role: Education
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
4.0/5
U Urgency
3.0/5
M Market
2.0/5
R Realizability
5.0/5
V Validation
3.0/5
NUMR-V Scoring System
N Novelty1-5How uncommon the service is in market context.
U Urgency1-5How urgently users need this problem solved now.
M Market1-5Market size and growth potential from proxy indicators.
R Realizability1-5Buildability for a small team with realistic constraints.
V Validation1-5Validation signal quality from competition and demand data.
Each dimension is scored 1-5 and weighted into grade S/A/B/C/D.
SaaS N=.15 U=.20 M=.15 R=.30 V=.20 Senior N=.25 U=.25 M=.05 R=.30 V=.15

Feasibility (80%)

Tech Complexity
40.0/40
Data Availability
20.0/25
MVP Timeline
20.0/20
API Bonus
0.0/15
Feasibility Breakdown
Tech Complexity/ 40Difficulty of core implementation stack.
Data Availability/ 25Practical availability and cost of required data.
MVP Timeline/ 20Expected time to ship a usable MVP.
API Bonus/ 15Bonus for viable public API leverage.
Total 100 points; below 50% is filtered out.

Market Validation (54/100)

Competition
8.0/20
Market Demand
6.2/20
Timing
14.0/20
Revenue Signals
7.5/15
Pick-Axe Fit
10.5/15
Solo Buildability
8.0/10
Validation Breakdown
Competition/ 20Signal quality from competitor landscape.
Market Demand/ 20Demand proxies from search and mention patterns.
Timing/ 20Fit with current shifts in tech, behavior, and regulation.
Revenue Signals/ 15Reference evidence for monetization viability.
Pick-Axe Fit/ 15How well the concept serves participants in a trend.
Solo Buildability/ 10Practicality for lean-team implementation.
Total 100 points; below 50 is filtered out.

Technical Requirements

Frontend [low] Backend [low]
Dashboard