$TXT Created by L. at MNTVBB.DOMAIN.EXT (KIDS) on Tuesday, 09/27/22 at 14:22 ============================================================================= Run Date: DEC 28, 2022 Designation: PSO*7*655 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #578 Status: Released Compliance Date: JAN 28, 2023 ============================================================================= Associated patches: (v)PSO*7*361 <<= must be installed BEFORE `PSO*7*655' Subject: CMOP EVENT LOG ENTRY DISPLAYS WRONG DATE Category: - Routine Description: ============ This patch will resolve the following issue: Multiple sites have reported separate incidents where the shipped date and time of an Rx's CMOP event are being overwritten when a reprint of a refill is executed locally. Since the refill's reprint is executed locally the CMOP event's shipped date and time should not change. Associated ticket(s): ===================== 1. INC16831138 - CMOP event log date changes from original date INC19683287 - CMOP event log does not match VistA (Duplicate) INC23136173 - CMOP event log entry displays wrong date (Duplicate) Associated NSR(s): ================== N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC16831138 - CMOP event log date changes from original date INC19683287 - CMOP event log does not match VistA (Duplicate) INC23136173 - CMOP event log entry displays wrong date (Duplicate) Problem: ------- Multiple sites have reported separate incidents where the shipped date and time of an Rx's CMOP event are being overwritten when a reprint of a refill is executed locally. Since the refill's reprint is executed locally the CMOP event's shipped date and time should not change. Resolution: ----------- The api DATE^PSORXVW2 was modified to use the DATE SHIPPED field (#9) of the CMOP EVENT multiple (#52.01) of the PRESCRIPTION file (#52) in the display of the CMOP Event Date/Time column. Technical Resolution: --------------------- Added 3rd parameter, PSXA, to tag line. This will be used to obtain the DATE SHIPPED field to display on the Date/Time column of the CMOP event record. The shipping date will be obtained, formatted and returned (PSXSDT) as follows: DATE(RX,RFL,PSXA) ; N ZDT,ZD1,ZD2,PSXSDT S PSXSDT=0 ;p655 if dispensed return shipping date I $G(PSXTST)=1 D . S ZDT=$P($G(^PSRX(RX,4,PSXA,1)),"^",2) K PSXA . S ZD1=$P(ZDT,"."),ZD1=$E(ZD1,4,5)_"/"_$E(ZD1,6,7)_"/"_$E(ZD1,2,3) . S ZD2=$E($P(ZDT,".",2),1,4) . S PSXSDT=ZD1_"@"_ZD2 I +PSXSDT Q PSXSDT ;--p655 end Patient Safety Issues (PSIs): ----------------------------- N/A Test Sites: ----------- Maryland HCS - Baltimore MD Danville VAMC, Danville IL 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 2 minutes to install. For this install there are no options that are required to be disabled. 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*655. 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*655. 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. a. When prompted 'Enter options you wish to mark as 'Out Of Order':', press the Enter key. b. When prompted 'Enter protocols you wish to mark as 'Out Of Order':', press the Enter key. c. When prompted 'Delay Install (Minutes): (0 - 60): 0//', answer 0. Back-out/Rollback Strategy: =========================== Post-Installation Instructions: ------------------------------- Installation Verification: -------------------------- Successful installation can be verified by reviewing the first 2 lines of the routines contained in the patch. The second line will contain the patch number (655) in the [PATCH LIST] section. ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997 The option Calculate and Show Checksum Values [XTSUMBLD-CHECK] can be run to compare the routine checksums to what is documented in the patch description. 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. 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 PSO*7.0*655 patch have been rolled back, the first two lines of the Routines will no longer contain the designation of patch PSO*7.0*655 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: PSORXVW2 Before: B44478716 After: B47392135 **33,71,117,152,148,367,361,655** Routine list of preceding patches: 361 ============================================================================= User Information: Entered By : Date Entered : SEP 24, 2021 Completed By: Date Completed: DEC 27, 2022 Released By : Date Released : DEC 28, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT