B
Chronic Care Prescription Timeline
2.95
Derivation Chain
Step 1
Integrated management of chronic condition medication and checkup data
→
Step 2
Scattered prescriptions and checkup results across multiple hospitals
→
Step 3
Inability to identify causal relationships between medication changes and checkup metric trends
Problem
Adults aged 50-65 managing 2-3 chronic conditions simultaneously (hypertension, diabetes, hyperlipidemia) visit 3-4 different specialists (internal medicine, cardiology, ophthalmology) and receive separate prescriptions. There is no way to track on a timeline 'when a medication was changed and how blood pressure, blood sugar, and cholesterol levels changed before and after.' The national Health Insurance portal shows visit history but lacks a view connecting prescription changes with Health Checkup results. Patients must verbally explain past history at every new hospital visit and cannot personally assess the effectiveness of medication changes.
Solution
Users upload their national health insurance treatment history PDF and Health Checkup results PDF on the web, and the system overlays 'prescription change events' and 'checkup metric changes' on a single timeline view. It auto-highlights medication-metric correlation events like 'Blood pressure medication changed from A to B in March 2024; systolic BP decreased from 145 to 128 at June checkup.' It generates a one-page 'My Medication & Checkup Summary' PDF to show at hospital visits.
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 (51/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]
AI/ML [medium]