Bliksund EWA Release 37

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

Versions 37.0 and 37.1 (SaaS)

Versions 37.0 and 37.1 of EWA were released exclusively to SaaS customers, as they include cloud-specific updates not applicable to on-premise setups.

Version 37.2 beta

Version 37.2 beta of EWA was released to customers on February 19th, 2025.

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

Component	Version
Chat Server	25.2.104.0
Client Application	25.2.104.0
Client Hub	25.2.104.0
Data Warehouse Export Service	25.2.104.0
EOC Integration	25.2.104.0
Export Service	25.2.104.0
EWA API	25.2.104.0
Form Module API	25.2.104.0
HP Link Patient Identity API	25.2.104.0
Insight	25.2.104.0
LiveView API	25.2.104.0
Medical Unit Broker	25.2.104.0
Migration and Seeding Tool	25.2.104.0
Personnel Registration API	25.2.104.0
Version Manager API	25.2.104.0
Version Manager Client Installer	25.2.104.0

Content of this Release

New Features

Updated Features

Fixes in Version 37.2

Tested Medical Devices

New Features

Enhancements for Documenting History of Presenting Complaint (Release Candidate)

The previous system for documenting patient complaints in EWA faced several issues, including double documentation, confusion due to unfamiliar formats like SAMPLER/OPQRST, and an overly complex interface. These problems led to inefficiencies and challenges for both prehospital and hospital staff. We addressed these issues with the new History of Presenting Complaint feature, which introduces a configurable and user-friendly interface to simplify workflows and enhance usability.

note

The 'History of Presenting Complaint' feature flag must be enabled for the resource, the HOPC form should be assigned to the resource in use, and the form must be published to ensure the configured history of presenting complaint feature is visible in the EWA Client. If the 'History of Presenting Complaint' feature is disabled for the resource, the client will revert to the previous feature.

Key Improvements:

• Configuration Page: A new configuration page in Insight allows users to create, edit, and delete forms for the History of Presenting Complaint. This page functions similarly to the existing Form administration but with added flexibility to configure forms and synchronize them with the app.

• Client Integration: The History of Presenting Complaint responses are now available in the client application, allowing ambulance staff to enter data directly in real-time during patient assessments.

• Print/Export: The print and export functionality has been updated to include History of Presenting Complaint data. Only questions that have received responses are included, ensuring clarity and relevance in printed or exported records.

• Insight View/Edit Record Page: The Insight view and edit record pages now support the History of Presenting Complaint responses. This means clinical staff can view and edit this data directly within the patient's record, improving workflow efficiency.

• LiveView ISBAR: History of Presenting Complaint has been integrated into the LiveView ISBAR page. The page now includes five sections (Patient Overview, EMCC Data, Ambulance Overview, History of Presenting Complaint, and Forms) as shown in the screenshot below, with real-time data updates. This section is built using Blazor components for improved performance and responsiveness, especially on tablet-sized devices and larger.

• Enhanced Flexibility and Configurability: Customers can configure the History of Presenting Complaint setup within Insight and synchronize it with the app, providing better control over the feature and how it is used in the field.

• Resource Linking and Trigger-Based Activation: Forms in the History of Presenting Complaint can now be linked to resources and triggered automatically, mirroring the functionality of other forms in the system.

• Simplified User Interface: The user interface has been simplified for the History of Presenting Complaint setup, reducing unnecessary complexity. The new layout reduces clicks and provides a clearer overview for users.

Affected components: Client Application, Client Hub, Export Service, Form Module API, Insight, LiveView API

More information on the flow change is described here History of presenting complaint user guide.

Installation guide for setting up EWA API is described here EWA API Installation guide

Changes to LiveView installation guide to include 'FormModuleAPI Path' and 'FormModule Api Key' is described here LiveView Installation guide

Introduction of New Urgency Level Tile and Sorting by Urgency Level

Customers across various countries use diverse dispatch and urgency codes, which required us to replace the rigid structure of handling urgency codes in our application with a more flexible and configurable solution. A new urgency level tile now allows adapting these configurations to the customers' specific needs, enabling greater alignment with regional or operational requirements and supporting connections to different EOCs. Tile visibility and mandatory settings are configurable based on mission types, and the tile becomes read-only when viewing signed or completed records. Legacy configurations used by existing customers are fully supported within the new tile, ensuring a seamless transition without disrupting their workflows.

The urgency levels can be managed centrally with the Migration and Seeding tool, making it easier to update and align them with operational changes. We added functionality for sorting urgency levels in all places in the EWA client application and Insight, such as in the record page, enabling better structure and prioritization of urgency levels across platforms.

We have made the 'Not selected' text in the mission type tile configurable, removing the hardcoded value. By default, the mission type tile will display 'Not selected,' which will also be available in the selection dropdown.

Please run the migration and seeding tool for 'ConfigurableMissionTypes.json' included with this release, to apply these changes.

Affected components: Client Application, Client Hub, Insight, Migration and Seeding Tool

Offline Functionality for Tablets

To ensure continuous operation even when the device loses online connectivity, we have introduced a feature that allows the system to maintain key functionalities, including the ability to register record information without an active network connection. This is especially important in environments where connectivity may be unreliable or temporarily lost, such as during missions in rural areas or tunnels.

What has been implemented:

• Offline Indicator: A clear offline status indicator has been added to the lock screen, overview page, and record page to inform users when the device is disconnected from the network. This visual cue (see screenshot below) helps users understand the offline status, ensuring they can take appropriate actions when connectivity is lost and continue working without confusion.

• Tracker Functionality: The tracker functionality now remains operational even after logging in, even when the device is disconnected from the network. This ensures that users are not unexpectedly logged out due to a lost connection, allowing them to continue working on records seamlessly during missions or in environments where network issues may arise.

• Error Messaging: In cases where the client cannot connect to the server for updates or data exchanges, an error message is displayed to inform users about the offline status. This message provides clarity on the situation, ensuring that users are aware of the connectivity issue and can manage their tasks accordingly until the network is restored.

The offline functionality is managed via a feature flag, allowing it to be activated only when required by the customers and providing flexibility to adapt to changing operational needs.

Affected components: Client Application

Updated Features

Enhanced Patient and Incident Data Visibility in Insight

In the latest update, the full EOC incident number will now be displayed in its complete format on the search record page in Insight. This ensures that users can easily distinguish between similar incidents. Additionally, the system now supports searching for the full incident number, making it quicker and easier to locate specific records.

As an additional update, the patient's name will no longer be shown by default in the overview of search records. Instead, users now have the option to show or hide the patient's name through a simple toggle in the context menu. If the user searches using patient-related filters, the name will automatically be revealed. This gives users more control over the visibility of sensitive data while maintaining ease of access when needed.

Both changes are designed to enhance user experience by improving the manageability of incident and patient data.

Affected components: Insight, Migration and Seeding Tool

JSON Version Update to Ensure Compatibility with Norwegian Cardiac Arrest Registry

The Norsk hjertestansregister (Norwegian Cardiac Arrest Registry) has updated the data structure in their system, requiring any imported JSON files to align with the changes to ensure error-free data imports. To maintain compatibility, we have adjusted our cardiac arrest JSON file to align with the changes from version 22 to version 24. The update has already been applied automatically, and no further action is required from customers. This adjustment ensures that manually uploaded JSON files meet the updated requirements of the registry, ensuring seamless and accurate data processing.

Affected components: Client Application, Cardiac arrest report

Reintroduction of the EOC Alerted Tile and Deprecation of Editable EOC Ticket

The tile allowing manual entry of the timestamp (CentralAlerted, former EOC_Alerted) for when the EOC was first alerted was previously removed from the EWA application, as this information was intended to be provided through the EOC Integration and was not meant to be editable by ambulance staff. However, with the onboarding of new customers who are not connected to a central EOC, it became necessary to reintroduce this feature to accommodate their needs. As a result, the tile has been reintroduced as an optional and editable feature.

To support this, the CentralAlerted field has been reintroduced, enabling the manual tracking of this timestamp. New logic ensures that this timestamp can be checked, updated, and displayed across the application. Validation processes have been implemented to maintain data integrity, while UI elements have been added to improve visibility and control over the CentralAlerted status. This tile can be hidden using configurable mission types, allowing customers with a central EOC to continue using the existing system, while providing flexibility for other customers who require manual data entry of this information.

To ensure the proper functionality of the reintroduced, editable EOC Alerted tile, the previously available feature for editing information in the EOC ticket tile has been removed. This change was made to streamline the system and prevent conflicts between the two features. As a result, users will no longer have the option to manually edit the EOC ticket, aligning with the new approach for handling the CentralAlerted timestamps.

Affected components: Client Application, Insight

SATS Upgrade: Improved Localization and Assessment Display

The SATS assessment module has been refined to enhance clarity, ensure consistency in terminology, and align with established guidelines across the interface and reports. Key terminology has been updated, scoring adjustments have been made, and localization improvements provide a more accurate representation of assessment statuses.

Key Improvements:

• Configuration PageRemoval of Hyperlinks: All hyperlinks have been removed from SATS, including those for phone numbers. A new reference text has been introduced: "See Helsedirektoratet.no, National professional guideline for handling CBRNE incidents with personal injury, chapter 3".

• Priority List Update: The term "No findings" has been replaced with "Green urgency level".

• NEWS2 Consciousness Scoring: The scoring display now follows the established format from e.Care. The term "Unknown" has been replaced with "Not registered" (scoring as 0). The structured list now reads:

  • 0 - A: Awake, normal contact
  • 3 - C: Newly onset confusion
  • 3 - V: Limp, responds to speech
  • 3 - P: Responds to pain
  • 3 - U: No response
  • 0 - Not registered

• Status Labels in SATS: The labels "Incomplete" and "Complete" have been replaced with "Preliminary" and "Final" in all relevant places within EWA and printouts. The final urgency level is only displayed when both the priority list and NEWS2/TEWS assessments are completed.

• Consistent Terminology: NEWS2 or TEWS is now used consistently throughout the system.

Affected components: Client Application, Export Service, Insight

New Training Mode Indicator with Notifications in Client Application

A new Training Mode Indicator has been added to the client application to help users clearly distinguish between training and normal mode, as shown in the screenshots below. A persistent label is displayed at the top of the interface, ensuring visibility at all times, and a notification appears at the start of a new mission to remind users that they are in training mode. These improvements enhance clarity, reduce the risk of confusion, and help prevent unintentional actions in a training environment.

Affected components: Client Application

Enhanced Log Traceability with Device Name in Audit and Technical Logs

The EWA client application now records and displays the device name for logs generated within the system, as shown in the audit and technical logs. This improves traceability by capturing the machine name responsible for each log entry. A new "MachineName" column has been added to the audit log table, and log transmissions from the client now include the device name. Additionally, Insight has been updated to display this information in both the audit log and technical log.

Affected components: Client Application, Insight

Fixes in Version 37.2

Records in LiveView Sorted by Text in Triage Columns (RETTS, NEWS2, and SATS) Instead of Severity

• Ticket: 36129211628 | DevOps: 28470 | Reported by: Helse Sør-Øst
• Issue: In LiveView, records were being sorted by the text in the severity columns (RETTS, NEWS2, and SATS) rather than by the actual triage priority. These columns were not intended to be sortable.
• Solution: To ensure records are no longer sorted by text values, sorting was removed from the three triage columns in LiveView.
• Affected components: Insight

EOC Updates to Place of Delivery Not Applied in Client if Mission Type Is Unselected

• Ticket: 38737585342 | DevOps: 27906 | Reported by: Helse Vest
• Issue: If the mission type was not selected in the client application, updates from EOC (via AMIS) to the place of delivery were not applied immediately. Instead, the update only became visible after another change (e.g., a timestamp update) was received.
• Solution: The update logic was modified to ensure that updates from EOC are processed immediately, even if the mission type is unselected, allowing the place of delivery and other relevant fields to be updated as soon as they are received.
• Affected components: Client Application

English Text on Triage State in Print from Client for First Record After Installation

• Ticket: 67731199182 | DevOps: 28416 | Reported by: Helse Midt-Norge
• Issue: After logging into the EWA Client and starting a mission, filling in SATS, RETTS, and News2 triages, and opening the print option, all triage state text was displayed in English. This happened only for the first record after installation. The print in Insight and exported PDF displayed the text correctly in Norwegian.
• Solution: The issue was caused by missing culture information when retrieving the text. To resolve this, a culture parameter was added to ensure the correct localized text is retrieved based on the language settings.
• Affected components: Client Application, Export Service

Automatic Scrolling Down on View/Edit Record Page

• Ticket: none | DevOps: 27472 | Reported by: Internal QA
• Issue: The View/Edit Record page in Insight automatically scrolled to the bottom each time it was accessed, unexpectedly disrupting navigation and making it difficult to view or interact with other elements on the page.
• Solution: The consultation history panel, which was previously integrated into this page and caused the issue, has been moved to a dedicated tab. This update prevents the unintended scrolling behavior and restores the ability for users to interact with the page elements.
• Affected components: Insight

Internal Server Error When Exceeding Character Limit in Forms

• Ticket: 9682769366 | DevOps: 27150 | Reported by: Helse Vest
• Issue: When creating a new form or adding form elements on the Forms Configuration page, users encountered a 500 internal server error if the name of the form, form element, option, or description field exceeded 260 characters.
• Solution: To prevent server issues, an error message will now appear on the forms configuration page when the character limit is exceeded. Additionally, the character limit will be checked during the JSON import process to ensure it's enforced, allowing users to be notified of the issue before encountering any server errors.
• Affected components: Form Module API, Insight

Invalid Position Information for AtIncident Due to Incorrect Latitude/Longitude Assignment

• Ticket: 5411715520 | DevOps: 27674 | Reported by: Helse Midt-Norge
• Issue: The position data for the AtIncident tile was being incorrectly loaded from the SQLite database, with both latitude and longitude values being placed into the Latitude property, resulting in invalid coordinate information.
• Solution: The issue has been fixed to properly load both latitude and longitude values into their respective properties, ensuring correct position information is displayed for AtIncident again.
• Affected components: Client Application

On-Screen Keyboard Causes Record to Scroll at the Beginning When Clicking Outside Kilometer Tile

• Ticket: 3733910721 | DevOps: 26992 | Reported by: Helse Nord
• Issue: When entering a distance value using the on-screen keyboard in the kilometer tile, clicking outside the tile causes the record to scroll to the start, rather than keeping the record in its current position.
• Solution: Fixed the issue by ensuring that the record keeps its position when the popup closes and does not set the pointer to the start of the record. The same fix has been applied to the Forms and History of Presenting Complaint tiles as well.
• Affected components: Client Application

Forms Partially Opens Outside the Screen on Tablets

• Ticket: 25604439274 | DevOps: 27239 | Reported by: Helse Midt-Norge
• Issue: When opening a form response on the tablet, the dialog sometimes appears partially off-screen if the forms tile is positioned in the middle of the client application. Additionally, the scroll bar is not visible, making navigation difficult.
• Solution: The UI of the forms element was decoupled from the records page, and two separate user control components were created: Form modal and form tile. The form response behavior was updated to use a centered modal/dialog instead of a flyout, similar to the History of Presenting Complaint dialog. This change resolves issues with scroll positioning, dialog size calculations, and inconsistencies caused by screen size, resolution and scaling, ensuring correct and consistent positioning of the user dialogs.
• Affected components: Client Application, Form Module API

Main Report Generation Fails When There Are No Records

• Ticket: 35719632087 | DevOps: 27726 | Reported by: Helse Sør-Øst
• Issue: When generating a main report for a period with no records to retrieve, the screen flickers briefly, but no error message appears, and no file is available for download. Technical logs show additional errors.
• Solution: The issue occurred due to improper handling of empty or null record lists in Insight when no records exist for the specified time frame. The data validation logic and data transformation functions have been updated to address this issue and ensure that, in these cases, a notification is shown to the user or an empty CSV file is provided, instead of generating no output without feedback from the system.
• Affected components: Export Service, Insight

Unable to See the Full Text in the Priority List in SATS

• Ticket: 24054460623 | DevOps: 27897 | Reported by: Helse Vest
• Issue: When selecting SATS and the priority list, the last part of the text is missing for the "Pain" category. Additionally, there is some text displacement in the "Injury" category.
• Solution: The UI for the SATS flyout has been updated to ensure the full text is now displayed correctly, and adjustments have been made to the positioning of the text to resolve the displacement issue in the "Injury" category.
• Affected components: Client Application

User Activity Not Recorded on Clicking HP-Link Integration in EWA Client

• Ticket: 7169590203 | DevOps: 26983 | Reported by: Helse Midt-Norge
• Issue: When a user clicks on the HP-Link integration in the EWA Client, their activity is not recorded in the user activity log in Insight.
• Solution: To resolve this, an audit log has been implemented to ensure that user activity is now tracked whenever the HP-Link menu is opened in the EWA Client. This update ensures better monitoring and transparency for user actions related to HP-Link integration.
• Affected components: Client Application, Integration

Incorrect Reason Logged When Accessing a Record in Insight

• Ticket: 23910718686 | DevOps: 27902 | Reported by: Helse Midt-Norge
• Issue: When opening a completed record in Insight, users must select a reason for accessing the record. This reason was incorrectly logged in the audit log. For example, if "Research" was selected, the audit log recorded it as "Support".
• Solution: The issue occurred due to a mismatch in the option IDs, which has now been corrected, ensuring the accessing reasons are logged accurately in the audit log.
• Affected components: Insight

Automatic Synchronization Feature Not Functioning in the Client

• Ticket: none | DevOps: 27895 | Reported by: Internal QA
• Issue: Automatic synchronization in the client no longer worked as expected. Previously, synchronization occurred automatically every hour, but now it requires manual synchronization, including restarting the client application and exchanging resources.
• Solution: The automatic synchronization feature was removed, and the "Sync All" button was updated to improve its usability. Additionally, the internet connectivity handling was refactored to ensure more reliable synchronization and address previous issues.
• Affected components: Client Application

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

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

Updates from Record Not Reflected in LiveView ISBAR View During Consultation

• Ticket: none | DevOps: 24568 | Reported by: Internal QA
• Issue: Changes made to a record in the client are not updated in the ISBAR view of LiveView when accessed through "Consultation." The data only refreshes after switching views or reopening LiveView.
• Solution: The background service responsible for detecting record changes was updated to address an exception that caused it to stop working. Additionally, changes made in the new LiveView now manually trigger updates in older ISBAR views to ensure consistent data synchronization.
• Affected components: Insight, LiveView API

LiveView Name Not Displayed in Consultation Window

• Ticket: none | DevOps: 26004 | Reported by: Internal QA
• Issue: When opening the chat window after setting a LiveView delivery location, the name of the LiveView is not displayed. Users can still communicate with the LiveView, but the absence of its name may cause confusion.
• Solution: The issue was resolved by updating how recipients for LiveView delivery locations are handled in consultations. It is now ensured that the LiveView name is correctly displayed in the chat window by including the appropriate recipient information during setup.
• Affected components: Client Application, Client Hub, LiveView API

Urgency Level in LiveView Incorrect After Page Refresh

• Ticket: 72491914459 | DevOps: 27297 | Reported by: Helse Sør-Øst
• Issue: After refreshing the page or accessing a LiveView after a record was attached, the urgency level displayed in the LiveView was incorrect. Initially, the urgency level showed the correct value based on the set criteria (e.g., Urgent - A.03.02), but after a refresh, it displayed based on the criteria number instead.
• Solution: The issue was resolved by updating the handler to include the urgency level for the record. This ensured that the correct urgency level was consistently displayed, even after a refresh or when accessing the LiveView after the record was attached.
• Affected components: LiveView API

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