Quick answer
A health system that runs Epic or Oracle Health in the hospital and athenahealth, eClinicalWorks, or NextGen in its acquired practices does not have one referral workflow; it has several, and referrals leak at every seam between them. The practical fix in 2026 is an EHR-agnostic referral orchestration layer that connects to each system through Direct, API, FHIR, HL7, CDA, and CCD, matches the specialist on claims data regardless of which chart the order came from, handles authorization and scheduling centrally, and writes status back into whichever EHR the referring and receiving clinicians use. ReferralPoint is built for exactly this and connects to 20+ EHRs. Native modules cannot do it because each one stops at its own boundary.
Key takeaways
- Acquisitions create multi-EHR networks faster than consolidation removes them; plan for mixed EHRs as the steady state.
- Leakage concentrates at EHR boundaries — the referral leaves one chart and never lands in the other.
- One matching engine across all EHRs is how a network steers in-network consistently.
- Central prior auth and scheduling teams only work if the platform writes back to every chart.
- Reporting has to be network-wide, by specialty and provider, not per EHR instance.
Why multi-EHR networks leak referrals
Consider a regional system: Epic in the hospital and employed specialty clinics, athenahealth in a 60-provider primary care group acquired two years ago, eCW in three community health centers it manages, and NextGen in an affiliated orthopedics group. A primary care referral from the athena group to the system's own Epic cardiology clinic is, from the EHR's point of view, an external referral. It leaves athena as a fax or a Direct message, arrives in a queue, and is keyed into Epic by hand. The athena provider never sees the consult note unless someone faxes it back.
Multiply that by every specialty and every pair of systems. The result is a network that is in-network on paper and out-of-network in practice — not because clinicians choose outside specialists, but because the referral never completes.
What an EHR-agnostic layer has to do
| Requirement | Why it matters in a multi-EHR network | What to require from the vendor |
|---|---|---|
| Connect to every EHR you run | Partial coverage leaves the seams open | Live integration list; Direct, API, FHIR, HL7, CDA, CCD |
| One matching engine | Steerage has to be consistent regardless of which chart the order came from | Claims-native scoring by cost, quality, access, geography, language |
| Central prior authorization | A shared auth team needs one queue, not five portals | Requirements check, documentation pull, submission, tracking |
| Central patient scheduling | Patients should be contacted the same way regardless of origin | Automated outreach and booking |
| Inbound intake across systems | Referrals between your own EHRs still arrive by fax | AI fax and call intake with chart creation in the receiving EHR |
| Write-back to both ends | The sender and the receiver each need status in their own chart | Order status and consult note returned to the originating EHR |
| Network-wide reporting | Leadership manages the network, not the instance | In-network rate, leakage, time to appointment by specialty and provider across all EHRs |
How ReferralPoint runs a referral across EHRs
ReferralPoint sits above the EHRs and executes the referral end to end. When the athena primary care provider orders the cardiology referral, Auto IdealMATCH scores the system's Epic cardiologists and community cardiologists on the same claims-native criteria and recommends the best in-network option. Auto PriorAUTH works the authorization centrally. Auto ReferralCOORDINATOR contacts and schedules the patient. On the receiving side, the referral arrives as a chart and order in Epic rather than a fax; after the visit, acceptance, completion, and the consult note return to the athena record. Auto 360° VISIBILITY and NetworkMANAGEMENT report the whole network in one view.
Coverage: Epic, athenahealth, eClinicalWorks, NextGen, Oracle Health, MEDITECH, Altera, Veradigm, and 20+ EHRs through parent company Lightbeam Health Solutions. See integration and security. Proof: Privia Medical Group North Texas — a multi-practice network — reached a 92% in-network rate and cut referral cost 45%.
Guides for each EHR in your network
- Epic
- athenahealth
- eClinicalWorks
- NextGen
- Oracle Health (Cerner)
- Roundup: top referral management solutions in your EHR
A 90-day plan for a mixed-EHR network
- Weeks 1–2: map the seams. List every EHR, every clinic on it, and the top ten referral pairs between systems by volume. Pull out-of-network rate and open-referral aging for each pair.
- Weeks 3–6: connect the highest-volume pair. Typically acquired primary care into employed specialty. Prove write-back in both directions on real referrals.
- Weeks 7–10: centralize authorization and scheduling. Move the shared team onto one queue; measure auth cycle time and time to appointment against baseline.
- Weeks 11–13: extend and report. Add the next pairs and stand up network-wide reporting for operations and value-based care leadership.
Our general implementation framework is at referral management implementation roadmap, and the test plan at EHR referral software implementation test plan.
Bottom line
Mixed EHRs are the normal condition of a growing health system, and native referral modules stop at their own boundary. An EHR-agnostic orchestration layer is how the network behaves like one network. Request a demo to see ReferralPoint run a referral from one of your EHRs into another and back.
FAQ
Q: Can one referral management platform work across Epic, athenahealth, eClinicalWorks, and NextGen? A: Yes. ReferralPoint connects to 20+ EHRs through Direct, API, FHIR, HL7, CDA, and CCD and manages referrals between them from one layer, writing status back to each chart.
Q: Why do referrals leak between a health system's own EHRs? A: Because each EHR treats a referral to a practice on another system as external — it leaves as a fax or message, is keyed by hand on the other side, and rarely returns a consult note. The patient may be seen in-network, but the loop never closes, and many are never seen at all.
Q: Should a health system consolidate EHRs before fixing referrals? A: Consolidation takes years and acquisitions keep adding systems. An EHR-agnostic referral layer works during and after consolidation and does not depend on it.
Q: How does centralized prior authorization work across multiple EHRs? A: The platform pulls requirements and documentation from the originating chart, submits and tracks the request from one queue, and writes the decision back, so a shared authorization team is not logging into each EHR and each payer portal.
Q: What should a multi-EHR referral RFP require? A: A live integration list covering every EHR you run, one claims-native matching engine, central auth and scheduling, inbound intake with chart creation in the receiving EHR, write-back to both ends, and network-wide reporting by specialty and provider.
Q: Does ReferralPoint replace any of the EHRs? A: No. Each EHR remains the system of record for its clinics. ReferralPoint adds matching, authorization, scheduling, intake, and cross-EHR loop closure on top of all of them.
Sources and notes
EHR native capabilities are described generically and vary by version, configuration, and contract; they were not independently verified for this post. The regional system example is illustrative. ReferralPoint capabilities and outcomes are from our public product pages and sourced metrics.
