2023-05-23 Release 146

Features 

We're thrilled to announce a new release update for ControlCheck that brings with it a host of exciting new features and improvements!

New User Roles Have Just Landed 

With this update, Managers can now map Users to new user roles such as Traveler Nurse, Float Nurse, Pediatric Anesthesiologist, and various student roles for RN, CRNA, and Anesthesia, among others. This allows for a much more granular level of tracking and reporting, giving users the ability to track important providers and use certain roles as peer groups in Analytics.

In the past, adding a new role type to BCS required a code change and affected many areas of the app. This was not scalable and prevented users from being able to track important providers and use certain providers as peer groups in Analytics. But with our recent updates, we've made some changes to the app to accommodate a long list of user role types to select from.

We are very excited about the new roles and the potential impact they will have on IRIS Analytics. These new roles will allow for greater flexibility in peer group comparisons, which is key for identifying anomalous behavior in ControlCheck’s algorithm. In the Operating Room, for example, ControlCheck uses role-based comparison logic to compare the behaviors of all CRNAs in a single peer group. With the new roles, we anticipate even more precise and detailed analysis, which will ultimately lead to better patient safety outcomes.

This update also pairs nicely with Auditors who oversee a specific role type like Float Nurse. Previously, assigning visibility for a Float-RN Nurse Manager in the audit workflow could be difficult because their staff typically moves all around the hospital so department-based permissions are insufficient. But with this new update, managers can now remap the Float Staff to the Float Nurse role and then advise the Float Manager to filter their audit view on the Float Nurse User Role type to have a quick and easy view of their staff’s discrepancies.

The new roles, along with the pre-existing ones, are organized into higher-level groups like Registered Nurse, Anesthesiologist, CRNA, Pharmacy, Mid-Level Provider, and Additional Roles (for the remaining role types). This structure will help provide a better user experience when mapping users or when filtering to a specific role type throughout the app. This makes it easier for users to find the specific role they're looking for and provides a more intuitive interface for users who may not be as familiar with the app.

• To see the full list of User Roles available to map to in ControlCheck, see the list below.
  • Additional Roles
    • Ancillary Care
    • Dentist
    • Diagnostics Imaging Technician
    • Paramedic
    • Physician
    • Resident Physician
    • Respiratory Therapist
    • Surgeon
  • Anesthesiologist
    • Anesthesia Fellow
    • Anesthesia Resident
    • Anesthesia Resident Y1
    • Anesthesia Resident Y2
    • Anesthesia Resident Y3
    • Anesthesia Student
    • Anesthesiologist
    • Cardiac Anesthesiologist
    • Pediatric Anesthesiologist
  • CRNA
    • CRNA
    • CRNA Student
    • GRNA (Graduate)
  • Mid-Level Provider
    • Advanced Practice Nurse
    • Physician's Assistant
  • Pharmacy
    • Pharmacist
    • Pharmacy Resident
    • Pharmacy Technician
  • Registered Nurse
    • RN
    • Float Nurse
    • Licensed Practical Nurse
    • Nursing Student
    • OR RN
    • Procedural Nurse
    • Traveler Nurse

To edit the role of an existing user, simply navigate to the Manage tab, Mapped Users page, find the User, click Edit, select a new role from the dropdown and click Save. The Role selection dropdown has a search function to make it easy to find the role you want to select. The roles are also sorted alphabetically, making it even easier to find the specific role you're looking for. We’ve updated our back-end logic so that a user’s events are not re-reconciled for all time if their role change does not change Care Areas. For example, a user being remapped from RN → Float Nurse would still be in the Nursing Care Area so we would not re-process their previous events, but we will update their role name on all their old and new events.

In addition, users can now map an Unmapped User as Not Audited. To do so, simply find the unmapped user on the Unmapped Users page, click Select, Create a New User, click into the role selection, scroll to the bottom, and select Not Audited.

Overall, this update represents a significant step forward for ControlCheck, providing users with a more flexible, intuitive, and powerful tool for tracking, reporting, and analyzing data. We're excited to see the impact that this update will have on our users' workflows, and look forward to continuing to improve and expand ControlCheck.

Notes on how new roles will affect IRIS:

• Roles are used as the basis for peer group comparison in the OR care area. CRNAs are compared with CRNAs, anesthesiologists are compared with anesthesiologists, etc. Providers are primarily assessed as compared to the peer group average. Some degree of whole-care-area average is incorporated, depending on the size of the peer group; for smaller peer groups, we will include greater weighting on the whole-care-area average to balanced out the small sample size.
• Say a provider is mapped to the new “Anesthesia Resident Y1” role. They will be compared with the average behavior of other “Anesthesia Resident Y1" in the OR, but some degree of whole-OR average will be included, and that degree will be higher if there are just a small number of providers mapped to “Anesthesia Resident Y1”.
• Departments are primarily used as the basis for peer group comparison in the Nursing care area, but in some cases, role peer groups are incorporated. For the Variance Trends and Dispense Patterns metrics, roles are used if (a) the role is not the most common one (i.e., non-RN) and (b) there are at least 5 providers. As described above, there would be some inclusion of the whole-Nursing average with the degree depending on the size of the peer group.
• So for instance, if you have 50 RNs in various departments, and 10 nursing students, then the RNs would all be assessed against their department peer groups, the nursing students would be assessed against their role peer group. If we had 3 LPNs, that would not be enough for a role peer group, so they would be part of department peer groups.
• With new roles, such as “Float Nurse”, if at least 5 providers are mapped, those providers will be compared with their role peers, specifically for Variance Trends and Dispense Patterns metrics.

ControlCheck's Audit Page Gets a Performance Boost 

ControlCheck has just released an update that enhances the performance of its audit page. The update includes improvements in how data is loaded from the back-end system, resulting in a much faster audit page. These changes specifically target users who are frequently loading hundreds of event summaries at once on their Audit page. This update significantly reduces the load on the system to load all of the results at once.

With this change, users can only bulk-edit up to the first 300 event summaries in the list at a time. If the results set is greater than 300, the user will either have to perform the edits in batches of 300 or update their filter criteria (e.g. Date Range) to narrow the results. This information is noted in a helpful new tooltip next to the Select… checkbox.

Also with this change, the Patient A-Z and Z-A Group By and Sort By filters have been removed and replaced by a simple sort of patients by their Secure Patient ID that ControlCheck stores for every unique patient. This change allows us to sort the patients securely and more quickly in our back-end system and then display the real patient name, MRN, FIN, or other personally identifiable information in our user interface after all other security and user permission checks have passed. We understand that this is a common workflow to sort by Patient, so with this change, we still ensured that when the Secure Patient ID Group By and Sort By filters are applied, all of the patient's event summaries are properly grouped and sorted together on the audit page.

We expect this enhancement to have a significant positive impact on the overall speed of loading data onto the Audit page, and we will continue to monitor page load times and prioritize issues of performance degradation.

If you experience significant page slowness, please reach out to us at help@bluesight.com. We're always here to help you have the best experience with ControlCheck.

Related Events is Going Live 

We are excited to announce the upcoming launch of our newest feature, Related Events, on May 25, 2023! This new feature is designed to simplify the lives of auditors by consolidating all relevant events for a patient into one single view.

Related Events empowers auditors to easily investigate further by pulling in all surrounding events for the patient. This includes all event summary statuses, making it easy to identify back-charting or med documentation errors. With this feature, auditors can more quickly identify any potential issues and take action to resolve them.

One of the added benefits of Related Events is that if a user can see an Event Summary, they can see Related Events for that summary, which includes if that patient navigates to other parts of the hospital, thereby giving them access to all activity, within the associated time, across the hospital for that Patient. This means that auditors can quickly find all relevant information about a patient in one place, without having to search through multiple systems or reports.

The Related Events feature is intuitive and easy to use. With just a click of a button, auditors can access all the relevant information about a patient and make informed decisions. This saves time and effort for the auditor, allowing them to focus on more critical tasks.

We are confident that the Related Events feature will be a valuable asset to our users, significantly simplifying their work and saving them time. Our team has worked hard to ensure that this feature meets the needs of our users and is user-friendly, making it easy to implement in their workflow. A special thank you to our Beta Community who has helped provide valuable feedback to get the feature to this point.

We are excited about the launch of Related Events and can't wait for our users to experience the benefits of this new feature. Stay tuned for more updates on ControlCheck’s new Event Editor feature set and all of our other exciting developments!

Updates & Fixes 

• Fixed an issue with two event summaries sometimes appearing when a user searches a unique ES ID.
• Fixed an issue with transaction details not showing on event summary emails when using the Email Event Summary feature.
• Fixed an issue where users were unable to update email notification preferences for investigations on the Account Settings page.
• Fixed a bug where events were ingested as a future date and time due to month/day switch in the source file compared to what the adapter was expecting.
• Improved performance when loading analytics reports for large numbers of Event Summaries which previously could fail.

Upcoming Features & Bug Fixes (next release) 

Release Ketamine 147 - Week of 06-06-23

• Enhancements to the User Mapper and Mapped Users pages to display more information about the provider, such as all the identifiers, hospital roles, and metadata we have saved for a given provider.
• Enhancements to Related Events to include cases for patients receiving infusions upon default load of the feature.
• A fix to address an issue with MRNs and FINs not properly displaying on the Pending Patients feature of the User Mapper and Medication Mapper pages.
• A fix to address an issue with events showing up on the Audit and Run Report pages that do not have a valid event type for auditing (e.g. Verify Inventory Count).