The referral arrived on day zero. Nobody has called.
Between a referral arriving and a patient being seen sit four systems that do not talk, two portals nobody owns, and a referring physician who will send the next one somewhere else.
Thirty minutes · no predetermined package
What a disconnected intake pathway feels like.
Referrals arrive by fax and are keyed into the EHR by hand, days later.
Prior authorisation sits in a payer portal nobody checks on a schedule.
A patient is called three times and never reached, and nothing escalates.
The referring physician is never told what happened to their patient, so the next referral goes elsewhere.
No-show rates are known monthly and not by clinician, slot type or reminder channel.
Recall and follow-up depend on a person remembering rather than a rule.
What you are probably running, and what constrains it.
The typical stack
What the rules require
Six questions before changing anything.
How a patient actually gets seen.
Referral or self-referral
fax, portal or phoneArriving in several formats, most of which need a person to transcribe them.
Eligibility and authorisation
across payer portalsTwo different checks, two different clocks, and frequently the longest part of the wait.
Patient contact
and the chaseWhere most referrals are lost — unanswered calls with no escalation behind them.
Scheduling
and remindersBooked, confirmed, and reminded through a channel the patient actually uses.
The loop closed
back to the referrerWhat happened, told to the physician who sent them. This is what produces the next referral.
What practices and clinics ask.
What is patient intake software?
It captures a referral or enquiry, verifies eligibility, tracks prior authorisation, contacts the patient and books the appointment — the pathway between a referral arriving and a patient being seen.
What should a healthcare CRM do that an EHR does not?
Hold everything before the chart exists: the referral, the eligibility check, the authorisation, the outreach and the relationship with the referring physician. The EHR is authoritative for care, not for coordination.
What makes a CRM HIPAA compliant?
Encryption, access controls, audit logging, a signed business associate agreement, and configuration to the minimum necessary standard. Compliance is a property of the whole arrangement rather than a feature.
Can this integrate with Epic or athenahealth?
Yes, through HL7 or FHIR interfaces. The EHR stays authoritative for the chart while the coordination layer sits in front of it.
How do you reduce referral leakage?
By measuring time from referral to appointment by source, escalating unanswered outreach, and telling the referring physician what happened. Most leakage is silence rather than capacity.
What about prior authorisation?
It needs a queue with an owner and an ageing clock rather than a portal somebody checks when they remember. It is frequently the longest single delay in the pathway.
Can patient reminders be automated?
Yes, with consent recorded per channel. TCPA and state rules apply to healthcare outreach, so consent has to be a code path rather than an assumption.
How should no-show rates be measured?
By clinician, slot type and reminder channel. A monthly practice-wide average hides the pattern that would actually reduce it.
What does custom healthcare software development cost?
It scales with integration count and the depth of the compliance requirement rather than with patient volume. HL7 and FHIR work is the usual driver.