============================================================================= Run Date: JUN 23, 2020 Designation: PSB*3*125 Package : PSB - BAR CODE MED ADMIN Priority: Mandatory Version : 3 SEQ #104 Status: Released Compliance Date: JUL 24, 2020 ============================================================================= Associated patches: (v)PSB*3*87 <<= must be installed BEFORE `PSB*3*125' (v)PSB*3*122 <<= must be installed BEFORE `PSB*3*125' Subject: BCBU MAR REPORTS EXPIRED MEDS AND USER INIT ISSUES Category: - Routine Description: ============ This patch will resolve the following issues: 1) INC8817299 - BCBU MAR Shows Expired Meds as Requiring Administration 2) INC9226190 - BCMA Contingency program requires verify code be changed each time you log into the program INC9209704(d) - Modify MIW BCMA BU devices to prevent users from needing to create a secondary Verify Code Patient Safety Issues (PSIs): ----------------------------- HITPS-6987 - INC8817299 Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1) INC8817299 -BCBU MAR Shows Expired Meds as Requiring Administration Problem: -------- BCBU MAR reports were showing medications on the grid as needing administration on their Stop date/time, when the time value ends in a zero, e.g. 0900 & 0930. Solution: -------- Correct BCBU routine ALPBFRM1 to put asterisks in that time cell on the MAR Grid. Technical Resolution: --------------------- In routine ALPBFRM1, "+" the variable, when it is created after it concatenates the time to the end of the date. This will trim off insignificant trailing zeros, prior to later compare operations checking if the grid cell date.time is = to the stop date.time of this order. 2) INC9226190 - BCMA Contingency program requires verify code be changed each time you log into the program Problem: -------- VA Western New York Healthcare System at Buffalo reported that after patch PSB*3*122 was installed the Initialize a Backup Workstation with BCMA Users [PSB BCBU USER INIT] option which is used to send BCMA users over from VistA to the BCBU workstation was forcing the users to change their VERIFY CODE at the BCBU workstations when they tried to logon. It was confirmed that the issue was introduced by PSB*3*122. In order to fix the problem that required the option above to be run twice in order for the new users ACCESS/VERIFY CODEs to work the re-indexing of the new records on the NEW PERSON file (#200) was moved past the "hard setting" of ACCESS/VERIFY CODEs, which resolved the original but the re-indexing also treats the ACCESS CODE as new and therefore forces a new VERIFY CODE to be entered by the user at the BCBU workstation. Solution: -------- Kept the "hard setting" of the ACCESS CODE prior to re-indexing the new record in the NEW PERSON file (#200) but moved the "hard setting" of the VERIFY CODE information after the re-indexing which addresses the issue. Technical Resolution: --------------------- Moved the call "D IX1^DIK" up to FILE+20, before setting the VERIFY CODE information. Test Sites: ----------- Hines VAMC Pacific Islands Health Care System Patch retrieval Instructions: ---------------------------- The software for this patch is being released using a host file. The host file is available at the following location: /srv/vista/patches/SOFTWARE/ PSB_3_125.KID. Patch Installation: ------------------- Pre-Installation Overview: This patch required Fileman v22.2 to be installed before this patch can be installed. Therefore, it is important that the BCBU workstations where the this patch will be installed already have been updated with the latest version of Fileman (v22.2). The BAR CODE MED ADMIN (BCMA) users should not be using the application while this patch is being installed. It should take less than 2 minutes to install this patch. Installation Instructions: 1. Use the Load a Distribution option contained on the Kernel Installation and Distribution System Menu to load the Host file. When prompted to "Enter a Host File:" enter vista/patches/SOFTWARE/ PSB_3_125.KID. 2. From the Kernel Installation & Distribution System menu, select the Installation menu. From this menu, you may select to use the following options: When prompted for INSTALL NAME, enter the patch # PSB*3.0*125: a. Verify Checksums in Transport Global - This option will allow you to ensure the integrity of the routines that are in the transport global. b. Backup a Transport Global - This option will create a backup message of any routines exported with this patch. It will not backup any other changes such as DD's or templates. c. 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 components of this patch routines, DDs, templates, etc. d. From the Installation menu, 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 Overview: 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 in the [PATCH LIST] section. 3.0;BAR CODE MED ADMIN;**[PATCH LIST]**;MARCH, 2004 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 Procedures ------------------- 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. Validation of Roll Back Procedure --------------------------------- The Roll Back Procedure can be verified by printing the first 2 lines of the ALPB Routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routines contained in the PSB*3.0*125 patch have been rolled back, the first two lines of the Routines will no longer contain the designation of patch PSB*3.0*125 in the patch list section on line 2. Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;BAR CODE MED ADMIN;**[Patch List]**;Mar 2004;Build 9 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: ALPBFRM1 Before: B93953970 After: B95230274 **8,48,69,59,73,87,125** Routine Name: ALPBGEN1 Before: B23953842 After: B25368227 **8,37,102,122,125** Routine list of preceding patches: 87, 122 ============================================================================= User Information: Entered By : Date Entered : JAN 14, 2020 Completed By: Date Completed: JUN 18, 2020 Released By : Date Released : JUN 23, 2020 ============================================================================= Packman Mail Message: ===================== No routines included