$TXT Created by F at CLN1G1.AAC.DOMAIN.EXT (KIDS) on Thursday, 10/29/20 at 15:18 ============================================================================= Run Date: FEB 03, 2021 Designation: PSN*4*571 Package : PSN - NATIONAL DRUG FILE Priority: Mandatory Version : 4 SEQ #552 Status: Released Compliance Date: MAR 06, 2021 ============================================================================= Associated patches: (v)PSN*4*513 <<= must be installed BEFORE `PSN*4*571' Subject: PPS-N MULTI FILE INSTALL CAUSES BAD ENTRIES IN VA PRODUCT FILE (50.68) Category: - Routine Description: ============ This patch will address the following issue: 1. INC12620504 - Requesting Assistance with an issue with PPS NEW 62 Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC12620504 - Requesting Assistance with an issue with PPS NEW 62 Problem: -------- The Clinical Product Support Team 1 (Clin 1) reported that after the release of PPS-N file #62 they received communication that the VA PRODUCT file (#50.68) contained additional entries that did not look correct. Most of the problems reported, if not all, seem to be related to non-production accounts but not all non-production accounts presented the problem. Resolution: ----------- After some extensive research it was determined that the cause of the specific problem reported is related to concurrent (grouped) installation of PPS-N file #62 and #63. Residual/temporary data from the file #62 installation is not properly cleaned up before proceeding to the installation of file #63 and it throws off the installation causing it to add thousands of corrupted records to the VA PRODUCT file (#50.68). Technical Resolution: --------------------- Line tag CKDIR+15^PSNPPSNF was using variable X22 instead of X2 in order to determine whether it should kill the ^TMP nodes used during installation of each file or not. Because of the wrong variable was used the software was not killing off the ^TMP nodes before starting installation of the next file. The solution applied was to ALWAYS kill off the ^TMP nodes after each file installation when multiple files are being installed at once. Data Clean-Up: -------------- The corrupted records will be removed from the VA PRODUCT file (#50.68) through a post-install routine with the following criteria: 1) The latest released PPS-N file was #70 released on 10/26/2020 and the last VA PRODUCT file (#50.68) record IEN was 30495. 2) A post-install routine will start looking at records with an IEN greater than 32900 as the first corrupted record was assigned the IEN 32926 as shown below: Global ^PSNDF(50.68,32000:,0 -- NOTE: translation in effect ^PSNDF(50.68,32926,0)="6610,1,1^3200624.15171^43,.02,.01^360^A" ^PSNDF(50.68,33094,0)="16647,1,1^3200624.15713^43,.02,.01^360^A" ^PSNDF(50.68,59087,0)="7647,1,1^3200624.15153^43,.02,.01^360^A" ... 3) For each record with an IEN greater than 32900 the post-install will check if each of the following required fields below has a valid value (numeric value corresponding to a valid entry in the file it points to). If at least one field is found to be valid, the record will be skipped, otherwise it will be deleted from the VA PRODUCT file (#50.68). Field # Field Name Points to ---------------------------------------------------------------- .05 VA GENERIC NAME VA GENERIC (#50.6) 1 DOSAGE FORM DOSAGE FORM (#50.606) 3 UNITS DRUG UNITS (#50.607) 4) All deleted records will be backed up to ^XTMP("PSN571PI") global and will set to remain on the database for 365 days. Test Sites: ----------- Veterans Health Care System of the Ozarks, Fayetteville AR Overton Brooks VA Medical Center, Shreveport LA Software and Documentation Retrieval Instructions: ------------------------------------------------- N/A 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. Staff should not be processing prescriptions while patch is being installed. This patch should take less than 5 minutes to install. 1. Choose the PackMan message containing this patch. 2. Choose the INSTALL/CHECK MESSAGE PackMan option. 3. From the Kernel Installation & Distribution System menu, select the Installation menu. From this menu, select Backup a Transport Global. This option will create a backup message of any routines exported with this patch. It will not backup any other changes such as DD's or templates. When prompted for INSTALL NAME, enter the patch #, PSN*4.0*571. 4. From the Kernel Installation & Distribution System menu, select the Installation menu. From this menu, you may select to use the following options: when prompted for INSTALL NAME, enter the patch #, PSN*4.0*571: a. 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 components of this patch routines, DDs, templates, etc. b. Verify Checksums in Transport Global - This option will allow you to ensure the integrity of the routines that are in the transport global. 5. From the Installation menu, select the Install Package(s) option and choose the patch to install. 6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', respond NO. 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', respond NO. 8. If prompted 'Delay Install (Minutes): (0-60): 0//' respond 0. Post-Install Routine: -------------------- The corrupted records will be removed from the VA PRODUCT file (#50.68) through a post-install routine with the following criteria: 1) The latest released PPS-N file was #70 released on 10/26/2020 and the last VA PRODUCT file (#50.68) record IEN was 30495. 2) A post-install routine will start looking at records with an IEN greater than 32900 as the first corrupted record was assigned the IEN 32926 as shown below: Global ^PSNDF(50.68,32000:,0 -- NOTE: translation in effect ^PSNDF(50.68,32926,0)="6610,1,1^3200624.15171^43,.02,.01^360^A" ^PSNDF(50.68,33094,0)="16647,1,1^3200624.15713^43,.02,.01^360^A" ^PSNDF(50.68,59087,0)="7647,1,1^3200624.15153^43,.02,.01^360^A" ... 3) For each record with an IEN greater than 32900 the post-install will check if each of the following required fields below has a valid value (numeric value corresponding to a valid entry in the file it points to). If at least one field is found to be valid, the record will be skipped, otherwise it will be deleted from the VA PRODUCT file (#50.68). Field # Field Name Points to ---------------------------------------------------------------- .05 VA GENERIC NAME VA GENERIC (#50.6) 1 DOSAGE FORM DOSAGE FORM (#50.606) 3 UNITS DRUG UNITS (#50.607) 4) All deleted records will be backed up to ^XTMP("PSN571PI") global and will set to remain on the database for 365 days. 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. The back-out plan is to restore the routines from the backup created. No data was modified by this patch installation and, therefore, no rollback strategy is required. Validation of Roll Back Procedure --------------------------------- The Roll Back Procedure can be verified by printing the first 2 lines of the PSN Routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routines contained in the PSN*4.0*571 patch have been rolled back, the first two lines of the Routines will no longer contain the designation of patch PSN*4.0*571 in the patch list section on line 2. Routine Information: ==================== The second line of each of these routines now looks like: ;;4.0;NATIONAL DRUG FILE;**[Patch List]**; 30 Oct 98;Build 5 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSN571PI Before: n/a After: B3564356 **571** Routine Name: PSNPPSNF Before: B92527436 After: B91681469 **513,571** Routine list of preceding patches: 513 ============================================================================= User Information: Entered By : Date Entered : OCT 19, 2020 Completed By: Date Completed: FEB 03, 2021 Released By : Date Released : FEB 03, 2021 ============================================================================= Packman Mail Message: ===================== $END TXT