Skip to main content

Bliksund EWA Release 35

Version 35.0 of EWA was released to customers on November 20th, 2024. For the Norwegian translation of these release notes, please refer here.

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

ComponentVersion
Chat Server24.11.275.0
Client Application24.11.275.0
Client Hub24.11.275.0
Data Warehouse Export Service24.11.275.0
EOC Integration24.11.275.0
Export Service24.11.275.0
Form Module API24.11.275.0
HP Link Patient Identity API24.11.275.0
Insight24.11.275.0
LiveView API24.11.275.0
Medical Unit Broker24.11.275.0
Migration and Seeding Tool24.11.275.0
Personnel Registration API24.11.275.0
Version Manager API24.11.275.0
Version Manager Client Installer24.10.151.0

Content of this Release​

New Features

Updated Features

Fixes in Version 35.0

Patch 35.1

Patch 35.2

Tested Medical Devices

New Features​

Extended Offline Mode (Release candidate)​

We have added the possibility to cache the login details to enable the users to stay logged in and reactivate the client after restart even without network. This is controlled by a feature flag that has to be activated for the resource. The functionality will only work after a normal login is performed after the feature is activated and client is synced. This will not affect the normal token validation times.

Affected components: Client Application

Updated Features​

Improved Management of Urgency Levels in EWA System​

We have enhanced how urgency levels are handled in the EWA system to provide greater flexibility and control. Urgency levels are now stored as entities in the database, rather than being embedded in the source code itself. This change allows users to add, modify, or soft-delete specific parts of these entities using the newly introduced specialized tools for managing urgency levels in the Migration and Seeding tool. This removes the requirement for developer intervention in tasks such as adding new urgency levels, simplifying configuration and management, and making updates more efficient while ensuring the consistency of existing records. The report pages (My Records, Billable Mission Report, and Overview Report) now display urgency levels based on the criteria number set in Insight.

note

We strongly recommend that Bliksund provides the definition file for this tooling. The file is a complex JSON structure, and any incorrect modifications could cause issues in the system.

Data Conversion for the New Urgency Levels​

To ensure a smooth transition to the new structure for urgency levels, we are performing a specific data conversion. This conversion will ensure that existing urgency levels are correctly mapped to the new entity structure in the system, and that all records are correctly linked to these new urgency level entities.

The following data conversion will run directly after specific database schema migrations, as part of this release:

  • Data Conversion: UrgencyLevelsDataConversion | DB Schema Migration: 202409100830216_UrgencyLevelsDataConversion
  • Description: This process will scan all existing records in the system and link them to the newly defined urgency level entities, ensuring the integrity of customer data within the updated structure.
warning

IMPORTANT: The UrgencyLevelsDataConversion process will take some time to complete, as it needs to scan all existing records in the system. There is also a high chance it may time out if the system is under heavy load. To avoid issues, we strongly recommend running this data conversion during off-peak hours. If the process times out, it can be rerun using the --run-converter argument in the Migration and Seeding tool, as shown below.

.\Bliksund.EWA.MigrationTool.exe --run-converter UrgencyLevelsDataConversion

Affected components: EOC Integration, Insight, Migration and Seeding Tool

Chat Consultation History Available in Insight View & Edit Record Pages​

The chat consultation history from the EWA client application is now integrated into the record view and edit pages in Insight. A new dedicated section provides a timeline of chat participants and their messages, together with the timestamps, as shown in the screenshot below. This enhancement improves audit and documentation processes for chat-based consultations conducted during missions, and reinforcing communication traceability.

Consultation History in Insight

Affected components: Insight

Fixes in Version 35.0​

Heading Overwrites Date in Print​

  • Ticket: 3211799527 | DevOps: 24094 | Reported by: Helse Nord
  • Issue: Long Health Trust names cause the heading to overlap with the date in the print view.
  • Solution: The Health Trust name and resource name are now displayed on a separate line, below the date and journal state, to avoid overlapping.
  • Affected components: Form Module API

Unable to Search and Add Locations in All Location Tiles in EWA Client​

  • Ticket: 3845373630 | DevOps: 21911 | Reported by: Helse Nord
  • Issue: The search field on all location tiles is occasionally disabled, preventing users from searching for location, especially whenever at least one Blazor component is active.
  • Solution: The Blazor WebView2 component was wrapped in an additional control to prevent overlapping, ensuring the search field functions correctly.
  • Affected components: Client Application

Missing Upload Button on Version Manager Page​

  • Ticket: E-mail | DevOps: 26595 | Reported by: Helse Vest
  • Issue: The upload button was not visible on the Version Manager page.
  • Solution: The upload component was updated to be compatible with recent changes to the frontend library, restoring visibility and functionality.
  • Affected components: Insight, Version Manager Client Installer

Resource Change Error After Record Deletion in Insight​

  • Ticket: 4954148336 | DevOps: 26751 | Reported by: Helse Sør-Øst
  • Issue: When attempting to change the resource after record deletion from Insight, an error message appears stating that it is not possible to change the resource due to ongoing missions.
  • Solution: Local data is now automatically updated whenever there are any changes from Insight, ensuring the latest information is available in the client before changing the resource.
  • Affected components: Client Application

Missing Total Score in Form Print​

  • Ticket: 6197744855 | DevOps: 26657 | Reported by: Helse Midt
  • Issue: The total score from the form response was not displayed in print.
  • Solution: The calculation method was fixed to ensure the total score is correctly displayed in the print output.
  • Affected components: Form Module API

Incorrect Mission Type Displayed on "My Records" Page and Category Filter​

  • Ticket: 8729620692 | DevOps: 26893 | Reported by: Helse Vest
  • Issue: The mission type on the "My Records" page and the mission category filter are displaying the ID value instead of the corresponding mission type name.
  • Solution: Fixed the page results and the filter to display the correct mission type names, utilizing the new configurable mission type feature.
  • Affected components: Insight

Data from Previous Records in EOC Ticket​

  • Ticket: 5992380918 | DevOps: 26705 | Reported by: Helse Midt-Norge, Helse Sør-Øst
  • Issue: When creating a new record, the EOC ticket information from previous records briefly appeared for a few seconds before the correct ticket was loaded. This delay lasted longer on tablets with poor internet connections.
  • Solution: Added a placeholder logo to temporarily replace the EOC ticket information while the old data is cleared during record switches or new record creation. This ensures that only the correct ticket data is displayed once available, preventing incorrect data from appearing during delays.
  • Affected components: Client Application

Missing Line Breaks in EOC Ticket Description​

  • Ticket: E-mail | DevOps: 27240 | Reported by: Helse Sør-Øst
  • Issue: Line breaks in the problem description field of the EOC ticket were not displayed correctly in the client application.
  • Solution: Enabled support for rendering line breaks in the description text, ensuring proper display of the content in the client application.
  • Affected components: Client Application, EOC Integration

Inconsistent Date Format for NEWS2 and SATS Triage in Insight and Export​

  • Ticket: 7544822497 | DevOps: 26984 | Reported by: Helse Midt
  • Issue: The date format for NEWS2 and SATS triage performed was inconsistent across cultures when displayed in print or exported.
  • Solution: Applied the correct culture settings to the datetime converter during PDF rendering, ensuring consistent and accurate date formatting across all regions.
  • Affected components: Export Service, Form Module API

Missing EOC Alerted Time in the Main Report in Insight​

  • Ticket: 26923246809 | DevOps: 27527 | Reported by: Helse Sør-Øst
  • Issue: The CSV file exported via the "Generate Main Report" feature in Insight is missing the EOC/EMCC Alerted Time. This is due to recent changes in the EMCC/EOC ticket structure, which causes the data to be NULL in the record.
  • Solution: Modified the report generation process to retrieve the EOC/EMCC Alerted Time from the separate database table containing the EOC/EMCC ticket information, if available. As a fallback, if the data cannot be found in this table, the EOC/EMCC Alerted Time stored within the record data will be used.
  • Affected components: Insight

Issue with Mission Type Display in CSV Export from Main Report in Insight​

  • Ticket: 28764919002 | DevOps: 27592 | Reported by: Helse Nord
  • Issue: The CSV file exported via the "Generate Main Report" feature in Insight incorrectly displays a GUID in the Mission category column due to recent changes in the Configurable Mission Types feature.
  • Solution: Modified the report generation process to retrieve the Mission type (mission category) data from the separate RecordConfigurableMissionTypes database table, if available. As a fallback, if the data cannot be found in this table, the Mission type (mission category) stored within the record data will be used.
  • Affected components: Insight

Mission Type Text Displayed in English in Exported PDF​

  • Ticket: 24971114715 | DevOps: 26752 | Reported by: Helse Nord
  • Issue: The PDF generated by the export service displayed the mission type text always in English, instead of the chosen application language.
  • Solution: Enhanced language code handling by updating the default language code from "no" to "nb-NO". Corrected the usage of scoped services and adjusted the initialization process to ensure proper language display.
  • Affected components: Export Service

Patch 35.1​

Version 35.1 of EWA was released exclusively to SaaS customers, as it includes cloud-specific updates not applicable to on-premise setups.

Patch 35.2​

Version 35.2 of EWA was released to customers on January 17th, 2025.

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

ComponentVersion
Chat Server25.1.201.0
Client Application25.1.201.0
Client Hub25.1.201.0
Data Warehouse Export Service25.1.201.0
EOC Integration25.1.201.0
Export Service25.1.201.0
Form Module API25.1.201.0
HP Link Patient Identity API25.1.201.0
Insight25.1.201.0
LiveView API25.1.201.0
Medical Unit Broker25.1.201.0
Migration and Seeding Tool25.1.201.0
Personnel Registration API25.1.201.0
Version Manager API25.1.201.0
Version Manager Client Installer24.10.151.0

This patch includes the following fixes:

Unable to Print from Consultation LiveView​

  • Ticket: 46548233423 | DevOps: 28012 | Reported by: Helse Sør-Øst
  • Issue: When attempting to print from the Consultation LiveView in the EWA Client, an error occurs indicating that the record must exist in the specified LiveView for it to be printable.
  • Solution: This issue has been resolved by updating the data validation logic, ensuring that the consultation location type is properly included for print processing. The fix allows printing to work as expected when the LiveView is properly associated with the record.
  • Affected components: Insight

Missing Content in Insight After Installation of Version 35​

  • Ticket: 42418516185 | DevOps: 27913 | Reported by: Helse Sør-Øst
  • Issue: After installing version 35 in the test environment, HSØ reported that content in Insight was not displayed until the user cleared cache/cookies or refreshed the page. The page appeared blank immediately after logging in following the installation.
  • Solution: Outbound rules were adjusted to prevent caching issues, ensuring that content loads correctly without the need for manual cache clearing or page refresh.
  • Affected components: Export Service, Insight

Random Delivery Locations Displayed in LiveView Consultations​

  • Ticket: 50956989679 | DevOps: 28253 | Reported by: Helse Sør-Øst
  • Issue: When using the consultation module in LiveView, the selected delivery location is not displayed correctly. Instead, a random location is shown, particularly when selecting a consultation partner tied to a standard LiveView. If multiple delivery locations are associated with the LiveView, the system defaults to the first listed location rather than the correct one.
  • Solution: The filtering logic has been updated to ensure only relevant configurations are retrieved. This adjustment improves the accuracy of the data being processed, ensuring the correct delivery location is displayed during consultations.
  • Affected components: Insight, LiveView API

Main CSV Report Fails for Large Data Sets Over 2100 Records​

  • Ticket: 49375240435 | DevOps: 28144 | Reported by: Helse Sør-Øst
  • Issue: With Release 32, customers reported that the Main CSV Report throws an exception when the number of records exceeds 2100. This occurs due to SQL Server's limitation on handling more than 2100 parameters in a single query. The issue causes the Main Report page to fail entirely.
  • Solution: Large data sets are now divided into smaller groups of up to 2000 records. Each group is processed separately, and the results are combined to generate the full report without errors, regardless of the data set size.
  • Affected components: Insight

Tested Medical Devices​

This release has 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