============================================================================= Run Date: SEP 16, 2021 Designation: WEBB*2*23 Package : WEBB - BED MANAGEMENT SOLUTION Priority: EMERGENCY Version : 2 SEQ #22 Status: Released Compliance Date: SEP 18, 2021 ============================================================================= Subject: EVS Inflow Replacement Category: - Enhancement () - Informational Description: ============ VistA Patch Display Page: 1 ========================================================================== === Run Date: JUN 23, 2021 Designation: WEBB*2*23 TEST Package : BED MANAGEMENT SOLUTION Priority : EMERGENCY Version : 1 Status : UNDER DEVELOPMENT ========================================================================== === Subject: COVID-19 RELEASE PATCH - EVS REPLACEMENT FOR BED MANANGEMENT SOLUTIONS Category: INFORMATIONAL Description: =========== The WEBB*2*23 patch is the second installment of replacing the Inflow software for Bed Management Solution (BMS). This patch addresses the following Enhancements/defects: 1. EVS Inflow Replacement 2. Replace EVS Workflow Services 3. Remove EVS Configuration Table 4. Replace EVS Cache 5. Evacuated Patients not moving from Whiteboard to PPBP properly 6. Adding a Discharge Clinic that does not exist causes an Exception 7. Removal of BedBoardModule Page 8. Display Correct User Login Account 9. Deleting a Discharge Clinic causes an Error 10.Display Specialty is not being Hidden on Whiteboard after unselecting Desktop checkbox (Add/Edit Ward) 11.Patients modified in Whiteboard not showing up in Whiteboard Patient Icon Usage (Audit Log) Patch Components: ----------------- N/A Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A Additional Information: ----------------------- N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Enhancements & Overview: --------------------------------------- 1. EVS Inflow Replacement - Seven tasks that included code-side and database changes for 46 EVS tables that would replace the legacy EVS database schema - database table creation and design, ETL replacement, replace database triggers, update stored procedures, code side changes for data access layer, Stored Procedure reporting, and replace workflow services - Each task was completed for 46 database tables to replace the current services and workflows within BMS. 2. WEBBMS-1716: Replace EVS Workflow Services - This would allow patient to appear more than once on a PPBP list - Completing this task will free up services, reduce network calls, and increase BMS performance overall. 3. WEBBMS-1717: Remove EVS Configuration Table - CONFIG_EVS only has two kinds of values in it: -TimeZone: Change the VALUE_TYPE to 'ST' (instead of 'EVS') Grab the CONFIG_EVS.CODE value and stick it straight into the CONFIG-CONFIG_VALUE as-is. -StrictDecision: Change the VALUE_TYPE to 'BL' (instead of 'EVS'). Grab the CONFIG_EVS.CODE value. If it is 'Yes', we want to store a 'true' in CONFIG.CONFIG_VALUE. 4. WEBBMS-1719: Replace EVS Cache - This was overcome by optimized direct database access instead of indirect EVS service cache calls. 5. WEBBMS-2178: Removal of the BedBoardModules Page - The BedBoardModule page was a legacy feature, but is no longer needed and can be removed - Removal of this page would significantly improve application performance - a significant portion of the EVS Conversion for StrictDecision is BedBoardModule flags. Instead of converting them, the flags will be removed Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. WEBBMS- 2006: Evacuated Patients not moving from Whiteboard to PPBPL properly Problem: -------- There are inconsistencies with the ability for users to Evacuate a patient from the Ward Whiteboard - Expected results include the ability to see that evacuated patient in the Patients Pending Bed Placement table. Resolution: ----------- Code-side change to remove the old workflow associated with patients on the PPBP list. 2. WEBBMS-2175: Adding a Discharge Clinic that does not exist causes an Exception Problem: -------- Sustainment found a defect, visible in our 700 environment and in pre-prod when adding a new clinic on the Site Options --> Discharge Appt Clinics Add/Delete page. If you attempt to add a Clinic that doesn't already appear in the table beneath the dropdown, it causes an unhandled exception. Resolution: ---------- A code-side fix that created a null check for adding a new clinic that doesn't allow for a non-existant clinic to be added. 3. WEBBMS-2198: Display Correct User Login Count Problem: ------- Depending on how users log out of the BMS system, whether that be via the logout button, not logging out at all, or using Internet Explorer which doesn't properly end user's sessions with a source application, the user count displayed on the BMS National Regional Page for each VISN is incorrect. The desire of the user count functionality has been to display the # of CONCURRENT users on the site for each VISN. There is not an efficient way to reflect that within the BMS application, especially per VISN. Counts of concurrent users are available via IIS (even though it's not completely accurate), but there's not a way to determine which VISN those individual users are associated with. The application currently utilizes the LOGGED_USER tables, but it doesn't check whether that user is already logged in. This means that each time a user logs in, the user is counted. If I log in 4 times throughout the day, it displays 4 users for that VISN until the next day, when the LOGGED_USER table is cleared. Resolution: ---------- The solution will be to only log an individual user ONCE per day, thereby reflecting the number of unique/individual users logged into the application. This count WILL be accurate, but will not reflect "Concurrent users", or the total # of users that are CURRENTLY logged in. The stored procedure, BMS.dbo.usp_Insert_Logged_User will be updated to check the existence of that user in the Facility. If it already exists in the table, it will not add the user to the table, thus leaving the number of logins reported on the page 1, instead of 2,3,4, etc.. 4. WEBBMS-2296: Deleting a Discharge Clinic causes an Error Problem: -------- Adding a new clinic on the 'Site Options' --> 'Discharge Appt Clinics Add/Delete' caused an exception - it was found that deleting a Discharge Clinic also caused an error with the Procedure or function 'usp_Get_Hospital_Location_Appointment' expects parameter '@FACILITY_UID', which was not supplied. Resolution: ----------- This issue was introduced by the AUTHZ release when we replaced the InFlow BMS.MT data layer with one of our own - The problem had to do with null parameters being required to the stored procedure, but we weren't providing them because they were null and didn't expect nulls to be required. A code-side null check was added to the stored procedure. 5. WEBBMS-1417: Display Specialty is not being Hidden on Whiteboard after unselecting Desktop checkbox (Add/Edit Ward) Problem: -------- When editing a Vista Ward (Site Options --> Vista Ward Add/Edit), disabling the Desktop checkbox does not properly hide the Display Specialty on the Whiteboard after the fact. Resolution: ----------- Previously this was a WARD-based solution only, but the whiteboard displays PATIENT specialty, not WARD specialty. The solution was expanded to work with both WARD and PATIENT specialties. 6. WEBBMS-1585: Patients modified in Whiteboard not showing up in Whiteboard Patient Icon Usage (Audit Log) Problem: -------- Modifying a patient from the Whiteboard and then viewing the Whiteboard Patient Icon Usage Report in Audit, the resulting report for the Facility under test is blank; there is a header but no additional information. Resolution: ----------- Updated stored procedure 'BMS_HISTORY.dbo.usp_rpt_WhiteboardAuditLog_PAT_ICONS' to correct the issue. In 800, 700, and 600 environments and added to EVS deployment script. Also did a bit of cleanup on the Audit Log Report.rdl and deployed to same environments. Test Sites: ---------- New York Harbor: VA NY Harbor Healthcare System, Manhattan Campus Marion: Marion VA Medical Center, Marion, IL Milwaukee: Clement J. Zablocki Veterans Affairs Medical Center, Milwaukee, WI Software and Documentation Retrieval Instructions: ---------------------------------------------------- Documentation describing the new functionality for the Packman message containing a build may be included in this release. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from DOWNLOAD.VISTA.DOMAIN.EXT. Documentation can also be found on the VA Software Documentation Library at: http://www.domain.ext/vdl/ Documentation Title File Name SFTP Mode ========================================================================= BMS USER GUIDE BMS_2_4_1_UG.PDF binary BMS TECHNICAL MANUAL BMS_2_4_1_TM.PDF binary Patch Installation: ------------------- Austin Information Technology Center (AITC) performs patch installation on a centralized web server. Pre/Post Installation Overview: ------------------------------- N/A Pre-Installation Instructions: ------------------------------ N/A Installation Instructions: -------------------------- The BMS application is a centrally managed web-based application hosted at AITC. WEBB*2*23 will be loaded into BMS Production account by AITC staff. No software will be installed at the facilities. Post-Installation Instructions: ------------------------------- N/A Back-Out Plan: -------------------- A back-out plan will be sent to AITC and attached to the installation change order (CO) in a separate document. Routine Information: ==================== No routines included. ========================================================================== User Information: Entered By : DAVIDSON, STEVEN Date Entered : JUN 23,2021 Completed By: Date Completed: Released By : Date Released : ========================================================================== Routine Information: ==================== No routines included. ============================================================================= User Information: Entered By : Date Entered : JUN 17, 2021 Completed By: Date Completed: SEP 16, 2021 Released By : Date Released : SEP 16, 2021 ============================================================================= Packman Mail Message: ===================== No routines included