This version of CTcue contains a number of new functionalities, improvements and various bug fixes. Below you will first find a brief overview. Below that, you can read the extended release notes with more detail about some of the main changes in this version.
- Audit logs can now be exported from the administrative section of the application
- Results can now be created from scratch, in addition to being created from existing results
- We've updated the DBC specialism labels with a new list from https://www.opendisdata.nl/. Most labels have remained the same, but others have gotten better explanations. It also adds additional specialisms in the dropdown
- Data permissions are not affected by this change. Only medical specialist specialisms are used, which results in the same list of codes as before
- You can now search for "is empty" and "is not empty" measurement units
- You can now search for textual measurement values that do not contain specific strings
- CTcue Hub:
- New fields are added when you share a project in the CTcue Hub: you can now select a finance type, for example if it is a sponsored project. You can specify the project types, such as "scientific research" or "value-based health care". You can also provide more information about the reason to share the project in the CTcue Hub
- Users are now notified when a project is shared with them on the CTcue Hub or when a project they have shared on the CTcue Hub is imported. Users also receive an email when a project has been shared
- Projects can be shared with the CTcue Hub directly from the "sharing" tab in the project settings. Here users can also monitor and manage the project in the CTcue Hub
- Autocomplete dropdown fields now show a specific message if they don't have any values to suggest (such as measurement test value)
- Allow hospital details to be changed in the administrative section of the application
- If you search for form entries, we now display the correct value so you don't have to click "Show all entries" first
- Custom answer options no longer disappear when a term no longer has results
- Using patient information (demographics) filters now behaves correctly in question preview, the data overview and exports
- Surgery procedure column headers are now aligned correctly
- Remove relative date filters that are not visible in the application
- Filtering on the start date of a parent term in the validation table now works
- Questions without (enabled) terms are now visible in the validation table
- Fix issue that caused the "Mark all as read" link in the notifications popup to be disabled incorrectly
- Fix issue that caused an error when refreshing results on the single patient page with data validation features enabled
- Prevent interrupted data validation synchronization from appearing as though it were still running
- The best result for a report on the single patient page when using (online) text processing now consistently matches the one shown in the patient cohorts table
- We no longer show the "Viewing as admin" badge to admins who are also the owner of a project
Extended release notes
Below is a more detailed overview of some of the bigger or impactful changes in this version.
For admins there may be moments when they need to be able to check specific actions in the app, such as who has had access to specific patient IDs or who has shared a project with the CTcue Hub. These types of actions are stored in a log and can now be searched from the Administrator panel. To prevent admins from having to scroll through thousands of log records, there is an option to specify several filters before exporting the log data. Admins can filter by date range, users, projects, patient ID and/or specific event types. An export summary provides a convenient overview of the expected output, so users know how much data they can expect before they export and download the audit logs. The output will be provided in an excel file.
Created results from scratch
Since version 4.1.1 we have added the option to create a result when the data you have found is not fully complete or correct. However, it is also possible that no data is found within the EHR and the field remains empty. In some specific cases, users may have found the relevant matching data in external sources outside of CTcue and want to add this to the overview. In that scenario, we allow users to create a result from scratch, so that their data is as complete as can be. The functionality is the same as the regular created result, but the fields will be empty (as no data was found) and can be populated by the user as needed. Please note that this data is only stored in the CTcue project and will not be added to the EHR.
CTcue hub changes
The CTcue hub allows users to share projects with users in other hospitals, so that they can run the same query on their data. The hub is used by more and more users, so to improve collaboration we have made a few changes. First off, we have made it easier to share projects through the CTcue hub by allowing users to share their project straight from the project settings page. Users that have access to the CTcue hub will find this option on the Sharing tab. From there they will have to provide a few details about the project before sharing the project.
Once a project is shared, the receiving person will get a notification in the app and an email to make them aware of the shared project. When they import the project into their own hospital, then the original project owner will receive a notification about this as well. That way, you know that the project is being picked up in the shared hospital. In the original project, the owner can see an overview of all the shared users and manage their access or update the latest version of the project with the hub.