Fire Arrow Server 2.6.9
Fire Arrow Server 2.6.9 has been released.
- (feature) A patient-chart tab can show vital signs with weekly and monthly trends
- (feature) A patient-chart tab can show a gallery of the patient's clinical images
- (feature) Daily check-in charts can plot answers from completed questionnaires
- (feature) Key signals show each series' latest reading, however old it is
- (feature) The CarePlan editor adds an activity board, linked requests, and request-group editing
- (feature) All administration lists share the directory layout, and pages keep a readable width on wide screens
- (maintenance) Next.js security update for the administration UI
Vital Signs on the Patient Chart
A configured patient-chart tab can include a vital-signs section. It shows one card per configured vital with the latest value, the change over the selected window, a status, and a small trend line. The window is the current calendar week or calendar month, and the user can step back to earlier ones. Opening a card shows the latest, average, minimum, and maximum values and how many readings were in range.
Each vital has one or two traces. A trace selects Observation resources with a FHIRPath path that must name exactly one code or component-code coding. The first trace is the headline value and the solid line. A second trace is drawn as a dashed line, so systolic and diastolic blood pressure share one card. The status comes from the Observation's interpretation, otherwise from referenceRange or the optional low and high bounds on the trace. A vital with no readings in the window is not shown.
A path that does not name a single coding is left out of the search and reported on the section, so a vital never searches all of a patient's observations.
Clinical Image Gallery
A configured patient-chart tab can include a media-gallery section. It shows the patient's clinical images newest first, 12 per page, with the clinical date on each image. Selecting an image opens it at full size, and the arrow keys move through the loaded images. Photos on Timeline cards open in the same full-size view.
The section reads images from one or more bindings:
source | Searches | Optional filter |
|---|---|---|
media | Media for the patient | type, a system|code token on Media.type |
attachment | DocumentReference, DiagnosticReport, or Observation for the patient, set with resource-type | code, a system|code token |
Only image attachments are shown. Resources with status entered-in-error, and for Media, Observation, and DiagnosticReport also cancelled, are excluded. Each binding loads at most 10 pages of 50 results. Beyond that, the gallery notes that older images may be missing. The same element can be placed on several tabs with different bindings.
Check-in Answers on the Daily Chart
The metrics-chart element can plot daily values from completed QuestionnaireResponse resources, in addition to or instead of Observation series. Each entry under questionnaire-responses-types names a questionnaire canonical and the link-id of the answer to plot. The item is found at any nesting depth. By default the value is answer.first().valueInteger. An optional FHIRPath value-path reads a different value.
The optional timezone-source sets the time zone used to assign readings to days, for the whole chart. care-plan uses the timezone extension on the patient's first active CarePlan that has one, and patient uses the same extension on the Patient. Any other value is used as a fixed zone, such as UTC or Europe/Berlin. When the extension is missing, UTC applies. Without timezone-source, the chart uses the browser's time zone, as before.
At least one of observation-types and questionnaire-responses-types must be set. Series ids must be unique across both lists. Existing charts that only use observation-types are unchanged.
Key Signals Without a Seven-Day Window
Key signals used to consider only readings from the past seven days, so a series without a recent reading disappeared from the card. Starting with 2.6.9, each configured series is searched on its own, newest first and without a date limit, and the card shows that series' latest reading and the change from the one before it. A busy series can no longer push another series off the card. When a reading is from an earlier year, its date includes the year. With no matching readings, the card stays visible with its title and a "No key signals recorded" message.
CarePlan Editor
The CarePlan editor opens plan details in a side panel with Basic, Subject, Team, and Clinical sections. A plan can be viewed as a board of its activities grouped by status, as a timeline of when each activity runs, or as the Tasks created for it. An activity can link an existing request or create a new linked request from the editor, and request groups can be edited together with the actions they contain. A care plan can be duplicated from the editor menu.
Unified Lists and Wider Screens
The Plan Definition, Care Plan, and Questionnaire lists use the same directory layout as patients, practitioners, devices, and organizations: a header with the count, a filter bar, column headings, and rows that open the editor. Actions that apply to a single entry, such as duplicate, delete, or applying a plan definition to a patient, moved into a More actions menu on the row. Deleting a care plan still offers to delete its Tasks. Import from LOINC and New Questionnaire are in the Questionnaire list header.
Related persons also have a directory with search by name, identifier, and patient. Creating a related person opens a side panel, and opening a row shows that person's record with a link back to the list. Users who can only view related persons do not see the create action.
On wide screens, administration pages limit their content width instead of stretching across the whole display.
Dependency Upgrades
The administration UI updates Next.js to 16.4.1, addressing CVE-2026-96889 (remote code execution in image optimization when serving SVG files), CVE-2026-94482 (denial of service through Server Actions), and GHSA-673q-mjm6-r5xr (remote code execution in use cache functions). The administration UI is shipped as static files and does not run the Next.js server, which all three advisories concern. The FHIR API is unaffected.