$TXT Created by MNTVBB.DOMAIN.EXT (KIDS) on Monday, 01/25/21 at 15:23 ============================================================================= Run Date: FEB 17, 2021 Designation: PSD*3*90 Package : PSD - CONTROLLED SUBSTANCES Priority: Mandatory Version : 3 SEQ #74 Status: Released Compliance Date: MAR 19, 2021 ============================================================================= Associated patches: (v)PSD*3*84 <<= must be installed BEFORE `PSD*3*90' Subject: CS RELEASE AND VAULT UPDATE ISSUES Category: - Routine Description: ============ This patch will resolve the following issues: 1) INC13067038 - Outpatient Controlled Substance Potential Loophole 2) INC13890889 - Controlled Substance Prescription Returned to Stock can be redispensed in the PSD package and rereleased in PSO package without a new label printed. 3) INC11383378 - Unable to Update Controlled Substance Vault after Rx Released Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1) INC13067038 - Outpatient Controlled Substance Potential Loophole 2) INC13890889 - Controlled Substance Prescription Returned to Stock (duplicate) can be redispensed in the PSD package and rereleased in PSO package without a new label printed. Problem: -------- There are two separate incidents that were reported that when a controlled substance (CS) has been returned to stock, the PSD OUTPATIENT (Outpatient Rx's) option inappropriately allows for the inventory update of the CS dispensing vault and also allows the subsequent release of the CS prescription without the reprinting of the prescription label. Resolution: ----------- The user will no longer be able, when using the option PSD OUTPATIENT, to update the CS vault and allow subsequent release if a CS prescription has been returned to stock without the prescription label being reprinted. When this condition occurs the user will be notified on the screen with the message "Label not reprinted for this Rx that was returned to stock". Technical Resolution: --------------------- The routine PSDOPT was modified at tag PROCESS+6 to check the values in the RETURNED TO STOCK field (#32.1) and the REPRINT field (#32.2) in the PRESCRIPTION file (#52). If the RETURNED TO STOCK field contains a value and the REPRINT field is not set to 1 (true) then the message "Label not reprinted for this Rx that was returned to stock" will display. The user will then be prevented from further processing and prompted for another rx number. 3) INC11383378 - Unable to Update Controlled Substance Vault after Rx Released Problem: -------- An incident was reported that a user, when using the PSD OUTPATIENT (Outpatient Rx's) option, is unable to update the controlled substance vault when an original fill of an Rx has been returned to stock and the Rx is subsequently released using an Outpatient Pharmacy release process in place of the Rx being released using the Controlled Substance (CS) release process. Resolution: ----------- In order to allow the update of the CS vault after the CS has been returned to stock and then released via the Outpatient Pharmacy release process, a change was applied that checks for the existence of a returned to stock type transaction for the Rx in the Drug Accountability Transaction file. If this type of transaction does exist and the label for the Rx has been reprinted then the CS vault will be able to be updated. Technical Resolution: --------------------- The function PSDREPR was added to routine PSDOPT0 to cycle through the DRUG ACCOUNTABILITY TRANSACTION file (#58.81) to check if a RETURNED TO STOCK transaction was posted more recently then an OUTPATIENT RX transaction. If this is true then the function will return a 1 (true). This function is utilized at various steps, as an addition to other conditions ,to check to see if the Rx was returned to stock. The routine PSDOPT was also modified to utilize the PSDREPR^PSDOPT0 function as an additional check that will either be used to bypass or to allow the posting of a CS in the CS inventory. Test Sites: ========== Miami VAMC Cincinnati VAMC Patch Installation: Pre-Installation Instructions: ============================= This patch may be installed with users on the system, but 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 patch. 2. Choose the INSTALL/CHECK MESSAGE PackMan option. 3. From the Kernel Installation & Distribution System menu, select the Installation menu. From this menu, select Backup a Transport Global. This option will create a backup message of any routines exported with this patch. It will not backup any other changes such as DD's or templates. When prompted for INSTALL NAME, enter the patch #: PSD*3.0*90 4. From the Installation menu, you may select to use the following options. When prompted for INSTALL NAME, enter the patch #: PSD*3.0*90 a. Verify Checksums in Transport Global - This option will allow you to ensure the integrity of the routines that are in the transport global. b. Print Transport Global - This option will allow you to print only a summary of the patch, to print a summary of the patch and the routines in the transport global, or to print only the routines in the transport global. c. 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 components of this patch's routines, DDs, templates, etc.). 5. From the Installation menu, select the Install Package(s) option and choose the patch to install. 6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', respond NO. 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', respond NO. 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 Back-out Procedure: -------------------------------- The Back-out 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 PSD*3.0*90 patch have been backed out, the second line of the Routines will no longer contain the designation of patch PSD*3.0*90 in the patch list section. Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;CONTROLLED SUBSTANCES;**[Patch List]**;13 Feb 97;Build 4 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSDOPT Before: B90223389 After: B95551274 **10,11,15,21,30,39,48,62,69, 71,79,84,90** Routine Name: PSDOPT0 Before: B87954847 After: B95128095 **10,30,37,39,45,48,66,79,90** Routine list of preceding patches: 84 ============================================================================= User Information: Entered By : Date Entered : NOV 05, 2020 Completed By: Date Completed: FEB 11, 2021 Released By : Date Released : FEB 17, 2021 ============================================================================= Packman Mail Message: ===================== $END TXT