Epic Systems

Epic Systems Corporation is a privately held electronic health record (EHR/EMR) software company founded in 1979 and headquartered in Verona, Wisconsin, United States. Epic's software supports the medical records of a large share of U.S. hospital systems and academic medical centers, and its "Epic on FHIR" developer program (fhir.epic.com / open.epic.com) exposes a standards-based HL7 FHIR interoperability surface for patient- and provider-facing apps. Epic serves live, public sandbox FHIR endpoints across three FHIR versions - R4 (4.0.1), STU3 (3.0.1), and DSTU2 (1.0.2) - aligned to the US Core implementation guides, with SMART on FHIR / OAuth 2.0 authorization, CDS Hooks, and FHIR Bulk Data ($export) access. Production access requires client registration and a health system's participation; the developer sandbox, specifications, and CapabilityStatements are openly published. Epic is a core node of the U.S. healthcare interoperability landscape shaped by the ONC/CMS 21st Century Cures Act information-blocking rules and TEFCA.

Epic Systems is listed with 6 APIs on the APIs.io network. Tagged areas include Healthcare, United States, Electronic Health Records, FHIR, and HL7.

The Epic Systems catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Epic Systems’ developer surface includes pricing, engineering blog, documentation, API reference, getting-started guide, authentication, signup flow, and 30 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

61.4/100 strong ▬ flat Agent 38/100 agent ready Front door AI 4/6 moderate Heartbeat 93/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreeOpen⚡ Free to try

6 APIs 3 Agent Skills

Healthcare United States Electronic Health Records FHIR HL7 Interoperability SMART on FHIR US Core Clinical Data

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 61.4/100 · strong

Contract Quality 9.4 / 21

Developer Ergonomics 11.2 / 17

Access Clarity 10.3 / 17

Operational Transparency 8.1 / 11

Contract Governance 1.9 / 10

Discoverability 6.7 / 9

Regulatory Posture 7.3 / 15

Agent readiness — 38/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/epic-systems/"><img src="https://apis.io/badge/epic-systems/card.svg" alt="Epic Systems on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too

5 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 44.2 — up to +14.0 composite points
Contract Governance scores 18.2 — up to +9.8 composite points
Access Clarity scores 60.5 — up to +7.9 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/epic-systems/apis.yml: open an issue on github.com/api-evangelist/epic-systems to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Medical Technology (certified health IT, FDA-authorized AI devices)	coverage	54.7	-	-
Certified Health IT (health IT accreditation and certification registers)	coverage	54.7	-	-
IVD, Diagnostics and Surgical Devices (FDA / EU regulated device makers)	coverage	54.7	-	-
GA4GH Genomics Standards (htsget, DRS, TES, WES, Beacon, Passports)	coverage	54.7	-	-
Canada Medical Device Licensing (Health Canada MDALL licence holders, incl. SaMD)	coverage	54.7	-	-
FHIR Implementation Guides (HL7 FHIR package and IG publishers)	coverage	54.7	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

HL7 FHIR

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

SMART on FHIR

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

US Core

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 6

Individual APIs this provider publishes, each with its own machine-readable definition.

Epic FHIR R4 API

Epic's HL7 FHIR R4 (4.0.1) REST API, aligned to the US Core implementation guides and exposing 59 resource types (Patient, Encounter, Observation, Condition, MedicationRequest, ...

Epic FHIR STU3 API

Epic's HL7 FHIR STU3 (3.0.1) REST API for clinical and administrative resources, authorized with SMART on FHIR / OAuth 2.0. A live public sandbox CapabilityStatement was harvest...

Epic FHIR DSTU2 API

Epic's HL7 FHIR DSTU2 (1.0.2) REST API, published as a FHIR Conformance resource covering the legacy DSTU2 resource set. A live public sandbox Conformance statement was harveste...

Epic SMART on FHIR Authorization

Epic's SMART on FHIR / OAuth 2.0 authorization surface backing the FHIR APIs. The live .well-known/smart-configuration advertises authorize/token endpoints, grant types (authori...

Epic FHIR Bulk Data Access API

Epic's implementation of the HL7 FHIR Bulk Data Access (Flat FHIR) specification, providing backend system-level population export via the $export operation, authorized with OAu...

Epic CDS Hooks API

Epic's support for the CDS Hooks specification, letting external clinical decision support services return cards and SMART app launch links at documented workflow hook points in...

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Export a population from Epic with FHIR Bulk Data

AGENT SKILL

Read a patient's clinical record from Epic (patient-context SMART app)

AGENT SKILL

Write data back into an Epic chart

AGENT SKILL

Epic Systems API pricing

Prices published by Epic Systems. A free plan or tier is listed.

Plan	Price
Epic on FHIR	Free
Vendor Services	—

Plan details, limits and sources →

Rate limits

Daily document query ceiling: day
Patient.Search result cap: 100
Search result processing cap: 100

All 5 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Epic Systems Plans Pricing

2 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Epic Systems Rate Limits

5 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Epic Systems Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Epic Systems Cds Hooks Webhooks

ASYNCAPI

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Epic Systems Authentication

0 schemes

SECURITY

Epic Systems Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Epic Systems Vulnerability Disclosure

security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Epic Systems Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 5

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

SignUp

Sandbox

Portal

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 8

Pagination, idempotency, versioning, errors, and events

Conformance

Conventions

Idempotency

ErrorCatalog

DataModel

Lifecycle

Webhooks

ErrorCodes

Scroll for all 8

Build 1

SDKs, sample code, and the tooling you integrate with

Packages

Packages

Access & Security 6

Authentication, authorization, and security posture

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

Authentication

SecurityTxt

OAuthScopes

Security

Operate 4

Status, limits, changes, and where to get help

ChangeLog

Deprecation

RateLimits

Support

Commercial 4

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

Plans

PrivacyPolicy

Company 3

The organization behind the API

Blog

Blog

Website

Website

LinkedIn

Other 1

Properties that don't map to a standard resource type

APICatalog

APICatalog

Source (apis.yml)

aid: epic-systems
url: https://raw.githubusercontent.com/api-evangelist/epic-systems/refs/heads/main/apis.yml
name: Epic Systems
kind: company
description: Epic Systems Corporation is a privately held electronic health record (EHR/EMR) software company founded in 1979
  and headquartered in Verona, Wisconsin, United States. Epic's software supports the medical records of a large share of
  U.S. hospital systems and academic medical centers, and its "Epic on FHIR" developer program (fhir.epic.com / open.epic.com)
  exposes a standards-based HL7 FHIR interoperability surface for patient- and provider-facing apps. Epic serves live, public
  sandbox FHIR endpoints across three FHIR versions - R4 (4.0.1), STU3 (3.0.1), and DSTU2 (1.0.2) - aligned to the US Core
  implementation guides, with SMART on FHIR / OAuth 2.0 authorization, CDS Hooks, and FHIR Bulk Data ($export) access. Production
  access requires client registration and a health system's participation; the developer sandbox, specifications, and CapabilityStatements
  are openly published. Epic is a core node of the U.S. healthcare interoperability landscape shaped by the ONC/CMS 21st Century
  Cures Act information-blocking rules and TEFCA.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: free
  onboarding: open
  trial: false
  try_now: true
  public: true
  gated: none
  gated_source:
  - onboarding
  label: Free · Open access
  confidence: high
  source:
  - plans
  - authentication
  - scopes
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Healthcare
- United States
- Electronic Health Records
- FHIR
- HL7
- Interoperability
- SMART on FHIR
- US Core
- Clinical Data
tags_raw:
- Healthcare
- United States
- EHR
- EMR
- FHIR
- HL7
- Interoperability
- SMART on FHIR
- US Core
- Clinical Data
created: '2026-07-24'
modified: '2026-10-06'
specificationVersion: '0.23'
x-enrichment:
  date: '2026-08-14'
  status: enriched
  artifacts_added: 14
  pass: local-v1
apis:
- aid: epic-systems:epic-fhir-r4-api
  name: Epic FHIR R4 API
  description: Epic's HL7 FHIR R4 (4.0.1) REST API, aligned to the US Core implementation guides and exposing 59 resource
    types (Patient, Encounter, Observation, Condition, MedicationRequest, DiagnosticReport, DocumentReference, Appointment,
    Coverage, ExplanationOfBenefit, and more) with read, search-type, create, and update interactions. Authorized with SMART
    on FHIR / OAuth 2.0. A live public sandbox CapabilityStatement was harvested verbatim.
  humanURL: https://fhir.epic.com/Specifications
  baseURL: https://fhir.epic.com/interconnect-fhir-oauth/api/FHIR/R4
  tags:
  - FHIR
  - R4
  - US Core
  properties:
  - type: CapabilityStatement
    url: fhir/epic-fhir-r4-capabilitystatement.json
  - type: SMARTConfiguration
    url: fhir/epic-fhir-r4-smart-configuration.json
  - type: Documentation
    url: https://fhir.epic.com/Documentation?docId=fhirtutorial
  - type: APIReference
    url: https://fhir.epic.com/Specifications
  - type: Authentication
    url: https://fhir.epic.com/Documentation?docId=oauth2
- aid: epic-systems:epic-fhir-stu3-api
  name: Epic FHIR STU3 API
  description: Epic's HL7 FHIR STU3 (3.0.1) REST API for clinical and administrative resources, authorized with SMART on FHIR
    / OAuth 2.0. A live public sandbox CapabilityStatement was harvested verbatim.
  humanURL: https://fhir.epic.com/Specifications
  baseURL: https://fhir.epic.com/interconnect-fhir-oauth/api/FHIR/STU3
  tags:
  - FHIR
  - STU3
  properties:
  - type: CapabilityStatement
    url: fhir/epic-fhir-stu3-capabilitystatement.json
  - type: Documentation
    url: https://fhir.epic.com/Documentation?docId=fhirtutorial
  - type: APIReference
    url: https://fhir.epic.com/Specifications
  - type: Authentication
    url: https://fhir.epic.com/Documentation?docId=oauth2
- aid: epic-systems:epic-fhir-dstu2-api
  name: Epic FHIR DSTU2 API
  description: Epic's HL7 FHIR DSTU2 (1.0.2) REST API, published as a FHIR Conformance resource covering the legacy DSTU2
    resource set. A live public sandbox Conformance statement was harvested verbatim.
  humanURL: https://fhir.epic.com/Specifications
  baseURL: https://fhir.epic.com/interconnect-fhir-oauth/api/FHIR/DSTU2
  tags:
  - FHIR
  - DSTU2
  properties:
  - type: CapabilityStatement
    url: fhir/epic-fhir-dstu2-conformance.json
  - type: Documentation
    url: https://fhir.epic.com/Documentation?docId=fhirtutorial
  - type: APIReference
    url: https://fhir.epic.com/Specifications
  - type: Authentication
    url: https://fhir.epic.com/Documentation?docId=oauth2
- aid: epic-systems:epic-smart-on-fhir-authorization
  name: Epic SMART on FHIR Authorization
  description: Epic's SMART on FHIR / OAuth 2.0 authorization surface backing the FHIR APIs. The live .well-known/smart-configuration
    advertises authorize/token endpoints, grant types (authorization_code, refresh_token, client_credentials, jwt-bearer,
    token-exchange), SMART capabilities (launch-ehr, launch-standalone, client-confidential-asymmetric, permission-patient/user/v2),
    and OpenID Connect. Captured verbatim.
  humanURL: https://fhir.epic.com/Documentation?docId=oauth2
  baseURL: https://fhir.epic.com/interconnect-fhir-oauth/oauth2
  tags:
  - SMART on FHIR
  - OAuth
  - Authorization
  - Authentication
  tags_raw:
  - SMART on FHIR
  - OAuth2
  - Authorization
  - Authentication
  properties:
  - type: SMARTConfiguration
    url: fhir/epic-fhir-r4-smart-configuration.json
  - type: Documentation
    url: https://fhir.epic.com/Documentation?docId=oauth2
  - type: Authentication
    url: authentication/epic-systems-authentication.yml
- aid: epic-systems:epic-fhir-bulk-data-api
  name: Epic FHIR Bulk Data Access API
  description: Epic's implementation of the HL7 FHIR Bulk Data Access (Flat FHIR) specification, providing backend system-level
    population export via the $export operation, authorized with OAuth 2.0 client-credentials (asymmetric client authentication).
    Documented on Epic on FHIR; production access is client-registration and health-system gated.
  humanURL: https://fhir.epic.com/Documentation?docId=bulkdataaccesstutorial
  baseURL: https://fhir.epic.com/interconnect-fhir-oauth/api/FHIR/R4
  tags:
  - FHIR
  - Bulk Data
  - BackendServices
  tags_raw:
  - FHIR
  - Bulk Data
  - Backend Services
  properties:
  - type: Documentation
    url: https://fhir.epic.com/Documentation?docId=bulkdataaccesstutorial
  - type: APIReference
    url: https://fhir.epic.com/Specifications
- aid: epic-systems:epic-cds-hooks-api
  name: Epic CDS Hooks API
  description: Epic's support for the CDS Hooks specification, letting external clinical decision support services return
    cards and SMART app launch links at documented workflow hook points inside the Epic EHR. Documented on Epic on FHIR; production
    access is client-registration and health-system gated.
  humanURL: https://fhir.epic.com/Documentation?docId=cdshookstutorial
  baseURL: https://fhir.epic.com/interconnect-fhir-oauth
  tags:
  - CDS Hooks
  - Clinical Decision Support
  - SMART on FHIR
  properties:
  - type: Documentation
    url: https://fhir.epic.com/Documentation?docId=cdshookstutorial
  - type: APIReference
    url: https://fhir.epic.com/Specifications
common:
- type: Pricing
  url: https://fhir.epic.com/Documentation?docId=cms_prior_auth_playbook
- url: https://www.epic.com/epic/newsroom/
  type: Blog
- type: VulnerabilityDisclosure
  url: security/epic-systems-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/epic-systems-domain-security.yml
- type: Website
  url: https://www.epic.com/
- type: DeveloperPortal
  url: https://fhir.epic.com/
- type: Documentation
  url: https://fhir.epic.com/Documentation
- type: APIReference
  url: https://fhir.epic.com/Specifications
- type: GettingStarted
  url: https://fhir.epic.com/Documentation?docId=fhirtutorial
- type: Authentication
  url: authentication/epic-systems-authentication.yml
- type: SignUp
  url: https://fhir.epic.com/Developer/Index
- type: TermsOfService
  url: https://fhir.epic.com/Download/ApiLicenseAgreement
- type: LinkedIn
  url: https://www.linkedin.com/company/epic1979/
- type: WellKnown
  url: well-known/epic-systems-well-known.yml
- type: SecurityTxt
  url: well-known/epic-systems-security.txt
- type: OAuthScopes
  url: scopes/epic-systems-scopes.yml
- type: Conformance
  url: conformance/epic-systems-conformance.yml
- type: Conventions
  url: conventions/epic-systems-conventions.yml
- type: Idempotency
  url: conventions/epic-systems-conventions.yml
- type: ErrorCatalog
  url: errors/epic-systems-problem-types.yml
- type: DataModel
  url: data-model/epic-systems-data-model.yml
- type: Lifecycle
  url: lifecycle/epic-systems-lifecycle.yml
- type: Webhooks
  url: asyncapi/epic-systems-cds-hooks-webhooks.yml
- type: LLMsTxt
  url: llms/epic-systems-llms.txt
- type: Security
  url: https://www.epic.com/epic/page/reporting-potential-security-vulnerability/
- type: Packages
  url: packages/epic-systems-packages.yml
- type: Sandbox
  url: sandbox/epic-systems-sandbox.yml
- type: ErrorCodes
  url: errors/epic-systems-error-codes.yml
- type: ChangeLog
  url: changelog/epic-systems-changelog.yml
- type: Deprecation
  url: https://fhir.epic.com/Documentation?docId=developerguidelines
- type: RateLimits
  url: rate-limits/epic-systems-rate-limits.yml
- type: Plans
  url: plans/epic-systems-plans-pricing.yml
- type: AgentSkill
  url: skills/_index.yml
- type: APICatalog
  url: fhir/epic-systems-endpoint-catalog.yml
- type: Support
  url: https://open.epic.com/Home/Contact
- type: PrivacyPolicy
  url: https://www.epic.com/privacypolicies/
- type: Portal
  url: https://open.epic.com/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Epic Systems API — frequently asked questions

Does Epic Systems have an API?

Yes. APIs.io lists 6 APIs from Epic Systems, including Epic FHIR R4 API, Epic FHIR STU3 API and Epic FHIR DSTU2 API, and 3 more.

How do I authenticate with the Epic Systems API?

Epic Systems documents its authentication (0 schemes). The details are profiled on APIs.io as Epic Systems Authentication.

How much does the Epic Systems API cost?

APIs.io lists 2 pricing plans for Epic Systems, with each plan's price, limits and inclusions under Pricing on this page.

Is the Epic Systems API ready for AI agents?

Epic Systems has a Kin Score of 61.4 out of 100 (strong) and an Agent Readiness score of 37.6 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/epic-systems"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/epic-systems/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/epic-systems/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.