$TXT Created by CEP2S.DEVSLC.DOMAIN.EXT (KIDS) on Thursday, 12/01/22 at 16:18 ============================================================================= Run Date: JAN 25, 2023 Designation: PSO*7*710 Package : PSO - OUTPATIENT PHARMACY Priority: EMERGENCY Version : 7 SEQ #580 Status: Released Compliance Date: FEB 02, 2023 ============================================================================= Associated patches: (v)PSO*7*441 <<= must be installed BEFORE `PSO*7*710' Subject: POST CPRS V32B REFILL ISSUES Category: - Routine Description: ============ This patch corrects two issues identified after the installation of CPRS v32b regarding refills. 1. In certain situation (where there are # OF REFILLS set to 0 and no labels printed for that Rx), CPRS is allowing a refill request to go through, when it should have blocked it. (It was still getting blocked when the pharmacist tried to process it in backdoor pharmacy). This patch will fix this issue, so that CPRS returns an error message and does not accept the refill request. 2. When processing a refill request from CPRS, if there is an issue processing the refill (e.g., it was a titration Rx, or the order was flagged and the pharmacist chose not to unflag it), the pending refill request gets deleted. This patch will fix that issue and not delete the pending refill request in this situation. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File Number New/Modified/Deleted --------- ----------- -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A Additional Information: ----------------------- N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): HITPS-9764 - CPRS Not Blocking Invalid Refill Request HITPS-9758 - Issue When Processing Rx Refill Request From CPRS Defect Tracking System Ticket(s) & Overview: 1. INC25267379 (VISTAPSO-6025) - CPRS Not Blocking Invalid Refill Request Problem: -------- Chillicothe reported that in certain situation, where there are # OF REFILLS is 0 and no labels printed for that Rx, CPRS is allowing a refill request to go through, when it should have blocked it. However, such a refill is being blocked when the pharmacist tries to process it in backdoor pharmacy. Resolution: ----------- In this patch we will revert the changes to REFILL^PSOREF that were made for Park in PSO*7*441. They will be restored in a future patch (with modifications, to prevent any issues to current functionality). 2. VISTAPSO-6026 - Issue When Processing Rx Refill Request From CPRS Problem: -------- Tomah reported that when processing a refill request from CPRS, if there is an issue processing the refill (e.g., it was a titration Rx, or the order was flagged and the pharmacist chose not to unflag it), the pending refill request gets deleted. Resolution: ----------- In this patch we will revert the changes to ORD^PSOORFIN that were made for Park in PSO*7*441. Test Sites: ----------- Chillicothe VA Medical Center Tomah VA Medical Center Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Patch Installation: ------------------- Pre/Post Installation Overview: There are no pre/post installation steps associated with this patch. 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 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*710. B. Select the Backup a Transport Global option to create a backup message. You must use this option and specify what to backup; the entire Build or just Routines. The backup message can be used to restore the routines and components of the build to the pre-patch condition. i. At the Installation option menu, select Backup a Transport Global. ii. At the Select INSTALL NAME prompt, enter your build PSO*7.0*710. iii. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build R Routines Enter response: Build iv. When prompted "Do you wish to secure this message? NO//", press and take the default response of "NO". v. When prompted with, "Send mail to: Last name, First Name", press to take default recipient. Add any additional recipients. vi. When prompted with "Select basket to send to: IN//", press and take the default IN mailbox or select a different mailbox. 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 . ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer . iii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer . Post-Installation Instructions: N/A 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. No data was modified by this patch installation and, therefore, no rollback strategy is required. 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: PSOORFIN Before: B96139513 After: B94275893 **7,15,27,32,44,46,84,106,111, 117,131,146,139,195,225,315, 266,338,391,372,416,446,505, 508,557,628,441,710** Routine Name: PSOREF Before: B73693132 After: B72313300 **1,23,27,36,46,78,130,131,148, 206,313,441,710** Routine list of preceding patches: 441 ============================================================================= User Information: Entered By : Date Entered : NOV 30, 2022 Completed By: Date Completed: JAN 24, 2023 Released By : Date Released : JAN 25, 2023 ============================================================================= Packman Mail Message: ===================== $END TXT