The API Report CardAPI Index
Epic Systems

Epic Systems API

Enterprise EHR for hospitals, health systems and large medical groups · epic.com

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.

Last verified: November 2026HealthcareMCP READYHYBRID
API GRADE
B
VERIFIED NOV 2026

SCORECARD

ExistenceGOODopen.epic and fhir.epic.com publish FHIR R4, HL7 v2 and Epic public API specs with a no-code Try It sandbox.
AccessMIXEDClient IDs are self-serve, but each Epic customer must download and activate the app before production calls work.
CoverageGOODUSCDI FHIR R4 read plus Create on several resources, bulk FHIR, CDS Hooks, FHIRcast and HL7 v2 interfaces.
AuthGOODSMART on FHIR OAuth 2.0 for patient, provider and backend apps, with JWT client credentials for system access.
Docs & DXGOODTutorials, sandbox test patients, Hyperdrive test harness, API change log and the mcp.open.epic.com docs server.
StabilityGOODQuarterly sandbox upgrades track Epic releases; DSTU2, STU3 and R4 versions stay listed side by side.
MCPGOODEpic 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. fhir.epic.com ↗ VERIFIED 2026-11
Supergood turns hard-to-integrate enterprise software into clean REST APIs and MCP tools: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

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.

Tried to integrate with Epic Systems?
SOURCES
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. sequoiaproject.org ↗
On the HL7 FHIR chat, a developer objected that Epic app registration requires attestations unrelated to API security before a client ID is issued. chat-archive.fhir.org ↗
Integration consultancy Nirmitee notes developers pay for Vendor Services and support hours, while health systems separately pay Epic for each production API subscription. nirmitee.io ↗
A 2025 PLOS Digital Health perspective argues Epic's dominance creates technical lock-in where interoperability works best for organizations already inside the Epic ecosystem. pmc.ncbi.nlm.nih.gov ↗
The Sequoia Project tracks a 2025 State of Texas suit alleging Epic acts as a gatekeeper over medical records and restricts interoperability; Epic disputes the claims. sequoiaproject.org ↗