PSN*4.0*571 (11972)    BUILD (9.6)

Name Value
NAME PSN*4.0*571
DATE DISTRIBUTED 2020-10-29 00:00:00
PACKAGE FILE LINK NATIONAL DRUG FILE
REQUIRED BUILD
  • PSN*4.0*513
    ACTION:   Don't install, leave global
TYPE SINGLE PACKAGE
DESCRIPTION OF ENHANCEMENTS
This patch will address the following issue: 
--------
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
1. INC12620504 - Requesting Assistance with an issue with PPS NEW 62
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"
Defect Tracking System Ticket(s) & Overview: 
     ^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.
1. INC12620504 - Requesting Assistance with an issue with PPS NEW 62
   
Problem: 
TRACK PACKAGE NATIONALLY YES
XPI1 NO
XPO1 NO
XPZ1 NO
SEQ# 552
BUILD COMPONENTS
  • ENTRIES:
    • PSNPPSNF
      ACTION:   SEND TO SITE
      CHECKSUM:   B91681469
    • PSN571PI
      ACTION:   SEND TO SITE
      CHECKSUM:   B3564356
POST-INSTALL ROUTINE EN^PSN571PI
DELETE POST-INIT ROUTINE Yes