Epic FHIR

Access electronic health records, patient data, and clinical observations via the Epic FHIR R4 API.

Detail	Value
Category	Healthcare
Base URL	https://fhir.epic.com/interconnect-fhir-oauth/api/FHIR/R4
Authentication	OAuth2
Endpoints	3
Connector key	epic-fhir

Using Epic FHIR in a workflow

1. Go to Connections and click New Connection.
2. Pick Epic FHIR from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /Patient/{id}	Get a patient by ID
GET /Observation	Search observations
GET /Encounter	Search encounters

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /Patient/{id}

Get a patient by ID

Detail	Value
Operation ID	healthcare.getPatient
Method	GET
Path	/Patient/{id}

Parameters

Name	Location	Type	Required
id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Epic FHIR connection from the Connection dropdown.
3. In the Operation dropdown, select healthcare.getPatient.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Epic FHIR API reference.

GET /Observation

Search observations

Detail	Value
Operation ID	healthcare.listObservations
Method	GET
Path	/Observation

Parameters

Name	Location	Type	Required
patient	query	string	No
category	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Epic FHIR connection from the Connection dropdown.
3. In the Operation dropdown, select healthcare.listObservations.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Epic FHIR API reference.

GET /Encounter

Search encounters

Detail	Value
Operation ID	healthcare.listEncounters
Method	GET
Path	/Encounter

Parameters

Name	Location	Type	Required
patient	query	string	No
date	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Epic FHIR connection from the Connection dropdown.
3. In the Operation dropdown, select healthcare.listEncounters.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Epic FHIR API reference.