B
Parent Medication Cross-Check Board
3.30
Derivation Chain
Step 1
Health Checkup result interpretation & tracking
→
Step 2
Increasing polypharmacy among middle-aged and seniors
→
Step 3
Cross-hospital prescription interaction risk blind spots
Problem
When people in their 50s manage the health of their parents aged 75-85, no institution provides an integrated check on drug interactions among the 8-12 medications prescribed separately by 3-4 different hospitals (internal medicine, orthopedics, ophthalmology, etc.). Korea's DUR (Drug Utilization Review) system only works within the same pharmacy, creating blind spots when parents use two or more pharmacies. Unnecessary hospitalizations due to polypharmacy side effects cost hundreds of thousands of won (hundreds of dollars) annually.
Solution
Users enter all medications their parents are currently taking (or upload prescription photos) on the web. The service classifies drug interaction risks into three levels (Caution/Warning/Danger). It automatically generates 'question cards to show the doctor at the next hospital visit,' enabling adult children to effectively ask questions on behalf of their parents—or for parents to ask themselves.
NUMR-V Scores
NUMR-V Scoring System
| N Novelty | 1-5 | How uncommon the service is in market context. |
| U Urgency | 1-5 | How urgently users need this problem solved now. |
| M Market | 1-5 | Market size and growth potential from proxy indicators. |
| R Realizability | 1-5 | Buildability for a small team with realistic constraints. |
| V Validation | 1-5 | Validation signal quality from competition and demand data. |
SaaS N=.15 U=.20 M=.15 R=.30 V=.20
Senior N=.25 U=.25 M=.05 R=.30 V=.15
Feasibility (68%)
Data Availability
19.2/25
Feasibility Breakdown
| Tech Complexity | / 40 | Difficulty of core implementation stack. |
| Data Availability | / 25 | Practical availability and cost of required data. |
| MVP Timeline | / 20 | Expected time to ship a usable MVP. |
| API Bonus | / 15 | Bonus for viable public API leverage. |
Market Validation (55/100)
Validation Breakdown
| Competition | / 20 | Signal quality from competitor landscape. |
| Market Demand | / 20 | Demand proxies from search and mention patterns. |
| Timing | / 20 | Fit with current shifts in tech, behavior, and regulation. |
| Revenue Signals | / 15 | Reference evidence for monetization viability. |
| Pick-Axe Fit | / 15 | How well the concept serves participants in a trend. |
| Solo Buildability | / 10 | Practicality for lean-team implementation. |
Technical Requirements
Frontend [medium]
Backend [medium]
Data Pipeline [low]