Why IntakeDesk exists: referrals are broken loops
The problem isn’t that clinics don’t care.
The problem is that referral intake is treated like a mailbox instead of an operating system.
Referrals arrive messy. Information is missing. The patient is anxious. The provider is booked. The staff is triaging in their head, routing by memory, and using a patchwork of tools that were never meant to carry clinical operations.
So the loop breaks—and the cost shows up everywhere:
- time-to-appointment stretches
- urgent cases hide in noise
- staff burn out
- revenue leaks quietly
IntakeDesk exists because this should not be normal.
The referral loop (what’s actually happening)
A referral isn’t a document. It’s a request for coordinated action.
The loop is:
- Receive referral
- Understand what it says (even when it’s incomplete)
- Decide urgency + correct specialty + right location/provider
- Act: schedule, request missing info, run benefits/PA checks, escalate
- Confirm outcome and track it to completion
Most clinics only have tooling for step 1 and a hope-and-pray approach for the rest.
That’s not an intake problem. That’s an operations problem.
A concrete example (realistic, common, painful)
A referral comes in: “joint pain, positive ANA.” No labs attached. No symptom duration. No current meds. Patient is 63. The referring note is vague. The clinic is booked for months.
What happens today:
- staff guesses whether it’s urgent
- they call the patient, leave a voicemail
- they request labs via fax
- two weeks pass
- patient calls back upset
- coordinator squeezes them in or drops them unintentionally
What should happen:
- the system extracts what’s present
- flags what’s missing
- runs a triage rule: age + systemic symptoms + lab markers could indicate urgency
- auto-generates a “needs more info” request to the referrer
- routes to the correct location/provider based on capacity and diagnosis
- gives the patient clear next steps with expectations
That’s not “nice to have.” That’s what clinical safety and operational dignity look like.
What IntakeDesk is (without the buzzwords)
IntakeDesk is a clinical operations decision system:
- It ingests inbound referrals in their messy formats
- Pulls the signal out of noise
- Drives next actions with accountability
- Keeps the loop closed until the referral becomes an appointment (or a documented reason it didn’t)
It’s built around reality:
- incomplete inputs are normal
- rules aren’t static
- urgency can’t be guessed
- staff time is the scarce resource
What I believe
“Intake” is not a queue. It’s a decision engine.
Every handoff is a chance to lose the patient.
If urgency is subjective, safety is accidental.
The staff shouldn’t be the glue. The system should.
Work that repeats should become a primitive.
What this looks like in practice
The system has to do a few things exceptionally well:
- Normalize inputs: PDFs, faxes, portals → structured record
- Capture missingness: Not just “what we know,” but “what we need next”
- Triage with guardrails: rules + escalation paths + auditability
- Route with constraints: location, provider, capacity, diagnosis-specific rules
- Drive next actions: schedule / request more info / benefits / PA / escalate
- Close the loop: track to outcome; no silent drop-offs
If it can’t close the loop, it’s not operations software—it’s another inbox.
The clinics that win won’t be the ones with the most staff. They’ll be the ones with the best loops.
Build the things you wish existed; one day one of them will outgrow your expectations. This is one of those things. It has to be.
Related Projects
Subscribe to the Build Log
I write about one deep-dive per month. No spam, just systems.