Saltar al contenido principal

FHIR Client

Category: Healthcare Standards: FHIR R4 · SMART on FHIR · HIPAA · TLS 1.2+

Universal FHIR R4 client with SMART on FHIR authentication

What this node does

  • SMART on FHIR OAuth2
  • PKCE
  • Search/Read/Create/Update/Delete
  • Batch operations
  • Patient summary

How to use

  1. In the Agentic Studio, open or create a workflow
  2. In the node palette on the left, find FHIR Client under the Healthcare category (or use the search bar)
  3. Drag the node onto the canvas
  4. Double-click the node to open its configuration dialog
  5. Fill in the required parameters (see Configuration below)
  6. Connect the Operation Parameters input port from an upstream node
  7. Optionally connect the Access Token port if needed
  8. Connect the FHIR Result and FHIR Bundle and Error output to the next node downstream

Inputs

PortTypeRequiredDescription
Operation ParametersjsonJSON data object
Access TokentextOptionalPlain text string

Outputs

PortTypeDescription
FHIR Resultfhir-resourceA single FHIR R4 resource (Patient, Observation, etc.)
FHIR Bundlefhir-bundleA FHIR R4 Bundle containing one or more resources
ErrorerrorError information if the operation failed

Configuration

Open the configuration dialog by double-clicking the FHIR Client node on the canvas.

ParameterWhat to enter
baseUrlBase URL of the FHIR server, e.g. https://fhir.example.com/r4
authentication (SMART/OAuth2)Authentication method: SMART on FHIR (recommended) or standard OAuth 2.0
operation typeFHIR operation type: read, search, create, update, or delete
resourceTypeThe FHIR resource type to operate on, e.g. Patient, Observation
search parametersFHIR search parameters as key-value pairs
batch operationsEnable batch mode to process multiple resources in a single request

When to use this node

  • Connect to any FHIR R4 server
  • Patient data retrieval
  • Clinical data queries
  • Multi-resource batch operations

Need help configuring this node?

Go to Settings → Connectors to set up the connection this node depends on, then reference the connector ID in the node configuration dialog.