2022-05-26 Release 121

Features

Infusions/IVs Reconciliation is Almost Here! 

The ControlCheck team has been working with numerous customer partners to validate ControlCheck's first iteration of closed-loop reconciliation for infusion meds. We have determined that there is value in tracking that the IV bag was hung at the patient's bedside after it was dispensed. The way this comes across in the data to ControlCheck today is we see a dispense of "1 bag" for a 20mL bag of fentaNYL 50mcg/mL infusion mix. Then, we see an administration record under an action such as New Bag that indicates that the provider has set an infusion rate for the patient and begun the infusion. ControlCheck will translate this New Bag action into the package size (in mass) of the infusion med to reconcile it with the dispense to ensure that the bag did get started on a patient. This reconciliation logic allows auditors to easily view the cases where an IV bag was dispensed and never given to a patient or returned.

In this release, we will be taking more early adopters live with the infusion reconciliation. If all goes well, we anticipate officially launching this form factor for all interested customers by the end of the quarter.

This form factor is built and available to map to in ControlCheck, but it is still in beta testing with early adopters. Please refer to the project tracker and FAQs on this Notion page for more details.

Support for Super-Patients and File Processing 

In this release, we added logic to ignore a patient MRN, FIN, or Order Number as an identifier if the value contains the sequence "E+" to prevent super-patients from forming. When a hospital's data in a csv file is downloaded and opened in Excel, there is an opportunity to introduce an unintended but catastrophic error where numeric values, such as patients' FINs, are converted to scientific notation. When this csv file is then re-uploaded into ControlCheck, the FIN column now contains the same exact value in potentially thousands of rows. This means that when the file is read by the ControlCheck file processor, the system reads all of the unique patients as having a FIN like "1.34E+10" and thinks they all have the same FIN and are the same patient. In the image below, we can see that the pat_id column contains FINs like "13456789000" that were converted to scientific notation when the file was opened in Excel.

Because of a process known as re-reconciliation, this incorrect merge spins off numerous system jobs to re-process data for all of those patients it is merging. When an unexpected patient merge that causes thousands of records to merge into one, the system has the potential to queue up so many jobs that it crashes and file processing comes to a stop. By adding logic that says ignore any MRN, FIN, or Order Number that contains the sequence E+, we are able to identify and ignore any variation of a number being converted to scientific notation in a file that gets uploaded to ControlCheck. When we see this value in a file, we will skip over it and will not use it to incorrectly merge two or more patients together.

The ControlCheck engineering and product team are continuing to join forces to eliminate super-patients from forming. In the next release, we are adding logic into the patient merge workflow that will prevent a patient record from having more than one MRN on it.

Audit 2.0 is Officially Live for All Hospitals!

We are LIVE! The ControlCheck Product, Engineering, and QA teams have spent over two years designing, interviewing, refining, building, and testing the new and improved Audit experience. For years, customers have shared common feature requests that we've wanted to give them but have been limited by outdated technology under the hood, holding us back from achieving our dreams. Upgrading our system and overall experience gives us the necessary tools and real estate to provide our users with the functionality they need to get their jobs done effectively.

Since February of this year, we have had over 90 hospitals and 180 users on Audit 2.0. With this release, we are taking about 50% of the remaining customers still on 1.0 live with 2.0. The remainder of the hospitals, and any new hospitals, will move to 2.0 with R121, scheduled for the week of May 24th. The Review Audit 1.0 page will be sunset on June 30, 2022.

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.

In this release, we've added an enhancement to the Status filter that will dynamically update the counts of each status, based on the other filters applied. For example, in the animation below, notice that the count of Open variances in the Status filter is 318 items. When the Department filter is applied for Unit 85, the Open count in the Status filter decreases to 114 to reflect the count of Open variances in Unit 85.

We've also decreased the size of the filter shapes to allow more filters to show up on the screen. Previously, the Assignment filter would frequently get dropped off the top filter bar and be hidden from view. In the animation below, the screen is capturing a Google Chrome view at 100% scale on a 13-inch laptop screen and all filters are viewable in the filter bar.

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 120.1
  • Fixed an issue with the nightly IRIS updates that was preventing the data from refreshing at night. 
• Fixed an issue with the negative symbol not appearing on missing values on the upgraded Run Report page. 
  • For example, if there was a dispense of 2mg of oxycodone and no corresponding admin, the missing amount should appear as "-2mg" but was incorrectly missing the negative sign when viewing the data on the report page. 
• Fixed an issue with the Progress Note for Investigations Email Notification that prevented the notification from sending due to an unexpected upgrade in the codebase servicing the notification. 
• Fixed an issue with the Assignment feature that was showing users departments from other hospitals that they have access to if they were assigned an event summary in that department. 
• Fixed an issue with the username plate at the right corner of the screen when the hospital name was long. 
• Upgraded the Formulary service (auto med mapping) to determine the validity of NDCs before storing them as identifiers. 
• Upgraded the color scheme for data visualizations and application menus to be consistent with the new app colors. 
• Upgraded the design and appearance of the navigation menu bar and the username plate.

Upcoming Features & Bug Fixes 

The feature enhancements and bug fixes below are tentatively scheduled the 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 122 - Week of 06-14-22

• Ability to auto-resolve PF (Preservative-Free) documentation errors for the Pharmacy module.
  • For example, if a PF NDC is ordered from the wholesaler but the pharmacy technician loads the med as a non-PF medication, ControlCheck will be able to auto-reconcile a variance caused by this, given that the hospital setting is enabled to do so.
• 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 123 - Week of 06-28-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 created.
• Upgrades to the Shift Analysis v2 Report that incorporates Kronos Time and Attendance data.