Appearance
Cerner FHIR
Access patient records, conditions, and medication requests via the Cerner (Oracle Health) FHIR R4 API.
| Detail | Value |
|---|---|
| Category | Healthcare |
| Base URL | https://fhir-open.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d |
| Authentication | OAuth2 |
| Endpoints | 3 |
| Connector key | cerner-fhir |
Using Cerner FHIR in a workflow
- Go to Connections and click New Connection.
- Pick Cerner FHIR from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /Patient | Search patients |
GET /Condition | Search conditions |
GET /MedicationRequest | Search medication requests |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /Patient
Search patients
| Detail | Value |
|---|---|
| Operation ID | healthcare.searchPatients |
| Method | GET |
| Path | /Patient |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
name | query | string | No |
birthdate | query | string | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Cerner FHIR connection from the Connection dropdown.
- In the Operation dropdown, select
healthcare.searchPatients. - 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 Cerner FHIR API reference.
GET /Condition
Search conditions
| Detail | Value |
|---|---|
| Operation ID | healthcare.listConditions |
| Method | GET |
| Path | /Condition |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
patient | query | string | No |
category | query | string | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Cerner FHIR connection from the Connection dropdown.
- In the Operation dropdown, select
healthcare.listConditions. - 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 Cerner FHIR API reference.
GET /MedicationRequest
Search medication requests
| Detail | Value |
|---|---|
| Operation ID | healthcare.listMedicationRequests |
| Method | GET |
| Path | /MedicationRequest |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
patient | query | string | No |
status | query | string | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Cerner FHIR connection from the Connection dropdown.
- In the Operation dropdown, select
healthcare.listMedicationRequests. - 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 Cerner FHIR API reference.