Bliksund EWA Release 20
Version 20.0 of EWA was released to customers on July 31st, 2023.
The compatible versions of the affected runtime components are listed below:
| Component | Version |
|---|---|
| Client Application | 23.7.60796.0 |
| Client Hub | 23.7.60796.0 |
| Data Warehouse Export Service | 23.7.60796.0 |
| EOC Integration | 23.7.60796.0 |
| Export Service | 23.7.60796.0 |
| HP Link Patient Identity API | 23.7.60796.0 |
| Insight | 23.7.60796.0 |
| Medical Unit Broker | 23.7.60796.0 |
| Migration and Seeding Tool | 23.7.60796.0 |
Content of this Release
New Features
EMCC ticket in UWP application
We have added a new feature to our UWP application that allows users to view an EMCC ticket containing important information about a mission. The EMCC ticket includes the following fields: AMIS-number, EMCC alerted timestamp, Emergency Code, Dispatch Code, Problem Description, and Callers.
When the EMCC ticket feature is active and the mission is from an EMCC, the existing tiles for AMIS-number, Dispatch Code, and EMCC Alerted are hidden to avoid duplication of information.
To activate this feature, you will need to enable the feature flag in Insight. Please note that this feature requires updated EMCC Integration, ClientHub, Insight, and UWP Client to work correctly. Additionally, WebView2 must be installed on the tablets running the UWP Client.
Please note that the feature is automatically hidden for manually created missions.
Updated Features
Reverted LiveView V2 to alpha state due to performance issues
During final stress testing of LiveView V2 we discovered that the performance was not good enough to be released to customers. We have therefore reverted LiveView V2 to alpha state and will continue to work on improving the performance.
Code relating to LiveView V2 has also been removed from the ClientHub and Integration components to avoid any unforeseen issues that could arise from the code being present.
EMCC Integration expanded with new fields
- EMCC integration expanded to allow the software to store additional information about people who call the EMCC (Emergency Medical Communication Center) regarding a mission. The new feature includes several fields, such as the caller's ID, the time the call was received, the type of caller, the caller's phone number.
- EMCC integration expanded to store the dispatch code description, the problem description, and the emergency code from the mission object.
Mission Simulator improvements
- Restructured the EMCC Mission Simulator and added new fields: Callers (including number, name, type and time), Dispatch Description, Emergency Code, Problem Description.
- Changed some fields in the EMCC Mission Simulator and set default values: EMCC Alerted, Transport Planned, Dispatch Code (now connected to Dispatch Description), Patient Birth Date, Patient Gender and Ambulance Alerted.
- Minor bugfixes and additional improvements for the EMCC Mission Simulator, like a button to regenerate the EMCC Mission Id, collapsible panels, some new icons and optional labels
Fixes in Version 20.0
1. Revert of Video Communication feature
Ticket: 1533426142 | DevOps: #none | Reported by: Helse Nord
Description:
The Video Communication alpha feature was causing critical issues with offline functionality of the UWP Client. As a result, we have decided to completely remove this feature in this release.
How it is solved:
- All code pertaining to the feature has been temporarily removed from the application to ensure that users can continue to use the application without any issues.
2. Location list in LiveView configuration page V2 does not show correctly
Ticket: internal | DevOps: #17889 | Reported by: internal
Description:
When making a new LiveView configuration or editing an existing configuration using the new Blazor setup, the location list only contains some of the available locations.
How it is solved:
The problem occurred because the number of displayed items in the list is limited (to 10) and the items are sorted by id rather than alphanumerically, which is confusing for the user. To make the display more intuitive for the user, we:
- increased the maximum locations shown in the list to 25.
- changed the default sorting order from id to the Group-/DisplayName of the locations.
- changed the filtering of the list from StartsWith() to Contains() and also now the items that doesn't match the entered search value are hidden properly.
- added a new element at the bottom of the list to dynamically inform the user (a) how many more items can't be displayed until he specifies his input, or (b) that no matching items could be found at all.
- fixed the "/" in front of the DisplayName when there is no GroupName and added proper locations including groups in our test environment.
3. Crash in client because log file in use
Ticket: 1403581406 | DevOps: #18190 | Reported by: Helse Vest
Description:
When one tries to start the EWA client while it is already running, EWA will freeze and crash.
How it is solved:
The problem occurred because the client tries to re-initialize the App.log file that is already in use, which leads to an unhandled file access error and the crash. To fix this, a new log file with name extension "_alt" is created and used in those cases (App_alt.log). This solution also prevents a crash when restarting the client several times, since it just generates new log files (like App_alt_alt_alt.log).
Patch 20.1
Version 20.1 of EWA was released to customers on August 10th, 2023.
The compatible versions of the affected runtime components are listed below:
| Component | Version |
|---|---|
| Client Application | 23.8.61260.0 |
| Client Hub | 23.8.61260.0 |
| Data Warehouse Export Service | 23.8.61260.0 |
| EOC Integration | 23.8.61260.0 |
| Export Service | 23.8.61260.0 |
| HP Link Patient Identity API | 23.8.61260.0 |
| Insight | 23.8.61260.0 |
| Medical Unit Broker | 23.8.61260.0 |
| Migration and Seeding Tool | 23.8.61260.0 |
This patch includes the following fixes:
1. AMIS statuses data being mixed up when merging manual mission
Ticket: 1601248228 | DevOps: #18494 | Reported by: HSØ
Description:
When merging a manual mission with an incoming EMCC mission, the system pulls status times and delivery location from the AMK mission with the same resource number as the manual mission if the AMK mission already exists on the same tablet.
How it is solved:
Fixed comparison of statuses when merging missions and re-entering merged mission.
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
Supported software versions:
- Versions 3.0.X to 4.2.2
SDK version:
- Version 4.3.0.0