Skip to main content

EWA Release 40.2.3

Version 40.2.3 stable: Component Versions​

Version 40.2.3 stable of EWA was released to customers on December 1st 2025.

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

ComponentVersion
Chat Server25.12.11.0
Client Application25.11.154.0
Client Hub25.12.12.0
Data Warehouse Export Service25.12.11.0
EOC Integration25.12.12.0
Export Service25.12.11.0
Insights API25.12.11.0
Form Module API25.12.1.0
HP Link Patient Identity API25.12.12.0
Insights Web25.12.11.0
LiveView API25.12.11.0
Medical Unit Broker25.12.1.0
Migration and Seeding Tool25.12.11.0
Personnel Registration API25.12.1.0
Version Manager API25.12.11.0
Version Manager Client Installer25.12.11.0

Version 40.2.3 stable: New Features​

No new features were included in this release.

Version 40.2.3 stable: Updated Features​

No updated features were included in this release.

Version 40.2.3 stable: Fixes​

EMCC Integration module does not work in 40.2.2​

  • Ticket: 266761986257| DevOps: 35245| Reported by: HSØ
  • Issue: The EMCCIntegration module fails to initialize and connect to the database. Attempts to run the module result in errors.
  • Solution: Updated target framework to .NET 8.0 and upgraded NuGet package dependencies from v7.0.9 to v8.0.21.
  • Affected components: Integration

The UpdatedAt timestamp is reset for all records linked to the LiveView whenever a new record is added.​

  • Ticket: - | DevOps: 35125 | Reported by: Internal
  • Issue: The UpdatedAt timestamp was incorrectly reset for all records in LiveView whenever any single record was updated, due to an incorrect filter condition.
  • Solution: Apply filtering by a unique identifier to ensure only the updated record is affected.
  • Affected components: Insight Web

History log is not getting displayed after updating data in SATS configuration page​

  • Ticket: - | DevOps: 35123 | Reported by: Internal
  • Issue: The history log shows empty after updating SATS configuration.
  • Solution: Correct the way to read the log context.
  • Affected components: Insight Web

Upgrade from 35.9 client to 40.2.2 client fails​

  • Ticket: 270376588511 | DevOps: 35271 | Reported by: HSØ
  • Issue: In release 40.2.2, a migration added new columns to a table in the Client application. However, if the application had pending records at the time, the migration failed and caused the app to crash.
  • Solution: Adjusted the migration process to update the default values only for the specific new columns, instead of updating the entire record entity.
  • Affected components: Client Application

Getting a 500 error when searching in the overview report.​

  • Ticket: - | DevOps: 35124 | Reported by: Internal
  • Issue: When searching in the overview report, a 500 error is thrown, and the page cannot return any result.
  • Solution: The root cause of the bug is that with the new Configurable Mission Types feature, we can disable some tiles. This makes the data of those tiles become null instead of using the default value like before. Updated the code to handle the null cases for the overview report.
  • Affected components: Insight Web

DIPS Export - CDA time value should not contain any UTC time format.​

  • Ticket: 268450137303 | DevOps: 35251 | Reported by: HSØ
  • Issue: The CDA time is currently formatted with the “+0000” suffix, which represents the UTC offset in a DateTimeOffset. This part should not be included.
  • Solution: Update the CDA time format to yyyyMMddHHmm, which is in UTC but excludes the UTC offset.
  • Affected components: Export Service

Audit Log “Changed Value” entries not mapped correctly — data shown only in “Details” (EWA 40.2.2).​

  • Ticket: 269379314932 | DevOps: 35283 | Reported by: HSØ
  • Issue: The audit log entries where the Action is “Changed Value” no longer display data in the Old Value, New Value, and Reason columns..
  • Solution: Correct the audit log data sent from Insight Api.
  • Affected components: Insight Api

Urgency level data is removed from ISBAR after the mission type is set for the record in the Client Application.​

  • Ticket: - | DevOps: 35093| Reported by: Internal
  • Issue: When the urgency level tile is disabled in Configurable Mission Types, after the EMCC/EOC mission reaches the EWA Client App, opening it, choosing a mission type with the urgency tile disabled, and selecting a delivery place causes the urgency level to be empty in the Liveview ISBAR page.
  • Solution: Updated the code to keep the urgency level data from EMCC/EOC, even when the urgency tile is disabled by Configurable Mission Types.
  • Affected components: Client Application

When trauma tile is mandatory in the tile mask and the value is set to no in the client journal, the validation in Insight should not validate for hidden tiles.​

  • Ticket: 269446063325 | DevOps: 35272 | Reported by: HSØ
  • Issue: Trauma fields were still being processed even when the case was not marked as “yes”.
  • Solution: Adjust the logic so trauma fields are only validated when the case is marked as “yes”; otherwise, they are skipped.
  • Affected components: Insight Api

When Via tile is mandatory in the tile mask and the value is set to no in the client journal, the validation in Insight should not validate for hidden tiles.​

  • Ticket: 268310969582 | DevOps: 35273 | Reported by: HSØ
  • Issue: The Via fields were incorrectly treated as required instead of optional.
  • Solution: Update the logic so Via fields are always optional.
  • Affected components: Insight Api

Unable to complete the record after filling all mandatory tiles in the record​

  • Ticket: 280551468240, 279158884544 | DevOps: 35707 | Reported by: HSØ, HMN
  • Issue: Records couldn’t be completed because the mandatory Treater field showed as optional and didn’t switch to its mandatory state when multiple workers were logged in.
  • Solution: Updated the Treater field configuration so it correctly displays as mandatory. The tile now flips to dark blue as expected when opening or switching records.
  • Affected components: Client Application

The consultation flyout appears blank when the app is used after being offline, and the user goes out of the record and accesses it again​

  • Ticket: 280135663834 | DevOps: 35705 | Reported by: HSØ
  • Issue: The Consultation attempts to start a new chat session while the device is offline, but the initialization fails and the UI does not respond.
  • Solution: Do not initialize the chat session when the device is offline. Instead, show a warning message. When the device comes back online, automatically reconnect and re-initialize the chat session.
  • Affected components: Client Application

App crashes when creating manually missions in training mode.​

  • Ticket: 278117699802 | DevOps: 35686 | Reported by: HSØ
  • Issue: App crashes when creating manual missions in training mode.
  • Solution: Make sure that only create patient when the mission is created.
  • Affected components: Client Application

While creating a new form, if a resource is assigned and the form is published or saved as a draft, the resource is not being mapped to the form.​

  • Ticket: 287590709452 | DevOps: 35786 | Reported by: Helse Midt
  • Issue: The resource is not being mapped to the form, the recourse section is empty.
  • Solution: Save the selected resources after changing.
  • Affected components: Insight Web

Start Location & Patient Care mandatory validation error​

  • Ticket: 271628337374, 280933127360 | DevOps: 35721 | Reported by: HSØ, HMN
  • Issue: When Start Location and Patient Care Completed are set as mandatory tiles in the tile mask, and their feature flag is turned off, the user can fill all required tiles in the Client App, but completing the record in Insight Web fails and shows a validation error.
  • Solution: Update the record completion validation so it also checks the feature flags for any fields that use a feature flag.
  • Affected components: Insight API, Insight Web

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.3.2
  • SDK version: 4.3.0.0

Zoll​

  • Software version: 02.36.21.00
  • SDK version: 6.44.315