B
Public Hospital AI Diagnosis Pre-Visit Guide
3.55
Derivation Chain
Step 1
Seoul Medical Center as a leading public healthcare AI hospital
→
Step 2
Lack of patient understanding when public hospitals adopt AI
→
Step 3
Pre-visit guide for AI diagnosis experience + question generation service
Problem
When patients in their 50s and 60s with chronic conditions receive AI-assisted diagnosis at public hospitals like Seoul Medical Center, even if the doctor explains the AI-read test results, anxiety such as 'Can I trust what AI did?' or 'Where does my data go?' remains unresolved. There is no material to understand the AI diagnosis process before the visit, and within the limited consultation time (average 5-7 minutes), they leave without asking all their questions.
Solution
Users select the hospital and department they plan to visit, and the service explains how the AI diagnostic tools used by that hospital work in layman's terms, and automatically generates '5 questions to ask during the visit'. It provides a Korean-language explanation of key clauses in the data usage consent form and a comparison table of what changes if they refuse.
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 (72%)
Data Availability
20.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 (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]