Strong public FHIR docs, a free sandbox and self-serve OAuth client IDs, plus an official MCP server. Production access is per health system: each customer activates your client ID and pays Epic for the APIs.
Epic Systems scores B on Supergood's API Report Card. Strong public FHIR docs, a free sandbox and self-serve OAuth client IDs, plus an official MCP server. Production access is per health system: each customer activates your client ID and pays Epic for the APIs.
Epic Systems has a workable official integration path. Most engineering teams can build against it directly. Solid API with minor gaps
Epic Systems Corporation, founded in 1979 and headquartered in Verona, Wisconsin, builds the Epic electronic health record.
Academic medical centers, community hospitals, integrated delivery networks, large multispecialty groups, children's hospitals and increasingly smaller hospitals through Community Connect affiliates. Clinicians chart, order, and review results in Hyperspace or Hyperdrive all day; registration, scheduling, HIM and billing staff work queues in the same system; patients message, schedule and view results in MyChart.
KLAS data reported by Becker's in May 2026 puts Epic at 43.7% of US acute care hospitals for 2025, up from 42.3%, after adding 77 hospitals. Epic says more than 325 million patients have a current record in Epic, and open.epic lists 3,508 live apps using its web services.
The full longitudinal patient chart (problems, medications, allergies, notes, orders, results, imaging reports), scheduling and ADT, registration and insurance coverage, hospital and professional billing, claims and remits, pharmacy, MyChart messaging, and analytics warehouses (Clarity, Caboodle).
Founded 1979, delivered through the Hyperspace thick client and the newer Hyperdrive web-based client. Epic ships quarterly versions; the FHIR sandbox was upgraded to the November 2026 version.
Particle Health's antitrust suit, summarized by the Sequoia Project, alleges Epic blocked its API-based record access and pressured customers; Epic denies it and the case is pending. On the HL7 FHIR chat, a developer objected that Epic app registration requires attestations unrelated to API security before a client ID is issued. Full sourced list under Sources below.
Common alternatives include Oracle Health (Cerner), Meditech, Athenahealth, eClinicalWorks, NextGen Healthcare. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Epic Systems is sold both ways: as a vendor-hosted cloud service and as an on-premises installation. The mix varies by customer. Each customer runs its own Epic instance, self-hosted or hosted by Epic's Hosting group or a partner, as described on open.epic and Epic Careers.
Epic Systems scores GOOD on MCP availability. Epic runs an official MCP server at mcp.open.epic.com that searches open.epic API specs and playbooks (no PHI), and documents Agent Factory connectors exposing USCDI v5 FHIR R4 APIs as MCP tools for authorized agents.
Yes. Epic Systems publishes an official MCP server, so MCP clients like Claude, Cursor, and Codex can connect to it directly. Setup instructions are in the vendor's documentation.