The booking flow shares capacity with work that does not need to interrupt a patient.
Background processing needs to finish, while an evening patient needs the booking request to complete now.
Who you’d be doing this for
“I found someone who takes my insurance, then the last screen just kept loading.”
Tyra Lund · Therapy-seeking patient
An insured patient attempting to book an evening appointment through the marketplace.
What is at stake
Evening booking requests fail when a background task exhausts Redis connections. You must protect patient booking without interrupting the processing that keeps the platform current.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- booking continuity vs background processing
- fast containment vs durable isolation
- shared capacity vs service boundaries
- evening demand vs safe release review
Why Headway
In-network booking is the point where a therapy-seeking patient turns a covered search result into care.
Written with these in mind
Not your kind of problem? 34 more at Headway, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.