Skip to main content

Fire Arrow Server 2.7.0

· 10 min read

Fire Arrow Server 2.7.0 has been released.

  • (breaking) Patient-chart observation series select their readings with match instead of path
  • (breaking) The Timeline tab of the patient chart is now Tasks, configured under default-tabs.tasks
  • (breaking) The Clinical data tab is hidden unless enabled, and every built-in patient-chart tab can be turned off
  • (security) The container image mitigates the Java4Shell Base64 vulnerability (CVE-2026-114938)
  • (feature) Key signals and daily charts can read the value from any part of an Observation with value-path
  • (feature) The Home page shows the tools each user can open
  • (bugfix) Measurement history loads a patient's full history unless max-pages is set
  • (bugfix) Clinical images stored in Azure Blob Storage display in the administration UI
  • (bugfix) The daily check-in chart no longer freezes the page, and the Clinical data tab loads on deployed servers
  • (bugfix) The patient list search box keeps every character when typing quickly
  • (bugfix) The MCP search tool applies its search parameters
  • (maintenance) Tomcat, PostgreSQL driver, HAPI FHIR, and Next.js security updates

Observation Series Use match​

Several patient-chart elements decide which Observation belongs to a series with a FHIRPath expression. That expression was configured as path. Starting with 2.7.0, it is called match on these elements:

ElementWhere the key sits
key-signalseach entry of observation-types
metrics-charteach entry of observation-types
time-series-listeach entry of series
vital-signseach entry of traces on a vital

The expression itself is unchanged, and it is still used to narrow the search when it names a single coding. Other keys keep their names: value-path, max-path, unit-path, timestamp-path, the match.path filter on Task cards, and path on patient-list columns.

Breaking Change​

Rename path to match on every entry listed in the table before upgrading. path is not read as a fallback. An entry without match fails validation with match is required, and the tab that contains it is left out of the chart until the configuration is fixed.

Timeline Tab Renamed to Tasks​

The built-in patient-chart tab that lists a patient's Task resources is now called Tasks. Its card configuration moved from fire-arrow.ui.patient-chart.timeline to fire-arrow.ui.patient-chart.default-tabs.tasks, and card-types is now cards. task-status, page-size, and the card settings themselves are unchanged.

2.6.x2.7.0
patient-chart.timeline.card-typespatient-chart.default-tabs.tasks.cards
patient-chart.timeline.task-statuspatient-chart.default-tabs.tasks.task-status
patient-chart.timeline.page-sizepatient-chart.default-tabs.tasks.page-size
Section element type: timeline-eventstype: tasks
?tab=timeline?tab=tasks

tasks is now a reserved tab id, so a configured tab can no longer use it. timeline is no longer reserved. ?mode=timeline still opens Clinical data.

Breaking Change​

Move the timeline block to default-tabs.tasks, rename card-types to cards, and change any timeline-events section to tasks. The old block is ignored without an error, and the Tasks tab then shows only the built-in medication and questionnaire cards. A configured tab that still contains a timeline-events section fails validation and is left out of the chart. Update saved links that use ?tab=timeline.

Built-in Patient-Chart Tabs Can Be Turned Off​

Each built-in tab of the patient chart can be shown or hidden with fire-arrow.ui.patient-chart.default-tabs.<id>.enabled, where <id> is details, medications, tasks, clinical-data, conditions, or questionnaires. The Conditions tab can also hide its conditions card or its procedures card without hiding the tab, with default-tabs.conditions.conditions-card and default-tabs.conditions.procedures-card.

When a flag is omitted, Clinical data is hidden and every other built-in tab is shown. A link to a hidden tab opens the first tab that is still shown. Hiding the Tasks tab does not affect tasks sections on configured tabs, which keep using the cards from default-tabs.tasks.

Breaking Change​

To keep the Clinical data tab, set fire-arrow.ui.patient-chart.default-tabs.clinical-data.enabled to true (FIRE_ARROW_UI_PATIENT_CHART_DEFAULT_TABS_CLINICAL_DATA_ENABLED=true). Without it, the tab no longer appears after the upgrade. The other built-in tabs are unchanged unless you turn them off.

Java4Shell Mitigation​

CVE-2026-114938, known as Java4Shell, is a memory corruption flaw in the Java runtime's accelerated Base64 decoder on CPUs with AVX-512. A malformed Base64 value, for example in an Authorization header or a JWT, can let an unauthenticated caller run code on the server. Fire Arrow Server decodes such values before it authenticates a request, so an unpatched server on an affected CPU is exposed to anyone who can reach it.

Starting with 2.7.0, the Fire Arrow Server container image starts Java with -XX:-UseBASE64Intrinsics. This turns off only the vulnerable decoder path, at the cost of slightly slower Base64 decoding. The flag is needed because the Java build in the image does not include the fix. It will be removed once the image is rebuilt on a fixed Java build.

If you run Fire Arrow Server with your own Java runtime or image, add -XX:-UseBASE64Intrinsics to the Java options (for example through JAVA_TOOL_OPTIONS) unless that runtime already includes the fix. Oracle JDK 17.0.21.1 and Amazon Corretto 17.0.21.1.2 are fixed builds.

Reading Values with value-path​

key-signals and the observation-types of metrics-chart accept an optional FHIRPath value-path for the number to show. Use it when the value sits on an Observation.component rather than on Observation.value[x]. When value-path is omitted, the value is valueQuantity.value | valueInteger | valueDecimal, as before. match still decides which observations belong to the series. A blank value-path is invalid and leaves that tab out of the chart.

Redesigned Home Page​

The Home page greets the signed-in user by name and shows tiles for the tools that user can open, grouped as Patients, Administration, and Dev Tools. The layout follows the user's access. A user who can only see the clinical section gets the patient list as their Home page. A user who can only see developer tools gets those tools. Users who can see several groups get a launcher with each of them. Users with developer-tools also see the server release and FHIR version. Administrators additionally see the resource types that hold data, with a link to a page that lists all of them. A user without access to any tool sees a note to ask an administrator.

Bug Fixes​

Measurement history stopped after 25 pages​

The time-series-list section stopped loading a series after 25 pages when max-pages was not set, and showed a notice that loading had stopped. Starting with 2.7.0, an unset max-pages loads the full history of each series. Setting max-pages (1 to 100) still caps it and shows the notice. Set max-pages if you relied on the implicit cap for patients with very long histories.

Two display problems in the same section are also fixed. After switching from By series to Chronological, rows for series that had not loaded yet stayed on "Waiting for" until the list was scrolled to the end. Both views also shared one scroll position. The pending rows now load right away, and each view keeps its own scroll position.

Clinical images from Azure Blob Storage did not display​

With binary storage enabled, image attachments are read through pre-signed Azure Blob Storage links. The administration UI's Content Security Policy did not allow images from that storage account, so the browser blocked them in the media gallery and on Task cards. The server now adds the storage account's origin to img-src automatically, based on the configured fire-arrow.binary-storage.azure settings. Only the scheme, host, and port go into the policy, never the account key. If no origin can be derived from the configuration, the server logs a warning at startup.

The daily check-in chart froze the page​

On a deployed server, switching the daily check-in chart between week, month, and year, or moving to the previous or next range, could stop the whole page from responding to clicks until it was reloaded. The chart now switches ranges normally.

Also on deployed servers, the Clinical data tab and other views that load the patient's clinical data in the browser could fail to start, because the administration UI's Content Security Policy blocked the in-browser database they use. script-src now includes 'wasm-unsafe-eval', which allows that database to start. 'unsafe-eval' stays disallowed. See Web UI Sign-In for the other Content Security Policy options.

The patient search box lost characters​

On a deployed server, typing quickly into the patient list search box could drop characters, and the search then ran with the shortened text. The box now keeps everything that is typed and updates the page address after typing pauses. Opening a link with ?q= and using the browser's Back button still restore the search.

The MCP search tool ignored its search parameters​

When MCP is enabled with spring.ai.mcp.server.enabled=true, the search tool ignored search parameters passed as a query string such as family=Silva&_count=5 and returned the first page of all resources of that type. The tool now applies them. Parameters are separated with &, and commas inside a value mean OR, as in the FHIR REST API. MCP calls also failed when the server ran under a server.servlet.context-path, and now work there too. MCP remains disabled by default.

Dependency Upgrades​

The embedded Tomcat is updated to 10.1.61, which includes the fixes from the Tomcat 10.1.60 and 10.1.61 security releases. The PostgreSQL JDBC driver is updated to 42.7.14, addressing GHSA-rhp9-mr79-r74h (some requireAuth values were treated as if requireAuth were not set) and GHSA-f64h-wr5q-3qf3 (a stored value could contain data from earlier statements on the same connection). The server also moves to HAPI FHIR 8.12.1 and Clinical Reasoning 4.15.0, along with routine library and build updates.

The administration UI updates Next.js to 16.4.5, addressing CVE-2026-119790, CVE-2026-119351, GHSA-vvgp-ww4w-46vf, GHSA-rhh4-g77r-r9qj, GHSA-pc58-hwjq-p385, GHSA-7qx7-33qx-rqx2, and GHSA-f3mh-rxg3-f5g2. These concern caching, image optimization, and response handling in the Next.js server. The administration UI is shipped as static files and does not run that server. The FHIR API is unaffected.