FUME Enterprise release notes
FUME Enterprise is the commercially supported FUME package that includes the backend FUME Enterprise Server and the FUME Designer web interface.
The publicly hosted FUME Playground is based on the latest version of FUME Enterprise.
v3.1.1
Release date: May 20, 2026
Summary
FUME Enterprise v3.1.1 improves production logging reliability, adds an explicit file-logging opt-out, and picks up parser and FHIR package installation fixes from the bundled engine stack. It also refreshes dependencies and moves the Docker image base to wolfi-base to reduce known vulnerability exposure.
Engine version
This Enterprise release bundles @outburn/fume-engine v3.1.1 (spec: ^3.1.1).
- Public engine notes: FUME Community v3.1.1
Highlights
- Preserve full readable message content in rotating file logs, including metadata and splat fields.
- Improve stdout/stderr mirroring into log files while eliminating duplicate console log output.
- Add
FUME_FILE_LOGGINGto control Enterprise file logging. It defaults totrue; set it tofalsefor stdout-only deployments. - When
FUME_FILE_LOGGING=false, Enterprise disables rotating file logs and stdout/stderr file mirroring while continuing to write process logs to stdout/stderr for platform collection. - Update through
fumifier@2.3.1to fix wildcard (*) assignment parsing in FLASH rules and improve parser recovery-mode error handling. - Update FHIR package tooling to improve locking for concurrent installs in shared caches and prefer pinned extension/terminology package versions over implicit latest-version fallback behavior.
- Refresh dependencies and migrate the Docker image base to
wolfi-baseto address reported vulnerabilities.
Breaking changes
None known.
Ops / Deployment
Review logging expectations after upgrading. Deployments that rely on file logs keep the default FUME_FILE_LOGGING=true; container and Kubernetes deployments that collect logs from stdout/stderr can set FUME_FILE_LOGGING=false to disable file logging and file mirroring. See FUME_FILE_LOGGING for details.
Upgrade to this release if your deployment evaluates mappings with wildcard assignments, uses parser recovery diagnostics, or installs FHIR packages concurrently into a shared cache. Deployments using Docker images should also pick up this release for the updated base image and dependency refresh.
v3.1.0
Release date: May 6, 2026
Summary
FUME Enterprise v3.1.0 adds optional Keycloak-backed authentication, policy-driven authorization, and FHIR multi-server support. Existing unauthenticated single-server deployments continue to behave as before until authentication or named FHIR connections are configured.
Engine version
This Enterprise release bundles @outburn/fume-engine v3.1.0 (spec: ^3.1.0).
- Public engine notes: FUME Community v3.1.0
Highlights
- Add Keycloak-backed bearer-token authentication with OIDC discovery, JWKS signature verification, issuer checks, audience checks, and configurable clock tolerance.
- Add policy-driven authorization for Enterprise routes, configured through
auth.yaml, with support for public, authenticated, and role-restricted access rules. - Add a token-mediating backend for confidential-client browser flows, alongside direct Authorization Code + PKCE support for public-client flows.
- Advertise OAuth protected-resource metadata for clients such as the Mapping Designer and Swagger UI, and return standards-aligned
application/problem+jsonresponses for auth failures. - Add the offline Policy Builder at
/auth/policy/builderto help author and test route policies before copying them intoauth.yaml. - Add FHIR multi-server support from
@outburn/fume-enginev3.1.0, including$useFhirServer()and named alternate FHIR connections fromconnections.yml. - Expand integration coverage for authentication and multi-server scenarios across the supported Enterprise runtime targets.
Breaking changes
None known.
Ops / Deployment
Authentication is off unless an auth.yaml file is present or supplied through AUTH_CONFIG_PATH. To enable it, configure Keycloak, mount or provide auth.yaml, keep client secrets in environment variables or your secret manager, and review the Authentication & Authorization guide.
To use FHIR multi-server mappings, add named connections in connections.yml or configure FHIR_CONNECTIONS_FILE; see Named FHIR Connections. Restart the server after changing auth.yaml, AUTH_CONFIG_PATH, connections.yml, or FHIR_CONNECTIONS_FILE.
If the Mapping Designer should authenticate against Enterprise, use Designer v3.1.0 or later and enable authenticated mode with FUME_DESIGNER_AUTH_ENABLED=true.
v3.0.3
Release date: Apr 5, 2026
Summary
This patch release updates the bundled engine to v3.0.6 and adds Enterprise OpenAPI documentation available at \api-docs.
Engine version
This Enterprise release bundles @outburn/fume-engine v3.0.6 (spec: ^3.0.6).
- Public engine notes: FUME Community v3.0.6
Highlights
- Updates the bundled engine from
v3.0.5tov3.0.6 - Exposes FUME Enterprise OpenAPI routes at
/api-docs/,/api-docs/swagger.json.
Breaking changes
None.
Ops / Deployment
Upgrade if you need the OpenAPI docs HTTP endpoints served.
v3.0.2
Release date: Mar 16, 2026
Summary
This patch release moves the bundled engine from v3.0.3 to v3.0.5 and improves Enterprise startup observability. On the engine side, it makes implicit FHIR package dependency resolution more resilient and restores recursive contentReference population for nested Parameters.parameter.part and similar cases. On the Enterprise side, background cache warmup activity is now reported more clearly.
Engine version
This Enterprise release bundles @outburn/fume-engine v3.0.5 (spec: ^3.0.5).
- Public engine notes: FUME Community v3.0.4 and v3.0.5
Highlights
- Updates the bundled engine from
v3.0.3tov3.0.5.- Improves resilience when resolving implicit FHIR package dependencies.
- Restores recursive
contentReferencepopulation for cases such asParameters.parameter.part.
- Background cache warmup now collects warning and error output and emits a structured summary when warmup completes or fails.
- Warmup summary reporting now tracks dropped and truncated log lines, which makes noisy or partial startup failures easier to diagnose.
Breaking changes
None.
Ops / Deployment
If your deployments install FHIR packages, this release should reduce failures around implicit dependency resolution.
If your FLASH mappings may populate nested contentReference elements (like Parameters.parameter.part), this upgrade is recommended.
v3.0.1
Release date: Mar 15, 2026
Summary
This patch release moves the bundled engine from v3.0.0 to v3.0.3. It carries forward the maintenance and vulnerability work from the engine updates, and fixes the stale static JSON reload behavior in file-backed mapping workflows.
Engine version
This Enterprise release bundles @outburn/fume-engine v3.0.3 (spec: ^3.0.3).
- Public engine notes: FUME Community v3.0.1, v3.0.2, and v3.0.3
Highlights
- Updates the bundled engine from
v3.0.0tov3.0.3.- Rolls in the related dependency and FHIR tooling refresh.
- Picks up the static JSON-backed mapping reload fix, so valid file edits no longer get stuck in a stale state until a later invalid-to-valid transition.
Breaking changes
None.
Ops / Deployment
Upgrade to this release if you want the vulnerability fixes included in the engine updates, or the static JSON reload correctness fix. No additional Enterprise configuration changes are required for this release.
v3.0.0
Release date: Feb 18, 2026
Summary
FUME Enterprise v3.0.0 is a major release that upgrades the embedded Community engine to v3 and modernizes the Enterprise server runtime.
Operationally, the core HTTP evaluation surface is intentionally kept stable (and covered by integration tests), but the internals are a big change: legacy JSONata-based evaluation is replaced by fumifier, and the v3 engine/runtime model unlocks better correctness, diagnostics, and scalability.
Enterprise also intentionally skips v2.x to align versioning across Community / Enterprise / Designer.
Engine version
This Enterprise release bundles @outburn/fume-engine v3.0.0 (spec: ^3.0.0).
- Full notes: FUME Community v3.0.0
Highlights
- Engine v3 upgrade (see FUME Community v3.0.0 for the canonical engine-level highlights).
- New evaluation core: JSONata → fumifier (parser/compiler/interpreter).
- Verbose evaluation reports: add
?verbose=trueto supported endpoints to receive a structured report (includesresult, structured diagnostics, andexecutionId). - Evaluation policy thresholds: control throw/log/diagnostics/validation behavior via
FUME_EVAL_*env vars. - Mapping sources: run mappings from a FHIR server and/or from local files (
*.fume), with polling/resync controls. - Production ergonomics:
GET /healthprobe endpoint and safer request metadata on mapping routes (sanitized headers in$fumeHttpInvocation).
Breaking changes
This is a major version release.
Versioning
- Enterprise jumps from
v1.xstraight tov3.0.0(skipsv2.x) to align versions across products.
Runtime / evaluation
- The evaluation engine is now fumifier instead of JSONata. This means that FUME expressions (including FLASH blocks) are now natively parsed and compiled instead of transpiled to JSONata and then parsed and compiled outside of the FHIR domain. This is the core upgrade that enables the deeper validation, automation and diagnostics introduced in v3.
HTTP behavior changes to be aware of
- If you previously called recache via
GET /recache, it now returns405. UsePOST /$recache. POST /recacheremains available for compatibility but is deprecated and will be removed in a future release.
Configuration and storage model
.env.example.stateful/.env.example.statelessare removed; use.env.example.- Snapshot/terminology caches are stored under the FHIR package cache path in v3 (no separate snapshots folder/volume concept).
Ops / Deployment
- Docker packaging updated (Dockerfile / docker-compose).
.env.exampleupdated and consolidated; review all defaults/knobs.- Review the full Enterprise runtime settings inventory: /docs/runtime-settings/enterprise.
- Recommended production probing:
GET /health. - For triage/debugging: use
?verbose=trueon evaluation endpoints (note: verbose mode changes the response shape).
v1.8.1
Release date: Nov 9, 2025
Summary
FUME Enterprise v1.8.1 includes updates to the Enterprise server packaging and embedded engine.
Engine version
This Enterprise release bundles @outburn/fume-engine v2.20.5 (spec: ^2.20.5).
- Full notes: FUME Community v2.20.5
Highlights
- Engine updated: v2.20.5.
Breaking changes
None.
Ops / Deployment
None.
Dependency updates
- Updated
@inquirer/prompts:^7.9.0→^7.10.0 - Updated
@outburn/fume-engine:^2.20.4→^2.20.5 - Updated
axios:^1.13.1→^1.13.2
v1.8.0
Release date: Nov 2, 2025
Summary
FUME Enterprise v1.8.0 includes updates to the Enterprise server packaging and embedded engine.
Engine version
This Enterprise release bundles @outburn/fume-engine v2.20.4 (spec: ^2.20.4).
- Full notes: FUME Community v2.20.4
Highlights
- Engine updated: v2.20.4.
Breaking changes
None.
Ops / Deployment
None.
Dependency updates
- Updated
@inquirer/prompts:^5.5.0→^7.9.0 - Updated
@outburn/fume-engine:^2.19.1→^2.20.4 - Updated
dotenv:^16.4.7→^16.6.1 - Updated
jsonata:^2.0.6→^2.1.0 - Updated
lru-cache:^10.4.3→^11.2.2 - Updated
winston:^3.17.0→^3.18.3 - Updated
zod:^3.24.1→^3.25.76
v1.7.2
Release date: Aug 24, 2025
Summary
FUME Enterprise v1.7.2 includes updates to the Enterprise server packaging and embedded engine.
Engine version
This Enterprise release bundles @outburn/fume-engine v2.19.1 (spec: ^2.19.1).
- Full notes: FUME Community v2.19.1
Highlights
- Engine updated: v2.19.1.
Breaking changes
None.
Ops / Deployment
None.
Dependency updates
- Updated
@outburn/fume-engine:^2.18.6→^2.19.1
v1.7.1
Release date: Jul 20, 2025
Summary
FUME Enterprise v1.7.1 includes updates to the Enterprise server packaging and embedded engine.
Engine version
This Enterprise release bundles @outburn/fume-engine v2.18.6 (spec: ^2.18.6).
- Full notes: FUME Community v2.18.6
Highlights
- Engine updated: v2.18.6.
Breaking changes
None.
Ops / Deployment
None.
Dependency updates
- Updated
@outburn/fume-engine:^2.18.2→^2.18.6 - Updated
axios:^1.7.9→^1.10.0 - Updated
js-sha256:^0.11.0→^0.11.1
v1.7.0
Release date: Jan 19, 2025
Summary
FUME Enterprise v1.7.0 includes updates to the Enterprise server packaging and embedded engine.
Engine version
This Enterprise release bundles @outburn/fume-engine v2.18.2 (spec: ^2.18.2).
- Full notes: FUME Community v2.18.2
Highlights
- Engine updated: v2.18.2.
Breaking changes
None.
Ops / Deployment
- Docker packaging updated (Dockerfile / docker-compose).
Dependency updates
- Updated
@outburn/fume-engine:^2.17.0→^2.18.2 - Updated
@commitlint/cli:^19.6.0→^19.6.1
v1.6.3
Release date: Dec 15, 2024
latest
Bug Fixes
- Fixed delete mapping errors when using HAPI as a FHIR server
v1.6.2
Release date: Dec 12, 2024
Bug Fixes
- Fixed issues preventing parallel processes from running inside a Docker container
v1.6.1
Release date: Dec 10, 2024
Bug Fixes
- Fixed Peepsy-related issues preventing the process from running in Node Single Executable Application mode (Windows EXE)
v1.6.0
Release date: Dec 9, 2024
Features
- Introducing the Peepsy module
- Enables easy and dynamic multithreading
- Promise-based inter-process communication channel
- Spawn background snapshot builder using Peepsy
- Build FLASH templates on the spawned child process
- FUME Engine upgraded to version 2.17.0
- Upgrade NPM dependencies
- Brand new FHIR package installer (replaces the
FHIR Package LoaderNPM module from HL7) - Global package index now resides in the current working folder, allowing for different FUME instances to have different packages loaded
- The
FUME ArtifactsFHIR package is now installed automatically
Improvements
- Improved package indexing performance
- Improved warmup time
Bug Fixes
- As part of FUME Engine upgrade:
- Fixed issue #119
- Fixed issue #127
Reverts
EXCLUDE_FHIR_PACKAGESenv parameter is cancelled (and ignored)
v1.5.0
Release date: Dec 5, 2024
Features
- Include Resource.meta elements in FLASH Templates
v1.4.2
Release date: Dec 2, 2024
Bug Fixes
- FUME Engine upgraded to version 2.15.5
v1.4.1
Release date: Nov 27, 2024
Bug Fixes
- FUME Engine upgraded to version 2.15.2
- Fixes incorrect element names for choice elements with a fixed value in the profile
v1.4.0
Release date: Nov 22, 2024
Features
- FUME Engine upgraded to version 2.15.1
- Includes new $wait() function
v1.3.0
Release date: Aug 22, 2024
Features
- FUME Engine upgraded to version 2.14.0
- Support unknown fields in V2 messages
- Added original line number from V2 message
- Include display element in $translateCoding() function’s results
- Upgrade axios package to version 1.7.4 (security related patch)
v1.2.4
Release date: Aug 20, 2024
Bug Fixes
- Fix conflicting version number in Windows executable file properties
v1.2.3
Release date: Aug 20, 2024
Features
- Support loading license from environment variable
v1.2.2
Release date: Aug 19, 2024
Bug Fixes
- Fixed errors when running on Node.js 20 outside of Windows executable
v1.2.1
Release date: Aug 19, 2024
Bug Fixes
- Incorrect recognition of deployment as Windows executable
v1.2.0
Release date: Aug 19, 2024
Features
- Upgrade Node.js to version 22
- Windows installer
- Installs and configures FUME Enterprise Server
- Installs and configures FUME Designer v2.0.0
- Installs Windows services
- Prior installation of Node.js no longer needed
v1.1.0
Release date: Jul 15, 2024
Features
- FUME Engine upgraded to version 2.11.3
- Added CodeSystem and ValueSet processing functions
- Validate required codes during FLASH transformation
- Supports XML inputs
- Upgrade NPM dependency packages
- Use storage to cache generated profile snapshots
- Gracefully handle not found StructureDefinition files
- Properly handle #contentReference as recursive BackboneElements
- Fixed false warnings about incomplete snapshot generation
- Consistent handling for different profiling conventions on choice elements
- Upgrade Node.js to version 20
- Smart caching for FLASH templates and profile snapshots
- Boost performance by pre-building snapshots and templates at startup
- New $transpile operation returns a mapping in the native JSONata syntax
- Updated README.md
Bug Fixes
- Fixed missing extension URL when using out-of-profile extensions
- Fixed wrong extension URL injected from previous step’s cache
- Correct representation of extensions on primitive elements
v1.0.0
Release date: Jun 1, 2024
Features
- Brand new core engine, based on FUME Community 2.8.1
- Major refactoring of codebase
- Implemented robust integration test infrastructure
- Brand new FLASH template generator
- Custom profile FLASH template generation is supported again
v0.4.8
Release date: Dec 31, 2023
Bug Fixes
- Fixed mapping count limit due to Bundle paging mishandling
v0.4.7
Release date: Dec 26, 2023
Features
- Dependency tree cleanup
v0.4.6
Release date: Dec 21, 2023
Features
- Performance tuning & memory cleanup
v0.4.5
Release date: Dec 21, 2023
Bug Fixes
- Fixed Bundle parsing error
v0.4.4
Release date: Dec 21, 2023
Bug Fixes
- Remove broken FLASH template
v0.4.3
Release date: Dec 20, 2023
Bug Fixes
- Don’t crash if internet access is blocked when attempting to download packages
- Fix object keys generated from array index numbers
- Choice elements with fixed values having wrong element names and types
v0.4.2
Release date: Dec 14, 2023
Features
- Boost performance of element definition fetching
Bug Fixes
- Retry downloading FHIR packages on temporary unavailability of registry
v0.4.1
Release date: Dec 13, 2023
Features
- Support DELETE of mappings through the RESTful API
Bug Fixes
- Correct handling of complex extension structures
v0.4.0
Release date: Dec 11, 2023
Features
- Brand new snapshot generator
- Support exclusion of specific FHIR packages from machine FHIR cache
- Load latest version of FHIR package when no version number is provided
- Use LRU caching strategy for element definitions and compiled mappings
- Added TTL caching infrastructure
- Support setting a datatype profile using the slice syntax (element[profile])
- Support the use of out-of-profile extensions using the slice syntax
- Recursive loading of FHIR package dependency tree
- Enforce minimum and maximum cardinalities
- Automatic conversion of dateTime values when assigned into date elements
- Improved error messages for profile validation exceptions
- Automatically set datatype of choice elements if profiled down to one type
Bug Fixes
- Fixed parsing of numeric values as strings
- Removed internal leftover attributes from results
- Prevent multiple datatype choices in polymorphic elements ([x])
- Prevent stringification of arrays assigned into single elements
- Fixed missing Boolean ‘false’ values in results
v0.3.9
Release date: Aug 20, 2023
Features
- Support FHIR server basic authorization
v0.3.8
Release date: Jun 2, 2023
Reverts
- Limit FLASH template support to base resources and profiles
v0.3.7
Release date: Jun 2, 2023
Bug Fixes
- Fixed errors when handling numeric environment variables
v0.3.6
Release date: Jun 1, 2023
Features
- Upgraded JSONata engine to version 2.0.2
v0.3.5
Release date: May 31, 2023
Reverts
- Deprecated the $bundle() function
v0.3.4
Release date: May 31, 2023
Features
- Support using key-value parameter object in all FHIR search based functions
v0.3.3
Release date: May 30, 2023
Bug Fixes
- Fixed missing child elements in slices when building profile snapshots
v0.3.2
Release date: May 29, 2023
Bug Fixes
- Fixed missing complex type headers under slices
v0.3.1
Release date: May 28, 2023
Bug Fixes
- Fix unwanted behaviour when using $reference() on empty values
v0.3.0
Release date: May 27, 2023
Features
- Automatic FHIR package download and import
- Brand new FLASH parser and compiler
v0.2.9
Release date: May 14, 2023
Features
- Improvements in Docker configuration
Bug Fixes
- Remove unnecessary logging of V2 key mappings
- Handle V2 field name normalization edge cases
- Fix errors in FLASH template generation
v0.2.8
Release date: Apr 30, 2023
Features
- Boost performance with parallel asynchronous function calls
v0.2.7
Release date: Apr 29, 2023
Features
- Improved caching of compiled mappings
- Boost compilation performance
- Improved CI/CD workflow
v0.2.6
Release date: Apr 28, 2023
Features
- Improvements in mapping pre-compilation
- Boost HL7 v2 performance by caching the v2 dictionary
v0.2.5
Release date: Apr 27, 2023
Features
- Improve transformation performance by pre-compilation of mappings
v0.2.4
Release date: Apr 20, 2023
Features
- Added support for CSV inputs
- Added support HL7 v2 message inputs
v0.2.3
Release date: Apr 19, 2023
Features
- Added support for Fire.ly FHIR server
Bug Fixes
- Fixed fhirVersion in Content-Type header
v0.2.2
Release date: Feb 19, 2023
Features
- Removed full input trace from log
Bug Fixes
- Prevent infinite element depth search
v0.2.1
Release date: Feb 18, 2023
Features
- Improved performance by upgrade JSONata engine to version 2.0.1
- Extended transformation logging
v0.2.0
Release date: Dec 16, 2022
Features
- FLASH syntax parser
- Native support for cloud deployment
- Dedicated functions for data types: Identifier, Coding, Extension
- Support health check in root endpoint
- FHIR server interaction functions
- Improved performance when using the mapping endpoint
- Caching of ConceptMap resources
- Support deployment using Docker
- Upgrade Node.js to version 16
- Support stateless mode
- Improved logging, including compression and rotation
- Improved documentation (README.md)
- Include FHIR R4 definition files
- Generate FLASH templates on demand
- FHIR definition compilation engine
Bug Fixes
- Allow cross-origin resource sharing (CORS)
- Fixed errors in mapping re-cache
- Fixed errors when loading environment variables
- Transformation errors now return 422 instead of 500 HTTP status code
v0.1.0
Release date: Aug 11, 2022 (Initial release)
Features
- Transformation invocation through RESTful API
- Mapping storage and retrieval using StructureMap resources and a FHIR server
- Mapping language based on JSONata syntax and extended functionalities