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.
- The support section has been reorganized.
- Note: as a result, the “Send us feedback” button has been moved from the user menu to the support section and renamed to “Contact CTcue support” for clarity.
- As an admin, you can define the CTcue support contacts for your hospital, so that users who need help know how to find the right person when they have questions.
- If you have “reports plus” enabled and requested AI results to be processed, you will now receive an email once the analysis has completed.
- We have added patient finder query versioning, so you can save your criteria and restore to a previous version.
- We have added patient information filters. You can now filter on the following columns in the patient cohorts and data validation pages: sex, age, birth year, living or deceased, year of death, and date of death.
- Note: for existing projects, the patient information filters on the data validation page will only work after you have searched again on the patient cohorts page.
- We have added "care provider permissions" on user level. By default, every user is allowed to search and export care provider names. Admins can revoke this permission in the administration section, which limits a user from viewing care provider names in structured data and the report texts.
- If you drag and drop groups, the info will be kept as a readable sentence.
- We have added a new category: "Episode of care" which allows users to identify all care linked to a specific diagnosis.
- We have updated the following categories to have a link with the new episode of care category (via IDs): admissions, appointments, care activities, DBCs, surgery procedures.
- We fixed an issue where the department would be "blank" after duplicating a project. You can now set this in the project duplication modal.
- We fixed an issue where pressing the "add created result" button gave an error for reports.
- Added translations for the date picker, so you should see it in your chosen language.
- We updated the Dutch translation for "Zorgtraject" to "Behandelplan".
- There was a bug in the overview page in both criteria and data validation tables. In research/contact consent columns, we showed "No" for "Empty" values. We corrected it with showing an empty value instead.
- We now correctly disable buttons that collaborators with view-only permission should not be able to click, such as sharing a project with the CTcue Hub or requesting an AI extraction.
- We fixed an issue where collaborators could get a CTcue Hub error on the project sharing page, if they didn't have permission to the Hub.
- We fixed an issue with importing a DBC term from an old project, where the filter would be invalid and ignored for search.
- We fixed an issue where sometimes the "custom result (x)" badge would not be removed and you had to refresh the page to see the update, when clicking on the "(x)".
- Combined columns should always be selected by default. We fixed an issue where in some cases this didn't work as expected.
Extended release notes
Below is a more detailed overview of some of the bigger or impactful changes in this version.
New category: episode of care
We have added a new category to the terms list: episode of care. An episode of care covers the full trajectory of health care that a patient receives for a specific diagnosis. With this category you can identify all patients for whom an episode of care was created and identify the various elements that are part of it. Within CTcue we link the following categories to episode of care: DBCs, appointments, admissions, surgery procedures and care plans.
To read more on this, click here.
Patient finder criteria versions
Sometimes when you are trying to finetune an existing query, you end up with unwanted results. Then you wish you could switch back to the previous version of the query instead of trying to undo all your changes manually. For this scenario, we have now added the ‘versions’ module to the patient finder criteria. With this module, you can view and restore older versions of the query. You will find this module in the top right corner of the ‘criteria’ page.
There are two types of versions: autosaved versions and named versions. The autosaved versions are automatically created every couple of minutes while you are active in a project. To keep the versions overview clean, we automatically remove older versions as well, but we always keep a version from the last hour, last day, last week, and last month. That way, there is always a recent version to go back to. If you want to store a specific version for longer, then you can manually create version yourself and give it a custom name that makes sense to you. Named versions are never removed automatically, but you can delete them yourself if you don't need it anymore.
Please note that the versions only store the inclusion and exclusion criteria in the patient finder. The patient cohorts and any validations are not stored in a version, so you will need to run a new search after restoring an older version.
To read more on this, click here.
Patient level filters
When you are analyzing or validating the data in the patient cohorts or data validation table, it may be easier to review patients by certain demographic variables, such as age groups or sex. Therefore, we have now added filters to multiple columns that are part of the patient information section: sex, age, birth year, living or deceased, year of death and date of death.
Reorganized support section
For users who need help in the app, it's important to know how they can get answers to their questions. There are three main channels to get support:
- Browse the available support documentation
- Ask for support from other (key) users in the hospital
- Submit a ticket to the CTcue support team
To streamline access to these channels, we have reorganized the support section that can be accessed via the menu in the lower left side of the app. This panel now includes three buttons to guide users to each of the three support channels.
The support panel now displays the suggested support articles in a more clearly laid out overview. This should help the user quickly find answers to common questions that relate to the screen they are viewing. If the suggested articles don't match a user's question, then they can easily browse to our support documentation page for more articles via the left button in the modal.
Users who are looking for support from a key user, admin or other experienced person within the hospital can find their contact details via the middle button. The pop-up modal that appears shows the name, email address and a custom description for any hospital support contact that can be configured in the admin panel (on the Configuration page). If these details are not provided, then this button will be hidden for users. However, we strongly recommend all hospitals to provide these details to users.
Finally, if none of the other support channels have helped, users can contact the CTcue support team directly through the support form that can be accessed via the right button. Note that this form has been moved from the account menu on the lower left side of the screen.
Care provider permissions
From a privacy perspective, administrators may want to revoke users’ access to care provider names in CTcue. To allow for this, we have added a new permission in the Admin panel on the permissions screen in the account for each user, under the section “data permissions”. To read more about how to enable/disable this permission as an administrator, click here.
When the permission is enabled, users can see the care provider names in all category filters and reports. With the permission revoked, all category filters related to care provider names will be disabled and all care provider names in reports will be pseudonymized.
If the permission is revoked for users who already have projects using care provider name filters in their query, then the query will not be changed. However, the name in the filter will be masked and users can no longer edit the filter or add new care provider name filters. To read our FAQ article about this permission for end users, click here.
Please note that this permission is by default set to enabled, which means that users can see all care provider names and administrators will have to actively revoke this permission for any user if needed. Therefore, there is no impact on any user that is already using care provider name filters in their existing projects.