$TXT Created by                   CLN1G1.AAC.DOMAIN.EXT  (KIDS) on Thursday, 03/19/20 at 16:14
=============================================================================
Run Date: JUL 21, 2020                     Designation: PSJ*5*385
Package : PSJ - INPATIENT MEDICATIONS         Priority: Mandatory
Version : 5       SEQ #344                      Status: Released
                  Compliance Date: AUG 21, 2020
=============================================================================

Associated patches: (v)PSJ*5*366   <<= must be installed BEFORE `PSJ*5*385'

Subject: Modify User Privilege Check

Category: 
  - Routine

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

  
 After patch PSJ*5*366 was released to the field, an exception was 
 discovered that screened out qualified providers.
 Incident # INC6856520 Reflects the urgency of this patch.
 After the install of PSJ*5*366, orders entered by policy cannot be 
 finished by Pharmacy Service. This issue delays patient care and is a 
 patient safety concern - if a nurse enters a medication order per policy,
 the pharmacist is unable to process the order. The order has to be 
 re-entered by a physician and then processed by pharmacy. This 
 will increase the time until a medication can be administered to the
 patient.
  
  
 Defect Tracking System Ticket(s) & Overview:
 --------------------------------------------
 INC6856520 - Orders entered by policy cannot be finished by Pharmacy 
  
  
 Problem:
 -------
 Patch PSJ*5*366 introduced checks to verify that a user had sufficient 
 privileges to perform certain tasks. After the release of PSJ*5*366 
 an exception was discovered that prevented qualified users from 
 performing those tasks.
  
  
 Resolution:
 ----------
 Routines PSGOE1 & PSIVCHK were modified to add a condition to the original
 provider check to allow providers with sufficient privilege to write
 medications.
 ACTPRO+10^PSGOE1(provider IEN)
 AH+8^PSIVCHK
  
 The security key "ORELSE" is now checked in addition to the "PROVIDER"
 key. The code change was the same for both routines.
  Q:'$D(^XUSEC("PROVIDER",PSJDA))&'$D(^XUSEC("ORELSE",PSJDA)) "0^NO PROVI
 DER KEY"
  
  
 Test Sites:
 ----------
 Manchester VAMC, Manchester NH
 Louisville VAMC, Louisville KY
  
 Software and Documentation Retrieval Instructions:
 --------------------------------------------------
 The software for this patch is being released in a PackMan message.
  
 Patch Installation:
  
 Pre-Installation Instructions:
 --------------------------    
 If installed during the normal workday, it is recommended that the 
 the Outpatient Pharmacy users be off the system. Other VISTA users
 will not be affected.   Install Time - less than 2 minutes (unless 
 otherwise indicated)
  
  
 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. <PSJ*5*385):
  
         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.  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//', NO.
            
            a. When prompted 'Enter options you wish to mark as 
               'Out Of Order':', press the Enter key.
  
  
            b. When prompted 'Enter protocols you wish to mark as 
               'Out Of Order':', press the Enter key.
  
            c. When prompted 'Delay Install (Minutes):  (0 - 60): 0//',
               answer 0. 
  
  
  
 Back-out/Rollback Strategy:
 ====================
 Post Installation Instructions:
 -------------------------------
 None.
  
 Installation Verification:
 --------------------------
 Successful installation can be verified by reviewing the first 2 lines of 
 the routines contained in the patch. The second line will contain the 
 patch number in the [PATCH LIST] section.
  
  ;;5.0;INPATIENT MEDICATIONS;**[PATCH LIST]**;16 DEC 97;[BUILD #] 
  
 The option Calculate and Show Checksum Values [XTSUMBLD-CHECK] can be run
 to compare the routine checksums to what is documented in the patch
 description.
  
  
 Back-out Procedures:
 --------------------
 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.
  
  
 Validation of Back-out Procedure:
 ---------------------------------
 The Back-out Procedure can be verified by printing the first 2 lines of
 the PSJ Routines contained in this patch using the option First Line
 Routine Print [XU FIRST LINE PRINT]. Once the routines contained in the
 PSJ*5.0*385 patch have been rolled back, the first two lines of the
 Routines will no longer contain the designation of patch PSJ*5.0*385 in
 the patch list section on line 2.

Routine Information:
====================
The second line of each of these routines now looks like:
 ;;5.0;INPATIENT MEDICATIONS;**[Patch List]**;16 DEC 97;Build 3

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

Routine Name: PSGOE1
    Before: B32244396   After: B32563604  **7,19,26,39,58,85,80,110,127,
                                           133,134,315,366,385**
Routine Name: PSIVCHK
    Before: B27420606   After: B27713528  **54,58,81,111,213,113,179,248,
                                           366,385**
 
Routine list of preceding patches: 366

=============================================================================
User Information:
Entered By  :                               Date Entered  : FEB 07, 2019
Completed By:                               Date Completed: JUL 21, 2020
Released By :                               Date Released : JUL 21, 2020
=============================================================================


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

$END TXT