Vision
"Every ACME Health patient can find, book, and complete a video visit with their provider from their phone in
under two minutes — and every provider can run their telehealth day from one console, without the workarounds
CareLink Classic forces on them today."
02Business Drivers
| Driver | Why It Matters Now |
|---|---|
| Vendor end-of-life | CareLink Classic's vendor announced end-of-support in 18 months; no mobile roadmap was ever delivered on the existing contract, and renewal pricing increased 34% at last renewal. |
| Patient experience gap | Patient-facing access is a desktop-only web portal. Competitor telehealth offerings in the region are mobile-first; patient satisfaction surveys cite "hard to use on my phone" as the top complaint. |
| Provider efficiency | Providers toggle between CareLink Classic and the EHR for scheduling and visit notes; no unified console. Average visit setup time runs ~6 minutes per patient, largely spent on system switching. |
| Scalability | CareLink Classic is priced and licensed per-desktop-seat, which doesn't scale as ACME Health adds telehealth-only provider contractors. |
03Success Metrics (Program-Level OKRs)
| Objective | Key Result | Baseline → Target |
|---|---|---|
| Patients can self-serve telehealth visits from mobile | % of visits booked via mobile app | 0% → 60% within first 60 days live |
| Reduce visit setup friction for providers | Average time from login to visit start | ~6 min → under 2 min |
| Cut support burden of the old system | Telehealth-related support tickets/month | ~410/mo → under 150/mo |
| Successful, safe cutover | Patient records migrated with zero critical data-integrity defects | 100% of active patient records validated pre-cutover |
| Provider adoption | Provider console daily active use, week 4 post-launch | ≥ 85% of scheduled providers |
04Release Roadmap — Now / Next / Later
Two releases across the 8-sprint program, both teams contributing to each. A Now/Next/Later view keeps the roadmap conversation with stakeholders honest about what's committed vs. what's still a candidate.
Now — Release 1 (MVP)
Sprints 1–5
- Patient login/registration (mobile)
- Appointment scheduling & reminders
- Video visit launch (feature parity with CareLink Classic)
- Provider console: daily schedule + visit launch
- Core patient record migration (active patients only)
Next — Release 2 (Full Cutover)
Sprints 6–8
- Secure patient/provider messaging
- Prescription refill requests
- Full historical record migration + legacy decommission
- Provider console: visit notes handoff to EHR
Later — Candidate Backlog
Post-program
- Remote patient monitoring device integration
- Multi-language patient app support
- Group/family visit scheduling
- Provider console analytics dashboard
05Program Timeline at a Glance
Sprint 0
Jan 5–16
Setup, environments, backlog seedingSprint 1
Jan 19–30
Auth & onboardingSprint 2
Feb 2–13
Scheduling coreSprint 3
Feb 16–27
Video visit integrationSprint 4
Mar 2–13
Provider console v1Sprint 5
Mar 16–27
Release 1 MVP hardening & launchSprint 6
Mar 30–Apr 10
Messaging & refillsSprint 7
Apr 13–24
Full data migrationSprint 8
Apr 27–May 8
Release 2 Cutover & decommission