$TXT Created by at MNTVBB.DOMAIN.EXT (KIDS) on Tuesday, 09/14/21 at 15:39 ============================================================================= Run Date: FEB 28, 2022 Designation: LR*5.2*552 Package : LR - LAB SERVICE Priority: Mandatory Version : 5.2 SEQ #452 Status: Released Compliance Date: MAR 31, 2022 ============================================================================= Associated patches: (v)LR*5.2*509 <<= must be installed BEFORE `LR*5.2*552' (v)LR*5.2*519 <<= must be installed BEFORE `LR*5.2*552' (v)LR*5.2*526 <<= must be installed BEFORE `LR*5.2*552' Subject: NUMERIC DATA NAME ISSUE, EPIDEMIOLOGY REPORT ERROR, LOAD BUILD ISSUE Category: - Routine Description: ============ This patch addresses the following issues: 1. Non-numeric data entries may be defined as minimum and maximum values as well as number of decimal places for numeric data names. 2. An error might occur during generation of the Epidemiology report if the LAB OOS encounter is edited for the addition of one or more CPT codes. In addition, an issue was discovered during testing of this patch in that the date range searched was not searching data for the last date specified. 3. Accessions which roll over from the previous day to "today" will not build to a Load/Worklist if the HOLD-OVER SORT URGENCY (#300) field in the LABORATORY SITE (#69.9) file is defined as "zero". BLOOD BANK REVIEW: ================== EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*552 does not contain any changes to the VISTA BLOOD BANK Software as defined by Process Asset Library standard titled: BBM Team Review of VistA Patches. EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*552 does not alter or modify any software design safeguards or safety critical elements functions. RISK ANALYSIS: Changes made by patch LR*5.2*552 have no adverse effect on Blood Bank software functionality, therefore RISK is none. VALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes made, no specific validation requirements exist as a result of installation of this patch. Defect Tracking System Ticket(s) & Overview: =========================================== 1. INC19093397: Numeric Data Name Validation Issues Problem: -------- When using the option "Add a new data name" or "Modify an existing data name", non-numeric data entries may be defined as minimum and maximum values as well as number of decimal places for numeric data names. The non-validation of entries for these values can cause downstream errors or validation problems when results are entered for the test. Resolution: ----------- Modify routine LRWU5 to require that only numeric entries may be defined for "Minimum value", "Maximum value", and "Maximum # decimal digits". Allowances are made for minimum and maximum entries which need to be prefixed with "<" or ">". Review of existing numeric data names showed that sites are sometimes using "<" and ">" prefixes in combinations with other configuration options depending on the test. Routine: LRWU5 2. INC19196409: Epidemiology Report Error INC19226359 (d) INC19252317 (d) INC18829444 (d) INC20009428 (d) INC20995319 (d) Problem: ------- An error will occur during generation of the Epidemiology report if the LAB DIV nnn OOS ID nnn encounter is edited to add a CPT code. During testing for this issue, another issue was discovered in that the date range searched does not match exactly the date range input by the user. The ending date search will be one day previous to the ending date specified by the user. Resolution: ---------- Modify routines LREPI and LREPI3 to prevent the software error and also search for the exact date range specified by the user. Routines: LREPI and LREPI3 3. INC19380848: Load List Build Issue Problem: ------- Accessions which roll over from the previous day to "today" will not build to a Load/Worklist if the HOLD-OVER SORT URGENCY (#300) field in the LABORATORY SITE (#69.9) file is defined as "zero". Resolution: ---------- Modify routine LRLL2 to allow for the HOLD-OVER SORT URGENCY (#300) field in the LABORATORY SITE (#69.9) file to be defined as "zero". Routine: LRLL2 Test Sites: ----------- Milwaukee - Clement J. Zablocki Veterans Affairs Medical Center (Milwaukee, WI) Northern Arizona - VA Health Care System (Prescott, AZ) Northern Indiana HCS - (Marion, IN) 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. NOTE: Patch LR*5.2*116 is not listed as a required build because patch installs were not tracked in June 1996 when LR*5.2*116 was released. 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. LR*5.2*552). 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 LR*5.2*552. 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 routines 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 printing the first 2 lines of the routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routines contained in the LR*5.2*552 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. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.2;LAB SERVICE;**[Patch List]**;Sep 27, 1994;Build 2 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: LREPI Before: B66831950 After: B67788128 **132,175,260,281,421,509,552** Routine Name: LREPI3 Before: B50624811 After: B55797078 **132,175,260,281,320,315,421, 442,526,552** Routine Name: LRLL2 Before: B12931187 After: B12955853 **99,116,552** Routine Name: LRWU5 Before: B36481062 After: B50565841 **140,171,177,206,316,519,552** Routine list of preceding patches: 116, 509, 519, 526 ============================================================================= User Information: Entered By : Date Entered : AUG 16, 2021 Completed By: Date Completed: FEB 28, 2022 Released By : Date Released : FEB 28, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT