UltraGenda Pro 10.1
The present release provides an important update to UltraGenda Pro and includes new features, feature enhancements and a number of bug fixes. UltraGenda recommends all customers to update their UltraGenda Pro environment to the latest version.
Please note that the present release includes all previously released bug fixes and feature enhancements.
Release date: 28 april 2023
This version of UltraGenda Pro is compatible with
- UG Authentication 1.2
- UG Broka 8.1
- UG Contacts Store 5.2
- UG Track Pro 2.7
- UG Bedman 2.6
NEW
PRO-1900
Along with the previously supported appointment synchronization, it is now possible to synchronize Non-availabilities with MS Exchange calendars via the Publish schedules feature. This functionality is currently only available for integrations with MS Exchange Online (Office 365). Please consult the Guide to UltraGenda Pro - MS Exchange synchronization for more details.
PRO-8566
UltraGendaPro now supports a new integration with Dedalus C4C Meeting for video consultation appointments. Please contact Support for more details.
PRO-8787
New pre-requisite: .NET Framework 4.8 is a pre-requisite for installation/upgrade.
IMPROVEMENTS
PRO-5511
In Central Setup, when linking a Department to a HIS department, the dropdown now lists these alphabetically.
PRO-6640
When editing session settings, it was possible to exceed the maximum length of characters for the following fields: Session name, abbreviation, external code and info.
This caused integration problems with UG Contacts Store (name and external code), and these sessions could not be processed. This is now solved on the input level, so that users are no longer allowed to insert data exceeding maximum lengths.
Note: For existing data, it is advisable to truncate those fields on the database level. Please ask our support to assist you on this during the upgrade.
PRO-7777
It is now possible to display the patient birth date in the individual view by selecting new preferences as a user.
PRO-7786
It is now possible to display the patient birth date and appointment duration in the department view by selecting new preferences as a user.
PRO-8419
When cloning a schedule, the schedule subscribers of the original schedule are no longer copied.
PRO-8439
A new version of the batch stored procedure that returned cancelled appointments has been added - crBatch_getCancelledAppointments_01_v10_1_0 - which includes additional patient related fields. Consult the Guide to batch printing for more details.
PRO-8596
Security improvement: UltraGenda Pro is now using the latest moment.JS library version. Vulnerabilities CVE-2017-18214 and CVE-2022-24785 are no longer present in UltraGenda Pro.
PRO-8625
While creating users directly in UltraGenda Pro via REST API (external user creation flow without the use of UG Authentication webhooks - API endpoint UltraGenda.Pro.Authorisation/api/users), it is now possible to pass the user abbreviation attribute.
PRO-8677
The Users setting on Central setup has now been modified, so certain fields that should be modified in or via UG Authentication are read only. Also it is no longer possible to delete a user in UG Pro, only in or via UG Authentication.
PRO-8685
Spanish version is improved and better adapted to Latin America.
PRO-8755
Security improvement: UltraGenda Pro is now using the latest log4net version. Vulnerability CVE-2018-1285 is no longer present in UltraGenda Pro.
PRO-8798
Some internal applications have now been migrated to .NET 6. One of the benefits of this migration is that it is now possible to change the log level of these applications only modifying the appsettings.Production.json file without the need to recycle the application pool via the IIS manager (.NET Hot Reload).
List of migrated applications:
- UltraGenda.Authentication
- UltraGenda.Trapi
- UltraGendaPro.Patients
- UltraGendaPro.UI
- UltraGendaProTriageServices
- UltraGendaPro.Printing
- UltraGendaPro.Admissions.WebApi
PRO-8892
The button to manually create a video consultation has a more user friendly icon.
BUGFIXES
PRO-1012
The episode type code information (when applicable) was being sent in two HL7 message fields: PV1-18.1 and PV1-18.2 for SIU and ADT messages. This was redundant and unnecessary information and didn't comply with the HL7 v2.3 message definition.
The episode type code is now only sent out on PV1-18.1.
Important: Note that for ADT A01, UltraGenda Pro makes use of PV1-18 to send out abbreviation and descriptions of the contact types linked to the visit and the appointment type. This has not been changed.
PRO-6735
When modifying reason and category of a period of non-availability along with extending the period to the next day, the category and reason would not be updated for the whole period (only the additional days had the correct data). This is now fixed.
PRO-6940
While repeating an order set and choosing another slot, other than the one first suggested, resulted in an application error. This is now solved.
PRO-7770
When an appointment type was indicated as 'Use as default selection in search criteria', then the appointment type was displayed twice in the drop down if the user books the appointment via the free button on department view. This is now resolved.
PRO-8004
When creating a patient (validated or temporary), clicking multiple times on save would create multiple duplicate patients. This is now fixed.
PRO-8415
Enabling "Show Answers" on individual view in the "Set preferences", while no questions have the "And show on individual view" resulted in a slow performance of the individual view. This is now solved.
PRO-8429
When scheduling a waiting list entry and editing the appointment right after would result in the appointment not being selected when running the stored procedure crBatch_getRescheduledAppointments_01. This is now solved.
PRO-8476
The episode (change) link was only available for repeated appointments after modifying these appointments. This has been resolved.
PRO-8539
In the future tab, the icons for multi-resource and order sets appointments are clickable and appointment details can be opened, while access rights should prevent this for single, multi-resource and order set appointments. This is now solved.
PRO-8614
Patients with apostrophe/single quote on their name (given name or family name) were displayed incorrectly in the patient header (html code was displayed instead of the apostrophe). This is now fixed.
PRO-8629
The unique ID sent out in outbound ZSE Z10 messages for a non availability changed after certain modifications to the non availability. From creation to modification to cancellation the same unique ID is now used and sent out in the outbound messaging. It is now resolved.
PRO-8720
The UGPro Rest API endpoints to modify (PUT) and delete (DELETE) users was not working in certain cases, because of case sensitivity. This is now solved.
PRO-8725
Event Replayer would replay events twice in case there was a gap in the RowNumbers causing projection tables to have duplicated entries for schedules, departments, etc. This is now fixed: Event Replayer now takes into account possible gaps in event row numbers.
Note: This gap is not created automatically by the software and is a result of manually deleting events from Event Stream. Contact support for further details.
PRO-8762
When requesting appointments by calling Endpoint 'GetAppointmentItemsByResource' on UltraGendaPro SOAP WebServices, with start date of today or in the future, the episode information linked to the appointments, if present, was not returned. This is now solved.
PRO-8767
The HL7 outbound message handler has been improved when retrieving the data to be included in the message. An internal retry mechanism has been added making sure that a maximum of 3 retries are executed before throwing an error when the minimal required data is not successfully retrieved. If the data is still not retrieved after 3 retries, an error will be visible in UG HL7 Engine. The fix includes all HL7 outbound messages except ZSE Z10 and ADT-A13.
PRO-8782
HL7 ZSE Z20 poison HL7 messages caused the soapoutbound queue to stall, preventing outbound processing of further messages. This is now solved.
PRO-8836
For a schedule with a friendly name (set on the departmental setup), when editing this schedule general settings on schedule setup, the friendly name was cleared out and saved as empty. This is now resolved since the friendly name is now preserved.