B
Parents' Hospital Receipt Decoder Service
3.80
Derivation Chain
Step 1
Multiple public APIs for food health and healthcare
→
Step 2
Increasing situation where 50s manage elderly parents' hospital expenses
→
Step 3
Problem of not understanding item meanings on hospital receipts and being unable to judge over-treatment
Problem
A worker in their 50s manages the hospital receipts of their 75-year-old parents monthly. Terms like 'selective benefits,' 'non-covered procedure fees,' and 'differential drug copayment rates' are complex, making it impossible to determine how much of the total 200,000 KRW is eligible for National Health Insurance reimbursement or whether non-covered items are appropriate. Despite spending 3-5 million KRW annually on hospital bills, they fail to apply for the out-of-pocket maximum reimbursement (800,000-1.2 million KRW per year), missing out on hundreds of thousands of won each year, and often omit claims for supplementary private insurance.
Solution
When a hospital receipt is photographed, OCR automatically recognizes items and explains each in plain language. It tracks cumulative annual out-of-pocket expenses and sends alerts when the user becomes eligible for out-of-pocket maximum reimbursement. Non-covered items are compared with average prices at other hospitals for the same procedure to indicate reasonableness. It also provides a document checklist for supplementary private insurance claims.
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 (70%)
Data Availability
20.8/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]