$TXT Created by MNTVBB.DOMAIN.EXT (KIDS) on Friday, 07/09/21 at 11:20 ============================================================================= Run Date: JAN 26, 2022 Designation: PSA*3*82 Package : PSA - DRUG ACCOUNTABILITY Priority: Mandatory Version : 3 SEQ #64 Status: Released Compliance Date: FEB 26, 2022 ============================================================================= Associated patches: (v)PSA*3*70 <<= must be installed BEFORE `PSA*3*82' Subject: EDITS NOT STORED AFTER INVOICE VERIFIED Category: - Routine Description: ============ This patch will resolve the following issue: INC15104903 - Drug change on invoice not saved properly. Defect Tracking System Ticket(s) & Overview: -------------------------------------------- INC15104903 - Drug change on invoice not saved properly. Problem: -------- An incident was reported that occurs when the Processor edits a drug for a line item on an invoice, then a Verifier changes that drug to another drug using the Edit Invoices to be Verified Screen of option VERIFY INVOICES [PSA VERIFY INVOICES]. If the Verifier answers "NO" to the "Do you want to change the invoice's status to be Verified?" prompt, upon which the user is exited from the option, the edit is stored and will display for the line item. If a different user subsequently verifies the invoice with no further edits to the drug, the first Verifier's change is not retained in the DRUG ACCOUNTABILITY ORDER file (#58.811). As a result, files, inventory, and reports associated with the line item do not update as intended. Resolution: ----------- The process was modified to properly save the internal entry number (IEN) to the verifier adjustment field when an invoice's drug has been changed by another user prior to the verification of the invoice. Technical Resolution: --------------------- The routine PSAVER3 was modified beginning at tag VERIFY1+4 to update the VERIFIER ADJUSTMENT field (#5) in the ADJUSTMENTS multiple (#58.811259) of the DRUG ACCOUNTABILITY ORDER file (#58.811) when there is a change to the invoiced drug during the verification process. The field will be updated with the IEN of the drug in the DRUG file (#50). Test Sites: ========== Coatesville VA Medical Center - (Coatesville) PA James A. Haley Veterans' Hospital - (Tampa) FL Patch Installation: Pre-Installation Instructions: ============================= This patch may be installed with users on the system, but it is recommended that it be installed during non-peak hours to minimize potential disruption to users. This patch should take less than 2 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 PSA*3.0*82. 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 ex. PSA*3.0*82 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/Rollback Strategy: ========================== 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 (PSA*3.0*82b) 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 2 lines of the PSA Routine contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routine contained in the PSA*3.0*82 patch has been backed out, the second line of the Routine will no longer contain the designation of patch PSA*3.0*82 in the patch list section. Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;DRUG ACCOUNTABILITY/INVENTORY INTERFACE;**[Patch List]**;10/24/97;Build 4 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSAVER3 Before: B72006337 After: B73693842 **3,19,21,64,70,82** Routine list of preceding patches: 70 ============================================================================= User Information: Entered By : Date Entered : NOV 20, 2020 Completed By: Date Completed: JAN 25, 2022 Released By : Date Released : JAN 26, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT