$TXT Created by SCOTT at MNTVBB.DOMAIN.EXT (KIDS) on Tuesday, 09/17/24 at 08:37 ============================================================================= Run Date: OCT 21, 2024 Designation: LR*5.2*573 Package : LR - LAB SERVICE Priority: Mandatory Version : 5.2 SEQ #472 Status: Released Compliance Date: NOV 21, 2024 ============================================================================= Associated patches: (v)LR*5.2*444 <<= must be installed BEFORE `LR*5.2*573' (v)LR*5.2*491 <<= must be installed BEFORE `LR*5.2*573' (v)LR*5.2*541 <<= must be installed BEFORE `LR*5.2*573' Subject: TEST COLLECTED BUT NOT ACCESSIONED Category: - Routine Description: ============ The patch addresses the following issue: In certain situations, tests that are showing as collected do not have an accession number. This happens when the user that accessions the test is logged into a division that is not defined in the LABORATORY TEST (#60) file for that test with a value in the ACCESSION AREA (#6) field. When the user uses the option, Accessioning tests ordered by ward order entry [LROE], there is a message that displays but it is easily missed by the user. This causes lab tests to be presumed accessioned by the provider when the lab does not know that the order still needs to be collected and processed. When the order is accessioned by Howdy, no error message is displayed on the screen and there is no way for the lab to know the order was needed. 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: ----------------------- N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): HITPS-11178 Associated NSR(s): ------------------ N/A Defect Tracking System Ticket(s) & Overview: 1. INC31078784 - TEST COLLECTED BUT NOT ACCESSIONED Problem: -------- In certain situations, tests that are showing as collected do not have an accession number. This happens when the user that accessions the test is logged into a division that is not defined in the LABORATORY TEST (#60) file for that test with a value in the ACCESSION AREA (#6) field. When the user uses the option, Accessioning tests ordered by ward order entry [LROE], there is a message that displays but it is easily missed by the user. This causes lab tests to be presumed accessioned by the provider when the lab does not know that the order still needs to be collected and processed. When the order is accessioned by Howdy, no error message is displayed on the screen and there is no way for the lab to know the order was needed. Resolution: ----------- The reporting sites prefer that the order not be accessioned when the ACCESSION AREA (#6) field conflict occurs. The following accessioning and HOWDY accessioning routines are modified to check for an accession area conflict, suspend accessioning for the order, and display an appropriate message to the user. Routine(s): LROE, LROE2, LRHYB Test Sites: ----------- Illiana HCS (Danville, IL) Marion HCS (Marion, IL) Test Sites -SNOW Change Order #: Danville - CHG0530399 Marion - CHG0527280 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Patch Installation: ------------------- Pre/Post Installation Overview: 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. It is not necessary to disable any options/protocols. Pre-Installation Instructions: N/A 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. LR*5.2*573) 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*573 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: Routines 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 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. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer NO. ii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? 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 Plan: ----------------------- Back-out will be done only with the concurrence and participation of the development team and appropriate VA site/region personnel. The decision to back-out or rollback software will be a joint decision between the 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. If the patch was backed up for the build, from the Kernel Installation and Distribution System Menu, select the Installation Menu. Then select the Install Package(s) option and choose the patch (LR*5.2*573b) to install. 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. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.2;LAB SERVICE;**[Patch List]**;Sep 27, 1994;Build 7 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: LRHYB Before: B41457137 After: B43864765 **405,417,446,457,467,491,573** Routine Name: LROE Before: B43781388 After: B44894662 **100,121,201,221,263,286,360, 423,432,438,450,479,541,573** Routine Name: LROE2 Before: B10836155 After: B14288613 **121,424,444,573** Routine list of preceding patches: 444, 491, 541 ============================================================================= User Information: Entered By : Date Entered : APR 18, 2024 Completed By: Date Completed: OCT 21, 2024 Released By : Date Released : OCT 21, 2024 ============================================================================= Packman Mail Message: ===================== $END TXT