$TXT Created by MNTVBB.DOMAIN.EXT (KIDS) on Thursday, 05/27/21 at 12:41 ============================================================================= Run Date: SEP 15, 2021 Designation: LR*5.2*549 Package : LR - LAB SERVICE Priority: Mandatory Version : 5.2 SEQ #449 Status: Released Compliance Date: OCT 16, 2021 ============================================================================= Associated patches: (v)LR*5.2*543 <<= must be installed BEFORE `LR*5.2*549' Subject: MISSING ORGANISM DATA Category: - Routine Description: ============ This patch addresses the following issue: Frequent M Errors at multiple sites: LST^LR7OSMZ2 BLOOD BANK REVIEW: ================== EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*549 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*549 does not alter or modify any software design safeguards or safety critical elements functions. RISK ANALYSIS: Changes made by patch LR*5.2*549 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. Associated ticket(s): ===================== INC17480746 Frequent M Errors at multiple sites: LST^LR7OSMZ2 Associated NSR(s): ================== N/A Defect Tracking System Ticket(s) & Overview: =========================================== INC17480746 Frequent M Errors at multiple sites: LST^LR7OSMZ2 Problem: ------- We are seeing errors in LST^LR7OSMZ2 at multiple sites due to Corrupted Organism nodes in the MI section of the ^LR global. Two errors are recurring and preventing microbiology reports from being generated: - If the zero node is missing in this sub-file, an undefined error occurs in LST+3. - If the organism pointer to file #61.2 is null in the first piece of the zero node, a subscript error occurs at the end of LST+4 Resolution: ---------- For sites to be able to find and report Corrupted Organism nodes to their regional support group, an update to the nightly LAB Cleanup routine is implemented. This update will search for Corrupted Organism nodes and send a mailman message to the LMI mailman group. The mailman message will continue to be delivered daily until the corrupted entry(s) in the LAB DATA file (#63) have been corrected. Please enter a YourIT ticket including the mailman message and requesting the ticket be routed to the group PLM.HEALTH.ClinicalAncillary.Sub_4. The report will display the zero node of the MI section that contains corrupt data. The Mailman message will look like this: Subj: CORRUPT ORGANISM DATA REPORT From: ORGANISM NIGHTLY TASK REVIEW In 'IN' basket. Page 1 --------------------------------------------------------------- The following entries in the LAB DATA file (#63) have corrupted Organism nodes and require repair. Please enter a YourIT ticket requesting regional support for the Laboratory package. --------------------------------------------------------------- ^LR(483671,"MI",6899495.8645,0)=3100503.1355^^3100505.1607^ 520719394^71^MICRO 10 707^520692211^WAFB^^3100504.132659^62^^ 223;SC(^442 ^LR(485726,"MI",6889782.8472,0)=3110216.1528^^3110218.1228^442 ^71^MICRO 11 357^520643364^ER^^3110216.193401^62^^325;SC(^442 Enter message action (in IN basket): Ignore// The new code will run nightly with LAB Nightly Cleanup routine and if there is no corrupt data located the site will not get a mailman message. Test Sites: ========== Columbia VA Health Care System VA Maryland HCS 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 loaded with users on the system. You may wish to install it during non-peak hours. Installation will take less than 1 minute. ** NOTE ** For site to receive the report in the TEST account and Production account the following must be checked: 1) Be sure the option LRTASK NIGHTY is scheduled. 2) Be sure the Laboratory Information Manager (LIM) is a member of the mail group G.LMI 3) The LIM must log into the test account the day after the installation to check for the mailman message with the list of corrupted file #63 entries. 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 LR*5.2*549 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*549 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 Post Installation Instructions: =============================== N/A Back-out/Rollback Strategy: ========================== In the event of a catastrophic failure, the Facility CIO may make the decision to back-out the patch. It is imperative that you have performed a backup of the routine included in this patch prior to installation. The back-out plan is to restore the routine from the backup created. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.2;LAB SERVICE;**[Patch List]**;Sep 27, 1994;Build 1 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: LRWU9A Before: B24519313 After: B38755960 **519,543,549** Routine list of preceding patches: 543 ============================================================================= User Information: Entered By : Date Entered : MAY 27, 2021 Completed By: Date Completed: SEP 14, 2021 Released By : Date Released : SEP 15, 2021 ============================================================================= Packman Mail Message: ===================== $END TXT