Release 21.0
Released to customers on September 1st. 2023
| Module | Version |
|---|---|
| Client Hub | 23.9.62033.0 |
| Data Warehouse Export | 23.9.62033.0 |
| EWA UWP Client Application | 23.9.62033.0 |
| Export | 23.9.62033.0 |
| HPLink Patient Identity API | 23.9.62033.0 |
| Insight | 23.9.62033.0 |
| Integration | 23.9.62033.0 |
| LiveViewApi | 23.9.62033.0 |
| Medical Device Broker | 23.9.62033.0 |
| Migration Tool | 23.9.62033.0 |
Content
Updated features in release 21
New features
LiveView
-
LiveView Overview has been rebuilt to support Blazor components and a new backend service
-
LiveView Backend service
- New LiveView Api has been added to the backend
- New LiveView Domain has been added to the backend
- New LiveView Infrastructure has been added to the backend
- New LiveView LegacyHandler added to the backend
See LiveView Documentation for more information about installation, configuration and performance
Affects: Insight |
Updated features
Updated Timeline report
- Added new Timeline report specific access rights.
- Added alphabetical ordering of the resources in the chart.
- Added journal filtering based on the selected Station.
See Documentation for timeline report for more information.
Affects: Insight | Timeline report |
Update of MUBroker
- Removed automatically reconnect to medical device if error occurs. Instead of that, client application will show notification corresponding to each cases to user so that he/she can try to reconnect manually. The following are specific scenarios that have been included:
- Connecting MTU and client then going out of range
- Connecting MTU and client then turning off MTU
- Connecting MTU and client when MTU is not turned on
- Connecting MTU and client to new second record without restarting MTU
- Trying to connect to MTU without Bluetooth turned on
- The MUBroker service has been stopped
Affects: Client Application
Fixes
Resolved Error Responses when Updating Measurements for Completed Journals
Ticket: 1487923922 | DevOps: #18448 | Reported by: Helse Vest
Description:
The customer noticed a substantial volume of requests at pepj.ihelse.net that resulted in 404 ("Not found") responses, placing considerable strain on the load balancing mechanism. This unexpected surge originated from a couple of boards attempting to submit automated measurement updates to already deleted or completed journals.
How it is solved:
- We have implemented a security measure to check for empty journal IDs when adding, updating or deleting measurements.
- As part of this enhancement, we have also taken the opportunity to clean up some unnecessary code and provided better internal documentation.
Not able to complete record after restart if ESS is set to "not performed" before restart
Ticket: internal | DevOps: #18252 | Reported by: Bliksund
Description:
Attempting to complete a journal with "not performed" ESS selected after restarting the application was not possible because of the minValue number for the ESSNumber wasn't being loaded on the initial data load during the application start up. This resulted in validation error not being skipped and not allowing the completion of the journal.
How it is solved:
- Removed nulling out/added assigning the min Value to the ESSNumber during initial data loading.
EMCC ticket displays no data when the mission is active for more than 24 hours
Ticket: internal | DevOps: #18564 | Reported by: Bliksund
Description:
EMCC ticket displays no data when the mission is active for more than 24 hours since the ClientHub will never send missions where UpdatedAt is older than 24 hours.
How it is solved:
- We have added a guard text if the ticket information is in an ambiguous state. Currently this can happen if the ticket information has not been received from the server yet, even if the Client expects it to be. Or if the ticket information is over 24 hours old, the server will then consider the ticket integrity to be invalid.
Optimized the overview report when the number of medical records is huge
Ticket:1394940394 | DevOps: #17928 | Reported by: Helse Sør-Øst
Description:
The queries to database would be stuck when making a monthly/annual overview report if there are a large amount of medical records created on the table.
How it is solved:
- Created new computed columns as well as indexes instead of using View. Moreover, the complex lingq queries also have been replaced by stored procedure.
Release 21.1
Released to customers on December 15th. 2023
| Module | Version |
|---|---|
| Client Hub | 23.12.1510.0 |
| Data Warehouse Export | 23.12.1510.0 |
| EWA UWP Client Application | 23.12.1510.0 |
| Export | 23.12.1510.0 |
| HPLink Patient Identity API | 23.12.1510.0 |
| Insight | 23.12.1510.0 |
| Integration | 23.12.1510.0 |
| LiveViewApi | 23.12.1510.0 |
| Medical Device Broker | 23.12.1510.0 |
| Migration Tool | 23.12.1510.0 |
Potential security issue in LiveView
Ticket: | DevOps: #20666 | Reported by: Internal
Description:
In some cases some code was being run that could give logged on users more information than they should have on the infrastructure behind LiveView.
How it is solved:
Made the code redundant and removed it.
On-screen keyboard and clicking outside the tile throws you back to the start
Ticket: 2077967054| DevOps: #20139 | Reported by: Helse Vest and Helse Midt-Norge
Description:
While using the on-screen keyboard or keyboard connected to the tablet, for example, the "Paid mission" tile and press outside the tile, the screen will jump all the way back to the EMCC ticket/start-up phase.
How it is solved:
Moved check for active tile that is set when navigating to Anamneses, ESS and Triage{1,2}, Paid mission.
Get access to medical records in the client application without being an active user
Ticket: 2113604795| DevOps: #20650 | Reported by: Helse Nord
Description:
Users have experienced getting access to assignments without being logged into EWA, This happens when the deletion process in EWA client took long time and the active user locks the screen and the new user logs in.
How it is solved:
Added check to navigate to lock screen if there is no active user when pages are loaded.
Invalid organization ID being used in filters when the role picker is enabled in a multiple department setup
Ticket: 2039873261 | DevOps: #20698 | Reported by: Helse Nord
Description:
Issue where the combination of role picker enabled and multiple departments claims in the token led to invalid organization ID being used for access filtering, which led to no results in several reports and searches.
How it is solved:
Updated the backend to respect the combination of rolepicker enabled and multiple departments claims in the token, which will now always use the Organization ID from the DepartmentIdMapping for the selected department in rolepicker.
Supported Medical device
Corpuls
Supported software versions:
- Version 3.0.X to 4.2.2
SDK version:
- Version 4.3.0.0