2023-08-01 Release 151

Modified on Wed, Nov 8, 2023 at 5:30 PM

Features 

Event Editor Updates

As mentioned in previous release notes, our team is hard at work on delivering the ability for power users to regroup events from one event summary and form a new one, making it easier than ever to properly manage a drug’s chain of custody in ControlCheck. We think we are only 1 sprint away from getting this in the hands of our beta users!

More details coming soon and here are a few sneak peak snapshots of things to look to out for when this becomes available:

 The Regroup Events review modal allows users to confirm the changes they are intending to make.

Users will be able to Run Report on Edited summaries. Within both the Summary and Detailed downloads, there will be columns listing the user that performed the edit and the date/timestamp of the edit.

Updates & Fixes 

  • Bug fix around the “Cinderella Rule” (i.e. whereby ControlCheck holds events near midnight).  There was an issue with Patient Care events not being properly held because we were also receiving EDI files for future dates.
  • As part of our second half of the year initiative focused on improvements to IRIS, we started with some low hanging fruit to help improve performance by dropping the bottom graph at the bottom of the Waste Networks page. In addition, currently the Waste Networks metric has four sub-scores, two are bidirectional, for a total of six potential sub-reasons that feed into the overall Waste Networks score. We’ve simplified Waste Networks scoring to make it cleaner and easier to convey, without reducing ability to detect diversion:
    • Removed the “clique” sub-score. This is the one that yields reasons of “sparse network” and “dense network” in the natural language reasons.
    • Keep the “waste buddy” sub-score since this is a very useful piece of this metric. But change it to only include positive (strong “edge”, i.e. connection to one provider, relative to number of wastes), and not the opposite, in the scoring. This won’t make any difference to the natural language reasons, just the algorithm.
    • Keep the “unique” sub-score (lots of witnesses or few witnesses relative to number of wastes). Also keep the “count” sub-score (lots of wastes overall).
    • So of the 6 possible reasons printed, 2 (sparse network / dense network) are being removed. And of the 4 components of the scoring, 1 is being removed, and 1 is being altered to be more focused on the behavior of interest.
  • Fixed a bug where no data was being displayed for providers with a highly unusual number with variances on Variance Trends.

Upcoming Features & Bug Fixes (next release) 

Release **Phenobarbital (Sprint 152) - Week of 08-14-23

  • Our goal will be to start beta with those power users that should have access to Event Editor once the next release goes out!
  • Minor look and feel updates to application styles of things such as: Notes icon, font size, color, and heights of buttons and filters.
  • Provider Identifiers update: when ControlCheck receives a new provider identifier for a given provider, and the identifier to their provider record so that the system always has the most up to date information about a provider and ensures that the most accurate provider is picked for a controlled substance event during processing. We recently communicated this was going out in the Oxycodone (151) release. We found an issue during testing which did not allow us to confidently release it this week and plan to deliver it in Phenobarbital (Sprint 152) - Week of 08-14-23.
  • Allow Managers to split and un-map medication identifiers! One of our top support requests, this will be released as a limited and closed beta initially to validate our solution. Once we are confident in our solution, we’ll circle back with more updates! We recently communicated this was going out in the Oxycodone (151) release. Since we anticipate this getting fairly significant use once this releases, we decided to hold this 1 more sprint for the team to have greater confidence in the functionality.
  • Add Ability for Managers to merge two Mapped Users through the existing Merge To feature that Admins have access to. This should cut down on some Support requests and is also related to a community idea: https://community.bluesight.com/discussion/457/give-manage-users-a-method-to-fix-mapped-user-errors#latest
  • Add Ability for Managers to export a CSV of users from the Account Management table of users at that hospital. In addition, we are adding “Last Login” to the table and the export. This is related to a community idea: https://community.bluesight.com/discussion/538/user-with-full-access-right-capability-to-download-list-of-all-account-users#latest
  • Planned bug fixes:
    • EDI invoices with no events remain in a “received” state which blocks other EDI files from going upload complete.
    • For users with access to multiple hospitals, they can receive errant Progress Note Update emails even though it is disabled for that individual hospital.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article