Skip to main content

Why I built Orchestrate Health

Orchestrate Health started with watching my wife, Jordan, an OB-GYN, spend hours building and fixing her group's physician call schedules. Between coverage needs, individual restrictions, vacations, and clinic and OR commitments, there was a lot to keep track of. Even a carefully built schedule could have conflicts, and finding and fixing them cut into our family time.

I started by trying to solve it with AI. Give it the physicians, their availability, and the rules, and let it build the schedule. But a schedule that looks mostly right can still put someone on call before an OR day, overlook PTO, or give one physician too many weekends. Getting that last 20% right was the hard part. That led me to build Orchestrate around explicit scheduling rules, with checks that flag conflicts as the schedule changes.

A conflict caught late means another round of swaps, and sometimes rescheduled patients. I want schedulers to get that time back.

Andrew Chappo

Andrew Chappo

Founder, Orchestrate Health

West Point graduate, former U.S. Army officer, and former Deloitte consultant.

Connect with Andrew on LinkedIn

Built by listening

One of the most useful things a physician or scheduler can tell me is, “That's not quite how we do it.” Sometimes that means making an existing setting easier to use. Sometimes it means building something I hadn't considered. When you tell me about a scheduling problem, you're talking directly to the person building Orchestrate. I enjoy working through those problems with the people using it.

Working with physicians and schedulers across practices and specialties has shown me how much scheduling varies. Many of the rules Orchestrate supports today came out of those conversations.

If you have a scheduling rule that software never seems to handle correctly, I'd like to hear about it.

You’ll work directly with me, Andrew Chappo, for setup, questions, and support.