Problem Statement
Maintenance meds fail not from cost alone but from forgetting: small text, confusing “2x a day” instructions, and shared phones with no load for app notifications that need internet. Seniors won’t make accounts or remember passwords. Family abroad can’t verify without surveillance apps seniors distrust.
Proposed Solution
One phone, one schedule: family encodes meds once with photos of the boxes. Big “INUMIN NA” buttons, voice prompts in the lola’s language, and local notifications that fire without internet. Weekly adherence shows as simple stars. Schedule moves to a new phone via QR — no cloud copy. All health data stays at home.
Target Market
- Primary users: Seniors on maintenance meds, family caregivers, barangay health workers doing home visits.
- Deployers: Senior citizens’ associations, parish health ministries.
How AI Is Used
- Label reader: On-device OCR reads med box labels to prefill name and dosage for checking.
- Schedule simplifier: Small LM turns “BID PC” into “Uminom pagkatapos almusal at hapunan” Tagalog.
- Why AI: Reduces encoding errors that cause missed doses.
Independent Deployment Angle
- No cloud health record, no carrier, no venue, no headset. Home owns the data.
- Works on old phones with no SIM; voice prompts help low-vision users.
- BHW can set up 10 households in a morning with QR carry.
Demo Scenario (3 minutes for judges)
- Snap a mock med box; OCR prefills name offline.
- Schedule “pagkatapos almusal” appears as a big-button reminder with voice playback.
- Show weekly stars after two mock confirmations.
- Move schedule to a second phone via QR with WiFi off.
- Close: “Walang account na makakalimutan.”
30-Hour Build Plan
| Hours | Task | Role |
|---|---|---|
| 0–3 | Gather mock labels, define schedule model | All |
| 3–9 | OCR prefill + schedule simplifier | AI lead |
| 3–10 | Local notifications + SQLite | Backend |
| 10–20 | Senior-first UI, voice prompts | Frontend |
| 20–26 | Senior usability test (mock), font/size pass | All |
| 26–30 | Pitch, disclosure | PM / Pitch |
Suggested stack: Flutter + local notifications, on-device TTS, SQLite schedule, QR carry-over. Public data / APIs: None; mock labels only.
Risks & Privacy Notes
- Medical safety: Reminder only, never dosage advice; labels say “sundin ang reseta, magtanong sa doktor.” Demo meds fictional.
- Privacy: Health schedules are sensitive and never leave the device. No analytics, no uploads — Data Privacy Act minimization by architecture.
- Accessibility: Always human-confirm OCR results; large text and voice by default.
AI Use Disclosure (draft)
Uses on-device OCR and a small LM for schedule wording. AI coding assistants helped with notification code. All demo schedules are fictional and checked by the team.
Rubric Scoring
| Criterion | Weight | Score (1–5) | Why |
|---|---|---|---|
| Innovation & creativity | 25% | 3 | Reminders exist; zero-cloud senior-first is the edge |
| Problem–solution fit | 25% | 5 | Fits shared-phone senior reality |
| AI application & value | 20% | 3 | OCR + wording help, modest AI |
| Feasibility | 15% | 5 | Very buildable |
| Impact & scalability | 15% | 4 | Huge senior need |
| Weighted total | 4.00 |