B
My Medication Interaction Checker
3.35
Derivation Chain
Step 1
AI paradox/economic changes in the AI era
→
Step 2
Increase in polypharmacy among 50s
→
Step 3
Blind spots in drug interaction side effects
Problem
68% of chronic disease patients aged 50 and older take three or more medications simultaneously, but information about interactions between drugs prescribed at different hospitals and pharmacies is scattered. A 55-year-old office worker visiting 2-3 departments (internal medicine, orthopedics, urology, etc.) must ask the pharmacist each time or understand DUR system results to check interactions with existing drugs, which is difficult for the general public. This leads to unnecessary side effects or taking medications with canceled-out effects for months without knowing.
Solution
Enter the names of current medications on the web, and it (1) visualizes drug interaction risk using a traffic light system, (2) automatically detects duplicate and conflicting ingredients, and (3) generates a 'My Medication Summary Card' to show the doctor at the next hospital visit. Based on Korea's MFDS DUR data and the Drug Safety Korea API, it translates into language that the general public can understand.
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. |
N=.15 U=.20 M=.15 R=.30 V=.20
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 (56/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]