The 2026 Guide to Epic Nexus: What Healthcare CIOs Must Know Now

In the U.S., a nationwide data-sharing network is emerging to break down silos between hospitals, clinics, and patient apps. The federal Trusted Exchange Framework and Common Agreement, created under the 21st Century Cures Act, defines a “network-of-networks” linking health information exchanges via Qualified Health Information Networks. 

TEFCA has driven exponential growth in data exchange: roughly 10 million documents had been shared through TEFCA by 2024, surging to 464 million by the end of 2025. 

Today’s Epic-centric QHIN, Epic Nexus, sits at the heart of this network, enabling Epic EHR users to connect seamlessly to other systems.

• TEFCA and its QHINs are redefining interoperability for CIOs. 
• Under TEFCA, any organization can join a QHIN and gain immediate access to query and retrieve patient records across the country. 
• Crucially for Epic sites, Epic Nexus is a TEFCA-designated QHIN built by Epic Systems specifically for the Epic EHR community. 
• All Epic hospitals and clinics will eventually connect through Epic Nexus, giving them a single nationwide exchange on-ramp with minimal technical setup. 
• Other networks are also QHINs, but Epic Nexus lets Epic-based organizations exchange data among themselves and with any other QHIN network automatically. 
• In practice, that means an Epic user needs only to onboard to Epic Nexus, once live, that organization can query any patient record held in any other TEFCA network.

The energy in the Epic community has been high: by mid-2025, over 1,000 Epic hospitals and 22,000 clinics were live on Epic Nexus, and Epic expects all of its 2,000 U.S. hospital customers (and hundreds of thousands of clinicians) to be on Epic Nexus by the end of 2025.

What Is Epic Nexus QHIN?

Epic Nexus launched in December 2023 as one of the first TEFCA QHINs. It leverages Epic’s long experience in interoperability. Today, Epic Nexus provides secure, standards-based connectivity so that when, for example, a hospital using Epic needs records for a patient who has been seen elsewhere, it can send a TEFCA query through Epic Nexus and get back a record summary from the other provider’s EHR. Epic’s Interoperability Director reports that TEFCA is breaking down long-standing barriers for data exchange, especially for rural and underserved facilities. 

By reducing admin burden, Epic Nexus helps any participating provider “connect quickly” to the national network. Stanford Health Care, an early Epic Nexus pilot site, explained that TEFCA “extends the integrated interoperability” providers expect and ensures clinicians have “the patient’s full story at the point of care” for better diagnoses and care plans. In other words, for CIOs, Epic Nexus represents a proven solution to get Epic-based systems exchanging seamlessly across the country.

What Is TEFCA and How Do QHINs Enable Nationwide Health Data Exchange? 

TEFCA grew out of a Congressional mandate to create a “trusted exchange framework” for all Americans’ health data. The Office of the National Coordinator led the design, and The Sequoia Project now serves as the Recognized Coordinating Entity. TEFCA’s Common Agreement defines the policies, technical specs, and governance for connectivity. Under TEFCA, QHINs are designated networks that connect directly to each other. Each QHIN has its own participants and subparticipants. 

By design, a query sent to one QHIN can be routed to any other QHIN, and vice versa. This means providers no longer need dozens of point-to-point interfaces – once in TEFCA, a single connection covers the entire nation.

TEFCA supports six “exchange purposes” that define why data can be requested. Relevant use cases include: Treatment, Individual Access Services, and Public Health reporting. Other purposes, like Payment or Government Benefits determination, exist but are still evolving. Epic organizations can and do use Epic Nexus for at least the treatment and patient-access purposes. 

• For example, Epic’s QHIN serves as the gateway for Epic sites to respond to inbound treatment queries from other systems. 
• And under IAS, a patient’s MyChart-linked device can send a FHIR request to Epic Nexus to retrieve the patient’s own records from all linked hospitals. 
• In late 2026, Epic plans to launch “MyChart Central,” a feature that lets patients aggregate data from all of their Epic-connected providers at once via FHIR, greatly simplifying personal health record retrieval. 
• Public health use is also supported: Epic Nexus participates in TEFCA’s case reporting flows so that laboratories and hospitals can electronically report notifiable conditions through Epic.

For CIOs, the rapid adoption of TEFCA means the technical and regulatory groundwork is already laid. The TEFCA network provides directory and lookup services, standardized data formats, and a consistent security framework across QHINs. In other words, connecting to Epic Nexus means immediately participating in the same national framework as thousands of other providers. 

The federal government has even incentivized TEFCA participation: CMS made TEFCA data exchanges count toward hospital interoperability requirements. This alignment means that by enabling Epic Nexus, CIOs can simultaneously advance their interoperability initiatives and satisfy evolving regulations.

Epic Nexus QHIN in 2026: Scale, Status, and CIO Priorities 

Epic Nexus QHIN Rollout Across Epic Health Systems 

By 2026, the Epic Nexus QHIN has attained critical mass. Epic reports that 41% of its customers were live on Nexus by mid-2025 (over 1,000 hospitals and 22,000 clinics), with 43% implementing and the rest planning. This reflects roughly half of all U.S. Epic sites already connected. 

Epic’s goal was for all customers to transition to TEFCA by the end of 2025 – given the progress, most large systems are now onboard. The Epic Nexus network itself, launched in Dec 2023, is now federating data for broad use cases. For perspective, Epic holds about 42% of the U.S. hospital EHR market, so bringing all those sites into TEFCA via Nexus represents a major share of national data.

Key Health Systems and Participants Using Epic Nexus QHIN 

Many of the nation’s leading health systems were early adopters of Epic Nexus TEFCA exchange. Stanford Health Care, Johns Hopkins, Mayo Clinic, Kaiser Permanente, and other renowned systems joined initial Epic Nexus cohorts. 

Community hospitals and rural systems have followed; for example, OCHIN went live on Epic Nexus in 2024 to ensure its community health centers and CAHs could share data nationwide. Epic’s internal metrics show that Epic-enabled case reporting and public health use cases have also begun via Nexus. With big systems and safety-net hospitals connecting, almost any Epic customer can now query or be queried via Nexus QHIN.

Supporting QHINs and Health Data Sharing Networks 

While Epic Nexus serves Epic shops, the TEFCA model is an interconnected network. There are now at least eight or nine designated QHINs. Initial QHINs approved in 2023 included Epic Nexus, eHealth Exchange, CommonWell Health Alliance, Health Gorilla, KONZA, Kno2, MedAllies, and eClinicalWorks. Since then, Surescripts was designated in early 2025, with Oracle Health and possibly others following. 

Importantly, any Epic system joining Epic Nexus can now exchange with any of these other networks, so even non-Epic organizations on other QHINs can easily reach Epic data via TEFCA’s mesh. This broad QHIN landscape means that Epic CIOs should consider Epic Nexus as their primary connection, but they should also stay aware of how TEFCA aligns with other frameworks.

How Epic Nexus QHIN Works for Epic EHR Interoperability 

Standards-Based TEFCA Exchange for Nationwide Data Sharing 

Epic Nexus and TEFCA rely on industry-standard protocols. Queries and data exchange use IHE (Integrating the Healthcare Enterprise) and HL7 FHIR standards under the hood. 

• For traditional document exchange, TEFCA initially used IHE profiles across QHINs, similar to existing HIE networks. 
• In practice, an Epic site sending a treatment query via Nexus will use the common workflow: an “XCPD” query locates which Epic systems the patient is in, then the system issues a request for a Consolidated CDA from those sources. 
• Epic’s internal QHIN technical framework adheres to the TEFCA QHIN Technical Framework requirements, ensuring all data is USCDI-compliant and routed securely via TEFCA services.

FHIR, APIs, and Epic Nexus Integration 

Crucially, Epic Nexus is built to support FHIR-based exchange, especially for patient-directed access and future expansions. Epic’s FHIR implementation is robust: Epic provides FHIR R4 resources with SMART-on-FHIR authorization for third-party apps. 

TEFCA stages 1 and 2 have already introduced FHIR content in bundles. Epic Nexus participates as a FHIR Responding Node for IAS, meaning that when a patient app requests the patient’s Epic data via TEFCA, the app uses OAuth2 (SMART on FHIR) to fetch FHIR resources from the Epic site. 

In late 2026, Epic will roll out MyChart Central, which allows a patient to link all their Epic-provider accounts and then trigger one FHIR query for the whole patient history across providers. This exemplifies the modern API approach: a patient’s mobile device (as a FHIR “client”) authenticates with Epic, then Nexus locates all relevant records and returns them via FHIR-compliant bundles.

FHIR Epic Integration: Development and Implementation Readiness 

Epic also supports custom integrations. Its developer portal provides documentation and sandboxes for OAuth2 and FHIR integration. 

CIOs should ensure any third-party or in-house apps are registered on the Epic on FHIR program and have appropriate scopes. Security is paramount: Epic’s APIs enforce TLS and OAuth2 with SMART scopes. 

• For Epic Nexus specifically, the QHIN handles routing queries, but each Epic hospital still needs to configure its interfaces. 
• Epic’s documentation notes that organizations must complete an API subscription agreement and set the “Participates in TEFCA” flag on the site profile to become active on Nexus. 
• While much of the heavy lifting is done by Epic’s network team, CIOs should still coordinate with Epic’s client services and their internal IT staff to provision certificates and test endpoints.

Epic Nexus QHIN Implementation Considerations for Health Systems 

For CIOs and IT leaders running Epic, Epic Nexus QHIN is an opportunity and a multi-step project. Key strategic considerations include:

Onboarding to Epic Nexus

Epic typically manages the QHIN onboarding process as part of its annual builds. Organizations must sign the updated Epic Nexus QHIN Participation Agreement, designate a site to host the Nexus service, and coordinate with Epic project managers. 

Many large systems have already completed this by 2025; others are scheduled in waves through Epic’s user group meetings. CIOs should confirm their status and timeline in Epic’s roadmaps.

Technical Setup

On the technical side, ensure that interfaces for TEFCA are configured. This involves turning on TEFCA/HIO codes in the Epic interface engine, deploying any required certificates for secure TLS communication with Epic Nexus servers, and verifying that FHIR endpoints are reachable through the organization’s firewalls/VPNs. Epic support may request test transactions. 

Additionally, organizations should review the required US Core Data for Interoperability data elements that must be shareable. Most Epic sites already capture these in their records, but the organization must confirm that all needed data is marked as shareable.

Exchange Policies and Training

Connecting to Epic Nexus also means adhering to TEFCA policies. CIOs should coordinate with compliance teams to understand information-blocking exceptions and privacy policies. Staff and clinicians need to be made aware that patient data can now flow more freely: for instance, a physician may receive query results from a distant clinic via Nexus. 

Training should clarify when and how to use Epic’s Care Everywhere button versus TEFCA queries, and educate care managers about patients’ rights to retrieve all data. From a patient’s perspective, HIT/CIO teams may need to update patient-facing materials to explain new portal capabilities.

Use Case Integration

Strategically, CIOs should incorporate TEFCA-based exchange into care pathways. For example, when scheduling an outpatient procedure for a transferred patient, the admitting hospital can now use Epic Nexus to fetch prior visit summaries automatically. 

For care transitions in rural areas, Epic Nexus means local hospitals can retrieve digital charts from referral centers. Hospitals that are funneling data to public health can now tap into TEFCA for redundant reporting as well. Similarly, organizations par. A best practice is to identify 2–3 priority workflows and design Epic Nexus usage around them.

Governance and Support

On the governance front, health system CIOs should maintain a seat at the table in TEFCA governance. The Sequoia Project and Epic itself hold periodic calls about TEFCA and QHIN issues; IT leadership should ensure representation so that any policy changes are communicated. 

In the Epic ecosystem, each “Epic community” member signs the Common Agreement automatically through their participation, but hospitals should still ensure their legal/compliance teams have reviewed the latest TEFCA terms. On the technical side, as the TEFCA network evolves, CIOs should plan future work. 

For instance, Stage 3 will require QHIN-to-QHIN FHIR API support, which means Epic Nexus will eventually need to act as both sender and receiver of FHIR queries between QHINs. Epic’s roadmap indicates readiness for this, but health systems may want to test these new flows in 2026.

Below is a checklist to guide Epic healthcare CIOs in 2026:

1. Verify Epic Nexus Enrollment: Confirm your organization’s onboarding status and timeline with Epic.
2. Complete Agreements: Ensure you have signed the Epic Nexus QHIN Participation Agreement and that your legal/IT teams have reviewed the TEFCA terms.
3. Enable Data Access: Configure Epic to share the required USCDI elements for TEFCA use cases. Update access controls.
4. Test Technical Interfaces: Work with Epic to test an XCPD patient discovery query and a FHIR record retrieval. Validate certificates, firewall rules, and OAuth2 configurations.
5. Train Staff: Educate clinical and IT staff on new workflows. Distinguish between Epic’s Care Everywhere and TEFCA exchanges. Inform patients about new portal features like MyChart Central.
6. Monitor & Measure: Track TEFCA metrics. Epic and The Sequoia Project offer dashboards for the number of documents shared, query volume, etc. Use these to show ROI.
7. Stay Compliant: Incorporate TEFCA use into your Information Blocking and Privacy/Consent policies. Leverage TEFCA exchanges for quality reporting as allowed by CMS rules.
8. Plan Next Phases: Keep an eye on upcoming capabilities: QHIN-to-QHIN FHIR APIs, bulk data for population health, and expanded exchange purposes. Prepare IT budgets and projects accordingly.

Real-World Impact of Epic Nexus QHIN on Hospital Health Data Sharing 

Epic Nexus is already making a difference in real health systems. 

For instance, OCHIN reported that joining TEFCA via Epic Nexus has “seamlessly” enabled their Epic sites to exchange clinical summaries with other TEFCA participants, even with providers on non-Epic platforms. Before, many OCHIN members had limited data exchange options with distant specialists or labs; now, a single TEFCA query can reach providers nationwide. 

OCHIN’s director of interoperability noted that this has been especially valuable for their rural patients, who often travel long distances for care. Moreover, OCHIN’s TEFCA participation also ensures that patients who receive their records via an approved IAS app will get a unified view of all their medical history in OCHIN, without having to manually combine information. This is a practical fulfillment of TEFCA’s promise: empowering patients and eliminating gaps in care.

Similarly, major academic centers like Stanford Health Care have praised the TEFCA exchange for improving clinical decision-making. Having “the patient’s full story at the point of care” through TEFCA-driven data helped his teams make better diagnoses and care plans. TEFCA gives its clinicians a broader reach, improving care by providing “a larger breadth and depth of patient electronic health information for a more holistic understanding” of the patient. 

These anecdotes reflect quantitative benefits too: By mid-2025, the Nexus QHIN exchange had already closed millions of care gaps by bringing external data into Epic workflows. For example, if a patient had a lab result done elsewhere, it now appears in the local EHR via a TEFCA query instead of being lost.

Epic Nexus QHIN Challenges and Practical Solutions for CIOs 

No major IT initiative is without challenges. CIOs have voiced some concerns with TEFCA and Epic Nexus, but solutions are emerging:

• Ensuring data quality and consistent patient matching across QHINs is critical. CIOs should work with their informatics teams to align patient-matching strategies and test them. The Epic technical framework uses XCPD, which requires high match rates; Epic and The Sequoia Project provide conformance tools to help.
• As Epic connects to many QHINs, each with its own rules, CIOs must manage multiple interfaces. In reality, Epic Nexus abstracts much of that complexity; queries flow through Nexus and return results – but CIOs should still track if and when specific QHIN policies change. It may help to document the end-to-end flow and have a cross-team working group (IT + care management + legal) overseeing any issues.
• Some sites worry about performance: what if every Epic site suddenly gets 1000 queries a day? In practice, Epic Nexus implements throttling and logging, and thus far QHIN traffic has been modest at most sites. CIOs should coordinate with Epic on capacity planning.
• Clinicians will only use TEFCA if it’s easy. In Epic’s interface, a doctor still clicks a button to pull external records, but now the lookup goes via Nexus. The key is minimizing extra clicks and educating staff. Success stories can help drive adoption.

In summary, CIOs should see Epic Nexus/TEFCA not as “yet another project,” but as a strategic enabler. The network is operational and growing fast, and leading systems are already deriving value. Epic’s market dominance means Nexus will capture much of the available data, creating a virtuous cycle: the more Epic customers join, the more data is accessible, and the more useful the network becomes. 

The remaining considerations are mainly managerial and technical details, which can be addressed through planning and incremental rollout.

Nationwide Health Data Exchange and the Future of Epic Interoperability 

Looking ahead, Epic Nexus and TEFCA are set to expand further. In 2026, TEFCA Stage 3 will require QHIN-to-QHIN exchange of FHIR resources, enabling any Epic Nexus participant to query another QHIN’s FHIR APIs directly. ONC is piloting this in 2025, and Epic’s roadmap suggests readiness for these flows. 

Additional exchange purposes are also coming: ongoing pilots are exploring TEFCA use for Prior Authorization, Quality Improvement, and even Payment data. Epic healthcare systems should watch these developments; for example, if insurers begin to request medical records via TEFCA, Epic Nexus will be the mechanism to respond.

Meanwhile, interoperability remains a broader initiative. Carequality has officially aligned with TEFCA, meaning data exchange policies will converge. Epic will continue supporting Carequality (its existing networks), but it sees TEFCA as the future “single on-ramp”. For CIOs, the guidance is clear: prioritize Epic Nexus TEFCA onboarding now to be ready for these advances.

Checklist for CIOs:

• On-Ramp: Ensure Epic Nexus QHIN participation.
• Standards: Verify USCDI and FHIR endpoints are enabled in Epic.
• Training: Educate clinicians and informatics teams on TEFCA workflows.
• Data: Map out which external data should flow in and confirm it appears correctly.
• Compliance: Align TEFCA usage with CMS/HHS rules.
• Monitoring: Use Sequoia Project dashboards and Epic’s reports to track query volumes and response quality.
• Governance: Establish a governance group to review any policy changes.
• Future-Proof: Plan for Stage 3 FHIR exchange and explore bulk FHIR APIs for population health.

By mid-2026, CIOs will look back and recognize that Epic Nexus QHIN was a pivotal step toward true nationwide interoperability. With tens of thousands of Epic providers already connected, patient data can flow as easily as an email. For the largest health systems, Epic Nexus provides immediate access to the full breadth of Epic-based care and beyond. 

For smaller and rural hospitals, it means bridging previously disconnected networks. And for patients, it delivers on the promise of having all their records at their fingertips. Epic Nexus is the proven solution that CIOs and IT leaders must implement now to stay ahead in the era of seamless healthcare data exchange.

CapMinds Epic Interoperability Service for Nationwide Health Data Exchange

Epic Nexus QHIN gives healthcare CIOs a stronger path toward TEFCA-aligned data exchange, but successful participation depends on more than enrollment. 

CapMinds helps hospitals, IDNs, and healthcare organizations plan, build, integrate, secure, and optimize the digital health infrastructure needed for scalable interoperability.

Our digital health tech services support every layer of the exchange journey, including:

• Epic EHR interoperability strategy and implementation
• TEFCA and QHIN readiness consulting
• HL7, FHIR, SMART on FHIR, and API integration
• EHR, HIE, LIS, RIS, PACS, payer, and third-party system connectivity
• Patient identity, data mapping, validation, and migration support
• Interface engine development using Mirth Connect and other platforms
• Compliance, security, audit, and data governance services
• Cloud infrastructure, monitoring, analytics, and managed support

CapMinds also delivers custom healthcare software development, patient portals, telehealth platforms, RPM solutions, RCM integrations, healthcare analytics, automation workflows, and more.

Whether you need to connect Epic with external networks, modernize legacy interfaces, prepare for nationwide data exchange, or build a long-term interoperability roadmap, CapMinds provides the technical depth and healthcare domain expertise to make it work reliably at scale.

Book a Free Strategy Call