A
Pre-Checkup Consultation Rehearser
4.00
Derivation Chain
Step 1
Connecting health checkup results to follow-up actions
→
Step 2
Insufficient doctor consultation time during checkups
→
Step 3
Pre-visit preparation to maximize information exchange during short consultations
Problem
When people in their 50s–60s undergo their national health checkup, the doctor consultation averages just 3–5 minutes—not enough time to effectively communicate symptoms, family history, medications, and lifestyle. Asked 'Any concerns?', they respond 'I'm fine' and fail to mention important symptoms like chest pain on the left side for the past 6 months or frequent nighttime urination. This reduces checkup accuracy and causes missed follow-up tests.
Solution
2–3 days before the checkup, complete a guided self-questionnaire on the web covering age, gender, family history, existing conditions, medications, and symptoms from the past 6 months. The system generates a 'My Health Summary Card' (1 page) with a printable PDF to show the doctor at the checkup, along with a 'Must Mention' checklist for critical symptoms.
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 (75%)
Data Availability
23.1/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 (64/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]