A health system with 100+ clinics was stuck on a scheduling module that couldn't keep up. We built a new scheduling engine on top of their EMR instead of replacing it.

Impact, measured in results
Booked through the platform annually
Down from several minutes per appointment
Across 100+ clinics including peak volumes
A federally qualified community health system with roughly 100 clinics in the Northeast, serving underserved and underinsured populations. They schedule about 250,000 appointments a year through several hundred call center and front desk staff, reaching somewhere between 800,000 and a million patients.
What used to take hours of call center time now takes minutes. And we didn't have to leave our EMR to get there.
Operations Director
Multi-Clinic Health System
They didn't need a new EMR. They needed a scheduling engine that sat on top of the one they had. The EMR stays the system of record. All day-to-day booking moves into a UI designed for call center speed.
We wired it together with HL7 for bi-directional sync on appointments and patient data, with error handling and reconciliation built in so the two systems stay in lockstep. The rules engine lets admins configure scheduling policies by clinic, provider, visit type, and insurance program. No code changes needed.
Rollout was incremental. We started with a handful of clinics, ran both systems in parallel until staff were confident, then scaled to 100+. Each iteration was shaped by the people actually using it.
Provided services
Our team
Justin Tannenbaum
Solutions Architect
Lukasz Chmielowski
Lead Engineer
Piotrek Szyperski
Engineering
Ernesto Quispe
Product Design
Tech stack

Stuck on a legacy system? We've built the engagement layer on top before. Let's talk about yours.
Schedule a discovery callReal-world examples of solving complex problems and scaling challenges.