$TXT Created by                MNTVBB.DOMAIN.EXT  (KIDS) on Tuesday, 06/02/20 at 14:54
=============================================================================
Run Date: NOV 18, 2020                     Designation: PSO*7*604
Package : PSO - OUTPATIENT PHARMACY           Priority: Mandatory
Version : 7       SEQ #508                      Status: Released
                  Compliance Date: DEC 18, 2020
=============================================================================

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

Subject: SCRIPT REMAINS IN SUSPENSE AFTER BEING PULLED

Category: 
  - Routine

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

 This patch will resolve the following issues:
   
 Defect Tracking System Ticket(s) & Overview:
 --------------------------------------------
 1.  INC8910835 - ePharmacy order remains in suspense after pull from
 suspense action
  
 Problem: 
 -------
 When an ePharmacy prescription is pulled from suspense via the PP action 
 in the option PSO LM BACKDOOR ORDERS (Patient Prescription Processing) and
 a subsequent refill action on another prescription is performed the
 ePharmacy order remains in suspense.
  
 Resolution:
 ----------
 Apply a change that will remove the ePharmacy prescription's suspense
 record following a PP action in the option PSO LM BACKDOOR ORDERS after a
 subsequent refill action is performed on a different prescription.
   
 Technical Resolution:
 --------------------
 Modify the api ECME^PSORXL1 to check for the existence of the RXRS array 
 which is created to keep track of any prescriptions that have had the PP
 action performed on it. As a result, this will allow the suspense record
 to be removed later down the processing stream.
  
 2.  INC10739380 - Kicked out of VistA session during Outpatient Pharmacy
 processing
  
 Problem:
 --------
 During processing of Outpatient Pharmacy order, user was kicked out of 
 VistA session with an undefined error DSPL+3^PSOORNE3 *PSLSTL
  
 After doing a speed refill for a prescription that results in it 
 being suspended, the error occurs when entering a new order for a supply
 item and answering No to the final prompt 'Is this correct?'
  
 Variable RX0 is set during the speed refill and is not killed if the Rx
 is suspended when the speed refill process is done nor is it killed 
 when starting a New Order.
  
  
 Resolution:
 -----------
 Modify routine PSORXL1 to Initialize (New) the variable RX0 at the 
 start of entry 
  
    
 Test Sites:
 -----------
 Heartland - West (Wichita,KS)
 Orlando VAMC ( Orlando, FL)
  
 Software and Documentation Retrieval Instructions:  
 --------------------------------------------------
 The software for this patch is being released in a PackMan message.
  
 Patch Installation:
  
 Pre/Post Installation Overview:
 -------------------------------
 It is not necessary to disable any options.  
  
 Pre-Installation Instructions:
 ------------------------------ 
 This patch should 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 or build name. 
         (ex. PSO*7.0*604).
  
         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//',
                answer 0.
  
 Post Installation Instructions:
 -------------------------------
 None.
  
   
 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.
  
 The back-out plan is to restore the routines from the backup created.
  
 Validation of Back-out Procedure:
 ---------------------------------
 The Back-out Procedure can be verified by printing the first 2 lines of
 the routines contained in this patch using the option First Line Routine 
 Print [XU FIRST LINE PRINT]. Once the routines contained in PSO*7.0*604
 patch have been backed out, the first two lines of the routines will no 
 longer contain the designation of patch PSO*7.0*604 in the patch list
 section on line 2.

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

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

Routine Name: PSORXL1
    Before: B54060761   After: B55965143  **36,46,148,260,274,287,289,
                                           358,251,385,403,409,482,604**
 
Routine list of preceding patches: 482

=============================================================================
User Information:
Entered By  :                               Date Entered  : MAR 16, 2020
Completed By:                               Date Completed: NOV 18, 2020
Released By :                               Date Released : NOV 18, 2020
=============================================================================


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

$END TXT