$TXT Created by A at MNTVBB.DOMAIN.EXT (KIDS) on Tuesday, 10/19/21 at 13:49 ============================================================================= Run Date: JUN 02, 2022 Designation: EDP*2*16 Package : EDP - EMERGENCY DEPARTMENT Priority: Mandatory Version : 2 SEQ #11 Status: Released Compliance Date: JUL 03, 2022 ============================================================================= Associated patches: (v)EDP*2*2 <<= must be installed BEFORE `EDP*2*16' Subject: MAINTENANCE FIXES FOR NEW ORDERS, 0 POINTER, ADD RPCS Category: - Routine - Other Description: ============ Patch EDP*2.0*16 addresses the following: 1. INC15877607 - Unverifiable order created in Emergency Department Integration System (EDIS) when pharmacy processes/edits medication orders. 2. INC12684952 - EDIS is passing a provider pointer of '0' to DATA2PCE. 3. Jira EDIS-418 - Remote Procedure Calls (RPCs) added to EDIS menu option. Patch Components: ----------------- Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- EDPF TRACKING SYSTEM Broker Modified Defect Tracking System Tickets(s) & Overview: 1. INC15877607 - Unverifiable order created in EDIS when pharmacy processes/edits medication orders. Problem: -------- When an outpatient pharmacy order is created in Computerized Patient Record System (CPRS) and then edited in the Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option, the "New" column in EDIS counts one order more than it should on the Clinical Practice Environment (CPE) screen. Technical Explanation: ---------------------- In the EDIS Mumps code, any time a new order is created, regardless of its status, it is automatically assumed to be an order with "New" status. When some fields are edited in pharmacy backdoor, such as dosage, instead of editing the current order, a new order is created. This order is sent to routine EDPFMON where EDIS checks the status of the HL7 message sent from Pharmacy. The current code does not check to see if the order is an edited order or an actual new order, so it adds the edited order as if it was a new order. In the ED LOG (#230) file, you can see both the original and edited order. Resolution: ----------- EDIS now checks if the order already exists and if the order status is "Active" or "New" before updating the "New" column. 2. INC12684952 - EDIS is passing a provider pointer of '0' to DATA2PCE. Problem: -------- There is a defect in the Document Storage Systems (DSS) software that is creating 'V' Purpose of Visit (POV) entries that have a provider narrative pointer of '0'. These 'V' POV entries are picked up in EDIS where they cause the system to error when the Activity Report is run. Technical Explanation: ---------------------- The '0' entry is in the PROVIDER NARRATIVE (#.04) field of the V POV (#9000010.07) file. EDIS uses this file to retrieve the diagnosis name for a patient when the Activity Report is run. An undefined error occurs in routine EDPQPCE when '0' is passed and EDIS attempts to assign this value to a variable. Resolution: ----------- EDIS now checks for null values to prevent undefined errors. Additionally, if the name pointer is invalid, EDIS will use the diagnosis's Internal Entry Number (IEN) to retrieve the name from the ICD DIAGNOSIS (#80) file. 3. Jira EDIS-418 - Remote Procedure Calls (RPCs) added to EDIS menu option. Problem: -------- The current login configuration for EDIS uses the VistA Integration Adapter (VIA) code which is slated for decommission and must be changed. Resolution: ----------- Multiple RPCs from the Kernel namespace are being added to the EDIS version 1.0 [EDPF TRACKING SYSTEM] option to login to the application instead of using the VIA system. The RPCs added are: RPC: XUS SIGNON SETUP RPC: XUS AV CODE RPC: XUS ESSO VALIDATE RPC: XWB CREATE CONTEXT RPC: ORWU USERINFO Test Sites: ----------- VA Greater Los Angeles HCS (West Los Angeles, CA) Lexington VA HCS (Lexington, KY) Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. 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 Technical Manual EDIS_2_2_TM.pdf Deployment, Installation, Back-Out, and EDP_2_2_P16_DIBR.pdf Rollback Guide Patch Installation: ------------------- 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*16) 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*16. 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 decision to back-out or rollback software will be a joint decision between development team, VA site/region personnel and other appropriate VA personnel. Prior to installing an updated KIDS package, the site/region should have saved a backup of the routines in a mail message using the Backup a Transport Global [XPD BACKUP] menu option (this is done at time of install). The message containing the backed-up routines 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) option and choose the patch (EDP*2.0*16b) to install. The back-out plan is to restore the routines or build from the backup created. No data was modified by this patch installation and, therefore, no rollback strategy is required. Validation of Back-Out Plan: ---------------------------- The back-out plan can be verified by printing the first two lines of the routines contained in this patch using the First Line Routine Print [XU FIRST LINE PRINT] option. After the routines contained in this patch have been backed out, the second line of the routines will no longer contain designation of this patch in the patch list section. Routine Information: ==================== The second line of each of these routines now looks like: ;;2.0;EMERGENCY DEPARTMENT;**[Patch List]**;May 2, 2012;Build 6 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: EDPFMON Before: B26481799 After: B28365715 **16** Routine Name: EDPMAIL Before: B7450955 After: B7551269 **16** Routine Name: EDPQPCE Before: B6816999 After: B7098690 **6,2,16** Routine list of preceding patches: 2 ============================================================================= User Information: Entered By : Date Entered : MAY 25, 2021 Completed By: Date Completed: JUN 01, 2022 Released By : Date Released : JUN 02, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT