2022-10-18 Release 131

Features

Hospital Setting for Excessive Full Package Waste ?

In a previous release, we updated the Full Package Waste report to filter out waste events from IRIS if the event had five or more full packages in a single transaction. We made that decision in an effort to ensure that erroneously documented wastes were not inflating the data and falsely skewing the Full Package Waste Report for a single user. For example, we saw instances in hospitals’ data where a user accidentally entered that they wasted 10 oral tablets instead of just the 1 they really wasted; this caused their IRIS score to increase dramatically because their peers were not wasting that many. In an effort to solve this problem, we created logic that purposely excluded a waste event if there were five or more packages wasted on a single event.

As this feature persisted, we heard feedback from children’s hospitals that had very real scenarios where a user could waste five, six, even seven full packages on a single transaction if a single dose was wasted for an adult-sized patient at a site carrying dose sizes for small children. For example, let’s say a 17-year-old patient is receiving Hydromorphone injections from a pediatric specialty doctor they see regularly at a children’s hospital. The largest dose the hospital carries of the Hydromorphone injectable is a 200mcg dose, so for an adult-sized patient, the provider must pull 10 syringes to meet the required 2mg dose. If this provider ends up wasting the dose, they have now wasted 10 full packages in a single transaction. Prior to this release, ControlCheck would filter this event from populating in the IRIS Full Package Waste report and score.

With this release, we are pleased to introduce a Hospital Setting that allows sites to customize their own excessive waste cutoff value. By default, all sites will be set at five full packages, but you can request this setting be updated by a Kit Check Admin user if you need or want it increased, like children’s hospitals. In the scenario above, the site could choose to set their cutoff at 12 packages so that any waste event with 12 or more full packages wasted on a single event are excluded from the IRIS report. A waste event filtered as excessive from the IRIS Full Package Waste report does not mean the event is filtered from ControlCheck or the audit workflow; it just means that the waste event is not included in the Full Package Waste assessment and will not impact a user’s IRIS score.

Manage Tab 2.0 is Coming ?

We couldn’t wait any longer to show you what we’ve been working on! This release features a more organized Manage tab side navigation menu. Stay tuned for more updates to the Manage pages and information on how you can be a development partner and trial new updates through our beta program. Manage Tab 2.0 will be an ongoing project over the new few quarters.

We’ve categorized the Manage pages into three main categories:

1. Application Management- the pages you use to maintain users and files for your site.
   1. Account Management
   2. Security Roles
   3. File Uploads
2. Hospital Settings- the page(s) you use to build hospital-wide standards for specific feature usage in your site’s ControlCheck application.
   1. Investigation Portfolio
3. Mappings- the pages you use to view and map locations, medications, and department.
   1. Departments
   2. Unmapped Locations
   3. Formulary
   4. Unmapped Medications
   5. Mapped Users
   6. Unmapped Users

Updates & Fixes

• Fixed an issue with the Investigation Collaborator feature where the bottom of the list of available users to add as a collaborator was cutoff and the necessary user could not be selected.
• Fixed an issue with the File Uploads page that unexpectedly changed the green progress bar experience when uploading a file.
• Fixed an issue with infusion administration events that were getting unexpectedly filtered even if they had the expected rate in the dose amount field.
• Fixed an issue that was causing an error to load the Labs → IRIS Trending page for some users.
• Fixed an issue with the session activity timeout where some users were getting kicked out of ControlCheck sooner than their expected inactivity setting.