Academy
⌘K
Getting Started
  • Platform Overview
  • AWS Marketplace Setup
  • Quickstart Guide
Connections
  • Overview
Workflow Builder
  • Overview
  • Nodes Catalog
Helix AI Assistant
  • Overview
Mapping Engine
  • Overview
Workflow Library
  • Overview
  • HL7
  • FHIR
  • Insurance
  • Agentic
  • Mapping
Security & Infrastructure
  • Architecture
  • HIPAA Compliance
  • Performance & Scalability
← Back to ConnectHealth
Get Started
Back to Nodes
SMART Auth1 input → 1 output

Backend to Backend

msg (object)SMART AuthBackend to BackendaccessToken (string)payload.access… (string)_auth (object)Data flowProperty

Backend authentication node for system-level SMART on FHIR/EHR integrations.

Overview

This node generates JWT bearer tokens for backend (system-to-system) authentication with EHR systems. It's designed for workflows that need to access EHR data without user interaction, using pre-configured service credentials. A fresh token is generated for each request to ensure maximum security.

Configuration

Name string
Display name for this node instance
Scopes string
Override the default scopes. Common backend scopes include:
  • system/*.read - Read all resource types
  • system/Patient.read system/Observation.read - Specific resources
  • system/*.write - Write access (use with caution)
Output Format select
  • Token Only: Outputs just the access token
  • Full Response: Includes token metadata, expiry time, scopes, and caching information

Inputs

msg object
Any input message triggers token generation. The input message is passed through with the token added.

Outputs

msg.accessToken string
The generated access token (always included for backward compatibility)
msg.payload.access_token string
The generated access token
msg.payload object
In full response mode, includes:
  • token_type - Usually "Bearer"
  • expires_in - Token lifetime in seconds
  • scope - Granted scopes
  • generated_at - Timestamp when token was generated
  • expires_at - Timestamp when token expires
  • integration_id - The integration used
msg._auth object
Internal auth context for downstream nodes (not shown in debug)

Requirements

This node requires:

  • An integration configured with backend type
  • JWKS private key and public key configured in the integration
  • Proper scopes configured for the desired operations

Usage Example

Typical workflow:

  1. Inject node (trigger) → Backend Auth → FHIR Read → Debug
  2. The Backend Auth node generates/caches a token
  3. FHIR nodes use the token for API calls

Error Handling

The node will report errors for:

  • Missing integration context
  • Integration not configured for backend auth
  • Missing JWKS configuration
  • Token generation failures
  • Network issues

Security Notes

  • Backend tokens have system-level access - use appropriate scopes
  • A fresh token is generated for each request to ensure maximum security
  • Each integration uses separate credentials
  • Tokens are not cached - this provides better security but may impact performance