Epic on FHIR API
★ Only Publicly Available OpenAPI DocumentHealthcareEhr EmrapiKey4 EndpointsREST
For Agents
Search and retrieve patient demographics, clinical observations (labs, vitals), and medication requests from Epic-connected health systems via FHIR R4 resources.
Use for: I need to look up a patient in an Epic health system, Retrieve lab results for a specific patient from Epic, I want to get a patient's current medication list from Epic, Search for a patient by MRN in an Epic-connected hospital
Not supported: Does not handle appointment scheduling, clinical note authoring, or billing — use for read-only patient data retrieval (demographics, labs, medications) only.
Jentic publishes the only available OpenAPI specification for Epic on FHIR API, keeping it validated and agent-ready. Retrieve patient demographics, clinical observations, and medication requests from Epic-connected health systems using FHIR R4 resources. The API provides read access to Patient, Observation, and MedicationRequest resources, enabling interoperable health data retrieval from one of the largest EHR networks in the United States serving over 305 million patient records.
Install Jentic One Beta
Connect the Epic on FHIR API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Epic on FHIR API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Epic on FHIR API.
Search patients by name, date of birth, identifier, or other demographics across Epic-connected systems
Retrieve individual patient records with full FHIR R4 Patient resource including contact and insurance information
Query clinical observations including lab results, vital signs, and social history by patient and category
Fetch active and historical medication requests with dosage, prescriber, and status details
Access health data from over 305 million patient records across Epic-connected organizations
Use Cases
Patterns agents use Epic on FHIR API for, with concrete tasks.
★ AI Agent FHIR Data Retrieval
AI agents access Epic patient data through Jentic using FHIR R4 resources without manually configuring Epic's authentication or endpoint discovery. An agent searches for 'retrieve patient from Epic' and Jentic returns the Patient resource schema with required parameters. The agent executes the query and receives standardized FHIR JSON, enabling health data workflows across Epic's network of hospitals and clinics.
Search for patient John Smith by name using GET /Patient with family=Smith and given=John, then retrieve their latest hemoglobin lab observation
Patient Record Lookup
Search and retrieve patient demographics from Epic-connected health systems using standard FHIR search parameters. The Patient resource supports search by name, date of birth, identifier (MRN), gender, and address. Results return full FHIR R4 Patient resources with telecom, address, and managing organization details for care coordination.
Search for patients with last name 'Garcia' and date of birth '1985-03-15' using GET /Patient, then retrieve the full record for the matching patient ID
Clinical Observations and Lab Results
Query Observation resources to retrieve lab results, vital signs, and other clinical measurements for a specific patient. FHIR Observations are categorized by type (laboratory, vital-signs, social-history) and include value, units, reference ranges, and interpretation codes. Supports date range filtering for longitudinal clinical trend analysis.
Retrieve all Observation resources of category 'laboratory' for patient ID abc123 from the last 90 days and list any values flagged as abnormal
Medication History Review
Fetch active and completed medication requests for medication reconciliation and drug interaction checking. The MedicationRequest resource includes drug name, dosage instructions, prescriber, dispensing pharmacy, and status. Supports filtering by status (active, completed, stopped) for current medication list generation.
Get all active MedicationRequest resources for patient ID xyz789 and list the drug names, dosages, and prescribing providers
Key Endpoints
4 endpoints — jentic publishes the only available openapi specification for epic on fhir api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/Patient
Search patients by demographics
GET
/Patient/{id}
Get a specific patient by ID
GET
/Observation
Query clinical observations and lab results
GET
/MedicationRequest
Get medication requests and prescriptions
GET
/Patient
Search patients by demographics
GET
/Patient/{id}
Get a specific patient by ID
GET
/Observation
Query clinical observations and lab results
GET
/MedicationRequest
Get medication requests and prescriptions
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Epic API keys and SMART on FHIR tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive pre-configured authorization headers — raw credentials and client secrets never enter the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'retrieve patient labs from Epic') and Jentic returns matching FHIR resource operations with their query parameter schemas, so the agent can construct the correct request without navigating Epic's FHIR documentation.
Time to first call
Direct Epic integration: 2-4 weeks for app registration, credential setup, and FHIR endpoint configuration per organization. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Epic on FHIR API through Jentic.
Why is there no official OpenAPI spec for Epic on FHIR API?
Epic does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Epic on FHIR API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Epic on FHIR API use?
The Epic on FHIR API uses an API key passed in the Authorization header. In practice, Epic implementations typically use SMART on FHIR (OAuth 2.0-based) for production access with client credentials or authorization code flows depending on the app type. Through Jentic, credentials are stored in the MAXsystem vault and agents receive pre-configured authorization headers.
Can I retrieve lab results with the Epic on FHIR API?
Yes. The GET /Observation endpoint returns clinical observations including lab results when queried with category=laboratory and a patient reference. Results include LOINC codes, numeric values with units, reference ranges, and interpretation flags (normal, abnormal, critical).
How many patient records can I access through Epic on FHIR?
Epic's network serves over 305 million patient records across connected hospitals and health systems. Access depends on your application's registration with individual Epic organizations. Each organization grants access to their patient population through the FHIR endpoint.
How do I search for a patient through Jentic?
Search Jentic for 'look up patient in Epic' to discover the GET /Patient endpoint. The agent loads the schema which accepts search parameters like family (last name), given (first name), birthdate, and identifier (MRN). Install via pip install jentic and use the search-load-execute flow to query without manual configuration.
What FHIR resources does the Epic on FHIR API support?
This spec covers Patient (demographics and identifiers), Observation (labs, vitals, social history), and MedicationRequest (prescriptions and medication orders). These three resources cover the core clinical data retrieval use cases for patient-facing and provider-facing applications.
GET STARTED