eConsults vs referrals: when each works and how they fit together

Specialist access is one of the most persistent bottlenecks in ambulatory care. Wait times for specialty appointments stretch weeks or months in many markets, and a meaningful share of the referrals filling those slots are questions a specialist could have answered from the chart: a medication adjustment, an abnormal lab that needs interpretation, a "do I need to worry about this" question.

eConsults exist for exactly that slice. Instead of moving the patient to the specialist, the ordering provider moves the question, and the specialist answers asynchronously through the record. When the program works, patients get answers in days instead of waiting weeks for a visit, and specialty slots stay open for the patients who need to be in the room.

But eConsults are a complement to referrals, not a replacement, and the operational seam between the two pathways is where things go wrong. This article defines both, lays out when each fits, summarizes how reimbursement works at a high level, and walks through what a combined workflow looks like for the referral team that has to run it.

What is an eConsult?

An eConsult (electronic consultation, sometimes called an interprofessional consultation) is an asynchronous, provider-to-provider exchange in which a treating clinician sends a focused clinical question to a specialist, who reviews the relevant record and responds with an assessment and recommendations, typically without seeing the patient. The exchange usually happens inside the EHR or through a dedicated eConsult platform, and the specialist's response is documented in the patient's record.

Three properties define the model:

• Asynchronous. Neither clinician has to be available at the same moment. The specialist answers within an agreed turnaround window, commonly measured in one to a few business days.
• Provider-to-provider. The patient is not a direct participant. This distinguishes eConsults from telehealth visits, where the specialist sees the patient by video, and from patient portal messaging.
• Question-scoped. A good eConsult asks a specific question ("is this rash consistent with X, and is the current regimen reasonable?") rather than transferring the patient wholesale.

The treating provider retains responsibility for the patient's care and decides what to do with the specialist's advice. That framing matters clinically and legally: an eConsult informs the ordering provider's decision, it does not hand the patient off.

What a traditional referral does

A traditional referral is a request for a specialist to evaluate and, as needed, treat the patient directly. The specialist takes on part of the patient's care: examining the patient, ordering or performing tests and procedures, and often managing the condition over multiple visits. The full lifecycle (intake, insurance checks, scheduling, the visit itself, and the consult note returning to the referring provider) is what referral management exists to run.

Referrals also carry administrative machinery that eConsults mostly avoid. Managed care plans may require the referral to be authorized or documented in specific ways before the specialist visit is covered, which is its own workflow; see how referrals work in managed care plans and how a referral differs from a prior authorization. And referrals fail operationally at well-documented rates: industry completion commonly sits at 50 to 65 percent, anchored to the Institute for Healthcare Improvement and National Patient Safety Foundation finding that up to half of referrals are never completed.

eConsult vs referral: side by side

When an eConsult can resolve the question

Whether any individual case fits an eConsult is a clinical decision that belongs to the ordering provider. That said, programs typically see eConsults work well for question patterns like these:

• Interpretation questions: an abnormal lab, imaging finding, or ECG where the ordering provider wants a specialist's read on significance and next steps
• Medication and management questions: starting, adjusting, or sequencing therapy for a condition the primary care provider will continue to manage
• Triage questions: whether a finding warrants an in-person specialty evaluation at all, and how urgently
• Pre-referral optimization: what workup the specialist would want completed before a visit, so that if a referral does happen, the first appointment is useful rather than a data-gathering session

That last pattern is worth underlining. Even when an eConsult ends in "send this patient to me," it often improves the referral: the specialist has effectively pre-screened the case, specified the workup, and implicitly accepted the patient. Given that specialist acceptance and response rates are a real failure point in referral networks, a referral that arrives pre-shaped by an eConsult tends to move faster.

When a referral is required

A referral, not an eConsult, is the fit when the patient needs something only an in-person specialty encounter can provide, per the ordering provider's judgment. Common patterns:

• A hands-on examination is needed to answer the question at all
• A procedure or specialist-performed test is the point of the visit (endoscopy, biopsy, injection, sleep study); the screening colonoscopy behind one of the hardest HEDIS measures to close is a referral, never an eConsult
• The condition needs ongoing specialty management rather than a one-time answer
• Urgency or severity makes an asynchronous exchange inappropriate
• The payer, program, or care model requires a documented specialist visit

Many organizations formalize this with specialty-specific guidance agreed between primary care and specialty leadership: which question types each specialty accepts by eConsult, and which should come straight through as referrals. That agreement is operational gold, because it moves the eConsult-or-refer decision from an ad hoc judgment call to a shared, teachable rule set, while leaving the final call with the ordering provider.

Reimbursement, briefly

eConsults are billable in many arrangements. Medicare recognizes interprofessional consultation services that compensate a consulting specialist for assessment and management provided through the record and communication with the treating provider, without a face-to-face visit; CMS finalized separate payment for that coding in the calendar year 2019 Physician Fee Schedule, and many commercial and Medicaid programs have followed with their own coverage policies. Requirements commonly include patient consent (since cost sharing can apply), a documented request and response, and time or content thresholds for the consulting clinician's work.

The safe operational posture: treat eConsult billing as payer-specific. Verify with each significant payer which interprofessional consultation services they cover, what documentation they require, and whether both the requesting and consulting clinicians can bill. In value-based arrangements the calculus often shifts again, because avoided specialty visits and faster answers carry value beyond fee-for-service revenue. Build the payer matrix once, keep it updated, and do not let coding folklore substitute for a written policy check.

What eConsults mean for the referral team

Here is the part that gets missed in clinical discussions of eConsults: someone operational has to run the combined pathway, and it is usually the referral team. A workable combined workflow looks like this:

1. Single front door. All specialty demand (eConsult requests and referrals) enters one triage queue, so nothing depends on the ordering provider remembering two systems.
2. Pathway triage. Requests are routed per the specialty-specific guidance: eligible questions to the eConsult pathway, everything else into standard referral intake with document collection and eligibility checks.
3. Turnaround tracking. eConsults get their own service-level clock (days, not weeks). An unanswered eConsult is a stalled patient just like an unscheduled referral, and it needs the same aging visibility.
4. Conversion handling. When a specialist's eConsult response says "this patient needs a visit," the conversion must create a referral automatically, carrying the eConsult exchange with it as clinical context. Conversions that rely on someone re-entering the request are the pathway's biggest leakage point.
5. Loop closure on both tracks. An eConsult closes when the response is documented and the ordering provider has acted on it; a referral closes when the visit happens and the note returns. Both need closure tracking, or the eConsult program quietly accumulates its own version of lost referrals.
6. Measurement. Track eConsult volume, turnaround time, conversion rate to referral, and the effect on specialty appointment lead times. The conversion rate in particular tells you whether the specialty guidance is calibrated: near-zero conversions may mean providers only send trivial questions, while very high conversions mean the eConsult step is just adding days before an inevitable referral.

The workload math matters too. eConsults reduce visit demand but add coordination work: routing, tracking, converting, closing. Teams already stretched by manual referral processing will feel a poorly tooled eConsult program as pure overhead.

That is also the argument for treating eConsults as part of your referral infrastructure rather than a separate program: the same referral coordination software disciplines (one queue, aging visibility, automated outreach, closed loops) are what keep the combined pathway from leaking.

The bottom line

eConsults and referrals answer different questions. An eConsult moves a focused clinical question to a specialist asynchronously and often resolves it without a visit; a referral moves the patient because an exam, procedure, or ongoing specialty management is needed. The choice between them belongs to the ordering provider, ideally guided by specialty-specific agreements. Operationally, the two pathways succeed or fail together: eConsults only relieve specialty access pressure when triage, turnaround tracking, and eConsult-to-referral conversion are run as one workflow with the same rigor as referral management itself.

Frequently asked questions

Sources

• CMS, Final Policy, Payment, and Quality Provisions Changes to the Medicare Physician Fee Schedule for Calendar Year 2019 (interprofessional internet consultation)
• American Medical Association, 2019 CPT codes offer new paths to payment for digital medicine
• AHRQ, Care Coordination (National Center for Excellence in Primary Care Research)