Skip to main content

EWA Release 40.7.0

Version 40.7.0 stable: Component Versions​

Version 40.7.0 stable of EWA was released to customers on 20th August 2026.

ComponentVersion
Chat Server26.4.293.0
Client Application26.8.12.0
Client Hub26.8.131.0
Data Warehouse Export Service26.8.113.0
EOC Integration26.8.117.0
Export Service26.8.132.0
Insights API26.8.116.0
Form Module API26.6.5.0
HP Link Patient Identity API26.8.132.0
Insights Web26.8.121.0
LiveView API26.8.113.0
Medical Unit Broker26.5.13.0
Migration and Seeding Tool26.8.119.0
Personnel Registration API26.5.5.0
Version Manager API26.4.293.0
Version Manager Client Installer26.1.286.0
EWA Multiplatform Client0.0.4592.0
EWA Multiplatform IIS0.0.4677

First release with EWA Multiplatform Windows version for testing​

40.7.0 is the first release in which the EWA Multiplatform client is delivered to a health trust, alongside the existing Windows client application.

Prerequisite for testing EWA Multiplatform: the Multiplatform client is supported on Windows 11 only. Testing must be carried out on a Windows 11 device; earlier Windows versions are not supported for the Multiplatform client in this release.

This release is expected to provide feature parity with the current UWP application, except for the following functionalities:

  • Chat consultation with non-delivery locations. Chat feature in the UWP works expected as earlier.
  • Paid mission with image tagging
  • Export configurations
  • Merging manual assignments with EMCC assignments
  • Tile helper texts
  • Warning when opening a journal where the user is not the assigned processor

See EWA Multiplatform - Installation Guide for installation guide.

For the 40.7.0 installation, customers should install all server components and perform the standard migration process. The only additional requirement is the installation of the two new MP artifacts(EWA Multiplatform IIS, EWA Multiplatform Client). However, if they are not testing MP and intend to use UWP instead, the MP artifacts are not required.

Version 40.7.0 stable: Updated Features​

Journal cleanup is now always on, and its feature flag is deprecated​

Every customer had the RemoveCompletedAndDeletedJournals feature enabled permanently, so the behaviour it guarded is now unconditional:

  • The client application always runs journal cleanup for completed and deleted journals.

The flag itself is marked as deprecated in code and will be removed in a later release. It is still listed in Insight → Administration → Features for now, but changing it no longer has any effect. This follows the same deprecate first, remove later approach used previously for RecordSearchV2.

There is no change in behaviour for customers, because all customers already ran with the feature enabled.

Affected components: Client Hub, Client Application

Patient National Id System 2.0, Vehicle ID from EOC and Dataset v2 promoted to Release Candidate​

The three features introduced in 40.4.0 now report Release Candidate instead of Alpha in Insight → Administration → Features:

  • Patient National Id System 2.0
  • Vehicle ID from EOC
  • Dataset v2

The promotion was intended for 40.4.0 but did not reach deployed environments, because release builds consume a pinned feature flag package that was produced before the change merged. The pinned package has now been updated, so the intended states are in effect from this release.

The same update also carries through the RemoveCompletedAndDeletedJournals deprecation described above, so the flag is now reported as deprecated in deployed environments as well.

Affected components: Client Application, Client Hub, Insight

Version 40.7.0 stable: Fixes​

Low resolution photos from built-in cameras on Windows tablets​

  • Ticket: 419315431656 | DevOps: 39971 | Reported by: Helse Vest
  • HubSpot Title: P12275 - Redusert kameraoppløsning for Bliksund EWA på Getac nettbrett
  • Internal Reference: P21275
  • Issue: Photos taken in the EWA gallery with the built-in camera of a Windows tablet were captured at a low resolution. The same tablet produced full resolution images from an external camera, and its built-in camera produced full resolution images in other applications such as Windows Camera. The same EWA version captured correctly on Windows 10 and incorrectly on Windows 11, so the cause was not a driver or a device model. It affected built-in cameras on Windows tablets in general.
  • Root cause: The client application left the capture configuration to the platform default. It never selected a camera profile and it picked the photo mode with the most pixels without reconciling the aspect ratio against the preview. Windows 11 gives integrated cameras a constrained, video oriented default when no video profile is selected, so the resulting frame was downscaled or cropped. Windows 10 defaulted the same cameras to their full still resolution, which is why the identical application version behaved differently on the two operating systems.
  • Solution: The client application now negotiates the capture format itself. It takes exclusive control of the camera, selects the video profile that exposes the largest photo resolution, and chooses the highest photo resolution the camera offers, using the aspect ratio only as a tie breaker so front cameras also stay at full resolution. The video preview is set to Full HD at approximately 30 fps where the camera's preview pin supports it. Each step is best effort, so a camera that rejects a setting still initialises. Captured photos are re encoded at JPEG quality 0.85 at full resolution, which roughly halves the stored file size.
  • Note: Exclusive control falls back to shared mode when the camera is already in use by an active LiveView consultation, so LiveView is unaffected. The preview resolution remains bounded by what the camera's preview pin reports. On some tablets that pin only offers 640x480, in which case the preview stays at 640x480 while the captured photo is full resolution.

Affected components: Client Application (Windows / UWP)

Patient age in the Insight journal view was calculated from today's date​

  • Ticket: 422691138746 | DevOps: 40513 | Reported by: HSØ
  • Issue: In Insight (Search Journal → View), the patient age was calculated against the current date rather than the date of treatment. A journal opened six years after the incident showed the patient six years older than they were at the time. The old calculation also compared months only, so the age could be one year too high during the patient's birth month.
  • Solution: Patient age is now calculated relative to the mission start date, falling back to the journal creation date, with day level precision. This matches how the data warehouse export has always calculated patient age. The patient summary, the NEWS2 visibility rule and the post edit patient display all use the corrected value. Live View and the client application intentionally continue to use the current date, which is correct while an incident is ongoing.

Affected components: Insight

Known issues in 40.7.0​

  1. Exports are failing in the client application (Windows / UWP).
  2. An error is shown while responding to a form in the client application (Windows / UWP).

We are looking into both issues and will have a fix for them in a new version.

Affected components: Client Application (Windows / UWP)

✅ Testing Focus Areas for 40.7.0​

📱 EWA Multiplatform first health trust rollout​

  • Prerequisite: test on a Windows 11 device, the only Windows version the Multiplatform client supports in this release
  • Confirm a journal created on Multiplatform is visible and correct in Insight, LiveView, the EMCC ticket and the PDF report
  • Confirm the routes the Multiplatform client depends on still resolve after upgrade

📷 Photo capture on Windows tablets​

  • Capture a photo with the built-in rear camera of a Windows 11 tablet and confirm the stored image is at the camera's full resolution, not a downscaled or cropped frame
  • Repeat with the built-in front camera and confirm it is also at full resolution
  • Repeat the same two checks on a Windows 10 tablet and confirm there is no regression
  • Start a LiveView consultation using the camera, then open the gallery and confirm the camera still initialises rather than failing on exclusive access
  • Confirm a camera that rejects the preview or profile settings still initialises and can take a photo
  • Compare stored file sizes before and after upgrade and confirm images are noticeably smaller while the pixel dimensions are unchanged

🧹 Journal cleanup and the deprecated feature flag​

  • With RemoveCompletedAndDeletedJournals enabled, confirm behaviour is unchanged from 40.4.0
  • Set the flag to disabled and confirm journal cleanup still runs and mission distance updates against completed or deleted journals are still rejected, since the flag no longer gates anything
  • Confirm the flag is shown as deprecated in Insight → Administration → Features

🎚️ Feature flag states​

  • Open Insight → Administration → Features and confirm Patient National Id System 2.0, Vehicle ID from EOC and Dataset v2 are reported as Release Candidate, not Alpha
  • Confirm that changing the reported state does not alter the behaviour of these features for organisations that already had them enabled or disabled
  • Confirm RemoveCompletedAndDeletedJournals is shown as deprecated and that existing journal cleanup behaviour is unchanged

🧓 Patient age at time of treatment​

  • Open an older record in Insight → Search Journal → View and confirm the patient age shown matches the age at the mission start date, not the age today
  • Verify a record where the patient's birthday falls between the mission date and today and confirm the age is not one year too high
  • Verify a record whose mission start date is absent falls back to the journal creation date
  • Confirm the NEWS2 visibility rule still triggers on the correct age boundary
  • Confirm Live View and the client application still show the current age for an ongoing incident, which is the intended behaviour
  • Confirm the age shown in Insight now agrees with the age in the data warehouse export

Tested Medical Devices​

All versions of this release have been tested on the listed medical devices and corresponding software versions, ensuring compatibility and performance in the specified environments.

Corpuls​

  • Software versions: 4.4.4
  • SDK version: 4.4.0.0

Zoll​

  • Software version: 02.36.21.00
  • SDK version: 6.44.315