Saltar al contenido principal

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​

NameTypeRequiredDescription
search_paramsjsonNoSearch parameters as key-value pairs
resource_idtextNoResource ID for read/update operations
resourcejsonNoFHIR resource object for create/update operations
family_nametextNoPatient family name for patient_search
given_nametextNoPatient given name for patient_search
birthdatetextNoPatient birth date for patient_search
identifiertextNoPatient identifier for patient_search

Output ports​

NameTypeRequiredDescription
resultjsonNoMain result data from the Cerner FHIR operation
metadatajsonNoResponse metadata including resource type, counts, and operation details
successbooleanNoWhether the operation succeeded

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Cerner Base URLcerner_base_urlstringYesBase URL of the Cerner Millennium instance
OperationoperationenumYessearchsearch, read, patient_search, create, updateFHIR operation to perform
Resource Typeresource_typestringNoPatientFHIR resource type to operate on

Auth​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Client IDclient_idsecretYesOAuth2 client ID for Cerner authentication
Client Secretclient_secretsecretYesOAuth2 client secret for Cerner authentication
Tenant IDtenant_idstringNoCerner tenant ID (sent as X-Cerner-Tenant header)

Advanced​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Search Parameterssearch_paramsjsonNoDefault search parameters as key-value pairs
Reverse IncluderevincludestringNoFHIR _revinclude parameter for search
CountcountnumberNoMaximum number of results to return
Resource IDresource_idstringNoResource ID for read operations (can also come from input)

Errors​

CodeDescription
CERNER_AUTH_FAILEDFailed to obtain OAuth2 token from Cerner
CERNER_SEARCH_FAILEDCerner FHIR search returned an error
CERNER_CREATE_FAILEDCerner rejected the resource creation
CERNER_UPDATE_FAILEDCerner rejected the resource update
RESOURCE_ID_REQUIREDresource_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.

¿Algo no está claro? Envíe sus comentarios sobre la documentación por correo electrónico..