$TXT Created by MNTVBB.DOMAIN.EXT (KIDS) on Tuesday, 08/09/22 at 13:30 ============================================================================= Run Date: FEB 07, 2023 Designation: PSO*7*699 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #582 Status: Released Compliance Date: MAR 10, 2023 ============================================================================= Associated patches: (v)PSO*7*654 <<= must be installed BEFORE `PSO*7*699' Subject: ISSUES WITH EDITING THEN REFILLING PRESCRIPTIONS Category: - Routine Description: ============ This patch addresses the following issue: In Patient Prescription Processing [PSO LM BACKDOOR ORDERS], editing a non-asterisk field of a prescription immediately before refilling it causes the label for the previous fill to print. Associated NSR(s): ================== N/A Defect Tracking System Ticket(s) & Overview: =========================================== 1. INC22631577 - ISSUES REFILLING PRESCRIPTIONS Problem: ------- When a non-asterisk field of a prescription is edited immediately before it is refilled in the Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option, the label will print for the previous fill. The Activity Log and the Label Log reference the previous fill instead of the fill requested. The Refill Log and ECME Log correctly reference the fill requested. If the prescription drug is a controlled substance, the refill cannot be signed out of the Controlled Substances package using option Outpatient Rx's [PSD OUTPATIENT] until the label is reprinted. Resolution: ---------- The issue is due to the variable RXFL not getting updated with the current fill number in routine PSOR52. Technical Resolution: -------------------- At line FINISH+36^PSOR52, the logic is modified to not jump to FINISHX but to only execute the next two lines that prevent a duplicate label from being printed. This allows RXFL to be reset with the current fill number. Line FINISH+36^PSOR52 is changed from: I PSODUP G FINISHX To: I 'PSODUP D And the next two lines are added into the Do dot structure: I 'PSODUP D . I $L(PSORX("PSOL",PSOX2))+$L(PSOX("IRXN"))<220 S PSORX("PSOL",PSOX2)=PSORX("PSOL",PSOX2)_PSOX("IRXN")_"," . E S PSORX("PSOL",PSOX2+1)=PSOX("IRXN")_"," S RXFL(PSOX("IRXN"))=PSOX("NUMBER") Patient Safety Issues (PSIs): ----------------------------- N/A Test Sites: ========== Rocky Mountain Regional VAMC Aurora, CO Iron Mountain VAMC Iron Mountain, MI 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 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 PSO*7.0*699 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. 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*699 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 your build? 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 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 Post-Installation Instructions: ------------------------------- None Installation Verification: -------------------------- Successful installation can be verified by reviewing the first 2 lines of the routine contained in the patch. The second line will contain the patch number (699) in the [PATCH LIST] section. The Calculate and Show Checksum Values [XTSUMBLD-CHECK] option can be run to compare the routine checksums to what is documented in the patch description. 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 routine in a mail message using the Backup a Transport Global [XPD BACKUP] menu option from the Kernel Installation and Distribution System Menu and selecting the Installation Menu. The back-out plan is to restore the routine from the backup created. The message containing the backed-up routine 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 routine onto the VistA System. If the patch was backed up for the build, from the Kernel Installation and Distribution System Menu, select the Installation Menu. Select the Install Package(s) option and choose the patch (PSO*7.0*699b) to install. 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 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*699 patch has been backed out, the first two lines of the routine will no longer contain the designation of this patch 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: PSOR52 Before: B37091644 After: B37132528 **10,22,27,181,148,201,260,281, 358,385,408,532,562,654,699** Routine list of preceding patches: 654 ============================================================================= User Information: Entered By : Date Entered : AUG 03, 2022 Completed By: Date Completed: FEB 07, 2023 Released By : Date Released : FEB 07, 2023 ============================================================================= Packman Mail Message: ===================== $END TXT