Skip to main content

EWA Release 40

For the Norwegian translation of these release notes, please refer here.

Version 40.1.0 beta: Component Versions​

Version 40.1.0 beta of EWA was released to customers on August 25th 2025.

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

ComponentVersion
Chat Server25.8.204.0
Client Application25.8.174.0
Client Hub25.8.223.0
Data Warehouse Export Service25.8.202.0
EOC Integration25.8.182.0
Export Service25.8.202.0
Insights API25.8.191.0
Form Module API25.8.59
HP Link Patient Identity API25.8.201.0
Insights Web25.8.201.0
LiveView API25.8.195.0
Medical Unit Broker25.7.1.0
Migration and Seeding Tool25.8.202.0
Personnel Registration API25.8.14.0
Version Manager API25.8.182.0
Version Manager Client Installer25.8.83.0

Version 40.1.0 beta: New Features​

Browser-based OpenID Connect login flow from EWA Client​

Implemented the possibility to activate for browser-based OpenID Connect login flow from the EWA Client.

When using this login flow, the client will launch the default system browser with the identity provider login page when clicking the login button in the EWA Client. After successful login in this page, the user will be brought back to the EWA application, where they should be able to set session PIN as normal.

This feature should make it possible to use OIDC identity providers with login methods that requires extra extensions or certificates in the browser to log into the EWA Client application.

To enable this feature, change the value of the new ServerSideOIDCAuthentication property in the settings.json for the EWA Client to true. Also requires that an updated ClientHub is installed for the system.

Client-Side Changes to Support OIDC Flow:

  • Instead of opening a webview, the Client now launches the browser with the URL: clienthub/login
  • A new protocol activation endpoint has been added to handle the callback containing cookie and user information.
  • Cookies are now stored in internal storage to represent authenticated users, replacing the previous use of access_token.

All HttpClient requests from the Client now use the stored cookie of the activated user for authentication, ensuring secure and consistent access across sessions.

Affected components: Client Application

Version 40.1.0 beta: Updated Features​

Replaced ISBAR page in Insight​

The previous version of the ISBAR page in Insight has been fully replaced by the new ISBAR page, which was previously available by turning on a feature flag.

The feature flag to activate the new ISBAR page has been made into the default behavior, and the feature flag is marked as Deprecated. The feature flag will disappear from the list after it has been deactivated for all resources.

Note: The new ISBAR page does not display data from the old history of presenting complaint feature. It is recommended to use the new history of presenting complaint feature

Version 40.1.0 beta: Fixes​

Checklist Administration' access right is required for deleting form responses when editing records​

  • Ticket: 168728956143| DevOps: 32702| Reported by: Product Team
  • Issue: Form administration should be restricted to users who are explicitly responsible for this task. The access control logic for completed forms must align with the existing rules for journal information. It is not appropriate to grant form administration rights to all users who have journal editing permissions.
  • Solution: The ChecklistAdministration permission is no longer required to delete form responses. This action can now be performed by any user with the appropriate JournalEdit permission, based on their assigned scope (department, organization, or All).

Affected components: Insight

  • Ticket: -| DevOps: 31991| Reported by: Internal
  • Issue: The client application The client app failed to sync Retts data if a linked resource type had been deleted. This caused disruptions in data synchronization and user experience.
  • Solution: We’ve added a safeguard to prevent deletion of a resource type if it is still linked to any active resources. This ensures data integrity and prevents sync failures in the client app.

Affected components: Insight

Version number for criteria number is added automatically if nothing is sent from EMCC​

  • Ticket: 137910576348 | DevOps: 33263 | Reported by: Helse Vest
  • Issue: The client application always appends the revision number 40 to dispatch codes before it’s sent to the server. This number does not necessarily match the correct revision of the dispatch codes used by the EMCCs.
  • Solution: Remove code to always append the hardcoded revision number 40 to dispatch codes before they are sent to the server.
  • Affected components: Client Application

Denial of Service via SQL server error​

  • Ticket: - | DevOps: 32718 | Reported by: Internal

  • Issue: The solution stops responding when performing an invalid query against the AuditLog.

  • Solution: Fixed issue in validator for audit log search that could result in heavy load on systems running Insight.

  • Affected components: Insight API

Medical Unit Broker Failures​

  • Ticket: - | DevOps: 33410 | Reported by: Lives
  • Issue: Client application spams the technical log with Medical Unit Broker Failure logs (~1400 in one day).
  • Solution: Reduced log level of the “Register equipment call to Medical Unit Broker failed” log messages to Debug.

Affected components: Client Application

Chat session in LiveView not correctly reset when changing records​

  • Ticket: 193231474909 | DevOps: 33121 | Reported by: Helse Sør-Øst
  • Issue: When switching between patient records in LiveView, the chat component continued to receive and display messages from the previous session. This led to messages intended for one patient record could appear while viewing another.
  • Solution: Modified the chat communication service to only display incoming messages if the message’s sessionId matches the current activeSession.

Affected components: Client Application, Insight

Missing Update of Urgency Level in LiveView When Modified from EOC​

  • Ticket: 162403033290 | DevOps: 32667 | Reported by: Helse Sør-Øst
  • Issue: Updates to the criteria number or urgency level from EOC were not reflected correctly in LiveView. Specifically, the color in the overview page was not updated based on the new urgency level.
  • Solution: Adjusted LiveView to correctly interpret incoming EOC updates and apply urgency level logic according to the Norwegian EOC integration. The overview color now updates as expected based on urgency level or criteria number, depending on the data received.

Affected components: EOC Integration, Insight, LiveView API

Pictures taken from EWA Client is not getting displayed in LiveView and record search page in Insights​

  • Ticket: - | DevOps: 32853| Reported by: Internal
  • Issue: Pictures taken from EWA Client is not getting displayed in LiveView and record search page in Insights.
  • Solution: Corrected the default routing of AttachmentController to ensure it now properly directs to the Index action.
  • Affected components: Insight, LiveView API

ECG taken in client is not shown in LiveView DECG tab​

  • Ticket: - | DevOps: 32852| Reported by: Internal
  • Issue: ECG taken in client is not shown in LiveView DECG tab, the ECG is sent to the server and available in view/edit records page only not visible in LiveView
  • Solution: Fixed incorrect JSON parsing and empty result check in AJAX response, ensuring proper viewer initialization only when valid attachment data is returned.
  • Affected components: Insight, LiveView API

EWA client crashes when clicking about application​

  • Ticket: - | DevOps: 32777| Reported by: Internal
  • Issue: EWA client crashes when clicking about application on either the Overview page or the Record Overview page.
  • Solution: Fixed a crash in the EWA client by safely accessing EssXml.Version using null-conditional logic when clicking "About Application" on the Overview or Record Overview pages.

Affected components: Client Application

Unable to save unobserved logs on ClientHub​

  • Ticket: - | DevOps: 33078| Reported by: Internal
  • Issue: When opening the app, log in and doing the sync, there are some warnings logged and sent to server but they cannot be saved to the db and spamming in the technical log. Clienthub is unable to save the logs for unobserved exception sent from Client app.
  • Solution: Fixed a logging error where the Logger field exceeded the database column limit by relocating detailed sender information to the Context field of the log payload.
  • Affected components: Client Application

The Insight application repeatedly switches to English, ignoring the user's selected language preference​

  • Ticket: 199843493081 | DevOps: 33246| Reported by: HSØ
  • Issue: Users are continuously experiencing that the Insight Client defaults to English, even though the application's language settings are configured to Norwegian.
  • Solution: Fixed an issue where language preferences were not retained in the Insight application by ensuring language and time zone cookies are set with proper expiration and path options.
  • Affected components: Insight

Patient ID verification data is not shown in ISBAR​

  • Ticket: 199711881442| DevOps: 33245| Reported by: HSØ
  • Issue: In the new ISBAR view, the "Verification of ID" is no longer displayed as it was in the previous view.
  • Solution: Refined patient data handling across multiple components to ensure accurate display, including updates to model usage, nullability checks, and data passing between MissionPatientsOverview, PatientItemContent, and RecordPatientOverview.
  • Affected components: LiveView API

Chat module doesn't have a proper way to validate to check weather the video feature is enabled or not​

  • Ticket: 158108695789| DevOps: 32505| Reported by: HSØ
  • Issue: When we don't have a valid configuration in system configuration table for MediaSDKSettings chat feature doesn't work
  • Solution: Updated video feature management by introducing ShouldEnableVideoFeature in VideoService, refining rendering logic in LiveViewConsultation.razor, and removing outdated WebRTC-based disabling and unused directives.
  • Affected components: Client Application, Insight, LiveView API

InsightsWeb - GetClaimsFromUserInfoEndpoint does not work for on-prem customers​

  • Ticket: 178090002658| DevOps: 32996| Reported by: HSØ
  • Issue: The OpenIdConnect option GetClaimsFromUserInfoEndpoint does not work with on-prem customers, or with custom EntraID application scopes.
  • Solution: Removed GetClaimsFromUserInfoEndpoint from OpenID Connect configuration due to limitations with Entra ID scopes in an on-prem setup, improving compatibility and stability for affected customers.
  • Affected components: Client Application, Insight, LiveView API

Known issues in 40.1.0​

  1. Loss of history of presenting complaint data(New history of presenting complaint feature) for completed records under poor network conditions.
  2. History of presenting complaint webview crashes while responding to the form in the client application, particularly under poor network conditions. This issue occurs inconsistently.

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.2.2 and 4.3.2
  • SDK version: 4.3.0.0

Zoll​

  • Software version: 02.36.21.00
  • SDK version: 6.44.315