$TXT Created by NNE at MNTVBB.DOMAIN.EXT (KIDS) on Monday, 06/24/24 at 15:30 ============================================================================= Run Date: AUG 14, 2024 Designation: PSO*7*744 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #630 Status: Released Compliance Date: SEP 14, 2024 ============================================================================= Associated patches: (v)PSO*7*712 <<= must be installed BEFORE `PSO*7*744' (v)PSO*7*725 <<= must be installed BEFORE `PSO*7*744' Subject: ACTIVITY LOG HEADER NODE ISSUES Category: - Routine Description: ============ This patch addresses the following issues: 1. INC28706897 - Missing Activity Log Header Node for old prescriptions causing ATP+4^PSO52API error that occurs for MyHealthVet queries. 2. INC34074305 - Activity Log Header node not updated on a Dosage Edit in Patient Prescription Processing [PSO LM BACKDOOR ORDERS]. 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: -------------------------------------------- Problem ------- 1. INC28706897 - Missing Activity Log Header Node for old prescriptions causing ATP+4^PSO52API error that occurs for MyHealthVet queries. Resolution: ----------- Post Install routine PSO744PI to correct prescriptions with a missing Activity Log Header node. Technical Resolution: --------------------- Post Install routine PSO744PI will identify any prescriptions that are missing the Activity Log Header node and create a correct Activity Log Header node based on the number of Activity Log Entries. In addition, a MailMan message will be sent to the PSNMGR key holders with a list of the prescriptions that were missing the Activity Log Header node and corrected, the number of Activity Log entries, the Expiration Date, and the Cancel Date (if available). In addition, the ATP+4^PSO52API error will be fixed by adding logic to Routine PSO52API to check for the prescriptions missing the Activity Log Header node and correct before proceeding. Routine PSO52API has new logic starting at line AT+2 thru AT+5: ;P744 Check for missing Activity Log Header node and fix I '$D(^PSRX(IEN,"A",0)) D . S COUNT="" S COUNT=$O(^PSRX(IEN,"A","Z"),-1) . S ^PSRX(IEN,"A",0)="^52.3DA^"_COUNT_"^"_COUNT Problem ------- 2. INC34074305 - Activity Log Header node not updated on a Dosage Edit in Patient Prescription Processing [PSO LM BACKDOOR ORDERS]. Resolution: ----------- Routine PSOORED3 in the UDSIG tag was identified as the logic that was updating the Activity Log entries, but NOT updating the Activity Log Header node. Logic will be added to check if the counters in the Activity Log Header node are correct, and additional logic will be added to increment the Activity Log Header node when the Activity Log entries are incremented. Technical Resolution: --------------------- Routine PSOORED3 has new logic starting at line UDSIG+9 thru UDSIG+13: ;P744 Check if header exists, and check if header count matches entries S:'$D(^PSRX(PSORXED("IRXN"),"A",0)) ^PSRX(PSORXED("IRXN"),"A",0)="^52.3DA^" S COUNT="" S COUNT=$O(^PSRX(PSORXED("IRXN"),"A","Z"),-1) I $P(^PSRX(PSORXED("IRXN"),"A",0),"^",3)'=COUNT S ^PSRX(PSORXED("IRXN"),"A",0)="^52.3DA^"_COUNT_"^"_COUNT ; Test Sites: ----------- Palo Altp VAMC, Palo Alto CA Erie VAMC, Erie PA SNOW Change Order #: -------------------- Palo Altp VAMC CO# - CHG0503160 Erie VAMC CO# - CHG0503035 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 loaded with users on the system. You may wish to install it during non-peak hours. Installation will take less than 1 minute. 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*744) 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*744. 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 confirming the checksums have been returned to the pre-patch value using CHECK1^XTSUMBLD. It can also be verified by printing the first 2 lines of the PSO routine(s) contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routine(s) contained in this patch have been backed out, the Second line of each routine will no longer contain the designation of patch PSO*7.0*744. Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSO52API Before: B83887599 After: B85808658 **213,229,252,387,386,566,441, 712,744** Routine Name: PSO744PI Before: n/a After: B16725897 **744** Routine Name: PSOORED3 Before: B75457839 After: B78805374 **46,78,99,117,133,148,249,251, 379,378,372,416,313,444,402, 515,574,441,725,744** Routine list of preceding patches: 712, 725 ============================================================================= User Information: Entered By : Date Entered : NOV 06, 2023 Completed By: Date Completed: AUG 14, 2024 Released By : Date Released : AUG 14, 2024 ============================================================================= Packman Mail Message: ===================== $END TXT