Release 35.0
Released to customers on TBD
| Module | Version |
|---|---|
| Client Hub | |
| Chat Server | |
| Data Warehouse Export | |
| EWA UWP Client Application | |
| Export | |
| HPLink Patient Identity API | |
| Insight | |
| Integration | |
| LiveViewApi | |
| FormModuleAPI | |
| FormModuleData | |
| Medical Device Broker | |
| Migration Tool | |
| Version Manager Client Installer | |
| Version Manager API | |
| PersonnelRegistrationApi |
Content
New features
Updated features
Enhanced handling of urgency levels in EWA system
We've made several enhancements to the handling of urgency levels in the EWA system. These changes are designed to allow for more flexibility in regards to how we can define and manage urgency levels in the system. The changes include the following:
- Urgency levels are now defined as entities in the database: With this change, urgency levels are now defined as entities in the database, which allows for more flexibility in how they can be managed and configured. This change also allows for the creation of new urgency levels through specialized tooling, rather than having to perform code changes to add new urgency levels.
- Tooling for managing urgency levels: We've added new tooling to the Migration and Seeding tool that allows for the management of urgency levels. This tooling allows for the creation, soft-deletion, and modification of specific parts of urgency level entities without code changes.
We highly recommend that the definition file this tooling uses is provided by Bliksund, as it is a complex JSON structure, and incorrect changes can lead to issues in the system.
Data conversions for urgency levels
To support the changes to urgency levels, we're doing specific data conversions to ensure that existing urgency levels are correctly represented in the new entity structure, and to ensure records are correctly linked to the new urgency level entities. These data conversions will be run directly after specific database schema migrations, and will ensure that urgency levels are correctly represented in the new entity structure.
The following data conversions are included in this release:
-
DB Schema Migration: 202409100830216_UrgencyLevelsDataConversion.
Data Conversion: UrgencyLevelsDataConversion
Description: This data conversion will scan all existing records in the system and link them to the new urgency level entities.
IMPORTANT: The UrgencyLevelsDataConversion data conversion will take some time to run, as it needs to scan all existing records in the system. It also has a high chance of timing out if the system is under heavy load. We recommend running this data conversion during off-peak hours to avoid any issues, and if it does time out, it can be rerun using the --run-converter argument in the Migration and Seeding tool.
.\Bliksund.EWA.MigrationTool.exe --run-converter UrgencyLevelsDataConversion
Fixes
Heading in print overwrites data
Ticket: 3211799527 | DevOps: #24094 | Reported by: Helse Nord
Description:
Heading in print overwrites the date when the name of the Health Trust is too long.
How it is solved:
The name of the Health Trust and the Resource is located on a new line in the print, underneath the date and the state of the journal
Unable to search and add locations in all location tiles in EWA Client
Ticket: 3845373630 | DevOps: #21911 | Reported by: Helse Nord
Description:
The search field on all location tiles is occasional disabled, preventing location searches. This issue occurs whenever at least one Blazor component is active.
How it is solved:
To resolve the issue, wrap the Blazor WebView2 component in another control with its overlay to prevent overlap.
Missing Upload Button on Version Manager Page
Ticket: E-mail | DevOps: #26595 | Reported by: Helse Vest
Description:
The upload button is not visible on the Version Manager page.
How it is solved:
The upload component was updated to align with the latest changes in the frontend library.
Not able to change resource after deleting record from Insight
Ticket: 4954148336 | DevOps: #26751 | Reported by: Helse Sør-Øst
Description:
After deleting records from Insight, error message saying that it is not possible to change resource with ongoing missions when trying to change resource.
How it is solved:
Check and update the local data when having any update from Insight.
Total score from form response is not getting displayed in print
Ticket: 6197744855 | DevOps: #26657 | Reported by: Helse Midt
Description:
Total score from form response is not getting displayed in print.
How it is solved:
Check and fix error on the calculation function to print the correct score.
Name of mission type displayed incorrectly in "My records" page
Ticket: 8729620692 | DevOps: #26893 | Reported by: Helse Vest
Description:
Recently, the mission type on the My Records page and the Mission Category filter has been displaying the ID instead of the name.
How it is solved:
Update both the page results and filter to display the mission type name instead of the ID, using the newly introduced configurable mission type.
EOC ticket "sticks" from previous records
Ticket: 5992380918 | DevOps: #26705 | Reported by: Helse Midt-Norge, Helse Sør-Øst
Description:
When creating a new record, the EOC ticket information from previous records briefly appears for a few seconds before the correct ticket is loaded. This delay can be longer on tablets with poor internet connections.
How it is solved:
Displays a placeholder logo while clearing the EOC ticket information whenever switching between records or creating a new record, ensuring it only loads once the correct data is available.
EOC ticket is missing linebreak
Ticket: | DevOps: #27240 | Reported by: Helse Sør-Øst
Description:
When the EOC includes text with line breaks in the problem description field, these line breaks do not appear in the client application.
How it is solved:
Implement support for handling both line breaks and HTML tags in the description text to ensure proper display.
Print from Insight and Export shows different format of date for NEWS2 and SATS triage performed
Ticket: 7544822497 | DevOps: #26984 | Reported by: Helse Midt
Description:
The date displays in an incorrect format across different cultures for NEWS2 and SATS.
How it is solved:
Apply the appropriate culture settings to the datetime converter when rendering the PDF to ensure consistent date formatting.
Medical devices
Corpuls
Tested software versions:
- Version 4.2.2 and 4.3.2
SDK version:
- Version 4.3.0.0
Zoll
Tested software versions:
- Version 02.36.21.00
SDK version:
- Version 6.44.315