Referral Intake
Surgical demand arrives from someone else's decision. Capture the referral, reach the patient who never calls, and book the consult inside your own window.
Almost every case in a general surgery practice starts because an emergency physician, a primary care office or a gastroenterologist decided to send it. A referral that never converts into a booked consult is invisible: no one calls to complain, and the volume simply appears at a different practice next quarter.
Discharge instructions that say to follow up with surgery put the burden on a patient who was in pain at three in the morning and has now gone back to work. Calling them, rather than waiting for them, is the entire difference between a referral list and a schedule.
Your practice already knows which referral reasons need a longer slot, which need imaging in hand, and which need to be seen sooner. Capturing the stated reason and requested timeframe accurately lets your own rules do that mapping, instead of a message that reads only that a doctor's office called.
Referring offices notice when their patients cannot get through, when nobody calls back, and when they never learn what happened. Answering every call from a referring practice on the first ring, in a consistent format, protects the relationship that generates your operative volume.
Referral source captured every time
Who sent the patient, why, and in what timeframe, recorded in a consistent structure
Outbound and inbound at the same time
Referral chasing runs without a single incoming line going to voicemail
Dozens of languages
Patients discharged from an emergency department are reached in the language they speak
No. It records what the referring clinician stated and applies the mapping your practice authored between referral reasons and appointment types. Any judgement about urgency belongs to your surgeons and to the clinician who sent the patient, never to the system.
Yes. Outbound calling runs from the list your staff or your system produce, within your call windows, with the attempt limits and voicemail rules you set. Opt-outs and do-not-contact status are honoured on every campaign.
The system works the telephone side of that pipeline: reaching the patient, booking the consult, and answering the referring office. Where your referral documents already populate a worklist, calling runs from it, and custom integration is available to pull that list from your system.
Only within the disclosure rules your practice sets, and clinical discussion routes to your staff. It is designed to confirm administrative facts you have authorised, such as that an appointment exists, rather than to relay findings or plans.
Yes, including plan, policy identifiers, and whether the patient's plan requires a referral on file. That is the data your authorization work depends on, and collecting it at first contact removes a call later.
Into the destination you choose, as a structured record rather than a message. Delivery is available through API or FHIR for supported systems, available through secure workflow automation elsewhere, and custom integration is available where no direct interface exists.
Intake
Records and Imaging Collection Before Surgical Consults
The next step once the consult is booked: getting the scan and the path report in the room.
Authorization
Prior Authorization Calls for Surgical Procedures
Why plan details captured at referral intake save a call three weeks later.
Growth
Medical Referral Growth Program
The broader mechanics of protecting and growing a referral channel.
Pillar guide
AI Receptionist for General Surgery Practices
How a general and robotic surgery practice handles consult, pre-op and post-op call volume end to end.
See how MedReception AI handles after-hours calls, scheduling, intake, and patient communication for medical practices like yours.
