$TXT Created by at MNTVBB.DOMAIN.EXT (KIDS) on Monday, 05/13/24 at 16:01 ============================================================================= Run Date: AUG 07, 2024 Designation: LR*5.2*566 Package : LR - LAB SERVICE Priority: Mandatory Version : 5.2 SEQ #469 Status: Released Compliance Date: SEP 07, 2024 ============================================================================= Associated patches: (v)LR*5.2*541 <<= must be installed BEFORE `LR*5.2*566' (v)LR*5.2*562 <<= must be installed BEFORE `LR*5.2*566' Subject: CPRS STATUS, INCOMPLETE REPORT, AND MERGING ISSUES Category: - Routine Description: ============ This patch addresses three issues: 1. The status in CPRS might be incorrect for one or more tests if accessions were merged. Also, comments regarding the merge are duplicated when viewing the order number in option Order/test status (LROS). 2. The Incomplete test status report (LRWRKINC) might display inaccurate information if the user specified a past date instead of today. 3. An error might occur when accessions are merged for Emergency Room patients. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File Number New/Modified/Deleted --------- ----------- -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A Additional Information: ----------------------- New Service Requests (NSRs): N/A Patient Safety Issues (PSI's) ----------------------------- HITPS-10275 (INC27105514) Defect Tracking System Ticket(s) & Overview: =========================================== 1. INC27105514: CPRS Status Issue after Accession Merge Problem: -------- The status in CPRS might be incorrect for one or more tests if accessions were merged. The issue occurs when all tests are linked to the same order number and at least one test is defined as "Unique Accession = yes". Also, comments regarding the merge are duplicated when viewing the order number in option Order/test status (LROS). Resolution: ----------- Modify routines LR7OMERG and LRTSTOUT to ensure that the LAB ORDER ENTRY (#69) file is set correctly if tests reside on the same specimen number and accessions are merged. 2. INC27753198: Incomplete Test Status Report Issue Problem: -------- If the user specifies a previous date instead of today when generating the Incomplete test status report (LRWRKINC) and if the accession area has "rolled over" to the current date, the information on the report might not be accurate. Resolution: ---------- If the accession area has "rolled over" to "today", modify routine LRWRKINC to: (1) display today's date in the "For Date" field of the report header; and (2) retrieve information from the current date level of the ACCESSION (#68) file. 3. INC27797254: Accession Merge Errors for Emergency Room Patients INC27722517 (d) INC28869171 (d) INC28937078 (d) INC29007698 (d) Problem: ------- When merging is performed on an Emergency Room patient's accessions and one of the accessions contains a profile, an error might occur. The error occurs if the corresponding accession contains an atomic test in common with the profile and if the accession containing the panel is merged to the accession containing the atomic test. Resolution: ---------- Modify routine LR7OMERG to use variable "LRSUBJ" rather than "J" when looping through tests on a panel. The killing of "J" by a downstream routine will then not affect the looping logic in LR7OMERG. Further research is being performed as to whether a change is needed to the downstream routine which kills variable "J". Test Sites: ----------- San Diego HCS - CA St. Cloud VAMC - MN SNOW Change Order #: -------------------- San Diego HCS - CHG0500567 St. Cloud VAMC - CHG0501104 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: 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 LR*5.2*566. 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*566. 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. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.2;LAB SERVICE;**[Patch List]**;Sep 27, 1994;Build 12 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: LR7OMERG Before: B60838866 After: B63788031 **121,221,386,350,445,566** Routine Name: LRTSTOUT Before:B272641325 After:B274198605 **100,121,153,202,221,337,350, 445,527,541,566** Routine Name: LRWRKINC Before:B191858825 After:B209638084 **153,201,221,453,536,543,562,566** Routine list of preceding patches: 541, 562 ============================================================================= User Information: Entered By : Date Entered : JUN 28, 2023 Completed By: Date Completed: AUG 06, 2024 Released By : Date Released : AUG 07, 2024 ============================================================================= Packman Mail Message: ===================== $END TXT