$TXT Created by               at CLN2G2.AAC.DOMAIN.EXT  (KIDS) on Tuesday, 05/05/20 at 14:54
=============================================================================
Run Date: JUL 30, 2020                     Designation: PSO*7*597
Package : PSO - OUTPATIENT PHARMACY           Priority: Mandatory
Version : 7       SEQ #499                      Status: Released
                  Compliance Date: AUG 30, 2020
=============================================================================

Associated patches: (v)PSO*7*416   <<= must be installed BEFORE `PSO*7*597'

Subject: WRONG RX# DISPLAYED DURING ORDER VERIFICATION

Category: 
  - Routine

Description:
============

 This patch will address the following issue: 
   
 1. INC9129002 - At the final step when verifying a non-verified prescription,
                 VistA displays the incorrect prescription number. 
  
 Defect Tracking System Ticket(s) & Overview: 
 --------------------------------------------
 1. INC9129002 - At the final step when verifying a non-verified prescription,
                 VistA displays the incorrect prescription number. 
  
 Problem: 
 --------
 The Veterans Health Care System of the Ozarks reported that at the final step
 when verifying a non-verified prescription through the Patient Prescription 
 Processing [PSO LM BACKDOOR ORDERS] option it displays the incorrect
 prescription number, as shown below:
   ...
   Now Processing Enhanced Order Checks!  Please wait...
   
   Press return to continue: 
   
   TEST,PATIENT                 ID#:999-99-9999      RX#: 9999999  <<<< Wrong #
   SIMVASTATIN  5MG TAB
    
   VERIFY FOR MFR,OUTPATFOUR? (Y/N/Delete/Quit): Y// 
   ... 
   
 Resolution: 
 -----------
 It was determined that if a pharmacist first tries to verify a prescription
 entered by a pharmacy technician that had a significant order check and 
 instead of verifying the prescription s/he enters "Q" to quit and move on to
 a different patient, when s/he tried to verify a prescription for the newly
 selected patient the RX# field displayed the number of the prescription from
 the previous patient, the one with the significant order check. The problem 
 was addressed by resetting the variable that held the Rx# information every
 time the user selects to verify a prescription.
   
 Technical Resolution: 
 ---------------------
 The problem was happening because the variable INT was being used and it was
 not properly NEWed or KILLed. So, the variable INT was added to the list of
 variables being NEWed at the line tag OERR+1 in the PSOVER routine.
   
 Test Sites: 
 -----------
 Fayetteville: Veterans Health Care System of the Ozarks (Fayetteville, AR)
 West Palm Beach VAMC  (West Palm Beach, 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.  Staff should not be processing prescriptions while patch is being
 installed.  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. 
         (PSO*7.0*597)
  
         NOTE: Using <spacebar><enter> 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 of any routines exported with this patch. 
         It will not backup any other changes such as DDs or 
         templates. 
  
     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.  When prompted 'Want KIDS to INHIBIT LOGONs during the 
               install? NO//', respond NO.  
           ii. When prompted 'Want to DISABLE Scheduled Options, Menu
               Options, and Protocols? NO//', respond NO.
           iii.When prompted 'Delay Install (Minutes):  (0 - 60): 0//',
               respond 0.
  
 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
 PSO Routines contained in this patch using the option First Line Routine Print
 [XU FIRST LINE PRINT]. Once the routines contained in the PSO*7.0*597 patch
 have been rolled back, the first two lines of the Routines will no longer
 contain the designation of patch PSO*7.0*597 in the patch list section on line

Routine Information:
====================
The second line of each of these routines now looks like:
 ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 1

The checksums below are new checksums, and
 can be checked with CHECK1^XTSUMBLD.

Routine Name: PSOVER
    Before: B87892032   After: B87933411  **16,21,27,117,131,146,251,375,
                                           387,379,391,372,416,597**
 
Routine list of preceding patches: 416

=============================================================================
User Information:
Entered By  :                               Date Entered  : FEB 10, 2020
Completed By:                               Date Completed: JUL 30, 2020
Released By :                               Date Released : JUL 30, 2020
=============================================================================


Packman Mail Message:
=====================

$END TXT