Skip to main content

EWA Release 40.2.11

Version 40.2.11 stable: Component Versions​

Version 40.2.11 stable of EWA was released to customers on May 29th 2026.

The compatible versions of the affected runtime components are listed below:

ComponentVersion
Client Application26.5.67.0
Client Hub26.5.288.0
Data Warehouse Export Service26.5.283.0
EOC Integration26.5.274.0
Export Service26.5.283.0
Insights API26.5.288.0
Form Module API26.5.3.0
HP Link Patient Identity API26.5.283.0
Insights Web26.5.282.0
LiveView API26.5.284.0
Migration and Seeding Tool26.5.285.0

Version 40.2.11 stable: New Features​

No new features were included in this release.

Version 40.2.11 stable: Updated Features​

No updated features were included in this release.

Version 40.2.11 stable: Fixes​

Journals with missing AMIS numbers could be created when the application was closed or terminated during mission creation.​

  • Ticket: 417134918851
  • DevOps: 39191
  • Reported by: HSØ
  • HubSpot Title: Manglende data i fullførte journaler
  • Internal Reference: N/A

  • Issue: Some journals could be created with missing AMIS (EMCCMissionId) values and NULL/empty Data, resulting in orphaned records after synchronization. Although initially reported as data loss after the upgrade, investigation confirmed this is a long-standing issue. The problem could occur under poor network conditions if the application was closed during journal creation, causing the AMIS number and journal data not to be stored as pending for later synchronization.

  • Solution:

    • Fixed an issue where journal creation relied on multiple non-atomic operations, which could leave partially created records if the application was interrupted. Introduced a new API endpoint that atomically creates journals together with the required fields (EMCCMissionId and ResourceId), replacing the previous flow where an empty journal was created first and later updated through synchronization. This ensures initial journal info and data are consistently stored together, even if the application is terminated during the operation. The legacy endpoint remains supported during the transition period.
    • Added a server-side safeguard to reject updates attempting to unbind a journal from its mission. When such an event occurs, a warning is generated and recorded in the Technical Log for monitoring and investigation.

  • Affected components: Client Application, Client Hub

Overview Report returns empty results​

  • Ticket: 414235140299
  • DevOps: 38680
  • Reported by: Helse Vest and HSØ
  • HubSpot Title: Oversiktsrapport feiler
  • Internal Reference: PY-173
  • Issue: After deploying version 40.2.7, users were unable to retrieve results in the Overview Report page. The API returned 200 OK, but the response contained an empty dataset (data: []). No errors appeared in logs or the browser. Users had correct access rights and could retrieve data in Record Search, My Records, and Timeline Report.
  • Solution: Fixed an issue introduced during the v40 Insight migration where the ReportsController constructed a partial OpenID Connect configuration, causing incorrect claim resolution and filtering out all data. The controller now uses the full TokenConfiguration, and the authorization service has been hardened to automatically backfill missing claim types in partial configurations. This ensures correct role resolution, restores global access logic, and prevents empty results due to misconfigured claims.

Affected components: Insights API

Form data lost on force close events​

  • Ticket: 414623447243
  • DevOps: 39077
  • Reported by: HSØ
  • HubSpot Title: Tap av tekst - ny sykehistorie
  • Internal Reference: PT-175
  • Issue: Data entered in the History of Illness form (and other forms) was lost when a “connection lost” or similar status message appeared. This issue could also be reproduced when minimizing the app while a form contained unsaved data. The problem only affected Windows 10 tablets and did not occur on Windows 11.
  • Solution: Fixed an issue where the form save logic was triggered during the modal’s Closing event, which is not consistently fired on Windows 10 when a flyout is dismissed by another UI element. The save logic has been moved to the Closed event, which is reliably triggered across both Windows 10 and Windows 11, ensuring that in-progress form data is always preserved. The Closing event now only handles input cancellation (e.g., touch keyboard behavior).
  • Affected components: Client Application

Large problem descriptions cause data loss and repeated technical logs​

  • Ticket: 409229760725, 413622399219
  • DevOps: 38172
  • Reported by: Helse Vest and Helse Midt-Norge
  • HubSpot Title: Størrelsesbegrensing i "ProblemDescription_Value" trigger gjentagende logginnslag i Teknisk logg i Bliksund EWA / ClientHub error x3 hvert 15. sekund
  • Internal Reference: P12188
  • Issue: When AMK operators pasted extensive critical information into the Problem Description field (e.g., from the Core Journal), the content could exceed the 2048-character limit. This caused API failures (SqlException – data truncation), resulting in the entire EMCC ticket update being dropped. Consequently, the information was not stored in the journal, and repeated errors were logged in both the application server logs and the Insight Client technical logs.
  • Solution: Increased the storage capacity of ProblemDescription_Value and DispatchCodeDescription_Value by switching support up to a 10,000-character limit enforced at the API boundary. Added validation to reject oversized inputs before database writes, preventing runtime failures. Increased SignalR message size limits to support larger payloads, and improved UI handling by making long descriptions scrollable within the display area. These changes eliminate truncation errors, ensure reliable data persistence, and prevent repeated logging issues.
  • Affected components: ClientApplication, Client Hub, Export service, Insights Web, LiveViewApi, Migration and Seeding Tool
  • Note: The logging behavior currently remains unchanged—when the text exceeds 10,000 characters, it is flagged as a warning. We are working on enhancing this by refining the retry logic during the data-saving process.

Insight pages fail to load (blank screen) after upgrade​

  • Ticket: 414974195931, 414756106486
  • DevOps: 38751
  • Reported by: Helse Vest and HSØ
  • HubSpot Title: Sanntidsskjerm åpner seg ikke for mange brukere / Tidslinjerapport og Sanntidsskjerm viser sider uten data
  • Internal Reference: P12244
  • Issue: After upgrading to version 40.2.7/40.2.8, some users experienced that Insight pages (including Real-time screen and Cardiac Arrest/Timeline reports) did not load. Only the menu was visible while the rest of the page remained blank. The issue primarily affected returning users with previously cached browser data.
  • Solution: Fixed an issue where browsers cached outdated versions of critical Blazor startup files (blazor.boot.json and *.lib.module.js), causing integrity check (SRI) failures that prevented the application from loading. Added Cache-Control: no-cache headers for these specific files to ensure browsers always revalidate them after deployment. This prevents stale assets from breaking the Blazor initialization while still allowing efficient caching of other static resources.
  • Affected components: Insight Web

Cardiac arrest report comment not saved on status change​

  • Ticket: 414220423411
  • DevOps: 38736
  • Reported by: HSØ
  • HubSpot Title: Lagring av kommentar i Oppdater status hjertestansskjema rapport
  • Internal Reference: PT-171
  • Issue: Comments entered on the Cardiac Arrest report page were not saved or retrieved when changing the report status. Users experienced that entered comments disappeared, leading to incomplete audit logs and missing context for status updates.
  • Solution: Fixed an issue caused by the use of loosely typed audit log context objects, which led to inconsistent serialization and data loss. Introduced a strongly typed CardiacArrestAuditLogContext. Updated API contracts, repository handling, and UI components to use the typed model. Additionally, improved comment retrieval to handle both legacy (comment) and new (Comment) field formats case-insensitively, ensuring backward compatibility with existing data.
  • Affected components: Insight Web

Mission Type filter excludes journals created before upgrade​

  • Ticket: 394407391462, 414220617958
  • DevOps: 37425
  • Reported by: Helse Vest and HSØ
  • HubSpot Title: Oppdragstype filter - ingen treff / Søk med Oppdragstyper gir kun treff på journaler som er opprettet etter oppgradering
  • Internal Reference: PT-172
  • Issue: After upgrading from version 35.9 to 40.2.7, applying the Mission Type filter in journal search only returned journals created after the upgrade. Journals created prior to the upgrade were not included in the filtered results, even though they appeared correctly when searching without the Mission Type filter. This resulted in incomplete search results and hindered access to historical data.
  • Solution: Fixed an issue in the SQL query logic within SearchRecordRepository where mission types with a NULL predecessor were incorrectly excluded. These records represent the latest active version of Configurable Mission Types but were unintentionally filtered out. The query was updated to include these entries, ensuring that both pre-upgrade and post-upgrade journals are returned correctly when applying the Mission Type filter.
  • Affected components: Insight Web, Insights API

✅ Affected components​

Compiled a list of affected components impacted by the fixes included in version 40.2.11.

  • Client Application
  • Client Hub
  • Data Warehouse Export Service
  • EOC Integration
  • Form Module API
  • HP Link Patient Identity API
  • Insights API
  • Insight Web
  • Export Service
  • LiveView API
  • Migration and Seeding Tool

For release 40.2.11 release we recommend to run the DB migration and install all the listed components above

✅ Testing Focus Areas for 40.2.11 Fixes​

🧾 Journal Creation & Sync​

  • Validate journal creation under poor network conditions
  • Verify no journal records with AMIS number and Data missing are created when app is force-closed
  • Ensure CentralMissionId and ResourceId are always persisted

📊 Overview Report​

  • Confirm data is returned correctly for all roles
  • Validate role-based filtering of data
  • Cross-check results with:
    • Record Search
    • Timeline Report
  • Verify no empty results (data: []) when valid access exists

📝 Form Data Persistence (Windows 10)​

  • Enter data in forms and simulate:
    • Connection lost events from MTU or any status message
    • App minimize / force close
    • Flyout interruptions
  • Ensure data is saved and restored correctly
  • Verify behavior on both:
    • Windows 10 (fix validation)
    • Windows 11 (no regression)

📄 EMCC Ticket / Problem Description​

  • Test large inputs:
    • Boundary values (2048, 5000, 10,000 chars)
  • Confirm:
    • No truncation errors
    • Data is persisted correctly
  • Validate:
    • UI scroll behavior for long text across solution(EWA Client, LiveView ISBAR)
    • Export service

🌐 Insight Web Page Loading​

  • Verify Insight pages load correctly:
    • Real-time screen
    • Timeline report
    • Cardiac arrest report
  • Test with:
    • Cached browser state (returning user)
    • Fresh load
  • Confirm:
    • No blank/white screens
    • Proper cache revalidation after deployment

❤️ Cardiac Arrest Report​

  • Validate:
    • Comment is saved when changing status
    • Comment persists after reload
  • Verify:
    • Audit logs store correct OldStatus, NewStatus, Comment
    • Both legacy and new comment formats are readable
  • Test UI flows:
    • Status update popup

🔍 Mission Type Filter – Journal Search​

  • Validate:

    • Mission Type filter returns journals created both before and after upgrade
    • Older journals are visible when filter is applied
    • Results match expected output when compared with unfiltered search + manual filtering

  • Verify:

    • Consistent results across all mission types (existing and new)

  • Test UI flows:

    • Apply and remove Mission Type filter

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