Release 27.0
Released to customers on March 1st. 2024
| Module | Version |
|---|---|
| Client Hub | 24.3.3.0 |
| Chat Server | 24.3.3.0 |
| Data Warehouse Export | 24.3.3.0 |
| EWA UWP Client Application | 24.3.3.0 |
| Export | 24.3.3.0 |
| HPLink Patient Identity API | 24.3.3.0 |
| Insight | 24.3.3.0 |
| Integration | 24.3.3.0 |
| LiveViewApi | 24.3.3.0 |
| FormModuleAPI | 24.3.3.0 |
| Medical Device Broker | 24.3.3.0 |
| Migration Tool | 24.3.3.0 |
| Version Manager Client Installer | 24.2.152.0 |
| Version Manager API | 24.3.3.0 |
Content
New features
Version Manager system
The Version Manager system is a new feature that allows users with a specific access right to manage the versions of the EWA Client and MUBroker on the client devices. The feature is available in the EWA Insight website and is accessible from the "Administration" menu.
This feature should be considered an early release candidate, and as such, there may be some issues or limitations. It is included in this release to allow customers to test in their on-prem environments and provide feedback.
Version Manager documentation
Installation guides for the Version Manager API can be found here, and installation guide for the Version Manager service can be found here.
The EWA Installation Guide has been updated with information about the Version Manager system. The section for installation of the Insight website has also been updated with relevant information.
Version Manager access rights
The following access rights are available for the Version Manager system:
- VersionManager: Allows the user to access and use the Version Manager system in Insight.
Release environments and environment landing page
A new system for deploying specific release version environments have been created. This system uses Kubernetes to deploy a specific release version of the EWA system in it's entirety, and allows us to have publicly available environments for each major and minor version of EWA going forward. The landing page where it's possible to see all deployed environments and their status can be found at https://ewa.releases.bliksundhf.no/.
This URL is very likely to change in the near future. This document will be updated when this happens.
The client download page for 27.0 can be found here, and Insight can be found here.
The Client Download page and Insight links will be updated at the same time as the landing page URL above.
More info about the landing page can be found here.
Updated features
Forms (Scoring of choices)
We have added possibility to configure and record score for choices in forms feature. While adding single or multiple-choice elements to a form, the score for each choice can be configured and the form response calculates the total score based on the selected items after completing the form in EWA Client.
Affects: EWA Client and Insight.
See Forms user guide
Attach D-ECG to records in EWA Client
We have enabled the option to attach D-ECG to records in EWA Client.The feature flag 'Enable attaching D-ECG to records in EWA Client' Should be enabled for the resources and new MUBroker from release 27 should be installed in the tablets to attach D-ECG.
Taken D-ECG measurement timestamps in the list will be automatically retrieved and updated from the device, as long as the EWA Client application has an active open connection to it. The attached D-ECG is added to the print in EWA Client and Insight, Also it will be available in D-ECG section of view/edit records page and in LiveView.
Affects: EWA Client and MUBroker.
See MTU user guide
Fixes
Possible to register HTML code in forms
*Ticket:*2343360734 | DevOps: #21873 | Reported by: Helse Sør-Øst
Description:
While recording a form response in EWA client, it is possible to enter HTML code.
How it is solved:
We display HTML link as plain text.
Validation of time tile for left place of incident is wrong
Ticket: 2269991643| DevOps: #21083 | Reported by: Helse Sør-Øst
Description:
Show wrong warning when setting time for left place that left place of incident must be after at place of delivery.
How it is solved:
This is because we used the wrong key for the time flyout of left place. We have now changed the key to the correct one, and the validation now works as expected.
Record gets connected to incorrect Corpuls.Mission Widget
Ticket: | DevOps: #21039 | Reported by: Internal
Description:
Corpuls mission id from the device was being connected to the wrong record in the EWA client because it was always assigned to the current, active record, instead of the record connected to the device with said mission id.
How it is solved:
Fixed by adding a check for if and which device is attached to the journal while assigning mission corpuls id to it.
Not possible to create LiveView with only limited access
Ticket: | DevOps: #22077 | Reported by: Internal
Description:
Can not create LiveView configuration without filling out Department Full Access.
How it is solved:
With Patient Reception type, it is possible to create LiveView configuration with only one of Full or Limited access being filled out.
Corpuls widget keeps refreshing when receiving data
*Ticket:*2271131837 | DevOps: #22144 | Reported by: Helse Sør-Øst
Description:
Every time new data is sent from EWA client to LiveView the widget refreshes and you are brought back to the "start page" of the corpuls.mission view
How it is solved:
Added check if the widget pane was user initiated, if not the widget pane will not be refreshed.
Newly created stations are not getting displayed in the resource page
Ticket:| DevOps: #22005 | Reported by: Internal
Description:
When adding a new station and map it to a new or existing health trust it is not getting listed in the manage resources page.
How it is solved:
Removed incorrect filter in resource controller while fetching the resources.
Medical devices
Corpuls
Tested software versions:
- Version 3.0.3, 4.2.2 and 4.3.2
SDK version:
- Version 4.3.0.0