Problem
- Fragmented hand‑offs across appointments → eRx → labs → billing.
- Overwhelming UIs; alert fatigue in prescribing & results.
- Small clinics lack IT; need sane defaults and offline resilience.
-
2025‑11‑30 — Foundations
Week 1/12- Shipped: MRN, demographics, consents; encounter model skeleton.
- Decisions: audit events on write; immutable logs.
- Obstacle: offline caching strategy for desktop.
- Next: appointments & queue.
-
2025‑12‑7 — Appointments & Queue
Week 2/12- Shipped: provider calendars, rooms, queue board.
- Decisions: block double‑booking at resource level.
- Obstacle: SMS gateways vary; fallback to email reminders.
- Next: start eRx flows.
News
Focused clinic‑first EMR. Transparent progress, rigorous scope. No screenshots of real PHI; all examples are synthetic.
Solution
- Opinionated workflows that reduce clicks and context switches.
- eRx with tuned interactions; clean lab result flows; simple billing.
- Multi‑tenant, offline‑friendly stack (Flutter + FastAPI).
Why Now
- Clinic digitization post‑COVID persists; pharmacy/lab networks maturing.
- Commodity infra + strong OSS lowers time‑to‑market.
- Regional vendors lack focused, modern UX for small practices.
Market (initial beachhead)
Estimate with your region’s clinic counts × ARPU. Include a bottoms‑up table here.
Product (architecture & scope)
- Modules at MVP: Appointments, eRx, Labs, Billing, Inventory (pharmacy).
- Security: RBAC, audit logs, encryption in transit/at rest, backups.
- Data region: AWS eu‑north‑1; multi‑tenant isolation strategy.
Moat
- Workflow depth in eRx ↔ pharmacy and lab returns.
- Distribution via local partners; language/RTL support.
- Data portability; no vendor lock‑in.
Traction
- Build log cadence; features stabilized.
- Design partners / pilot MoUs (if any).
- Benchmarks: staging uptime, e2e test pass rate, render times.
Team
Short bio(s), roles to hire (e.g., clinical advisor, QA, integrations).