============================================================================= Run Date: AUG 09, 2023 Designation: WEBB*3*4 Package : WEBB - BED MANAGEMENT SOLUTION Priority: Mandatory Version : 3 SEQ #8 Status: Released Compliance Date: SEP 08, 2023 ============================================================================= Subject: COMM CARE SCREENS / DEFECT FIXES Category: - Informational - Enhancement (Mandatory) Description: ============ Bed Management Solution (BMS) patch, WEBB*3*4, implements defect fixes for creating Emergency Department Diversions, Combined Ward displays, Veterans Health Information System Technology Architecture (VistA) Out of Service (OOS) beds, DevExpress Grids on Veterans Integrated Services Network (VISN) Patient Pending Bed Placement Lists (PPBPLs), Bed Controller available beds list, and PPBPLs Auto-Removal. The patch will also introduce Enhancements for the PPBPLs records for Community Care information display. 1. HDSO-869, INC23843843 - Multiple Active Emergency Department Diversions 2. HDSO-1314, INC24533707 - Beds Missing from Combined Wards on Whiteboard 3. HDSO-2204, INC28231262 - BMS Issues - Cant remove OOS for bed 4D117-A 4. HDSO-4633, INC26689223 - VISN BMS Application: Unable to Delete Two Veterans 5. HDSO-5032, INC27446367 - PPBPL Bed Controller Dropdown Displays VistA OOS Beds Duplicates: INC27566074 6. HDSO-5067, INC27529050 - MIW BMS - EDIS Auto removal issue Duplicates: INC27442155, INC27215070 7. WEBBMS-4130 - Require a Facility PPBP 'Reasons for using Community Care' drop-down selection 8. WEBBMS-4275 - Suppress the 'Community Care Hospital?' checkbox from the facility PPBP add/edit patient screen 9. WEBBMS-4376 - Suppress the Contract and Authorized fields from the facility PPBP add/edit patient screen 10. WEBBMS-4378 - Add Community Care ("Did the transfer request or completed transfer originate from the community?") column to facility PPBP Standard view 11. WEBBMS-4379 - Remove the 'Community Care' (Authorized), 'Contract' and 'Community Care Hospital' columns from the facility PPBP Community Care view 12. WEBBMS-4380 - Acute column within facility PPBP Community Care view should be labeled "Disposition" instead 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. WEBBMS-4130 - Require a Facility PPBP 'Reasons for using Community Care' drop-down selection Request: -------- The "Reasons for Using Community Care?" drop down menu should be required, whenever the "Did the transfer request or completed transfer originate from the community?" checkbox is set to 'Yes', so that the end user is forced to supply a reason for why the patient was is using community care. Solution: --------- Make the "Reasons for Using Community Care?" drop-down menu be required, whenever the "Did the transfer request or completed transfer originate from the community?" field is set to 'Yes'. 2. WEBBMS-4275 - Suppress the 'Community Care Hospital?' checkbox from the facility PPBP add/edit patient screen Request: -------- Suppress the "Community Care Hospital?" checkbox on the PPBPL add/edit page. Solution: --------- Update the code to no longer display the checkbox. 3. WEBBMS-4376 - Suppress the Contract and Authorized fields from the facility PPBP add/edit patient screen Request: -------- Suppress the Contract and Authorized fields from the facility PPBPL add/edit page. Solution: --------- Update the code to no longer display the fields. 4. WEBBMS-4378 - Add Community Care ("Did the transfer request or completed transfer originate from the community?") column to facility PPBP Standard view Request: -------- I need to know whether the patients on my facility's PPBP list are Community Care-related or not, so that I can quickly assess the needs of the veterans associated with my VAMC. Solution: --------- When end user goes to facility PPBP, the default Standard view will contain a new "Community Care" column, which will be either a "Yes" or "No" or empty, based on the value of the Did the transfer request or completed transfer originate from the community?" field. 5. WEBBMS-4379 - Remove the 'Community Care' (Authorized), 'Contract' and 'Community Care Hospital' columns from the facility PPBP Community Care view Request: -------- As a BMS end user utilizing my facility PPBPL Community Care view, I don't understand what the "Community Care", "Contract" and "Community Care Hospital" columns refer to. Solution: --------- Remove the "Community Care", "Contract" and "Community Care Hospital" columns from the facility PPBP Community Care view. 6. WEBBMS-4380 - Acute column within facility PPBP Community Care view should be labeled "Disposition" instead Request: -------- The Disposition field determines what populates the 'Acute' column within the facility PPBP Community Care view, which is confusing for users who see "Disposition" within the add/edit patient screen as well as the Facility PPBP by Date Range report. Solution: --------- Change the "Acute" column header to say "Disposition" instead. On the Facility PPBPL Community Care view Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: 1. HDSO-869, INC23843843 - Multiple Active Emergency Department Diversions Problem: -------- A user can create multiple Emergency Department (ED) Diversions for a site. Resolution: ----------- When a user attempts to add a new ED Diversion when one already exists, prevent it, and display a message to the user to edit the current Diversion. 2. HDSO-1314, INC24533707 - Beds Missing from Combined Wards on Whiteboard Problem: -------- When selecting a Combined Ward from the Ward Whiteboard's parameter page, there are beds missing from the display. Resolution: ----------- Update the code to not filter out beds that are empty. 3. HDSO-2204, INC28231262 - BMS Issues - Cant remove OOS for bed 4D117-A Problem: -------- Beds that are VistA OOS have the option to remove the status from the Ward Occupancy report's Bed Edit page and then when the Room Bed Entity background processor runs, it reapplies the status. Resolution: ----------- Update the code that if the Bed is VistA OOS, remove the 'DELETE THIS REASON' and empty selection options from the Unavailable Reason drop down list. 4. HDSO-4633, INC26689223 - VISN BMS Application: Unable to Delete Two Veterans Problem: -------- If a user right-clicks on a DevExpress grid, there are options like 'DELETE' that are not mapped to any actual functions of BMS code. Resolution: ----------- Update the code to remove the ability to right-click on the DevExpress grids. Resolution was approved by the business office. 5. HDSO-5032, INC27446367 - PPBPL Bed Controller Dropdown Displays VistA OOS Beds Problem: -------- The Bed Controller Bed List displays beds that are VistA OOS which will result in the Bed Assigned feature to be hidden on the Whiteboard if these beds are selected. Resolution: ----------- Update the code to filter out the VistA OOS beds from the Bed Controller bed list. 6. HDSO-5067, INC27529050 - MIW BMS - EDIS Auto removal issue Problem: -------- Emergency Department Integrated Software (EDIS) records from the PPBPL are not being auto removed on patient admission. Resolution: ----------- Update the code to fix the fallback check for Facilities within a VistA in the auto removal method. Test Sites: ----------- Herschel "Woody" Williams VA Medical Center (Huntington, WV) Marion VA Medical Center (Marion, IL) VA Central Iowa Health Care (Des Moines, IA) SNOW Change Order#: CHG0394945 ------------------- TBD 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.4 Technical Manual bms_3_0_tm_3_4.pdf Bed Management Solution Version 3.4 User Guide bms_3_0_ug_3_4.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 AITC. Routine Information: ==================== No routines included. ============================================================================= User Information: Entered By : Date Entered : OCT 17, 2022 Completed By: Date Completed: AUG 04, 2023 Released By : Date Released : AUG 09, 2023 ============================================================================= Packman Mail Message: ===================== No routines included