Family Medical Info Emergency Card

4.15

Derivation Chain

Step 1 Post-health-checkup follow-up care

→

Step 2 Checkup record management

→

Step 3 Problem: family medical info cannot be relayed during emergencies

Problem

When adults in their 50s-60s lose consciousness in sudden emergencies (stroke, heart attack, car accident), there is no way to relay critical medical information—current medications, allergies, underlying conditions, blood type—to ER medical staff. Fewer than 10% of spouses or children know the exact names of their parents' medications. Lack of medical information causes delays in emergency treatment or administration of contraindicated drugs.

Solution

Enter (1) underlying conditions, (2) current medications, (3) allergies, (4) blood type, and (5) emergency contacts on the web to generate a unique URL and QR code. Place the QR on a smartphone lock screen wallpaper or print a wallet-sized PDF card. Scanning the QR displays medical information without a PIN. A family sharing feature lets spouses and children update the information.

Target: Ages 50-65 with at least one chronic condition or regular medication, living with or near a spouse and/or adult children

Revenue Model: Single-person basic medical info card is free. Family plan for up to 4 members + automatic alerts on medication changes + annual update reminder for 9,900 KRW/year (~$7.50/year).

Ecosystem Role: Infrastructure

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

3.0/5

U Urgency

5.0/5

M Market

4.0/5

R Realizability

5.0/5

V Validation

3.0/5

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%)

Tech Complexity

34.7/40

Data Availability

20.6/25

MVP Timeline

20.0/20

API Bonus

0.0/15

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 (55/100)

Competition

8.0/20

Market Demand

6.2/20

Timing

14.0/20

Revenue Signals

7.5/15

Pick-Axe Fit

10.5/15

Solo Buildability

9.0/10

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] Infrastructure [low]

Dashboard