Referral Intake for Pain and Spine Practices

Referring-office callers from primary care, orthopaedics, neurosurgery and emergency departments are handled as a referral conversation, capturing the referring physician, the reason stated on the referral, and a direct line back to that office
The records a pain evaluation depends on are asked for by name: recent imaging and where the study was performed, prior injections and their dates, treatment already tried, and the current medication list
Patients who call after being told the pain office would contact them are matched to a referral already on file where one exists, and captured as a pending referral where it does not
What is missing comes back as a specific list to chase rather than a generic records-needed flag, so your staff make one call to the referring office instead of three
Where your rules require imaging or documented prior treatment before a particular appointment type can be booked, the call collects what is needed and offers the visit type your practice does allow in the meantime
Referral calls, patient calls and payer calls all land on the same number and are sorted before they reach your team

How it pays back

A Referral Is Not Yet an Appointment

What an interventional pain evaluation can conclude depends on what arrives with the patient. Coverage policies for facet interventions, epidural injections and neurostimulation lean on documented duration of pain, prior conservative treatment and relevant imaging. Booking a new patient before any of that is in hand converts a consultation slot into a records-gathering appointment that has to be repeated.

Referring Offices Should Not Sit in a Phone Queue

The person calling is usually a medical assistant working through a stack, and a pain practice that cannot be reached quickly is competing with every other pain practice in the market for that stack. Answering immediately, capturing the referring physician and reason, and sending it straight to intake is the low-drama version of referral development.

The Records Chase Is the Actual Work

Most referral delay is not a scheduling problem, it is an incomplete-packet problem: the MRI report is at an imaging centre, the physical therapy notes are at a clinic, and nobody knows which piece is outstanding. Asking for each item by name, on the call, and returning a specific outstanding list makes the chase finite instead of open-ended.

Self-Referred Callers Handled Under Your Own Rules

Pain practices field a steady stream of patients who found you themselves, some of whose plans require a referral before an evaluation is covered. Your rules decide what happens: capture and hold, book anyway, or explain the requirement in your own wording. The system applies the rule you wrote instead of improvising a coverage answer.

Referral source captured every time

Referring physician, practice and direct callback recorded on the call, not reconstructed later

A named list, not a generic flag

Outstanding records returned item by item so the chase can actually be worked

Answered on every line at once

A referring office never waits behind patient calls to send you a new patient

Frequently asked questions

Does the system decide whether to accept a referral?

No. It captures the referral and applies the administrative rules you have written, such as which plans you accept and which appointment types require particular records. Whether a referral is clinically appropriate for your practice is a decision for your clinicians, and the call is routed accordingly.

Can it book the new patient on the same call?

Where a scheduling integration is available and your prerequisites are satisfied, yes. Where something is outstanding, it can book the appointment type your rules permit in that situation, or capture the request and route it so your intake staff book once the packet is complete.

Most of our referrals arrive by fax. Does that help?

The system handles the call traffic around the referral rather than the fax itself, which is where the delay usually sits: the referring office chasing status, the patient chasing an appointment, your staff chasing records. Where your team supplies a pending referral list, callers are matched to it.

Can it chase records outbound?

Yes, against a list you supply. Outbound calls request the named items, capture what the other office says about availability and how it will be sent, and return anything unresolved as an exception.

Does it verify insurance?

It captures plan, identifier and policyholder detail and applies your accepted-plan rules, including any referral requirement you configure. Benefits verification stays with your team unless an integration supports it, and it does not quote coverage or patient responsibility.

Where do captured referrals go?

Into the destination you choose: an EMR task or referral work queue, a shared inbox, or a structured summary. Writeback is available through API or FHIR for supported systems, and custom integration is available where no direct interface exists.

Turning a Spine Referral Into a Bookable Appointment