2021-07-23 Release 101

FEATURES

Care Area Role Mappings Refactor

Providers and their designated care areas (Nursing or OR) is a common topic and frustration for internal and external customers; particularly when it comes to those providers displaying in the correct care area in IRIS User Analytics. Through multiple iterations of ControlCheck, we have found ourselves in a state where multiple data adapters are prescribing the care area for a single provider and the outcome is conflicting data with an inaccurate association between a provider and the care area an event belongs to. 

Care areas are important in ControlCheck. Time is one reason they are relevant to ControlCheck; we use the amount of time between two events to determine if they do or do not go together and different care areas have very different “typical” behaviors when it comes to total interaction time with controlled substances. For example, on OR floors, anesthesia providers will likely have case times longer than 8 hours because a typical surgery can last about that long. A typical nursing floor interaction should involve a simple dispense from a machine on the patient’s floor with a 5-10 min window to walk to the patient and administer the medication. In this example, nursing cases are expected to be less than 30 mins from start to finish, whereas OR cases are expected to be 8 or more hours long. 

Another reason care areas are important are because providers in the OR have very different dispensing patterns than their nursing counterparts. For example, on OR floors, anesthesia providers must dispense all of the medications for the entire case at the start of the case. They may or may not use the entire dispensed amount so they will likely have full package returns or waste at the end of the case and likely have a much higher average mass dispensed tied to their user profile. On a nursing floor, an RN is more likely to just dispense the dose needed for that particular case: 2 tablets, no waste or returns, and much smaller mass quantities. 

The distinction between Nursing and OR events is imperative to ControlCheck effectively identifying anomalous providers in IRIS Analytics and properly comparing peer groups to each other. Because of this, we have completed a comprehensive refactor of provider role mappings to care areas to ensure there is no collision between the data and providers are properly displayed and included in the right care areas in Analytics. Rather than setting the role mappings at the data adapter level, they will now be defined by the mappings assigned in the hospital's settings.

If you are seeing users or providers displayed in the wrong care area analytics (e.g.

Anesthesiologists showing up in Nursing IRIS), please reach out to your Solutions Consultant or help@ControlCheck.com so that we can adjust your care area role mapping settings to be correct.

Audit Page 2.0 Updates, New Page Coming Soon!

The ControlCheck team continues to make progress on the new Audit page; check out the progress in this release below. Let us know what you think of the new design!

Event Summary Status Filter

The Status filter allows auditors to refine the audit results by event summaries with a particular status. This enhancement will replace the Open, Closed-Staff, and Closed-ControlCheck tiles that are currently at the top of the audit page.

Drugs Filter

The Drugs filter allows auditors to refine the audit results by a particular medication or group of medications.

The filter allows users to search for a particular medication. In the example below, we can find all meds related to the search input of “fentanyl”.

Let us know what you think! Interested in being a development partner with our Product team for the new Audit page? Contact your Solutions Consultant or email help@ControlCheck.com. 

Upgrades & Fixes

• Performed a Redis upgrade.
• Added the event type ‘canceled’ to the ControlCheck DB so that canceled and null events from ADC files can be properly mapped as canceled in ControlCheck. This gets us closer to being able to enable the Labs Canceled Transactions Report for all customers. 
• Updated the aggregate logic that checks if there are any unmapped meds on a patient’s events when re-aggregating data to only check for unmapped meds within the timeframe of the aggregate. Previously, we would check back for all time and see if any events for that patient had unmapped meds on them. This process can be very expensive, especially if the patient is a repeat customer and has a lot of events. The reason for checking this might be that if there are events for the patient with unmapped medications they might be for the aggregate’s medication and we don’t want to aggregate without those events. This makes sense if there are any of those events within the aggregate’s time frame, but if there are events in before or after the aggregate’s time frame, we can reasonably ignore them. If they are close by and for the same medication when mapped properly, the Aggregator should pick up those events and re-aggregate anyway.