Skip to content
For LLMsView as Markdown·

Cerner FHIR

Access patient records, conditions, and medication requests via the Cerner (Oracle Health) FHIR R4 API.

DetailValue
CategoryHealthcare
Base URLhttps://fhir-open.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d
AuthenticationOAuth2
Endpoints3
Connector keycerner-fhir

Using Cerner FHIR in a workflow

  1. Go to Connections and click New Connection.
  2. Pick Cerner 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

EndpointSummary
GET /PatientSearch patients
GET /ConditionSearch conditions
GET /MedicationRequestSearch medication requests

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

GET /Patient

Search patients

DetailValue
Operation IDhealthcare.searchPatients
MethodGET
Path/Patient

Parameters

NameLocationTypeRequired
namequerystringNo
birthdatequerystringNo

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Cerner FHIR connection from the Connection dropdown.
  3. In the Operation dropdown, select healthcare.searchPatients.
  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 Cerner FHIR API reference.

GET /Condition

Search conditions

DetailValue
Operation IDhealthcare.listConditions
MethodGET
Path/Condition

Parameters

NameLocationTypeRequired
patientquerystringNo
categoryquerystringNo

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Cerner FHIR connection from the Connection dropdown.
  3. In the Operation dropdown, select healthcare.listConditions.
  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 Cerner FHIR API reference.

GET /MedicationRequest

Search medication requests

DetailValue
Operation IDhealthcare.listMedicationRequests
MethodGET
Path/MedicationRequest

Parameters

NameLocationTypeRequired
patientquerystringNo
statusquerystringNo

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Cerner FHIR connection from the Connection dropdown.
  3. In the Operation dropdown, select healthcare.listMedicationRequests.
  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 Cerner FHIR API reference.