$TXT Created by MNTVBB.DOMAIN.EXT (KIDS) on Wednesday, 02/08/23 at 07:34 ============================================================================= Run Date: APR 28, 2023 Designation: PSO*7*717 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #591 Status: Released Compliance Date: MAY 30, 2023 ============================================================================= Associated patches: (v)PSO*7*441 <<= must be installed BEFORE `PSO*7*717' Subject: PRESCRIPTIONS SENT TO OUTPATIENT DISPENSE ROBOT AFTER BEING HELD Category: - Routine Description: ============ This patch addresses the following issue: INC25835278 - PRESCRIPTIONS SENT TO SCRIPT PRO AFTER BEING HELD 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 New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: INC25835278 - PRESCRIPTIONS SENT TO SCRIPT PRO AFTER BEING HELD Problem: -------- A prescription was placed on hold in a Vista session separate from the session where the prescription was finished and before labels were queued to print. The scenario is that multiple prescriptions are entered in CPRS and signed. In Pharmacy Prescription Processing, finish one of the orders and then, in a second Vista session, place that prescription on hold. Back in the first Vista Session, finish the remaining prescriptions and queue the labels. When you go back into Pharmacy Prescription Processing and view the Activity Logs, you will notice that the prescription on hold was sent to external interface (or Outpatient Dispense Robot) even though it was on hold. Resolution: ----------- Modify routine PSORXL1 to add the status of hold to the conditions that cause the prescription number to be removed from variable PPL that contains a string of prescriptions to print. Technical Resolution: --------------------- At ECME+8^PSORXL1 ADD PSOSTA=3 TO THE CONDITIONS: . . I PSOSTA=12!(PSOSTA=11)!(PSOSTA=3)!((PSOSTA=5)&(ESTAT'="")) D ;p717 add HOLD status Test Sites: ----------- Tennessee Valley Health Care System (Tennessee Valley, TN ) Heartland - West (Kansas City, Columbia, Topeka, Leavenworth, Wichita,KS) 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 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. PSO*7.0*717) 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*717 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 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 build 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 build 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 build 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 routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the build contained in the PSO*7.0*717 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 1 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSORXL1 Before: B63852645 After: B64295579 **36,46,148,260,274,287,289, 358,251,385,403,409,482,604, 562,441,717** Routine list of preceding patches: 441 ============================================================================= User Information: Entered By : Date Entered : FEB 07, 2023 Completed By: Date Completed: APR 27, 2023 Released By : Date Released : APR 28, 2023 ============================================================================= Packman Mail Message: ===================== $END TXT