Cerner FHIR
Category: EHR & Practice Mgmt
Node id: cerner-fhir
Standards: HIPAA, GDPR, SOC2
Integrates with Oracle Cerner Millennium via FHIR R4 API for searching, reading, creating, and updating clinical resources
What it does
- OAuth2 client credentials authentication for Cerner Millennium
- FHIR R4 search, read, create, and update operations
- Multi-tenant support via X-Cerner-Tenant header
- Automatic X-Request-Id generation for request tracing
- Patient-specific search by demographics
- _revinclude support for related resource retrieval
Use cases
- Integrate Cerner Millennium clinical data into analytics pipelines
- Create and update patient records in Oracle Cerner via FHIR
- Search Cerner for patients across multiple tenants
- Retrieve related resources using reverse includes
Runtime
- Performance tier:
variable
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
search_params | json | No | Search parameters as key-value pairs |
resource_id | text | No | Resource ID for read/update operations |
resource | json | No | FHIR resource object for create/update operations |
family_name | text | No | Patient family name for patient_search |
given_name | text | No | Patient given name for patient_search |
birthdate | text | No | Patient birth date for patient_search |
identifier | text | No | Patient identifier for patient_search |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Main result data from the Cerner FHIR operation |
metadata | json | No | Response metadata including resource type, counts, and operation details |
success | boolean | No | Whether the operation succeeded |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Cerner Base URL | cerner_base_url | string | Yes | Base URL of the Cerner Millennium instance | ||
| Operation | operation | enum | Yes | search | search, read, patient_search, create, update | FHIR operation to perform |
| Resource Type | resource_type | string | No | Patient | FHIR resource type to operate on |
Auth
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Client ID | client_id | secret | Yes | OAuth2 client ID for Cerner authentication | ||
| Client Secret | client_secret | secret | Yes | OAuth2 client secret for Cerner authentication | ||
| Tenant ID | tenant_id | string | No | Cerner tenant ID (sent as X-Cerner-Tenant header) |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Search Parameters | search_params | json | No | Default search parameters as key-value pairs | ||
| Reverse Include | revinclude | string | No | FHIR _revinclude parameter for search | ||
| Count | count | number | No | Maximum number of results to return | ||
| Resource ID | resource_id | string | No | Resource ID for read operations (can also come from input) |
Errors
| Code | Description |
|---|---|
CERNER_AUTH_FAILED | Failed to obtain OAuth2 token from Cerner |
CERNER_SEARCH_FAILED | Cerner FHIR search returned an error |
CERNER_CREATE_FAILED | Cerner rejected the resource creation |
CERNER_UPDATE_FAILED | Cerner rejected the resource update |
RESOURCE_ID_REQUIRED | resource_id is required for read/update operations |
Runtime notes
- create and update operations set resourceType on the resource automatically from the config — do not rely on it being in the input resource
- A unique X-Request-Id header is generated per execution for Cerner request tracing
- patient_search returns both bundle and a flat patients array; search returns only bundle; read returns a single resource
- metadata.status is 'created' or 'updated' for write operations — use this to distinguish in downstream logic
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
Something unclear? Send documentation feedback by email.