Saltar al contenido principal

FHIR Webhook

Category: Trigger
Node id: fhir-webhook

Trigger node for FHIR R4 Subscription notifications with resource type and event filtering

What it does​

  • Parses FHIR R4 Subscription notification Bundles
  • Handles direct resource notifications (non-Bundle)
  • Extracts SubscriptionStatus event type from Bundle entries
  • Extracts focus resource from notification entries
  • Filters by FHIR resource type (e.g., Patient, Observation)
  • Filters by subscription event type (e.g., event-notification)
  • Accepts raw JSON body string with automatic parsing

Use cases​

  • Trigger a pipeline when a new Patient is created in the FHIR server
  • React to Observation changes for real-time clinical decision support
  • Filter FHIR subscription events to process only specific resource types
  • Integrate with FHIR R4 Subscription framework for event-driven workflows

Runtime​

  • Performance tier: fast

Input ports​

NameTypeRequiredDescription
notificationjsonNoFHIR notification object (Subscription Bundle or direct resource). In production, injected by the webhook receiver. For testing, provide via a test fixture or input override.
raw_bodytextNoRaw JSON string of the webhook body. Alternative to notification — the node parses it automatically.

Output ports​

NameTypeRequiredDescription
resultjsonNoNotification data (notification bundle, focus_resource, resource_type, event_type, filtered)
successbooleanNoWhether the trigger fired successfully

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Filter Resource Typefilter_resource_typestringNoOnly accept notifications for this FHIR resource type (e.g., Patient). Empty accepts all.
Filter Eventfilter_eventstringNoOnly accept notifications with this event type. Empty accepts all.

Errors​

CodeDescription
MISSING_NOTIFICATIONNeither notification object nor raw_body was provided
INVALID_NOTIFICATION_BODYraw_body could not be parsed as valid JSON

Runtime notes​

  • TRIGGER NODE: In production, notification/raw_body is injected by the FHIR webhook receiver. For pipeline testing, you MUST add a test fixture or input override with a sample FHIR notification.
  • When filtered=true, focus_resource is absent and reason explains the filter mismatch
  • Accepts both FHIR R4 Subscription Bundle notifications and direct resource payloads
  • Downstream nodes should check result.filtered before processing focus_resource

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..