Healthcare, 2025
Cadence
Appointment scheduling for a network of 40 clinics, used by patients and front-desk staff.
- Sector
- Healthcare
- Year
- 2025
- Duration
- 6 months
- Team
- 5 engineers, 1 designer
- Focus
- Interface
Architecture, 7 components
- Client
- Service
- Queue or log
- Data store
- External system
The problem
Patients booked by phone because the old portal failed on mobile and with screen readers. Front-desk staff juggled three tools to reschedule a single visit.
What we built
- 01Designed one typed scheduling API that serves both the patient app and the clinic console.
- 02Built both interfaces with server-rendered React, tested with screen readers and on low-end phones.
- 03Kept the electronic health record as the system of record, synced through a dedicated bridge service.
- 04Sent reminders through a queue so a slow SMS provider never blocks a booking.
What changed.
- of bookings now made online
- 71%
- WCAG 2.2 conformance, audited
- AA
- for front-desk rescheduling, down from 3
- 1 tool
Stack
- Next.js
- React
- Node.js
- PostgreSQL
- Prisma