$TXT Created by A at MNTVBB.DOMAIN.EXT (KIDS) on Thursday, 03/16/23 at 13:50 ============================================================================= Run Date: APR 26, 2023 Designation: EDP*2*20 Package : EDP - EMERGENCY DEPARTMENT Priority: EMERGENCY Version : 2 SEQ #14 Status: Released Compliance Date: MAY 10, 2023 ============================================================================= Associated patches: (v)EDP*2*16 <<= must be installed BEFORE `EDP*2*20' Subject: SCHEDULING & FILE 100 API FIXES Category: - Routine - Other Description: ============ Patch EDP*2.0*20 addresses the following issues: 1. INC21639750 - EDIS board is displaying old (discharged) patients on the board as if they are currently being seen in the ER. 2. JIRA EDIS-458 - Update Mumps code to remove direct references to the ORDER file (#100) and replace with ORX8 API. Patch Components: ----------------- Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- EDPF SCHEDULING TRIGGER Modified Defect Tracking System Tickets(s) & Overview: 1. INC21639750 - EDIS board is displaying old (discharged) patients on the board as if they are currently being seen in the ER. Problem: -------- When a patient is added to Emergency Department Integration Software (EDIS) and then doesn't complete their visit (entered in error, left without being seen, duplicate visit, etc.), the appointment must be cancelled in VistA's Appointment Management [SDAM APPT MGT] option. Before the SD*5.3*803 patch was released, the appointment could be cancelled without deleting the check-in. However, now the check-in must first be deleted before the appointment can be cancelled. When the check-in is deleted, it triggers EDIS to put the patient back on the board. Technical Explanation: ---------------------- Routine SDAM^EDPFMON monitors changes from scheduling by protocol "SDAM APPOINTMENT EVENTS". This current code does not check the check-in time and assumes any transmission from the protocol is an admission of a patient even if the after action check-in time is null. As a result of correcting this code to check for null values, the triggers that EDIS uses to automatically add patients to the EDIS board have been changed. Patients will no longer be added to the EDIS board when an appointment is made, only after they have been checked in. "Make Appointment" is no longer available as a selection under the "EDPF SCHEDULING TRIGGER" parameter. Resolution: ----------- The EDIS application now checks to see if the check-in value is null and if so, does not add the patient to the EDIS board. The "EDPF SCHEDULING TRIGGER" parameter has been updated to only allow patients to be added to the EDIS board when checked-in to their appointment. 2. JIRA EDIS-458 - Update Mumps code to remove direct references to the ORDER file (#100) and replace with ORX8 API. Problem: -------- EDIS currently references ORDER file (#100) directly in Mumps code to pull information related to orders in VistA. If any fields were to be updated or moved, EDIS would have to update its references to file #100. To avoid this, these direct references will be replaced with an application programming interface (API) to retrieve the data instead. Technical Explanation: ---------------------- Remove direct references to ^OR(100 and replace with information retrieved from API EN^ORX8(ORIFN). Resolution: ----------- All routine references to file #100 have been removed and replaced with API. Test Sites: ----------- Upstate New York HCS VA Greater Los Angeles HCS Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Documentation describing the 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 Technical Manual EDIS_2_2_TM.pdf EDIS User Guide EDIS_2_2_UG.pdf Patch Installation: ------------------- Pre/Post Installation Overview: After installation all entries in the PARAMETERS (#8989.5) file whose "EDPF SCHEDULING TRIGGER" parameter has value "Make Appointment" will be replaced with value "Check-in". Please note divisional parameters will not be updated for sites not configured in EDIS file #231.9. Pre-Installation Instructions: Capture the system's "EDPF SCHEDULING TRIGGER" values using the List Values for a Selected Parameter [XPAR LIST BY PARAM] option (sample steps below). These captured values will be needed in the event the patch needs to be backed out. VISTA>D ^XUP Select OPTION NAME: XPAR LIST BY PARAM List Values for a Selected Parameter Select PARAMETER DEFINITION NAME: EDPF SCHEDULING TRIGGER Scheduling Trigger for EDIS 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*20) 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*20. 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. 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 of the routines 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 routines and parameters 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*20b) to install. Sites that had the VALUE field (#1) for the "EDPF SCHEDULING TRIGGER" parameter in the PARAMETERS file (#8989.5) set to "Make Appointment" before installation will need to manually change this value back to its pre-install value. Note: If a site decides to back out this patch, they should contact the National Service Desk (NSD) to submit a Service Now Incident. Routine Information: ==================== The second line of each of these routines now looks like: ;;2.0;EMERGENCY DEPARTMENT;**[Patch List]**;May 2, 2012;Build 7 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: EDP20P Before: n/a After: B1065925 **20** Routine Name: EDPFMON Before: B28365715 After: B29381800 **16,20** Routine Name: EDPHIST Before: B59451957 After: B60737317 **20** Routine Name: EDPLAB Before: B51111821 After: B52178376 **6,20** Routine list of preceding patches: 6, 16 ============================================================================= User Information: Entered By : Date Entered : JUN 24, 2022 Completed By: Date Completed: APR 25, 2023 Released By : Date Released : APR 26, 2023 ============================================================================= Packman Mail Message: ===================== $END TXT