2022-06-15 Release 122

Features

Ability to hide PHI in the App

As ControlCheck ramps up and takes on larger, more developed health systems, we have a goal to empower customers to develop their own training content by using their own ControlCheck instance. The problem with doing that today is that customers with access to at least one department of data, see PHI all the time. So if a trainer wants to take a screenshot of an event summary in ControlCheck, they have to take many manual steps after to hide the PHI from the images.

We are excited to release an update that allows any user the ability to Disable PHI and have the PHI on screen obfuscated so that screen images and recordings can easily be used for training and troubleshooting purposes. By default, Admin users will continue to have PHI disabled and end users will have PHI enabled. To enable or disable PHI in the app, click into your username menu and click the toggle to Enable PHI. Patient Names, MRNs, FINs, and Order Numbers are all considered PHI and are affected by the setting of this toggle. Provider names, roles, and locations are not considered PHI.

Ability to Auto-resolve Preservative-free (PF) Documentation Errors in the Pharmacy Module

One of our main goals this quarter was to reduce the time it takes to implement a new customer, particularly when implementing the Pharmacy Module. In our Patient Care modules (OR and Nursing), we have a setting where hospitals allow ControlCheck to auto-resolve a case discrepancy when there are medications on the summary with a mixed PF status. For example, when the Provider dispenses the dose from the Automatic Dispensing Cabinet (ADC), they select the PF dose of the med. When they administer the dose, they select the non-PF dose of the med when documenting the med as given, creating a discrepancy in the PF statuses of the meds. ControlCheck can auto-resolve these discrepancies in Patient Care, and now hospitals can choose to also auto-resolve these in the Pharmacy Module.

The lack of this feature has been particularly painful for customers who have already been live with Patient Care and now are ready to go live with the Pharmacy Module. During the implementation of Patient Care, the users likely mapped their ADC/Narc Vault medication identifier to a non-PF med, because the PF distinction really didn't matter at the time. Then when they start mapping the NDC medication identifiers seen in the Wholesaler data, users are distinctly choosing a PF status for the NDC. This results in false variances on the Pharmacy Audit page where the user can see the Invoice on one line and the Load on another, of the same medication, just different PF status, creating a frustrating experience when they want to review only true variances.

Customers of the Pharmacy Module generally agree that a difference in PF status should not create a variance in their audit workflow so we are pleased to introduce this new hospital setting that allows hospitals to auto-resolve these discrepancies.

Audit 2.0 is Officially Live for All Hospitals! ?

We are LIVE! Please note that we've updated the Audit page URL to https://app.bluesight.com/#/audit-review. This is the final URL for the Audit page. Once we sunset Audit 1.0, we will also retired the review-audit URL.

Where can I find more information on Audit 2.0?

There are some helpful articles on the new auditing experience in the in-app Knowledge Base, such as the Audit 2.0: Overview article. You can find this information by clicking the Help icon next to your User Account profile and searching Audit 2.0 in the Search bar. 

The pages below can also be exported as PDF and kept as a resource:

• Audit 2.0 One Pager with Highlights
• Audit 2.0 Help Guide 

Please reach out to the #ControlCheck-asks channel if you have any questions. 

Upgrades & Fixes

• Hotfix 121.1
  • Removed the status counts from the Status filter on Audit 2.0 because of a performance degradation issue introduced by the feature.
• Hotfix 121.2
  • Fixed an issue with the nightly IRIS updates that was preventing the data from refreshing at night.
• Hotfix 121.3
  • Fixed an issue with audit page performance.
• Fixed an issue with the hospital names in the ControlCheck System Benchmarks report. If a hospital name was updated in the Kit Check settings, the update was not being passed into System Benchmarks and the report was displaying the original hospital name that was set.
• Fixed an issue with the System Benchmarks report that would allow a user to get into an invalid date parameter scenario and result in an infinite spinning loader and no results ever showing up.
• Fixed an issue with medications in a ControlCheck formulary that were left with no Source System Med IDs when a med identifier was split from its previous medication and the Reconcile Summaries box was unchecked.
• Fixed an issue with the Role Mappings upload workflow.

Upcoming Features & Bug Fixes 

The features enhancements and bug fixes below are tentatively scheduled to go live on the dates listed. For a full rundown of all new features and fixes, make sure to read the Release Notes articles for those dates. 

Release 123 - Week of 06-28-22

• Upgrade to date pickers throughout miscellaneous parts of the app.
• Adding logic into the patient merge workflow that will prevent a patient record from having more than one MRN on it. 

Release 124 - Week of 07-12-22

• Ability to re-reconcile pharmacy events and auto-resolve false variances caused by incorrect med mapping. When an NDC is split and remapped to a new ControlCheck med or a wholesaler multiplier is changed on a medication used in the Pharmacy Module, a user can choose to re-reconcile the events for that medication identifier to auto-resolve past variances.
• Upgrades to the Shift Analysis v2 report that incorporates Kronos Time and Attendance data.