$TXT Created by at CLN1G1.AAC.DOMAIN.EXT (KIDS) on Sunday, 07/19/20 at 22:04 ============================================================================= Run Date: MAR 02, 2021 Designation: PSO*7*616 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #520 Status: Released Compliance Date: APR 02, 2021 ============================================================================= Associated patches: (v)PSO*7*372 <<= must be installed BEFORE `PSO*7*616' Subject: MISSING LABEL HEADER NODE, HARD ERROR LBP+4~PSO52API Category: - Routine Description: ============ This patch addresses an issue that happens at sites which perform technician entry of non-verified prescriptions. The issue is that prescription label multiple in PRESCRIPTION (#52) file may be created without a header node. This manifests in CPRS as a hard error "LBP+4^PSO52API" when displaying the Medication Reconciliation component from the "Essential Med List for Review" Health Summary. Otherwise, there is no adverse impact or error to users within the Outpatient Pharmacy package. This patch fixes the root cause of the missing header node, performs a post install repair of missing nodes, and sends a notification email to holders of the PSNMGR key. Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC10913375 - file 52 Label multiple created with a missing header node. Duplicate(s) INC12012970 - LBP+4^PSO52API error on Health Summary Med Reconcilation. INC11806029 - LBP+4^PSO52API when using TIU Template INC13101564 - LBP+4^PSO52AP Error CPRS keeps closing on her when she trys to enter a note Problem 1: ---------- When a PSO TECH ADV user enters a non-verified Rx which causes a Critical drug-drug interaction or Dosage warning and then prints a Tech warning label, at that point the PRESCRIPTION (#52) file Label multiple will be created with a missing header node. Resolution 1: ------------- Modify code to create the appropriate header node in the Label multiple. A Mailman report of all updates to any Label multiple(s) found will be sent to anyone with the PSNMGR key (see example below). Mailman report example: -------------------------------------------------------------------------- Subj: PSO*7*616 - Autocorrection Utility [#153825] 07/17/20@12:52 From: POSTMASTER In 'IN' basket. Page 1 -------------------------------------------------------------------------- This report documents missing file #52 [PRESCRIPTION] Label multiple header records. Any instance of a Label multiple that has been created without the appropriate Label multiple header record will automatically be corrected to have the appropriate Label multiple header record. ========================================================================== Prescription# File #52 IEN ------------- ------------ 258918A 357732 258920A 357733 2298991 2211516 Technical Resolution 1: ----------------------- Change routine PSOLLL8 adding additional code to create the appropriate Label multiple header record. In addition, the Post-install routine PSO616PI will process through PRESCRIPTION (#52) file if a Label multiple is found without the appropriate Label multiple header record, the appropriate header record will be created. Test Sites: ----------- Cheyenne VA Medical Center, (Cheyenne, WY) James H. Quillen VA Medical Center (Mountain Home, TN) Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Patch Installation: ------------------- Note to Installer: The post-install routine runs interactively, so there will be a 15-30 minute hang during installation, depending on the number of Prescription records to process. Pre/Post Installation Overview: ------------------------------- It is not necessary to disable any options. 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 30 minutes to install, including the post-install routine processing. 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*616) B. Select the Backup a Transport Global option to create a backup message of any routines exported with this patch. It will not backup any other changes such as DDs or templates. 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. When Prompted "Want KIDS to INHIBIT LOGONs during the install? NO//", respond NO. ii. When Prompted "Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//", respond NO. iii. If prompted 'Delay Install (Minutes): (0-60): 0//', respond 0. Post Installation Instructions: ------------------------------- The post-installation report should be reviewed to account for any PRESCRIPTION (#52) file entries that were missing the Label multiple header node. The post-installation routine PSO616PI is not automatically deleted as part of the patch installation process. You may delete the routine after installation if you require, using the following command from the programmer prompt: >D ^%RDELETE Delete routines/INCLUDE files. WARNING: When .MAC.0 is deleted, the latest backup is moved to .MAC.0, UNCOMPILED. Routine(s): PSO616PI Routine(s): Output on Device: Right margin: 80 => PSO616PI.INT Okay to continue? Yes => Yes 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 in the [PATCH LIST] section. ;;7.0;INPATIENT MEDICATIONS;**[PATCH LIST]**;[DATE];[BUILD NUMBER] 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/Roll Back Plan: ------------------------ Back-out will be done only with the concurrence and participation of the development team and appropriate VA site/region personnel. The decision to back-out or rollback software will be a joint decision between the 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. 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 First Line Routine Print [XU FIRST LINE PRINT] option. Once the routines contained in the PSO*7.0*616 patch have been backed out, the first two lines of the routines 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 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSO616PI Before: n/a After: B5621538 **616** Routine Name: PSOLLL8 Before: B28829603 After: B29343647 **120,251,387,367,372,616** Routine list of preceding patches: 372 ============================================================================= User Information: Entered By : Date Entered : JUN 26, 2020 Completed By: Date Completed: MAR 02, 2021 Released By : Date Released : MAR 02, 2021 ============================================================================= Packman Mail Message: ===================== $END TXT