Parent Medication Schedule Family Sharing Service

3.00

Derivation Chain

Step 1 Health broadcasts by Yoo-sun Yoon — interest in health management

→

Step 2 Polypharmacy problem among parents aged 70+

→

Step 3 Children unable to track parents' medication status in real time

→

Step 4 Auto-generated medication schedule + real-time family sharing

Problem

65% of adults aged 70+ take 3 or more medications simultaneously, averaging 5.2 drugs. Dosing instructions vary — 'after meals,' 'before bed,' 'on an empty stomach' — leading to frequent missed or mistimed doses. When adult children in their 40s-50s try to remotely check on their parents' medication compliance, calling to ask 'Did you take your medicine today?' only yields a perfunctory 'Yes, I did.' There is no way to verify actual adherence.

Solution

Register the parent's prescription medications on the web (via OCR from medication packets or manual entry), and the system auto-generates a dosing timetable for each drug. Parents simply tap a 'Dose Taken' button, and children can check today's medication status in real time on a separate screen. If a dose is missed past a set time, children receive an alert. Drug interaction warnings are also displayed.

Target: Ages 42-55, adult children living in a different city who remotely manage the health of parents aged 70+, families with 2-3 siblings sharing caregiving responsibilities

Revenue Model: 1 person registration free. Premium (Monthly Subscription ~$2.20/mo): 3+ family member sharing, missed dose alerts, drug interaction warnings, automatic prescription change sync.

Ecosystem Role: Infrastructure

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

2.0/5

U Urgency

4.0/5

M Market

3.0/5

R Realizability

3.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 (68%)

Tech Complexity

29.3/40

Data Availability

18.3/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 (51/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

5.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 [medium] Backend [medium] Data Pipeline [low]

Dashboard