$TXT Created by at MNTVBB.DOMAIN.EXT (KIDS) on Tuesday, 08/11/20 at 16:32 ============================================================================= Run Date: SEP 22, 2020 Designation: LR*5.2*527 Package : LR - LAB SERVICE Priority: Mandatory Version : 5.2 SEQ #439 Status: Released Compliance Date: OCT 23, 2020 ============================================================================= Associated patches: (v)LR*5.2*439 <<= must be installed BEFORE `LR*5.2*527' (v)LR*5.2*445 <<= must be installed BEFORE `LR*5.2*527' (v)LR*5.2*505 <<= must be installed BEFORE `LR*5.2*527' (v)LR*5.2*523 <<= must be installed BEFORE `LR*5.2*527' (v)LR*5.2*524 <<= must be installed BEFORE `LR*5.2*527' Subject: DELETED TESTS, DELETION COMMENTS, FILE FRAGMENTS, AND NIGHTLY WORKLOAD REPORT Category: - Routine Description: ============ This patch addresses four (4) issues: 1. The CPRS status of an order might not be correct when panel components are deleted using an option in the VistA Laboratory Accessioning menu. 2. Order status and comments entered when deleting orders are not displaying on some CPRS Labs tab reports as expected. 3. The "NIGHTLY WKLD CODE CHECK REPORT" contains orders which have been purged from the VistA environment. 4. A VistA software error might occur during background processing involving the LABORATORY TEST (#60) file due to an incompletely filed test. Additional Information: ---------------------- Blood Bank Team Coordination: ---------------------------- EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*527 does not contain any changes to the VISTA BLOOD BANK Software as defined by ProPath standard titled: BBM Team Review of VistA Patches. EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*527 does not alter or modify any software design safeguards or safety critical elements functions. RISK ANALYSIS: Changes made by patch LR*5.2*527 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. Patient Safety Issues (PSIs): ---------------------------- HITPS-6739 (INC6227021) Defect Tracking System Ticket(s) & Overview: ============================================ 1. INC6130120: CPRS Status Issues for Deleted Tests Problem: ------- When panel components are deleted using an option in the VistA Laboratory Accessioning menu, the status displayed in CPRS might not be an accurate reflection of the order's status. During the testing process for this patch, it was noticed that two options were not placed "out of order" several years ago. The options "Delete test from an accession (LRTSTJAM)" and "Remove an accession (LRDELOG)" had been deemed years ago as no longer to be used. However, the options were not updated with an Out of Order message. In addition, the option "Remove an accession (LRDELOG)" should be deleted from the "Accessioning menu (LR IN)" as a choice. Resolution: ---------- Modify routines LRTSTOUT and LRCENDEL to ensure that the order status displayed in CPRS is accurate after tests are deleted from an order. A documentation update to the "Laboratory User Manual Version 5.2" is also included for this ticket to clarify the use of cancel reasons which may require an electronic signature. If a panel component is specified as the test being deleted, one or more results have been verified on the order. Otherwise, it would not be possible to specify a panel component. In this case, an electronic signature will not be required for cancel reasons which normally require an electronic signature since the entire ordered test is not being canceled. A post-install routine (LR527PST) for this patch placed an Out of Order message of "Out of Service per patch LR*5.2*527" into the OUT OF ORDER MESSAGE (#2) field of the OPTION (#19) file for options "Delete test from an accession (LRTSTJAM)" and "Remove an accession (LRDELOG)". The post-install routine also deletes the option from the "Accessioning menu (LR IN)". The "Laboratory Technical Manual Version 5.2" has been updated to document that the "Remove an accession (LRDELOG)" option is no longer available under the "Accessioning menu (LR IN)" as a choice. Routines: LRTSTOUT, LRCENDEL, LR527PST 2. INC6227021: Order Status and Canceled Order Comments Not Displaying Problem: ------- If all tests on an order are canceled using an option in the VistA Laboratory Accessioning menu, the order status and "not performed" comments do not display on some CPRS Labs tab reports as expected. Resolution: ---------- Modify routines LR7OGMC and LR7OGMU to display "not performed" statuses and comments on the CPRS Labs Tab reports: (1) Most Recent; (2) All Tests By Date; and (3) Selected Tests by Date. A documentation update to the "CPRS User Guide: GUI Version" is included in the informational patch OR*3.0*517. The documentation update clarifies the expected content of various reports on the CPRS Labs tab. Routines: LR7OGMC, LR7OGMU 3. INC8323095: NIGHTLY WKLD CODE CHECK REPORT Contains Purged Orders Problem: ------- The "NIGHTLY WKLD CODE CHECK REPORT" might contain Lab order numbers for orders which were purged from the VistA environment. Resolution: ---------- Modify routine LRCAPPH3 to not include an order number on the report if the related order information no longer exists in the LAB ORDER ENTRY (#69) file. Research into the Lab purge process uncovered the fact that the "AA" subscript of the LAB ORDER ENTRY (#69) file is not killed when entries are purged. It was decided that this patch will not include a change to the Lab purge routines because: (1) the orphan ^LRO(69,"AA" entries cause no harm; and (2) it will be extremely difficult to recruit field test sites to test a purge modification. Routine: LRCAPPH3 4. INC8795122: Incompletely Filed Test Causing Software Error Problem: ------- When adding or editing tests in the LABORATORY TEST (#60) file, occasionally a situation happens that causes file fragments or an incomplete filing of the test. These fragments will cause downstream software errors. The error for this ticket occurs during generation of a MailMan message informing Laboratory personnel of the existence of an incompletely filed test. In this case, information concerning the user who filed the test was missing. The missing user information causes a subscript error. Resolution: ---------- Modify routine LRCAPPH3 to display "UNKNOWN" in the MailMan message if information is missing concerning the user who filed the test. Routine: LRCAPPH3 Test Sites: ---------- VA San Diego HCS (San Diego, CA) VA Upstate New York HCS (Albany, NY) Documentation Retrieval Instructions ------------------------------------ The software for this patch is being released in a PackMan message. Documentation describing the new functionality is included in this release. Documentation can be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/ Documentation Title File Name -------------------------------------------------------------------------- Laboratory User Manual Version 5.2 lab5_2um.pdf Laboratory Technical Manual Version 5.2 lab5_2tm.pdf Binary Patch Installation: ------------------ Pre/Post Installation Overview: The post install routine LR527PST will be deleted automatically after this patch is installed. 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. Menu options do not need to be disabled. 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 or build name. (ex. or XXXXX BUILD X.X) 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 of any routines exported with this patch. It will not backup any other changes such as DDs or templates. 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. a. When prompted 'Enter options you wish to mark as 'Out Of Order':', press the Enter key. b. When prompted 'Enter protocols you wish to mark as 'Out Of Order':', press the Enter key. c. When prompted 'Delay Install (Minutes): (0 - 60): 0//', answer 0. Post-Installation Instructions: The post-install routine LR527PST automatically places an Out of Order message of "Out of Service per patch LR*5.2*527" into the OUT OF ORDER MESSAGE (#2) field of the OPTION (#19) file for options "Delete test from an accession (LRTSTJAM)" and "Remove an accession (LRDELOG)". The post-install routine also deletes the option from the "Accessioning menu (LR IN)". Back-out/Rollback Plan: ---------------------- 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 routines included in this patch prior to installation. 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. To verify the back-out completed successfully, ensure the checksum matches the pre-patch checksum from the patch description. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.2;LAB SERVICE;**[Patch List]**;Sep 27, 1994;Build 16 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: LR527PST Before: n/a After: B1006949 **527** Routine Name: LR7OGMC Before: B38181513 After: B62087900 **187,230,312,286,356,372,395, 350,516,523,527** Routine Name: LR7OGMU Before: B6947212 After: B10422283 **187,312,395,350,527** Routine Name: LRCAPPH3 Before: B57510272 After: B61357733 **263,291,505,527** Routine Name: LRCENDEL Before: B64874476 After: B78276656 **100,121,202,221,263,350,439,527** Routine Name: LRTSTOUT Before:B176003856 After:B272926833 **100,121,153,202,221,337,350, 445,527** Routine list of preceding patches: 439, 445, 505, 523 ============================================================================= User Information: Entered By : Date Entered : JUL 15, 2019 Completed By: Date Completed: SEP 18, 2020 Released By : Date Released : SEP 22, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT