Epic and Greenway Intergy differ most clearly in how their interoperability documentation is structured and what each vendor states about API capabilities. Epic's public materials describe a broad set of standards-based interfaces, FHIR resources, and Epic-specific web services, with a federated model in which each customer controls connections. Greenway's developer documentation describes a FHIR R4 API that currently supports read operations only, alongside a proprietary Greenway API with reads and writes for Intergy and Prime Suite. A direct feature-for-feature comparison is limited because the available sources do not provide equivalent detail on Intergy's interface inventory, transaction volumes, or customer-specific configurations. Buyers should treat vendor statements as claims and verify current capabilities against their own integration requirements.
Documented FHIR Support and Current Limitations
Epic's technical specifications state that the software includes support for a range of DSTU2, STU3, and R4 read, search, and write resources, with continued additions [1]. The vendor also describes participation in the Argonaut Project and Da Vinci Project and support for FHIR Bulk Data for population-level exports [1]. Epic's August 2026 release notes mention support for USCDI v5 and US Core 8, including new resources for advance directives, patient care experience preferences, and medication adherence information [8]. These statements describe documented capabilities, not a guarantee that every Epic customer has enabled every resource.
Greenway's developer platform overview states that the Greenway FHIR API provides a subset of FHIR resources compliant with 21st Century Cures Act requirements [9]. A separate note specifies that the current Greenway FHIR API supports read operations only at the present time [9]. The reference documentation lists read endpoints for resources such as AllergyIntolerance, CarePlan, Condition, DiagnosticReport, Encounter, Immunization, MedicationRequest, Observation, Patient, Practitioner, and Procedure [11]. Greenway also states that support for more FHIR resources will be added over time [9]. The documentation does not provide a comparable list of write-enabled FHIR resources for Intergy.
Proprietary APIs and Write Capabilities
Epic describes Epic Private Technologies as extensions for cases where no appropriate industry standard exists, available to developers in the Vendor Services program [1]. The vendor also lists purpose-built Epic-specific web services for needs such as patient lookup, personnel management, e-signature, credit card integration, and enterprise image access [7]. Epic states that it prioritizes industry-standard APIs but developed private APIs to address specific needs [1]. These private APIs are not presented as a single unified product API but as a set of services with separate technical specifications.
Greenway describes the Greenway API, or GAPI, as a proprietary API with separate and distinct API calls and data structures for each EHR product [9]. The documentation states that GAPI supports reads and writes across a variety of clinical and financial data elements [9]. This is a meaningful distinction from the FHIR API, which is currently read-only [9]. However, the Greenway overview does not enumerate which specific clinical or financial data elements support writes through GAPI for Intergy. A buyer evaluating write workflows should request a detailed endpoint list from Greenway rather than assume parity with Epic's private web services.
Suggested Workflow for a Buyer Evaluation
A buyer could structure the comparison around three documented decision points. First, determine whether the required data exchange is read-only or requires writes. If writes are needed, Epic's FHIR documentation describes write resources [1], while Greenway's FHIR API is currently read-only and writes would require GAPI [9]. Second, identify the connection model. Epic requires per-customer client ID syncing [6], while Greenway requires an opt-in request and minimum version check for FHIR services [10]. Third, request the missing documentation. Ask Greenway for Intergy's C-CDA, Direct, and document exchange specifications, and ask Epic for the specific private web services relevant to the planned workflow. This approach avoids assuming that one vendor's broader public documentation automatically translates into easier implementation for a particular practice.
Connection Models and Customer Control
Epic uses a federated model in which every customer runs an independent Epic instance and decides which apps can connect [6]. There is no central Epic endpoint for data exchange [6]. Developers register a client ID with Epic, and customers may then request that the client ID be synced to their instance; app developers can directly approve these requests without involvement from Epic [6]. This means that integration availability can vary by customer, even when Epic publishes a specification. Epic also states that each month more than 45 billion messages are sent between Epic and non-Epic systems, with over 60,000 active interfaces and more than 2,000 vendors [1].
Greenway's documentation describes a different onboarding path for FHIR services. Intergy or Prime Suite systems must be on a minimum version that changes annually, and practices must submit an opt-in request through records.greenwayhealth.com [10]. The documentation states that activation takes up to 15 days on average, with large practices potentially taking longer [10]. For Intergy sites, the Site ID is the Intergy License number [10]. This opt-in process suggests that FHIR access is not automatically available to every Intergy customer and depends on version and request completion. The documentation does not state whether GAPI access follows the same opt-in process.
Document Exchange and Clinical Interoperability
Epic's EHR to EHR documentation describes support for IHE Cross-Community Patient Discovery, Cross-Community Access, and Cross-Enterprise Document Sharing profiles [3]. Epic states that its EHR can consume any valid C-CDA or CDA document and can create HL7/ASTM CCD and HL7/IHE Consolidated CDA documents [3]. The vendor also describes Direct protocol support for sending and receiving structured documents, with additional elements for closing the referral loop [3]. Diagnostic image exchange is described as available only for treatment and only to organizations with a point-to-point connection to a healthcare organization using Epic [3].
Greenway's public developer documentation does not provide an equivalent inventory of C-CDA, Direct, XCA, or XDS.b capabilities for Intergy. The FHIR reference includes a Generate CCD endpoint under DocumentReference [11], but the documentation does not describe the full range of document exchange profiles or transport methods. This absence does not mean Intergy lacks those capabilities; it means the retrieved Greenway sources do not document them. A buyer comparing document exchange should request Intergy's interface specifications directly from Greenway and verify them against the specific trading partners and use cases involved.
Scale Claims and What They Do Not Establish
Epic's interoperability page states that organizations use Care Everywhere to exchange over 30 million patient records daily, with around half of those exchanges involving organizations that use a different interoperable EHR [2]. The page also reports 1,014 million records exchanged per month, 33 million patient record documents exchanged daily between health systems, and 337 billion web service transactions in the last year using Epic's publicly available APIs [2]. Epic further states that 100% of Epic customers are interoperable [2]. These figures are vendor-reported and reflect the Epic community as a whole, not a comparison with Greenway Intergy.
Greenway's documentation does not publish comparable transaction volume or interface count figures for Intergy. The Greenway materials describe FHIR access enabling over 80 third-party applications via the Greenway AppGallery [10], but this is a count of listed applications, not a measure of exchange volume or clinical interoperability depth. MedtechLedger analysis cannot calculate a meaningful volume comparison from the public documents because Greenway does not report equivalent metrics. Buyers should not interpret Epic's larger published scale as evidence of better fit for a specific practice; scale claims describe community activity, not the quality or completeness of a particular integration.
Sources & references
- open.epic :: Technical Specifications · open.epic.com
- Interoperability | Epic · www.epic.com
- EHR to EHR clinical information interfaces · open.epic.com
- open.epic :: Design Overview · open.epic.com
- open.epic :: Design Overview · open.epic.com
- open.epic :: Developer Resources · open.epic.com
- open.epic :: Explore By Interface Type · open.epic.com
- open.epic · open.epic.com
- Greenway Health APIs - An Overview · developers.greenwayhealth.com
- Introduction to FHIR · developers.greenwayhealth.com
- Getting started · developers.greenwayhealth.com
- Discover Intergy Suite: EHR and Practice Management | Greenway Health · www.greenwayhealth.com