$TXT Created by at MNTVBB.DOMAIN.EXT (KIDS) on Monday, 01/30/23 at 13:42 ============================================================================= Run Date: MAY 22, 2023 Designation: LR*5.2*562 Package : LR - LAB SERVICE Priority: Mandatory Version : 5.2 SEQ #462 Status: Released Compliance Date: JUN 22, 2023 ============================================================================= Associated patches: (v)LR*5.2*543 <<= must be installed BEFORE `LR*5.2*562' Subject: LEDI PANELS INCOMPLETE TEST STATUS REPORT ISSUE Category: - Routine Description: ============ This patch addresses one issue: A test might not display a status of "Results received" at a Laboratory Electronic Data Interchange (LEDI) collecting site after results have been received. Defect Tracking System Ticket(s) & Overview: =========================================== NOTE 1: This ticket is also addressed under companion patch LA*5.2*101. NOTE 2: LA*5.2*103 will address this issue for non-VistA LEDI interfaces, such as Quest. INC22082550: LEDI Results Available Status Issue Problem: -------- LEDI collecting site Laboratory workflow might include relying on the Incomplete Test Status Report (LRWRKINC) to determine when results have been received from a LEDI host site and are ready for review. Several sites utilizing this workflow have discovered that there are times when results have been received, but the ordered test status on the Incomplete Test Status Report remains at "Test shipped" instead of updating to "Results received". Patch LR*5.2*101 corrects the issue so that the status for a test is "Results received" if results have been received. However, in the case of a profile, results might have been received for some component tests on the profile but not all test components. The status for the remaining test components then might display on the report as "In lab" instead of "Test shipped". This could cause confusion in Lab workflow since the test was already shipped and does not need to be built to a shipping manifest. (The incorrect status will only display if the profile is defined in Laboratory files to transmit the order as a profile instead of being broken out into individual test components.) Resolution: ----------- Modify routine LRWRKINC to correctly evaluate the status of a LEDI test on the Incomplete test status report. Test Sites: ---------- Columbia VA Health Care System(Columbia,SC) Augusta VAMC (Augusta, GA) San Diego VAMC (San Diego, CA) VA Long Beach Heathcare System (Long Beach, CA) SNOW Change Order # ------------------- CHG0346602 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. NOTE: LA*5.2*101 is a companion patch to LR*5.2*562. The two patches should be installed together but one is not dependent on the other. The patches may be installed in any order. 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. LR*5.2*562). 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*562. 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. 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 routines contained in the patch has 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 5 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: LRWRKINC Before:B116812246 After:B191858825 **153,201,221,453,536,543,562** Routine list of preceding patches: 543 ============================================================================= User Information: Entered By : Date Entered : SEP 08, 2022 Completed By: Date Completed: MAY 18, 2023 Released By : Date Released : MAY 22, 2023 ============================================================================= Packman Mail Message: ===================== $END TXT