============================================================================= Run Date: APR 04, 2023 Designation: WEBB*3*3 Package : WEBB - BED MANAGEMENT SOLUTION Priority: Mandatory Version : 3 SEQ #5 Status: Released Compliance Date: MAY 05, 2023 ============================================================================= Subject: COMM CARE ENH / AUDIT LOG REPORT DEFECT, ETC. Category: - Informational - PATCH FOR A PATCH Description: ============ The WEBB*3*3 patch resolves the following defects and one enhancement 1. HDSO-448, INC21303958 - Times in BMS and VistA are off by 4 hours 2. HDSO-1116, INC24273393 - Patient records being over updated 3. HDSO-4214, INC26275891- Icon Audit Reporting - Inaccurate Icon Collection reporting 4. HDSO-862, INC23843018 - Audit Log Report - Veterans Integrated Services Networks (VISN) List Not in Order 5. HDSO-1115, INC24309952 - Beds Out of Service By Date report incorrectly displays beds in service or beds not in date range 6. HDSO-1168 - Patient Removed from Patient Pending Bed Placement List (PPBPL) Not Showing on Today-24 Hour view 7. HDSO-2815, INC24953516 - BMS-SHR- BMS Contingency Whiteboard Report Path 8. HDSO-3867, INC26021574 - Group Ward Names are incorrectly displaying special characters Duplicates: INC26049753 9. HDSO-3874, INC26020836 - VISN Finalization Error Duplicates: INC26076384 10. HDSO-2956, INC25411111 - Audit Log Report - Unable to Run Patient Icon Audit Log report in BMS under Site Options 11. HDSO-4192, INC19249545 - Audit Log Report - times are off by a full hour 12. WEBBMS-4009 - Force Community Care Selection on Facility and PPBP Edit Patient Patch Components: ----------------- Files & Fields Associated: N/A File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File Number 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): 1. JIRA ID: WEBBMS-4009 - User Story: As a BMS admin, I need the 'Community Care Patient?' designation for PPBP records (facility and VISN level) to be a required value, so that reporting can be done on patients seeking a VA bed but still in the community. Solution: Force the answer to the newly worded question of "Did the transfer request or completed transfer originate from the community?" which was previously "Community Care Patient?" by utilizing a new field in the table WAITING_LIST called "COMMUNITY_CARE_VERIFIED". When the question is answered either Yes or No, the field "COMMUNITY_CARE_VERIFIED" field will be set to 1 instead of 0, removing the validation requirement for the Community Care question on the facility Edit Patient PPBP screen. The same is true for the VISN Edit Patient screen, where in this case, the table being used is the TRANSFER_REQ table and the same field "COMMUNITY_CARE_VERIFIED" will be added and utilized for forcing user selection. In the case of the Facility Edit PPBP patient screen, the selection will be moved higher and separated from the other selected views. Both of the labels for "Community Care Patient" for the Facility and VISN Edit PPBP patient have been modified to read "Did the transfer request or completed transfer originate from the community? and will be a Yes/No dropdown. Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: 1. HDSO-448, INC21303958 - Times in BMS and VistA are off by 4 hours Problem: -------- Auto-removed waiting list items were being converted to Universal Time Coordinated (UTC) when they were already in UTC. Resolution: ----------- The code running the extra UTC conversion was removed. 2. HDSO-1116, INC24273393 - Patient records being over updated Problem: -------- Attending Provider not displaying on the correct patient in some rare cases. When a patient has been to more than one facility, the BMS background processors will bring in updates from each facility. BMS only stores one current patient record so when the data is different at each facility, the patient data can be inaccurate. Resolution: ----------- The logic for checking if a patient had changed in the PatientWriter had an erroneous assumption when checking Treating Specialties. This logic error was fixed to resolve the issue with treating specialty comparisons. The Patient Update stored procedure was updated to only allow a patient record update to occur if 1) the patient is currently admitted to the facility where the update is coming from or 2) if the patient is currently on the PPBPL where the update is coming from. 3. HDSO-4214, INC26275891- Icon Audit Reporting - Inaccurate Icon Collection reporting Problem: -------- Any time icons are updated for either a patient or bed, the application has a flaw in that it resets the entire collection of icons using the username of the person performing the last action For example, if user B adds Icon BB to a Patient record, the Audit Log reports from the application that all icons are first removed by that user and then all icons are added, in addition to the new Icon (BB) to the collection-- all with the same system time and user account. This is an inaccurate and a unclear way to keep an audit of icons. Resolution: ----------- The stored procedures which perform the updates have been updated to correct an issue where it was removing all icons and re-adding them, including the deltas to the temporary table. An additional check was added to ensure the icon IDs in the parameter being passed were not all removed and readded. Using the example above, only the addition of Icon "BB" will show in the report at that date/time and by the correct user. 4. HDSO-862, INC23843018 - Audit Log Report - Veterans Integrated Services Networks (VISN) List Not in Order Problem: -------- The VISN dropdown list is not in numerical order. It was in alphabetic order, treating the numbers as characters such that they were listed as VISN1, VISN10, VISN11, etc.. instead of VISN1, VISN2, VISN3, etc.. Resolution: ----------- The report to list the VISN was updated to be in proper numerical order. 5. HDSO-1115, INC24309952 - Beds Out of Service By Date report incorrectly displays beds in service or beds not in date range Problem: -------- When the end user executes the Beds Out of Service (By Date) report, the dates that appear on the report do not match between the Start and End Date parameters. The majority of BED_REASON_COMMENT_HISTORY records were not getting the completed date that the report relies on. Resolution: ----------- In addition to confirming/updating the original date logic, a change has been made to the report stored procedure usppi_BedsOutOfServiceByDate to only include records where the Updated or Entered Dates fall within the date range selected. 6. HDSO-1168 - Patient Removed from Patient Pending Bed Placement List (PPBPL) Not Showing on Today-24 Hour view Problem: -------- BMS is not converting to local time of the site which caused a several hour delay in the patient showing up on the PPBPL. Resolution: ----------- In the database stored procedure, a local time zone conversion was added to the patient display filter. 7. HDSO-2815, INC24953516- BMS-SHR- BMS Contingency Whiteboard Report Path Problem: ------- Using a contingency report path in the contingency settings form produces an error if the path contains a fully qualified domain. Users are unable to work around the error without assistance from the Tier 3 technical team. Resolution: ------- Created an input validator attribute class that properly tests if the contingency path input is a valid UNC path. The attribute class is named UncValidationAttribute.cs replaced the old regex-based validator attribute with a new validator attribute. This update allows for end users to input a FQDN path without the input validator rejecting the data. Users are encouraged to update their Whiteboard Report paths to include the Fully Qualified Domain Name of the network share/machine. An example of this would be "\\PRC-US123.v24.domain.ext\Contingency" 8. HDSO-3867, INC26021574 - BMS bed board kiosk WARD SITE NOT WORKING Duplicates: INC26049753 Problem: ------- BMS Group Wards with special characters are displayed with underscores and this causes issues with BMS Kiosk. Resolution: --------- Updated the code to generate the Whiteboard Report file name (which is based on Group Ward text) as a separate variable in order to break the reference link to the Group Ward in the Entity Cache. This resulted in the text name changing for display on the website. 9. HDSO-3874, INC26020836 - VISN Finalization Error Duplicates: INC26076384 Problem: ------- When trying to finalize movements from the VISN PPBP list in BMS we get the error, "Sorry, the patient you are trying to transfer was not found in VistA". There is a code problem where the VistA IEN Map field for the patient is not mapped to return on the object, so it is viewed by the code as null and takes it down a path to display that message when it shouldn't. Resolution: ------- Update the Patient class code to process and read the VistaIenMap property correctly with the DataMember attribute to resolve patient to VistA linking. 10. HDSO-2956, INC25411111 - Audit Log Report - Performance Improvement Problem: -------- Unable to Run Patient Icon Audit Log report in BMS under Site Options, even for a one day date range. The user is receiving an error that says "for more information about this error navigate to the report server on the local server machine, or enable remote errors." Resolution: ----------- The stored procedures for Bed and Patient Icons have been optimized to execute much faster than before. The primary optimization was to pre-filter the temporary patient table with the date parameters supplied instead of gathering all possibilities of patients that ever had an admission in the facility as well as removing an unnecessary temp table for wards. 11. HDSO-4192, INC19249545 - Audit Log Report - Time Zone Issue Problem: -------- Whenever the Audit Log Report is run, some facility times are off by one hour. Resolution: ----------- The stored procedures usppi_Rpt_WhiteboardAuditLog_PAT_ICONS and usppi_Rpt_WhiteboardAuditLog_BED_ICONS have been updated to utilize the correct facility time zone parameter Test Sites: ----------- Clement J. Zablocki Veterans Affairs Medical Center (Milwaukee, WI) Marion VA Medical Center (Marion, IL) VA Black Hills Health Care System (Fort Meade, SD) verified issues #7-8 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being deployed by the IO Enterprise Server Support Team. Documentation describing the new functionality is included in this Release. Documentation can be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/. Documentation can also be obtained at https://download.vista.domain.ext/index.html/SOFTWARE. Documentation Title File Name --------------------------------------------------------------------- Bed Management Solution Version 3.3 Technical Manual bms_3_3_tm_4_0.PDF Bed Management Solution Version 3.3 User Guide bms_3_3_ug_4_0.PDF Patch Installation: ------------------- Pre/Post Installation Overview: Austin Information Technology Center (AITC) performs patch installation on a centralized web server. BMS is a .NET based web application build. This is a centralized server promotion. No installation is required at local sites. Pre-Installation Instructions: This patch may be installed with users on the system although it is recommended that it be installed during non-peak hours to minimize potential disruption to users. However, no installation is required at local sites. Installation Instructions: N/A Post-Installation Instructions: N/A Back-Out/Roll Back Plan: ------------------------ Backout plan is provided as part of deployment instructions provided to Routine Information: ==================== No routines included. ============================================================================= User Information: Entered By : Date Entered : AUG 16, 2022 Completed By: Date Completed: APR 03, 2023 Released By : Date Released : APR 04, 2023 ============================================================================= Packman Mail Message: ===================== No routines included