2022-03-15 Release 116

R115.2 Hotfix Release

Fixed an issue with the hour when Daylight Savings starts: 2-3am

When Daylight Savings starts and the time changes from 1:59am to 2am, the clocks push time forwards by an extra one hour and it becomes 3am instead. This is colloquially known as "Spring Ahead" when we lose an hour of sleep on a sleepy Sunday heading into the spring season. This missing hour between 2-3am can cause catastrophic issues with file processing. Some hospitals' source systems respect the time change and their system does not record any events between 2:00-2:59am. However, other systems do not respect the time change and end up sending ControlCheck events that happen in that 59-min time window that it cannot recognize because the time does not exist.

With this fix, if we encounter one an event at a time in that 2:00-2:59 window, we will correct it by adding an hour to the time.

It's a quirky and interesting problem that has required severe manual intervention in the past and we are pleased to announce that this, along with "Fall Back" in the fall when Daylight Savings ends, will no longer be an issue. Kit Checkers of all time zones can rest peacefully knowing that files will not fail miserably because of a time change.

Features

Upgraded Experience in Audit 2.0
Our first round of Early Adopters for Audit 2.0 shared really helpful and insightful feedback. From the placement of buttons to the grace of the infinite scroll, you spoke and we listened! We spent the last few weeks refining and iterating on enhancements to our first version of Audit 2.0.

We are delighted to share the following updates to the new auditing experience:

1. More stream-lined Edit/Bulk-Edit experience that keeps the event summary information focused on the screen until the user is ready to perform the editing actions.
2. Integrated the ControlCheck Home Page Dashboard with the new Audit 2.0. Note this update is only live for hospitals who have 2.0 enabled via hospital settings.
   1. When a user clicks on the 'Open' variances % from the Dashboard, they will be taken to the Audit 2.0 page with the 'Open' Status and 30 days selected for the Date Range.
   2. When a user clicks on the 'Closed - Reconciled' variances % from the Dashboard, they will be taken to the Audit 2.0 page with the 'Closed - Reconciled' Status and 30 days selected for the Date Range.
   3. When a user clicks on the 'Closed - Unable to Reconcile' variances % from the Dashboard, they will be taken to the Audit 2.0 page with the 'Closed - Unable to Reconcile' Status and 30 days selected for the Date Range.
   4. When a user clicks on the 'Closed by ControlCheck' variances % from the Dashboard, they will be taken to the Audit 2.0 page with the 'Closed - ControlCheck' Status and 30 days selected for the Date Range.
3. Improved the infinite scrolling to be more reliable and less jumpy.

Check out the next release for the following enhancements to Audit 2.0:

• We are adding a second button to collapse an event summary card once open; currently, users must click the 'x' at the top right corner of the event summary card to collapse it close. We want to make this experience more user friendly by adding another 'close' button on the left-hand side of the expanded card.
• We are adding a "Scroll to top" button that will appear as users begin to scroll back up from a list of event summaries or once they reach the bottom of the results list.
• We are adding functionality so that when a user clicks the Notes icon on a collapsed event summary card, the event summary card will expand and open up directly to the Noted tab.
• We are re-ordering the event summary information on the card to the following:
• Event Summary ID
• Date
• Department
• Patient Name

All of these enhancements were derived from feedback directly from our Early Adopters. Their feedback is invaluable to the success of this product and we hope to continue to keep the ideas and suggestions rolling in!

Upgrades & Fixes

• Updated the Cerner formulary adapter to store med name (from the LABEL_DESC column) as a medication identifier; along with the NDC, Charge Number, and Pyxis ID from the file. For a given row in a formulary file, the expected medication identifier count is four.
• Removed a Data-Science-Service-Late-Waste migration step that was taking down instances.
• Added infinite scrolling to the Manage > Security Roles page.
• Fixed an issue with the Location Mapper where some locations would not properly show up on the front-end for mapping but the back-end was recognizing at unmapped. For example, the Location Mapper badge would show 12 items pending but when the Mapper would load, only two locations would display. This fix addresses the issue and properly displays all 12 locations in the Mapper.
• Fixed an issue with how the formulary adapters were formatting the NDCs that was causing a mismatch of the same NDC. For example, the Wholesaler invoices would pull in the NDC in the format '123456789' and in the EMR formulary file, we would see '123-45-6789' and the system would read both of these in as unique values when they should be the same. This fix means that NDCs will not need to be manually mapped when they are seen in Wholesaler data because they will automatically mapped through the Formulary service.
• Fixed an issue with the Status filter in Audit 2.0 where the 'Closed - Unable to Reconcile' counts were not visible due to the size of the filter box. With this fix, the filter box is wider and all statuses and counts are viewable.
• Fixed an issue in Audit 2.0 with the saved filters feature for same-session page navigation.
• Fixed an issue with the Sort By function in Audit 2.0