$TXT Created by at MNTVBB.DOMAIN.EXT (KIDS) on Wednesday, 05/25/22 at 09:30 ============================================================================= Run Date: SEP 15, 2022 Designation: PSJ*5*431 Package : PSJ - INPATIENT MEDICATIONS Priority: Mandatory Version : 5 SEQ #371 Status: Released Compliance Date: OCT 16, 2022 ============================================================================= Associated patches: (v)PSJ*5*404 <<= must be installed BEFORE `PSJ*5*431' Subject: PATIENT MERGE ISSUE WITH PHARMACY PATIENT FILE Category: - Routine Description: ============ This patch addresses the following issue: During patient merge, if the "TO" entry in the PHARMACY PATIENT (#55) file has no prior intravenous (IV) or unit dose (UD) orders, the "zero" node for each will be built without the sub-file number. Defect Tracking System Ticket(s) & Overview: =========================================== INC21462052: Patent Merge Issue with Pharmacy Patient File Problem: -------- During patient merge workflows, if the "TO" entry in the PHARMACY PATIENT (#55) file has no prior intravenous (IV) or unit dose (UD) orders, the "zero" node for each will be built without the sub-file number. The absence of the sub-file number has the potential of causing errors in Pharmacy order verification as well as other VistA applications. Resolution: ----------- 1. Modify routine PSJPATMR at MOVEIV^PSJPATMR and MOVEUD^PSJPATMR to set the sub-file number at the zero nodes for the IV (sub-file 55.01) and unit dose (sub-file 55.06IA) subscripts if the sub-file has not already been set. Examples: IV (sub-file = 55.01): ^PS(55,patient,"IV",0)="^55.01^1^1" Unit Dose (sub-file = 55.06IA): ^PS(55,patient,5,0)="^55.06IA^1^1" 2, Post-install routine PSJ431P is tasked after install of the patch. The routine will scan the IV and Unit Dose "zero" node subscripts and check for missing sub-file entries in the second piece. If a sub-file entry is missing, the second piece is populated with the appropriate sub-file (i.e. 55.01 or 55.06IA). An entry for each instance which had been missing a sub-file entry is kept in ^XTMP("PSJ431 POST" for 60 days after install. A MailMan message is sent to the installer after the post-install task completes. The MailMan message states how many IV and Unit Dose entries in the PHARMACY PATIENT (#55) file had been missing the sub-file number. If any entries were corrected, the MailMan message states that the details can be found in ^XTMP("PSJ431 POST". Example - no corrections were needed: ------------------------------------ Subj: PSJ*5.0*431 Post-Install Findings [#3102702] 04/21/22@18:21 10 lines From: PSJ*5.0*431 Post-Install Routine PSJ431P In 'IN' basket. Page 1 -------------------------------------------------------------------------- The post-install routine for PSJ*5.0*431 has completed. The number of instances in the PHARMACY PATIENT (#55) file which were missing sub-file entries in the second piece of the zero node for Unit Dose (subscript 5) and IV (subscript "IV") are: Unit Dose: None IV: None Enter message action (in IN basket): Ignore// Example - corrections were needed: --------------------------------- Subj: PSJ*5.0*431 Post-Install Findings [#3102701] 04/21/22@18:19 13 lines From: PSJ*5.0*431 Post-Install Routine PSJ431P In 'IN' basket. Page 1 -------------------------------------------------------------------------- The post-install routine for PSJ*5.0*431 has completed. The number of instances in the PHARMACY PATIENT (#55) file which were missing sub-file entries in the second piece of the zero node for Unit Dose (subscript 5) and IV (subscript "IV") are: Unit Dose: 5 IV: 10 The appropriate sub=file entries have been filed if they were missing. Details as to which instances were missing sub-file entries can be found in ^XTMP("PSJ431 POST" for the next 60 days. Enter message action (in IN basket): Ignore// Test Sites: ----------- Miami VA Healthcare System (Miami, FL) Louis A. Johnson VA Medical Center (Clarksburg, WV) 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 name. (ex. PSJ*5.0*431). 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 PSJ*5.0*431. 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/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. The back-out plan is to restore the routine from the backup created. The post-install routine PSJ431P will remain on the system and might be removed by a future patch. If - for some reason - the null entries in the zero nodes of the Unit Dose (subscript 5) and IV (subscript "IV") need to be restored to null, submit a ticket. (However, by doing so, errors could occur when performing various VistA functions on the patient data.) Validation of Back-out Procedure: --------------------------------- The Back-out Procedure can be verified by printing the first two lines of the routine contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. After the routine contained in PSJ*5.0*431 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. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.0;INPATIENT MEDICATIONS;**[Patch List]**;16 DEC 97;Build 5 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSJ431P Before: n/a After: B15364596 **431** Routine Name: PSJPATMR Before: B67137255 After: B69088425 **36,217,404,431** Routine list of preceding patches: 404 ============================================================================= User Information: Entered By : Date Entered : MAR 11, 2022 Completed By: Date Completed: SEP 14, 2022 Released By : Date Released : SEP 15, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT