Epic's open.epic.com resources describe a federated interoperability model in which external developers connect directly to individual Epic customer environments rather than to a central Epic endpoint. The documentation spans interface specifications, FHIR guidance, developer onboarding steps, and vendor-facing web services. This profile focuses on documented technical capabilities and implementation boundaries, distinguishing vendor statements from technical specifications. [1][6][8]

Interoperability Architecture and Scale

Epic's technical documentation states that each month more than 45 billion messages are sent between Epic and non-Epic systems, with over 60,000 active interfaces involving more than 2,000 vendors. The company describes interfaces compliant with international standards that can support real-time exchange. Epic's interoperability page reports that organizations use Care Everywhere to exchange over 30 million patient records daily, with around half of those exchanges involving organizations using a different interoperable EHR. [1][2]

The open.epic.com homepage presents additional scale figures, including 10.0 billion annual patient records exchanged, with 55% going to non-Epic organizations, and 376 billion annual interface transactions using standards-based interfaces. These are vendor-reported statistics and should be read as marketing claims rather than independently verified measurements. [8]

Standards-Based Exchange Options

Epic's specifications describe support for HL7 FHIR across DSTU2, STU3, and R4 read, search, and write resources. The company states it participates in HL7 standards development and is a member of the Argonaut Project and the Da Vinci Project. The technical documentation also covers FHIR Bulk Data for population-level exports and FHIRcast for synchronizing context across applications. [1]

For clinical document exchange, Epic's EHR-to-EHR documentation describes CDA as the content standard for patient summary documents, with support for consuming valid C-CDA or CDA documents and creating HL7/ASTM CCD and HL7/IHE Consolidated CDA documents. The Direct protocol is documented for sending structured documents with XDR/XDM options. Diagnostic Image Exchange uses the FHIR R4 ImagingStudy resource and WADO-RS for DICOM image retrieval, available only for treatment and only to organizations with a point-to-point connection. [3]

Planning a Connection to an Epic Customer

Epic's design overview recommends that developers first define the discrete data types their app will exchange, including specific data elements such as dosage information or RxNorm codes. Next, developers should determine the direction of exchange, whether reading from Epic, writing to Epic, or both. The documentation cautions that when writing data to Epic, additional care is needed to ensure data is accurate, complete, and documented on the correct patient, because improper use may create patient safety and data integrity concerns. [4][5]

A hypothetical demonstration could involve a developer building a medication reconciliation app. The developer would define medication data elements, determine that the app reads medication lists from Epic and writes reconciliation status back, select FHIR as the exchange method for on-demand queries, register a client ID on open.epic.com, test against the Sandbox, and then coordinate deployment with a specific Epic customer. This scenario is illustrative and does not describe a documented Epic product or guaranteed outcome.

Developer Onboarding and Federated Access

Epic's developer resources describe a federated model where every customer runs an independent Epic instance and decides which apps can connect. There is no central Epic endpoint for data exchange. Developers obtain client IDs from open.epic.com, and customers may request that the client ID be synced to their instance. App developers can directly approve these requests without involvement from Epic. [6]

The documented developer guide outlines a sequence of steps: data sharing design, registering a client record, developing and testing, customer implementation and going live, and requesting a Showroom listing. Testing options include no-code API calls through the Sandbox, SMART on FHIR app launch testing via OAuth2, and Hyperdrive connection testing for web-based applications embedded in Epic. [6]

Epic-Specific Web Services

Epic states that it prioritizes industry-standard APIs but has developed Epic Private Technologies for cases where no appropriate industry standard exists. These private APIs are available to developers in the Vendor Services program. The web services documentation describes purpose-built integrations for coding workflows, patient lookup and identifiers, enterprise image access, e-signature, and credit card and bank account integration. [1][7]

The design overview recommends using industry standards whenever possible, with examples including NCPDP for pharmaceutical data and DICOM for medical images. Epic-specific methods are positioned as extending industry standards for particular use cases. OAuth 2.0 is described as the preferred security method for apps where Epic users interact with data, while TCP/IP connections and TLS/SSL certificates are common for system-to-system connections. [4][5]

Versioned FHIR Capabilities and Regional Scope

Epic's August 2026 release notes describe support for USCDI v5 and US Core 8. Documented enhancements include new DocumentReference, Binary, and Observation resources for advance directives, Observation resources for patient care experience preferences, and _lastUpdated search parameters for DiagnosticReport and Observation resources. The notes also mention extending MedicationAdministration support to all regions, indicating that some capabilities are versioned or regionally scoped. [8]

The release notes state that upcoming APIs include support for improved prior authorization flows and staff duress notifications, both described as coming in February 2026. Epic also describes playbooks supporting the CMS-0057 Interoperability and Prior Authorization Final Rule. These statements are vendor announcements about planned or versioned functionality, not guarantees of current availability across all customer environments. [8]