B
Family History-Based Checkup Item Designer
3.60
Derivation Chain
Step 1
Health Checkup result interpretation & tracking
→
Step 2
Checkup metric trend analysis
→
Step 3
Unable to select customized additional screening items linked to family history
Problem
When people in their 50s get comprehensive Health Checkups, they must choose optional items (colonoscopy, cardiac CT, thyroid ultrasound, genetic testing, etc.), but cannot get personalized recommendations based on their parents' and siblings' disease history (family history). Hospital consultants push the most expensive packages, and individuals either pay an extra $225–$375 'just in case' for unnecessary items, or conversely miss items they actually need.
Solution
Users simply check their parents' and siblings' major diseases (cancer, cardiovascular, diabetes, dementia, etc.) and enter their recent checkup results. The system then recommends 'with this family history, add this test / skip this test' based on Korean Society of Preventive Medicine guidelines, complete with supporting evidence. Average costs and recommended screening intervals are also provided for each recommended item.
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 (74%)
Data Availability
22.5/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 (53/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 [low]
Backend [medium]