============================================================================= Run Date: MAY 13, 2022 Designation: WEBB*2*25 Package : WEBB - BED MANAGEMENT SOLUTION Priority: EMERGENCY Version : 2 SEQ #24 Status: Released Compliance Date: MAY 15, 2022 ============================================================================= Subject: EIS Replacement Category: - Informational Description: ============ VistA Patch Display Page: 1 ========================================================================== === Run Date: NOV 10, 2021 Designation: WEBB*2*25 TEST Package : BED MANAGEMENT SOLUTION Priority : EMERGENCY Version : 1 Status : UNDER DEVELOPMENT ========================================================================== === Subject: COVID-19 RELEASE PATCH - EIS REPLACEMENT FOR BED MANAGEMENT SOLUTIONS Category: INFORMATIONAL Description: =========== The WEBB*2*25 patch is the final installment of replacing Inflow in Bed Management Solution (BMS) with replacement of the Entity Identification Services (EIS) and CONFIG database schemas. WEBB*2*25 addresses the following changes/defects: 1. EIS Inflow Replacement 2. Change Data Capture for EIS 3. Change Data Capture for CONFIG 4. Inflow Identifier (II) replacement with primary keys from new tables 5. Inflow/InfoWorld Decommission 6. Change Selection of "Transfer" on PPBP to "Interfacility Transfer" 7. PPBP Standard and Patient Flow Views display the same field title "Bed Needed By:" 8. Remove users ability to add multiple comments to a bed that is listed in multiple Wards 9. Audit Log Reports 10.Bulk Deactivate when editing BMS Users 11.Background Processor issue with integrated sites 12.Patient Pending Board Placement List (PPBPL) "Standard" View 13.Enable comment button on the Environmental Management Service (EMS) Admin Page for cleaned beds. 14.NUMI icon not updating correctly. 15.Cannot Remove "Do Not Display" in BMS and receiving an unhandled exception error. 16.Staff edits do not remain on whiteboard after Ajax refresh. 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. EIS Inflow Replacement - Nine tasks that included code-side and database changes for 24 EIS and CONFIG tables that would replace the legacy EIS database schema - database table creation and design, ETL replacement, replace database triggers, EIS wrapper unit tests, update stored procedures, code-side changes for data access layer, stored procedure reporting, code-side repointing, and cache functionality. Each task was completed for 24 database tables to replace the current services and workflows within BMS. 2. WEBBMS-2580: EIS Change Data Capture - This effort was to change the way the data was archived in the history database for EIS - The change in data archiving will be more efficient and improve performance. 3. WEBBMS-2833: CONFIG Change Data Capture - This effort was to change the way the data was archived in the history database for CONFIG tables - The change in data archiving will be more efficient and improve performance. 4. WEBBMS-2410: Inflow Identifier (II) replacement with primary keys from new tables - replace all II with a new primary key integer in order to remove the II type because it is not serializable. Removal of II types is being done so that BMS integers become scalable. 5. WEBBMS-2413: Inflow/InfoWorld Decommission - find all uses of inflow services and DLL's and strip them from the code in order to complete the final code solution clean up for inflow replacement. Sections containing Inflow/InfoWorld References: Inflow Services, II References, Removing MISC DLL References, Methods entry/exit Logging and timing. 6. WEBBMS-2660: Change the selection of "Transfer" on the PPBP to "Interfacility Transfer" - change the PPBP bulk selection of "Transfer" to say "Interfacility Transfer" in order to clarify what is being selected and prevent users from mistaking the option for a different kind of Transfer. 7. WEBBMS-2983: PPBP Standard and Patient Flow Views display the same field title "Bed Needed By:" - There was a discrepancy between the column headers and field label on the PPBP list found on the facility's BMS home page. On the Standard view the datetime column that the bed is needed had a column header of "Requested", on the Patient Flow view on the PPBP the same column has the header "Anticipated Removal DT", and on the ADD/EDIT Patients Pending Bed Placement page the field has a label of "Date/Time Bed Requested" (Use "Decision to Admin Time")". For continuity, these three locations need to reflect the same wording of "Bed Needed By". 8. WEBBMS-3061: Remove users ability to add multiple comments to a bed that is listed in multiple Wards - Users need the ability to comment on a bed one time, regardless of how many wards the bed is displayed on, in order to allow BMS to be more bed driven and only display a single comment for a single bed. 9. WEBBMS-2695: Audit Log Reports - BMS to generate reports for any changes made in BMS, such as patient movement, bed type, and bed out of service, in order to improve performance of BMS system and meet enhanced reporting needs. Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1.WEBBMS-2577/2896: Bulk Deactivate when editing BMS Users Problem: ------- Bulk Deactivate when editing BMS Users at the Facility and BMS Admin level throws an error. Resolution: ---------- A code-side fix that changed the conversion of 'int' to 'string'. 2.WEBBMS-3082: Background Processor issue with integrated sites not auto adding transfers to waiting lists Problem: -------- a preexisting issue in Pre-prod and Prod where integrated sites were not auto-adding transfer patients to their wait lists. Resolution: ----------- A code-side change was made to optimize the background processor so integrated sites will be able to see transfer patients on their waiting lists if they have the facility settings turned to on to automatically add transfer patients to their wait lists. 3. WEBBMS-2588: Bed Clean Table displays "NULL" in the Created by column Problem: ------- Bed Clean Table lists "NULL" in the created by column, when the column should display the username of the person requesting the bed to be cleaned. "NULL" should not be listed to identify who created the Bed Cleaning request. It is believed that the system could be performing updates and incorrectly identifying a username, causing the created by column to display "NULL". Resolution: ---------- This happens when the system tries to match a username and the username is unknown. The system display's "NULL" because the user's name is unknown. However, we know that "NULL" means a system user has made the change. Change data capture and archiving should address this issue. 4.INC18700977 - PPBPL Standard view continues to appear even after the end user switches the page to another view. Problem: -------- End users are reporting slow response times when changing views on the PPBPL. When users work on a view of the site PPBPL other than "Standard", and switch pages or make any edits, the view changes back to the "Standard" default view. Resolution: ----------- The resolution is to maintain the state of the current view that the end user is working in a session variable. This will store the state of the site's PPBPL view and the viewed time frame (today +24, current, today -24 and past 30 days). This will reduce the frequency in which the user will need to switch their views, also reducing the number of unnecessary requests to BMS. The viewed state will be maintained while user is logged into BMS and will be reverted to the default "Standard" view once user is logged out of BMS. 5.INC18914757 - Enable comment button for EMS Admin Page for cleaned beds. Problem: -------- Users cannot edit comments on the EMS Admin page for beds that are marked clean. End users are unable to add additional comments to a closed bed (or a bed already cleaned). Resolution: ----------- Currently, the "Comment" button is grayed out for cleaned beds, and the Business would like to re-enable the "Comment" option for those cleaned beds. The new comments will be appended to existing comments in a top-down order. This change requires the buttons to be re-enabled and the current logic supports that new comments displayed first delimited by a comma followed by existing comments. 6.INC16793725 - NUMI icon not updating correctly Problem: -------- BMS is attempting to infer the NUMI Review up to date status without having the correct information to do so. BMS then marks the whiteboard as out of date even when it is not. This is mostly due to comparing a datetime movement date to a "date" review date. When any patient movement is registered for a day, BMS will mark the patient as not up to date. Resolution: ----------- The BMS enhancement that attempts to judge NUMI up to date review status will be removed. 7.INC20836055 - Cannot Remove "Do Not Display" in BMS, and getting an unhandled exception error. Problem: -------- End users attempting to remove "Do Not Display" reason comments are receiving an unhandled exception error on the Ward Occupancy page. Resolution: ----------- A null check will be added to the code to prevent the unhandled exception. 8. WEBBMS-2635 - Staff edits do not remain on whiteboard after Ajax refresh. Problem: -------- When a user attempts to make an edit to the staff column on the ward whiteboard, the update does not remain after the Ajax refresh. Resolution: ----------- A call to refresh the whiteboard cache must be made in order to see the changes after an Ajax refresh. Test Sites: ---------- 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*25 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: Hold Date : APR 01, 2022 Entered By : Date Entered : SEP 09, 2021 Completed By: Date Completed: MAY 13, 2022 Released By : Date Released : MAY 13, 2022 ============================================================================= Packman Mail Message: ===================== No routines included