Interoperability and Health Data

Fast Healthcare Interoperability Resources (FHIR)

Description

The FHIR component enables the standardized exchange of healthcare data between systems, ensuring interoperability and communication consistency. It defines a flexible structure based on resources, representing clinical, administrative, and financial entities, allowing standardized communication across different platforms.

Example

  • The example flow retrieves a specific patient from the FHIR server using ID 596526 and returns the data in JSON format.

  • The integration is triggered by a GET request to a specific endpoint.

  • The request is forwarded to a FHIR server.

  • The retrieved resource is of type Patient and the patient identifier is 596526.

  • The data returned by the FHIR server is processed by the marshal EIP, converting the response to JSON format.

Script

Diagram

 
- from:
    uri: rest:get:/demo
    steps:
      - to:
          uri: fhir:read/resourceById
          parameters:
            serverUrl: http://hapi.fhir.org/baseR4
            resourceClass: Patient
            stringId: 596526
      - marshal:
          fhirJson: {}
component fhir

Guidelines for using the FHIR component

  • The component’s response will be placed in the body of the Exchange as a Java object.

    • The object varies depending on the API and protocol version used.

    • For the R4 version, the object will be in the package org.hl7.fhir.r4.model.

  • To use the object in other components, it must be converted to JSON using the EIP marshal.

    • Use the Data Format fhirJson.

    • The traditional JSON Data Format is not compatible with FHIR classes.

  • The component parameters do not support expressions to obtain a payload from the body.

    • To achieve this, use the inBody parameter.

  • Expressions cannot be used in just any field.

    • To parameterize values, use environment variables.

Thanks for your feedback!
EDIT

Share your suggestions with us!
Click here and then [+ Submit idea]