One of the most common objections to dedicated referral management platforms goes like this: "We already have Epic — doesn't it handle referrals?" The short answer is: yes, for fee-for-service workflows. No, for value-based care performance.

EHRs are transaction systems built to document clinical encounters, manage billing, and support care coordination within a single health system's network. They're very good at what they were designed to do. But they were designed before in-network routing, claims-native specialist scoring, automated prior authorization, cross-EHR closed-loop tracking, and real-time referral analytics became operational necessities.

The result is that most organizations using their EHR's native referral functionality are flying VBC blind — they can place a referral order, but they can't see whether it went to the right specialist, whether it was authorized efficiently, whether the patient showed up, or what it cost relative to alternatives.

What EHR Referral Modules Do Well

  • Placing a referral order within the clinical workflow
  • Generating a referral summary document with relevant clinical notes
  • Sending the referral via Direct secure messaging to another EHR
  • Tracking referral orders within the same health system's EHR environment
  • Linking referral orders to billing and coding workflows

For fee-for-service, this is adequate. For VBC contracts — where in-network rates, cost per episode, and closed-loop performance are financial metrics — it's not.

The Seven Things EHRs Can't Do for VBC Referral Management

  1. Claims-native specialist scoring. EHRs rank specialists from provider directories, not claims data. They can't tell you which cardiologist in your market has the lowest total cost per episode or the best readmission rate.
  2. Real-time insurance verification at the moment of referral. EHR provider directories are updated periodically, not in real time. Verification at the moment of referral requires an API call to payer data that EHRs aren't designed to make.
  3. Cross-EHR closed-loop tracking. An EHR can close the loop within its own network. Most specialist visits happen outside that network. Cross-EHR loop closure requires a dedicated integration layer.
  4. Automated prior authorization inside the referral flow. EHR PA tools typically require leaving the referral workflow for a payer portal. Background submission requires purpose-built payer integrations.
  5. Inbound referral management for specialty practices. EHRs are built for the sending side. They have limited capability for specialty practices to consolidate inbound referrals from fax, Direct, email, and portal into a unified queue.
  6. VBC-specific referral analytics. EHR reporting tells you how many orders were placed. It can't tell you in-network rate, cost per referral, closed-loop performance, or financial impact on VBC contracts.
  7. AI-driven specialist matching across multiple patient-specific factors. Scoring by cost, quality, availability, SDoH, language, proximity, and loop-closing compliance simultaneously requires ML infrastructure outside the EHR's core competency.

How ReferralPoint Works With Your EHR — Not Instead of It

The right framing isn't "replace your EHR" — it's "extend your EHR for VBC." ReferralPoint operates entirely inside the EHR workflows your team already uses. When a coordinator opens a referral order in Epic, athena, or eCW, IdealMATCH pushes the optimal in-network specialist into the "Refer To" field automatically — no second screen, no separate portal. Prior auth submits in the background. Closed-loop status returns to the EHR without duplicate data entry. The EHR stays the system of record; ReferralPoint adds the VBC intelligence layer.

Frequently Asked Questions

Q: Can Epic's referral module handle value-based care referral management? A: Epic's referral module handles the transactional basics — placing orders, sending referral summaries, tracking orders within the Epic network. For VBC-specific requirements like claims-native specialist scoring, real-time insurance verification, cross-EHR closed-loop tracking, and automated prior authorization, a dedicated referral management platform like ReferralPoint is required. ReferralPoint integrates with Epic via the Epic Showroom and works inside Epic's existing workflows.

Q: What is the difference between a referral order and referral management? A: A referral order is a clinical transaction — a physician instructing that a patient be seen by a specialist. Referral management is the end-to-end process of ensuring that order goes to the right specialist, is authorized, results in a scheduled appointment, generates clinical data, and closes the loop with the referring provider. EHRs handle referral orders well; dedicated platforms handle the full management lifecycle.

Q: Does ReferralPoint replace the EHR? A: No. ReferralPoint works inside the EHR — pushing specialist recommendations, automating prior auth, and closing loops directly within existing EHR workflows. The EHR remains the system of clinical record. ReferralPoint adds the VBC intelligence, automation, and analytics layer.

Q: Which EHRs does ReferralPoint integrate with? A: ReferralPoint integrates with Epic, athenahealth, eClinicalWorks, NextGen, Altera Digital Health, Veradigm, and 20+ additional EHRs through its parent company Lightbeam Health Solutions. Integration methods include Direct Message, API, FHIR, HL7, CDA, and CCD.