Great Clinical Scheduling is More than CRUD

Why is building a great clinical scheduling system so hard?

On its face, it seems easy, especially if you've got a healthy AI token budget. Borderline, it's an intro computer science class project*

It even has a standard Computer science acronym.. which certainly doesn't make it sound too hard: "CRUD" (create, read, update, delete). CRUD is essentially what a clinical shift system does, you build a schedule, give visibility of that schedule to a team, update shifts and/or delete them. "Sounds like a simple 'CRUD' App" is something that an Engineer might say as a dismissal, meaning, "that's not hard"

I've discussed this at length with my cofounder, the incredibly talented Shachar Har Yeda. To the two of us, it feels a bit silly, since we live inside an operation that often stretches a talented technical team to their limits. "Of course this is hard- last sprint we almost missed multiple features because they took so long to debug..."

However... of course, our flippant initial answer of "it just is" is NOT a satisfactory answer to investors who want to understand why our product is defensible in the age of vibe coding, nor to our customers who we ask to bet on us in part due to the quality of and the extent to which we've invested in our technology

Ultimately, we boil the challenge down to 3 interconnected reasons, which I'll summarize here and expand on in future posts

A great clinical scheduling system needs to be:

1) Flexible and configurable

2) Integrated with multiple other complicated systems

3) Automated and smart

Each of these 3 things is hard to accomplish on its own, and the interactions between each lever expand the complexity manyfold (Delivering flexibility while integrated with other systems, delivering automations on top of something highly configured). Further, in 2026, "Automated and smart" means the system effectively leverages LLMs and integrates agents to accomplish common tasks, which is an incredible opportunity, but increases the surface area further.

‍

*Author's note: I built a peer-to-peer lunch scheduling system for my college CS class

‍