$TXT Created by F at CLN1G1.AAC.DOMAIN.EXT (KIDS) on Thursday, 11/19/20 at 11:16 ============================================================================= Run Date: MAR 12, 2021 Designation: PSJ*5*404 Package : PSJ - INPATIENT MEDICATIONS Priority: Mandatory Version : 5 SEQ #355 Status: Released Compliance Date: APR 12, 2021 ============================================================================= Associated patches: (v)PSJ*5*217 <<= must be installed BEFORE `PSJ*5*404' Subject: PATIENT MERGE BCMA MED LOG UPDATE Category: - Routine Description: ============ This patch will resolve the following issue: INC9104304 - Patient Merge is incorrectly merging BCMA MED LOGS Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1) INC9104304 - Patient Merge is incorrectly merging BCMA MED LOGS Problem: ------- The Dallas Field Office reported that BCMA MEDICATION LOG file (#53.79) does not get updated properly when 2 patients are merged. More specifically, the ORDER REFERENCE NUMBER field (#.11), which contains a pointer to UNIT DOSE (#55.06) and IV (#55.01) sub-files in the PHARMACY PATIENT file (#55) does not get updated with the new pointers when the entries in these two sub-files are moved to a different IEN (Internal Entry Number). In some rare cases, this will cause the BCMA Medication History Reports to hide one of the orders for the newly merged patients if both patients had the orders of the same type (UD/IV) with the same pointer and were administered on the same day. Resolution: ---------- It was confirmed that the patient merge updates did not update the BCMA MEDICATION LOG file (#53.79) entries when the IENs for UD/IV orders in the PHARMACY PATIENT file (#55) were changed. The code was correct to correctly update the BCMA MEDICATION LOG file (#53.79), ORDER REFERENCE NUMBER (#.11) when two patients are merged. Technical Resolution: -------------------- Added a new line tag at the end of the routine PAJPATMR called UPDBML to updated the ORDER REFERENCE NUMBER field (#.11) on the BCMA MEDICATION LOG file (#53.79) file for all administrations right after the new IEN is assigned to UD/IV orders. In addition, the code in UPDBML will kill the old (From) and set the new (To) cross-references "AADT", "AEDT" and "AOIP" because it was determined that the Patient Merge routines did not update them either. Patient Safety Issues (PSIs): ----------------------------- N/A Test Sites: ----------- Erie VAMC, Erie PA Palo Alto VAMC. Palo Alto CA Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Patch Installation: Pre/Post Installation Overview: ------------------------------- It is not necessary to disable any options. Pre-Installation Instructions: ------------------------------ This patch should be installed during non-peak hours to minimize potential disruption to users. This patch should take less than 2 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. 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 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. 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//', 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: ------------------------------- None. 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 (404) in the [PATCH LIST] section. ;;5.0;INPATIENT MEDICATIONS;**[PATCH LIST]**;16 DEC 97;[BUILD #] 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/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 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 PSJ*5.0*404 patch have been rolled back, the first two lines of the Routines will no longer contain the designation of patch PSJ*5.0*404 in the patch list section on line 2. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.0;INPATIENT MEDICATIONS;**[Patch List]**;16 DEC 97;Build 14 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSJPATMR Before: B65386243 After: B67137255 **36,217,404** Routine list of preceding patches: 217 ============================================================================= User Information: Entered By : Date Entered : JUN 19, 2020 Completed By: Date Completed: MAR 11, 2021 Released By : Date Released : MAR 12, 2021 ============================================================================= Packman Mail Message: ===================== $END TXT