$TXT Created by A at MNTVBB.DOMAIN.EXT (KIDS) on Thursday, 01/16/25 at 11:08 ============================================================================= Run Date: FEB 24, 2025 Designation: EDP*2*31 Package : EDP - EMERGENCY DEPARTMENT Priority: EMERGENCY Version : 2 SEQ #25 Status: Released Compliance Date: FEB 25, 2025 ============================================================================= Associated patches: (v)EDP*2*12 <<= must be installed BEFORE `EDP*2*31' Subject: INTERFACE FIXES AND APP HOUSEKEEPING Category: - Routine - Other Description: ============ EDP*2.0*31 contains both a Veterans Health Information Systems and Technology Architecture (VistA) component and JAVA graphic user interface (GUI) component for the Emergency Department Integration Software (EDIS) application. The Massachusetts General Hospital Utility Multi-Programming System (MUMPS) portion of EDP*2.0*31 has a compliance date. The GUI portion will be deployed separately. After release, the EDIS GUI/Web Server version will be 2.2.53. - This patch is approved to be installed at EHRM converted sites. Patch EDP*2.0*31 addresses the following defects: 1. INC33193019: Delay Summary Report Changes. 2. INC35220209: Diagnosis 500 error which results in logout fix. 3. INC27991352: Production JAVA logs error cleanup. 4. INC36652449: Access/Verify (A/V) code 500 error when no option assigned. 5. INC36508590: Patient stuck in a hidden room in EDIS. Patch Components: ----------------- Files & Fields Associated: 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 New/Modified/Deleted ----------------- ----------------- 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 Defect Tracking System Tickets(s) & Overview: 1. INC33193019: Delay Summary Report Changes. Problem: -------- On the "Delay Summary Report" in the reports tab there are several changes the business required to be made for certain metrics and layout. First the headers needed to be more defined so users can distinguish between the various data types. Second various metrics have had their time values adjusted. Resolution: ----------- Added underlining to the headers for "All ED Visits", "VA Admitted", and "Not VA Admitted". Changed the labels on the JAVA GUI and data values for the following: All ED Visits: "Total Visits Over Six Hours" to "Total Visits Over 240 Minutes" VA Admitted: "Total Visits Over Six Hours" to "Total Visits Over 360 Minutes" "Average Delay Time" to "Average Admit Delay Time" "Number of Admit Delays Over Six Hours" to "Number of Admit Delays Over 150 Minutes" 2. INC35220209: Diagnosis 500 error which results in logout fix. Problem: -------- When editing or selecting multiple diagnoses for a patient in the Clinical Practice Environment (CPE) screen when a user tries to navigate to another page they are met with a 500 error. Resolution: ----------- The functionality of the diagnosis table was rewritten to make sure multiple items from the list are not selected. 3. INC27991352: Production JAVA logs error cleanup. Problem: -------- In the JAVA errors logs, there is an error that appears related to a data element type mismatch. This error is only seen in logs and causes no user work stoppages. Technical Description: ---------------------- The application receives this data element . The B value in the JAVA application is assigned to an int variable which causes an error to populate in the logs. These status and id fields do not serve any purpose in the application. Both fields are hard coded in the VistA side to always be the same value. Resolution: ----------- Changed the variable which contains the id to be a String instead of an int. 4. INC36652449: A/V Code 500 error when no option assigned. Problem: -------- In patch EDP*2*27, there was a new error message added to the single sign-on (SSOI) login page which told users they were missing options in VistA and therefore could not login. However there is a contingent of users who after validating their Personal Identity Verification (PIV) cards sign in using their Access/Verify codes using the A/V login page. This is likely because they have the A/V page saved to their favorites. Resolution: ----------- Added the error check used in the SSOI validation to the A/V validation. 5. INC36508590: Patient stuck in a hidden room in EDIS. Problem: -------- When a Room/Bed is marked as never display any patient assigned to that Room or Bed will disappear from the CPE board. This occurs because the drop down boxes that Rooms/Beds can be selected from still included those that are marked to not be displayed on the board. Once this happens the only way to find the patient is to move their location in VistA or mark the Room/Bed as visible on the Board through the configuration page. Resolution: ----------- Added a check to exclude Rooms/Beds from the Room/Bed selection drop down when the field "DISPLAY WHEN" ((DISPLAY WHEN (#.07) field in the TRACKING ROOM-BED file (#231.8) is set as "Never". Test Sites: ----------- Robert J. Dole VAMC, Wichita, KS Overton Brooks VAMC, Shreveport, LA SNOW Change Order #: ------------------- VistA CO#: Robert J. Dole VAMC: CHG0567310 Overton Brooks VAMC: CHG0567310 GUI CO#: CHG0573289 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message and with a release 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 --------------------------------------------------------------------- EDIS User Guide EDIS_2_2_UG.pdf EDIS_2_2_UG.docx EDIS Technical Manal EDIS_2_2_TM.pdf EDIS_2_2_TM.docx Patch Installation: ------------------- Pre/Post Installation Overview: EDIS is a hybrid application which contains a VistA backend with a JAVA graphic user interface (GUI) frontend. This release will contain an installation for both components. The Austin Information Technology Center (AITC) will perform a patch installation on a centralized web server to update the GUI component. 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. This patch should take less than 5 minutes to install. Installation Instructions: 1. Choose the PackMan message containing this build. Then select the INSTALL/CHECK MESSAGE PackMan option to load the build. 2. From the Kernel Installation and Distribution System Menu, select the Installation Menu. From this menu, A. Select the Verify Checksums in Transport Global option to confirm the integrity of the routines that are in the transport global. When prompted for the INSTALL NAME enter the patch or build name. (ex. EDP*2.0*31) NOTE: Using will not bring up a Multi-Package build even if it was loaded immediately before this step. It will only bring up the last patch in the build. B. Select the Backup a Transport Global option to create a backup message. You must use this option and specify what to backup; the entire Build or just Routines. The backup message can be used to restore the routines and components of the build to the pre-patch condition. i. At the Installation option menu, select Backup a Transport Global ii. At the Select INSTALL NAME prompt, enter your build EDP*2.0*31. iii. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build R Routines Enter response: Build iv. When prompted "Do you wish to secure your build? NO//", press and take the default response of "NO". v. When prompted with, "Send mail to: Last name, First Name", press to take default recipient. Add any additional recipients. vi. When prompted with "Select basket to send to: IN//", press and take the default IN mailbox or select a different mailbox. C. You may also elect to use the following options: i. Print Transport Global - This option will allow you to view the components of the KIDS build. ii. Compare Transport Global to Current System - This option will allow you to view all changes that will be made when this patch is installed. It compares all of the components of this patch, such as routines, DDs, templates, etc. D. Select the Install Package(s) option and choose the patch to install. i. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//', answer NO ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer NO iii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer NO Post-Installation Instructions: N/A. Back-Out/Roll Back Plan: ------------------------ The back-out plan is to restore the routines or build from the backup created. The decision to back out the patch will be a joint decision between development team, VA site/region personnel and other appropriate VA personnel. Prior to installing the patch, the site/region should have saved a backup in a mail message using the Backup a Transport Global [XPD BACKUP] option (this is done at time of install). The message containing the backed up option can be loaded with the "Xtract PackMan" function at the Message Action prompt. The PackMan function "INSTALL/CHECK MESSAGE" is then used to install the backed up routines onto the VistA system. If the patch was backed up for the build, from the Kernel Installation and Distribution System Menu, select the Installation Menu. Then select the Install Package(s) [XPD INSTALL BUILD] option and choose the patch (EDP*2.0*31b) to install. Note: If a site decides to back out this patch, they should contact the National Service Desk (NSD) to submit a Service Now Incident. Validation of Back-Out Plan: ---------------------------- In order to verify the patch has been fully backed-out sites can check the checksums of the routines listed in this patch. Routine Information: ==================== The second line of each of these routines now looks like: ;;2.0;EMERGENCY DEPARTMENT;**[Patch List]**;Feb 24, 2012;Build 4 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: EDPQLE Before: B60984334 After: B61799551 **6,2,12,31** Routine Name: EDPRPT4 Before: B32540898 After: B32849940 **6,31** Routine list of preceding patches: 12 ============================================================================= User Information: Entered By : Date Entered : DEC 09, 2024 Completed By: Date Completed: FEB 24, 2025 Released By : Date Released : FEB 24, 2025 ============================================================================= Packman Mail Message: ===================== $END TXT