$TXT Created by at CLN1G1.AAC.DOMAIN.EXT (KIDS) on Wednesday, 01/29/20 at 12:56 ============================================================================= Run Date: JUL 06, 2020 Designation: PSO*7*596 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #495 Status: Released Compliance Date: AUG 05, 2020 ============================================================================= Associated patches: (v)PSO*7*385 <<= must be installed BEFORE `PSO*7*596' Subject: Release of Controlled Substance (CS) after Return to Stock issue Category: - Routine Description: ============ This patch will address the following issue: INC7273701 - Release of Controlled Substance (CS) after Return to Stock issue. Defect Tracking System Ticket(s) & Overview: 1. INC7273701 - Release of Controlled Substance (CS) after Return to Stock issue. Problem: ------- An Rx was released in the VistA controlled substance package at one site, then returned to stock. Label was reprinted at another site for shipping to the patient. Controlled Substance package allowed release of the medication with inventory update. No further updates were posted to the script showing that any additional action had occurred. Outpatient Pharmacy package was not updated with the subsequent release at the second site. This potentially represents a vulnerability for diversion. The Release action works as it should in the Outpatient Pharmacy package (PSO* options). The Outpatient RX's [PSD OUTPATIENT] option is not updating Outpatient Pharmacy. This option is being addressed with this patch. Resolution: ---------- A modification was made in routine PSOCSRL to follow through and update Outpatient Pharmacy when an Original fill that was returned to stock is released. Test Sites: ---------- Tennessee Valley HCS (Murfreesboro, TN) William S. Middleton Memorial Veterans Hospital (Madison, WI) 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. This patch should take less than 5 minutes to install. Installation Instructions: 1. Choose the PackMan message containing this patch. Then select the INSTALL/CHECK MESSAGE PackMan option to load the patch. 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. (ex. PSO*7.0*596) NOTE: Using 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//', answer NO. iv. When prompted 'Delay Install (Minutes): (0 - 60): 0//', answer 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 Routine contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routine contained in the PSO*7.0*596 patch has been rolled back, the first two lines of the routine will no longer contain the designation of patch PSO*7.0*596 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 1 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOCSRL Before: B37870006 After: B37820840 **27,71,118,148,247,373,385,596** Routine list of preceding patches: 385 ============================================================================= User Information: Entered By : Date Entered : JAN 29, 2020 Completed By: Date Completed: JUL 02, 2020 Released By : Date Released : JUL 06, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT