Skip to main content

FHIR_CONNECTIONS_FILE

Applies to​

  • Community v3.1.0+
  • Enterprise v3.1.0+

Default​

./connections.yml (relative to server working directory)

Examples​

# Use default location in working directory
FHIR_CONNECTIONS_FILE=./connections.yml

# Use an explicit absolute path
FHIR_CONNECTIONS_FILE=/etc/fume/connections.yml

# Use inline base64-encoded YAML instead of a file
FHIR_CONNECTIONS_FILE=ZmhpcjoKICAtIG5hbWU6IHB1YmxpY0ZoaXIKICAgIGJhc2VVcmw6ICJodHRwczovL3I0LnNtYXJ0aGVhbHRoaXQub3JnIg==

Purpose​

Defines the source for the YAML document that contains named alternate FHIR server connections used by $useFhirServer(). The value can be either a filesystem path or an inline base64-encoded YAML document.

Notes​

  • If unset, FUME reads ./connections.yml.
  • If the configured value resolves to an existing file, FUME loads that file.
  • Otherwise, FUME treats the configured value as an inline base64-encoded YAML document.
  • Missing file paths are ignored, so FUME still starts with no named connections.
  • Relative paths are resolved from the server process working directory.
  • The YAML document must use a top-level fhir: node.
  • ${ENV_VAR} placeholders are resolved after the file is read or the base64 payload is decoded.
  • Restart the server after changing this value.
  • For schema and examples, see Named FHIR Connections.