$TXT Created by at MNTVBB.DOMAIN.EXT (KIDS) on Friday, 06/03/22 at 19:10 ============================================================================= Run Date: SEP 02, 2022 Designation: LR*5.2*559 Package : LR - LAB SERVICE Priority: Mandatory Version : 5.2 SEQ #458 Status: Released Compliance Date: OCT 03, 2022 ============================================================================= Subject: INVALID COLLECTION TIME AND MONTHLY STARTING ACCESSION ISSUES Category: - Routine Description: ============ This patch addresses two issues: 1. An invalid "seconds" value for an accession's collection date/time might be stored when using "Accessioning tests ordered by ward order entry" [LROE] option. This has caused problems downstream when transmitting information to Corporate Data Warehouse (CDW). Research of the issue uncovered the fact that when used a certain way, the option will add ten seconds to the collection date/time entered by the user. 2. The "Set a new starting accession number" option on the Supervisor menu [LRSUPERVISOR] option does not set a new starting number for monthly accession areas. Defect Tracking System Ticket(s) & Overview: 1. INC22015599: LROE Invalid Collection Time Problem: -------- An invalid "seconds" value for an accession's collection date/time might be stored when using "Accessioning tests ordered by ward order entry" [LROE] option. This has caused problems downstream when transmitting information to Corporate Data Warehouse (CDW). Research of the issue uncovered the fact that when used a certain way, the option will add ten seconds to the collection date/time entered by the user. Resolution: ----------- Modify routine LROE1 to not add ten seconds to the collection time entered by the user. 2. INC22477819: Monthly Accession Area Execute Code Issue Problem: -------- The "Set a new starting accession number" option on the Supervisor menu [LRSUPERVISOR] option does not set a new starting number for monthly accession areas. Resolution: ----------- Post-install routine LR559PST will correct the execute code for monthly accession areas so that a new starting number may be set, if desired. The post-install routine will also check the ACC CODE (#.051) field in the ACCESSION (#68) file for monthly accession areas. If the entry in that field matches the "standard" incorrect execute code, a correction is made automatically. If the entry does not match the "standard" correct execute code and does not match the "incorrect" execute code, the MailMan message will alert the sites to manually check that accession area. Example of MailMan message: Subj: LR*5.2*559 Post-Install [#240402] 06/03/22@19:08 20 lines From: LR*5.2*559 Post-Install In 'IN' basket. Page 1 -------------------------------------------------------------------------- Entries in the EXECUTE CODE (#62.07) file which were corrected: --------------------------------------------------------------- MONTHLY (IEN: 2) The following entries in the EXECUTE CODE (#62.07) file must be checked manually and evaluated as to whether correction is needed. ------------------------------------------------------------------ MISCMON (IEN: 80) Entries in the ACCESSION (#68) file which were corrected: --------------------------------------------------------- SPEC MISC The ACC CODE (#.051) field in the ACCESSION (#68) file for the following accession areas must be checked manually and evaluated as to whether correction is needed. ---------------------------------------------------------------- TOX Test Sites: ----------- Southern Nevada Healthcare System (Las Vegas, NV) Northport Healthcare System (Northport, NY) 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: NOTE: LR*5.2*121 would normally be listed as a required build. LR*5.2*121 was released in 1997, and it is possible that some site environments might not have the background file indicating that LR*5.2*121 was installed. In all likelihood LR*5.2*121 has been installed at all sites. 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*559). 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*559. 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 LROE1 from the backup created. There should not be a need to restore the previous settings of the execute code which were changed in the EXECUTE CODE (#62.07) file or the ACCESSION (#68) file since the logic was previously erroneous. If the MailMan message, which was generated by the post-install routine, cannot be located the text of the MailMan message is stored for sixty days after install in ^XTMP("LR 559 MAILMAN MESSAGE". Validation of Back-out Procedure: --------------------------------- The Back-out Procedure can be verified by printing the first two lines of the routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. After the routines contained in the LR*5.2*559 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 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: LR559PST Before: n/a After: B27515950 **559** Routine Name: LROE1 Before: B11513035 After: B11043005 **100,121,559** Routine list of preceding patches: 121 ============================================================================= User Information: Entered By : Date Entered : MAY 16, 2022 Completed By: Date Completed: SEP 01, 2022 Released By : Date Released : SEP 02, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT