$TXT Created by A at MNTVBB.DOMAIN.EXT (KIDS) on Tuesday, 03/23/21 at 07:49 ============================================================================= Run Date: JUN 29, 2021 Designation: EDP*2*15 Package : EDP - EMERGENCY DEPARTMENT Priority: Mandatory Version : 2 SEQ #10 Status: Released Compliance Date: JUL 30, 2021 ============================================================================= Associated patches: (v)EDP*2*6 <<= must be installed BEFORE `EDP*2*15' Subject: Disappearing Patients VistA fix Category: - Routine Description: ============ This patch includes changes for both the VistA Mumps code and for the EDIS graphic user interface (GUI). Patch EDP*2.0*15 addresses the following defects: 1. INC15787506 - EDIS v2.2 patient movement issues which caused patient to disappear from EDIS display board. 2. EDIS-122: Users can incorrectly remove a patient from the board when certain required fields were not filled out. 3. EDIS-189: Free text diagnosis cannot be expanded in the Diagnosis section of Edit Closed due to not having a key. 4. EDIS-352: Single sign on (SSOi) integration not working for integrated sites which use a single VistA. 5. EDIS-381: The landing page for non-provisioned users does not tell them how to rectify the problem. 6. EDIS-373: Room/Area Data Type is not large enough. Defect Tracking System Tickets(s) & Overview: ============================================= 1. INC15787506 - EDIS v2.2 patient movement issues which caused patient to disappear from EDIS display board. Problem: -------- When moving a patient between rooms the patient would in some cases disappear from the board. These patient entries when viewed in VistA would display in file #230 (ED LOG) as having a LOC field (3.4) entry of "0". When a patient disappears from the board they are unable to be edited or re-added to the board as the application still considered them as being on the board. Technical Explanation: ---------------------- On the room select boxes used in the popups, on the CPE screen, using the "click" event to capture changes to the selection which works properly if you click directly on the list item you want to change to. If for some reason you miss clicked on the select boxes but did not click on a list item it was still triggering the click event and which was causing the save functionality to run but doing so with the default value, in the case of room bed that is 0 which was the patient ghosting. Resolution: ----------- The click method which updates the room has been changed to no longer default to "0". The VistA routine EDPQDB has been updated to display any existing patients with a LOC field entry of "0" as being on the default room set by the TRACKING AREA File (231.9) field INITIAL ROOM. A pre-install routine will close all ambulance patients and named patients older than 5 days with a LOC of "0". 2. EDIS-122: Users can incorrectly remove a patient from the board when certain required fields were not filled out. Problem: -------- When attempting to save a record there is no indication as to which fields are required. Technical Description: ---------------------- Added some additional validation to the java UI code rather than relying just on the VistA validation. This allows for more fine-grained and complex validation behavior that may change based on selected values. There is also some new checks using other app configuration that was not previously being done. Resolution: ----------- Added validation that makes sure certain required fields are filled out when adding a new patient to the board that were not previously being checked correctly, and displays any missing required fields in an alert when attempting to save. 3. EDIS-189: Free text diagnosis cannot be expanded in the Diagnosis section of Edit Closed due to not having a key. Problem: -------- Due to the use of the ICD Code as the key for the Diagnosis display table Edit Closed diagnosis section breaks the Javascript and prevents the expansion and contraction of the Diagnosis section of the screen. Technical Description: ---------------------- On the Edit Closed screen the list backing the selected diagnosis section of the page needs to have each item in the list wrapped in a SelectionModel object that will allow for a unique key other than the ICD Code be used to identify a unique row. Resolution: ----------- Replaced the existing key field which was the ICD code with one that is generated on creation of the list that backs the component this allows both ICD 10 and free text to be handled properly. 4. EDIS-352: Single sign on (SSOi) integration not working for integrated sites which use a single VistA. Problem: -------- Users are currently unable to log in to EDIS if they belong to an integrated site, i.e., site code ending with letters. E.g., VistA 502 may support multiple integrated sites designated with letter-code suffixes (e.g., 502DT). When the fix for integrated sites was implemented the SSOi had been turned off and a bug was introduced which caused the system to error when a siteId came directly from IAM, this was not found until the SSOi was turned back on in the development environment. The system also was not presenting a list of sites when a site has integrated sites so the user can pick their integrated site. Technical Description: ---------------------- In the ApplicationSecurityFilter the line that sets division in vista needed to account for the siteId passed by IAM or the one coming from the site selection screen. Also in the security libraries VistAAuthenticationFilter there needed to be a check added to determine if the site has integrated sites and if so direct the user to the site selection page so they can choose their integrated site if they are part of one. Resolution: ----------- EDIS will now allow sign on for users that belong to integrated sites using SSOi. 5. EDIS-381: The landing page for non-provisioned users does not tell them how to rectify the problem. Problem: -------- When logging into the EDIS application users who could not authenticate because they were not provisioned with two factor authentication would not know why they could not login. Resolution: ----------- The login page has been updated to instruct the users to provision with two factor authentication. 6. EDIS-373: Room/Area Data Type is not large enough. Problem: -------- Clicking or creating new beds in the configure section of EDIS highlights multiple beds for sites where the 231.8 TRACKING ROOM-BED file has over one hundred thousand entries. Technical Description: ---------------------- The variable in the EDIS Java GUI which stored the IEN for the bed was defined as a short. This meant the maximum possible value for a bed could not exceed thirty two thousand at which point the application considered all beds to have the same number. Resolution: ----------- The variable which stores the bed IEN can now accommodate larger numbers. Test Sites: ----------- Greater Los Angeles Health Care System VA Long Beach Health Care System Boston Health Care System Software and Documentation Retrieval Instructions: ================================================= The software for this patch is being released in a PackMan message. 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. File Name Title ---------------------------------------------------- EDIS_2_2_IG.pdf EDIS Server Installation Guide with Client Configuration EDIS_2_2_TM.pdf EDIS Technical Manual EDIS_2_2_UG.pdf EDIS User Guide EDIS_2_2_GLOSSARY.pdf EDIS Glossary EDP_2_2_P15_DIBR.docx Deployment, Installation, Back-out, and Rollback Guide 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*15) 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 of any routines exported with this patch. It will not backup any other changes such as DDs or templates. i. At the Installation option menu, select Backup a Transport Global ii. At the Select INSTALL NAME prompt, enter your build EDP*2.0*15 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. Backout/Rollback Strategy: -------------------------- In the event of a catastrophic failure, the Facility CIO may make the decision to back-out the patch. It is imperative that you have performed a backup of the routines included in this patch prior to installation. The back-out plan is to restore the routines from the backup created. To verify the back-out completed successfully, ensure the checksums match the pre-patch checksums from the patch description. Routine Information: ==================== The second line of each of these routines now looks like: ;;2.0;EMERGENCY DEPARTMENT;**[Patch List]**;JAN 13, 2021;Build 4 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: EDP15P Before: n/a After: B2688979 **15** Routine Name: EDPQDB Before: B56093021 After: B57296617 **6,15** ============================================================================= User Information: Entered By : Date Entered : JAN 11, 2021 Completed By: Date Completed: JUN 29, 2021 Released By : Date Released : JUN 29, 2021 ============================================================================= Packman Mail Message: ===================== $END TXT