B
Health Checkup Family History Mapper
3.00
Derivation Chain
Step 1
Health Checkup result longitudinal interpretation
→
Step 2
Checkup metric trend analysis
→
Step 3
Re-evaluating personal risk levels in family history context
Problem
When people in their 50s receive annual Health Checkups, even if blood sugar, blood pressure, and cholesterol levels fall within 'normal range,' the risk profile changes entirely if parents had diabetes or cardiovascular disease. However, checkup results never reflect family history context, and the 3-5 minute doctor consultation leaves no time for comprehensive family history discussion. Cross-analyzing parental and sibling disease history with personal metrics could provide early 10-year onset risk warnings, but no such tool exists.
Solution
Users enter family disease history for parents and siblings (diabetes/hypertension/cancer/cardiovascular, etc.) and register their own checkup results by year. The system highlights items that are 'normal by general standards but in the caution zone considering your family history.' It recommends additional screening tests for early detection of related conditions and auto-generates a question list for the next doctor visit.
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 (63%)
Data Availability
19.4/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 (50/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]