Skip to main content

Fire Arrow Server 2.6.8

· 5 min read

Fire Arrow Server 2.6.8 has been released.

  • (feature) The practitioner detail page adds a Memberships tab for managing that practitioner's organizations and roles
  • (feature) The Conditions tab on the patient chart lists and records the patient's operations
  • (feature) The PlanDefinition editor opens plan details, goals, and actions in side panels, and a plan can be duplicated
  • (feature) The profile menu lists the signed-in user's organizations and roles, and the dark theme is easier to read
  • (bugfix) A stalled request no longer makes every later write for the same email address fail with 503 until restart

Memberships on the Practitioner Detail Page​

The practitioner detail page has a Memberships tab. It lists every organization the practitioner belongs to, together with the clinical roles and dashboard features they hold there. From this tab, an administrator can add the practitioner to another organization, change their roles in an organization, or remove the membership. Removing a membership deletes the practitioner's PractitionerRole resources for that organization, after a confirmation.

The organization page still manages memberships as before. The new tab manages the same PractitionerRole resources from the practitioner's side.

Operations on the Conditions Tab​

The Conditions tab of the patient chart lists the patient's operations below the diagnoses, newest operation date first. Each operation is a FHIR Procedure for the open patient.

A user who can manage patients can add an operation with a name, an optional SNOMED CT code, and the date it took place. The server stores it with status completed, subject set to the patient, and the date in performedDateTime. The date the entry was recorded is stored once in the http://hl7.org/fhir/5.0/StructureDefinition/extension-Procedure.recorded extension and is not changed by later edits. If two users edit the same operation at the same time, the second save is refused with a conflict message and the list reloads. A user who can only view patients sees the list without Add, Edit, or Delete.

PlanDefinition Editor​

The PlanDefinition editor opens plan details, goals, and actions in side panels. Changes in a panel are kept separate until they are applied, and discarding a panel leaves the plan as it was. Clicking a validation finding moves to the field or action it refers to.

A plan can be duplicated from the list or from the editor menu. The copy is saved as a draft without the original's id and url, so it does not collide with the source plan.

Profile Menu and Dark Theme​

The profile menu in the header shows the signed-in user's name and email address, with each organization they belong to and the clinical roles they hold there. Only roles that are active and within their validity period are listed. When the identity provider sends unknown as the user's name, the menu shows the given and family name or the email address instead. License moved from the profile menu to the Dev Tools group, where administrators and users with developer-tools can open it.

The dark theme has new surface, text, and status colors, and stronger card and section borders. The light theme is unchanged.

Bug Fixes​

Identity writes failed with 503 until restart​

When fire-arrow.authentication.protect-identity-resources is set, the server makes sure no two identity resources of the protected types share an email address. While it checks, it holds a short lock for each email address on the resource. Every update to such a resource took these locks, even when its email addresses did not change. If one of those requests stalled while holding a lock, every later create or update carrying that email address waited 30 seconds and failed with 503. Retrying gave the same result, and the condition lasted until the instance was restarted. Sign-in and $me for that identity kept working.

Starting with 2.6.8:

  • An update locks and checks only the email addresses it adds. Updates that keep or remove addresses, such as routine profile changes, no longer wait for a lock.
  • A lock is released only once the change has been committed or rolled back. Before, two requests adding the same email address at the same moment could both succeed.
  • A lock held longer than fire-arrow.mutex.jdbc.lock-ttl-seconds (default 300) is reclaimed by the next request waiting for it. A stalled request therefore blocks an email address for about five minutes at most, instead of until restart. The same applies to the other server operations that use these locks.

Each reclaimed lock is logged as a warning. Alert on these warnings, because they mean a request stalled for longer than the lock lifetime. In the rare case where that stalled request later completes anyway, a duplicate email address can result. Set fire-arrow.mutex.jdbc.stale-lock-steal-enabled to false to turn reclaiming off and restore the previous behavior.

Because updates no longer check unchanged email addresses, a duplicate created before protection was enabled is no longer reported when an unrelated field of that resource is updated. New duplicates are still refused on create and on update.