$TXT Created by F at CLN1G1.AAC.DOMAIN.EXT (KIDS) on Tuesday, 04/13/21 at 13:40 ============================================================================= Run Date: JUL 16, 2021 Designation: PSJ*5*418 Package : PSJ - INPATIENT MEDICATIONS Priority: Mandatory Version : 5 SEQ #360 Status: Released Compliance Date: AUG 16, 2021 ============================================================================= Associated patches: (v)PSJ*5*319 <<= must be installed BEFORE `PSJ*5*418' Subject: STOP DATE/TIME ACTIVITY LOG ENTRY SHOWS WRONG VALUE FOR 'Changed from' Category: - Routine Description: ============ This patch resolves the following issue: INC16771491 - Activity Log shows wrong 'Changed from' value when Stop Date/Time field is edited and Order is discontinued (DC'd) Defect Tracking System Ticket(s) & Overview: 1) INC16771491 - Activity Log shows wrong 'Changed from' value when Stop Date/Time field is edited and Order is DC'd Problem: -------- The Togus VA Medical Center reported a problem with the Activity Log after editing the Stop Date/Time on an IV order using the Inpatient Order Entry [PSJ OE] option. After they edited the Stop Date/Time field, it correctly created a new order; however, the Activity Log for the original/ discontinued order showed a 'Changed from' value equal to the new Stop Date/Time entered by the user instead of the original Stop Date/Time before the order was edited. Below is a capture of the Activity Log display showing the problem: ... # MMM DD,YYYY HH:MM:SS EDIT USER,NAME Comment: Order discontinued due to edit Field: 'STOP DATE/TIME' Changed from: 'MMM DD,YYYY HH:MM' <<< New Stop Date/Time (wrong) To: 'MMM DD,YYYY HH:MM' <<< Current Date/Time (correct) ... Resolution: ----------- After a few tests it was identified that the software was indeed using the wrong value for the Stop Date/Time when recording the 'Changed From' value in the Activity Log of the original/discontinued order when the Stop Date/ Time was edited by the user. A change was made to use the Stop Date/Time value from the original order instead of using the Stop Date/Time entered by the user for the new order. Technical Resolution: --------------------- The Activity Log entry is recorded by the code in STOP^PSIVORAL. It used the value in the P(3) array variable to compare against the value in the order to identify whether or not the field had been changed. It also used this value to record the 'Changed from' value in case it determined a change had occurred. The problem happened because the value in the P(3) array variable contained the Stop Date/Time value for the new order and not the original value (before the user's edit). The code was changed to use the value from the ORIGINAL STOP DATE field (#116) in the IV sub-file (#55.01) of the PHARMACY PATIENT file (#55) for DC'd orders as the 'Changed from' value, instead of the value in the P(3) array variable. Test Sites: ----------- VA Maine HCS (Togus, ME) Miami VA HCS (Miami, FL) Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. 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. or XXXXX BUILD X.X) 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 PSJ*5.0*418. 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: ------------------------ Back-out will be done only with the concurrence and participation of development team and appropriate VA site/region personnel. 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. Select the Install Package(s) option and choose the patch (PSJ*5.0*418b) 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 Procedure: --------------------------------- The Back-out Procedure 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 the patch have been backed out, the second line of the routines will no longer contain the designation of this patch in the patch list section. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.0;INPATIENT MEDICATIONS;**[Patch List]**;16 DEC 97;Build 1 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSIVORAL Before: B22277228 After: B23046156 **58,135,267,279,319,418** Routine list of preceding patches: 319 ============================================================================= User Information: Entered By : Date Entered : APR 09, 2021 Completed By: Date Completed: JUL 15, 2021 Released By : Date Released : JUL 16, 2021 ============================================================================= Packman Mail Message: ===================== $END TXT