$TXT Created by at MNTVBB.DOMAIN.EXT (KIDS) on Wednesday, 07/21/21 at 16:57 ============================================================================= Run Date: OCT 07, 2021 Designation: LR*5.2*547 Package : LR - LAB SERVICE Priority: Mandatory Version : 5.2 SEQ #451 Status: Released Compliance Date: NOV 07, 2021 ============================================================================= Associated patches: (v)LR*5.2*536 <<= must be installed BEFORE `LR*5.2*547' Subject: MICROBIOLOGY MESSAGES AND DOCUMENTATION UPDATE Category: - Routine - Informational Description: ============ This patch addresses the following issues: 1. Laboratory users may not be aware that accessing a previously verified accession in the Results entry [LRMIEDZ] option under the Microbiology menu [LRMI] causes the "RPT DATE APPROVED" field to be removed. If the users exit without entering a new "RPT DATE APPROVED", the results are not viewable in the Computerized Patient Record System (CPRS) application. 2. It has been causing confusion for physicians and other users when a Microbiology report previously contained results but is now not displaying any results during the time that the Laboratory is editing the results. 3. The Laboratory Planning and Implementation Guide (PIG) contains a discrepancy from the Data Dictionary for cumulative report definition. Patch Components: ----------------- Blood Bank Team Coordination: EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*547 does not contain any changes to the VISTA BLOOD BANK Software as defined by Process Asset Library standard titled: BBM Team Review of VistA Patches. EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*547 does not alter or modify any software design safeguards or safety critical elements functions. RISK ANALYSIS: Changes made by patch LR*5.2*547 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. Defect Tracking System Ticket(s) & Overview: =========================================== 1. INC18095263: Microbiology Results Entry Warning Message Problem: -------- Patient safety ticket HITPS-6945 was opened for ticket INC10856615 in LR*5.2*536 because results were displaying in CPRS while a tech was in the process of editing the results. The results are not yet verified and should not be viewable in CPRS. However, Laboratory users are now accessing previously released accessions in the Results entry [LRMIEDZ] option under the Microbiology menu [LRMI] to view results. They enter "^" to exit without proceeding through all of the prompts. Providers later call the Laboratory to ask why results are not viewable in CPRS. Resolution: ----------- Modify routine LRMIEDZ2 to display a warning after the "edit" prompt if results were previously verified on the accession. The user is required to answer "YES" acknowledging that the "RPT DATE APPROVED" prompt must be answered before exiting the Microbiology Results Verification option. The message is tied to the "RPT DATE APPROVED" prompt. When the "RPT DATE APPROVED" prompt is missing, either as a new accession or due to previous editing, it won't show the message. But if the "RPT DATE APPROVED" prompt is added back then the message is displayed if the results are edited again. Also, when the message displays, the background audit is set so the last user is noted but the audit is killed out when the "RPT DATE APPROVED" prompt is re-entered. The message is displayed after the "Edit this accession?" prompt. If the accession contains more than one test which may be edited, the message will display after the user selects which test will be edited. Edit this accession? YES// WARNING: Results have previously been verified. If you proceed, a new RPT DATE APPROVED MUST be re-entered, so results are viewable in CPRS. Exiting early will cause results not to be viewable in CPRS. Do you wish to edit the accession and re-enter RPT DATE APPROVED? NO// Routine: LRMIEDZ2 2. INC18346696: Microbiology Report Informational Message Problem: ------- It has been causing confusion for physicians and other users when a report previously contained results but is now not displaying any results during the time that the Laboratory is editing the results. A request was made to display an informational message so that the users will know the accession is currently being edited and will be updated at a later time. Resolution: ---------- Display a message in CPRS and in VistA if a user pulls up a patient report on a Microbiology test that is being edited and which previously contained verified results. The message text is displayed below. ("xxxx" equals the Microbiology area such as Bacteriology, Mycology, etc. "nnnnn" equals the internal entry number (IEN) of the tech in the NEW PERSON (#200) file.) **** ATTENTION **** The xxxx Report is being edited by tech code nnnn and current results may not be visible until approved. Routines: LRMIEDZ2, LR7OSMZ2, LR7OSMZ3, LR7OSMZ4, LRMIPSZ2, LRMIPSZ3, LRMIPSZ4 3. INC18270289: Lab Documentation Discrepancy vs. Data Dictionary Problem: -------- The Laboratory Planning and Implementation Guide (PIG) states that a number between 1 and 999 may be entered when defining the order in which test names are to display in the minor header subgroup on a major header page. However, the data dictionary logic only allows a number between 1 and 50 to be entered. Resolution: ----------- Modify the Laboratory Planning and Implementation Guide (PIG) to state that a number between 1 and 50 may be entered. Test Sites: ----------- Pittsburgh Healthcare System (Pittsburgh, PA) South Texas Health Care System (San Antonio, TX) Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Documentation can be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/. Documentation can also be obtained at https://download.vista.domain.ext/index.html/SOFTWARE. Documentation Title File Name ------------------------------------------------------- Laboratory Version 5.2 Planning lab5_2pi.docx Implementation Guide (PIG) lab5_2pi.pdf 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*547) 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*547. 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 installation and, therefore, no rollback strategy is required. Validation of Back-out Procedure: --------------------------------- The Back-out Procedure can be verified by printing the first 2 lines of the routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routines contained in the LR*5.2*547 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 on line 2. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.2;LAB SERVICE;**[Patch List]**;Sep 27, 1994;Build 10 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: LR7OSMZ2 Before: B47170390 After: B57392979 **121,244,392,350,427,547** Routine Name: LR7OSMZ3 Before: B18295546 After: B22085573 **121,244,547** Routine Name: LR7OSMZ4 Before: B29272550 After: B34387294 **121,244,350,547** Routine Name: LRMIEDZ2 Before: B79846257 After:B100783965 **23,104,242,295,350,427,474, 536,547** Routine Name: LRMIPSZ2 Before: B37459030 After: B44172779 **388,350,427,547** Routine Name: LRMIPSZ3 Before: B29744803 After: B35473707 **350,427,547** Routine Name: LRMIPSZ4 Before: B32976079 After: B38584617 **350,547** Routine list of preceding patches: 536 ============================================================================= User Information: Entered By : Date Entered : MAY 24, 2021 Completed By: Date Completed: OCT 06, 2021 Released By : Date Released : OCT 07, 2021 ============================================================================= Packman Mail Message: ===================== $END TXT