$TXT Created by MNTVBB.DOMAIN.EXT (KIDS) on Wednesday, 03/06/24 at 14:44 ============================================================================= Run Date: APR 23, 2024 Designation: LA*5.2*104 Package : LA - AUTOMATED LAB INSTRUMENTS Priority: Mandatory Version : 5.2 SEQ #76 Status: Released Compliance Date: MAY 24, 2024 ============================================================================= Associated patches: (v)LA*5.2*67 <<= must be installed BEFORE `LA*5.2*104' Subject: POINT OF CARE REPORTING FACILITY ISSUE Category: - Routine - Other Description: ============ For sites that display REPORTING LABORATORY on Lab reports, this patch along with LR*5.2*568 addresses the following issues: VistA Laboratory (POC) Point of Care interface logic might incorrectly determine the reporting facility for POC results. 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 ----------- ---- -------------------- LA7 POC SETUP run routine Modified 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 -------------- -------------------- LR POC REPORTING LAB New Additional Information: ----------------------- New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: =========================================== *************************************************** * LR*5.2*568 must be installed after LA*5.2*104. * *************************************************** 1. INC28461544: Point of Care Reporting Facility Issue INC28508430 (d) INC30186028 (d) Problem: -------- Reporting Lab facility displaying incorrectly on Point of Care Lab results. The Pathology and Laboratory Medicine Program office provided clarification on the Reporting Lab facility designation for test results. In summary: The REPORTING laboratory is the lab responsible for how the report displays in CPRS. This display is a function of the middleware which is generally controlled by the parent site. The site responsible for maintaining the middleware and CPRS display should be listed as the REPORTING laboratory. The PERFORMING laboratory is where the testing is being performed. Each PERFORMING laboratory should have their own CLIA number. VistA Laboratory POC (Point of Care) interface logic determines reporting facility by the ordering location's INSTITUTION (#4) field in the HOSPITAL LOCATION (#44) file. If the Institution field does not have an entry, the first entry defined in the ASSOCIATED DIVISION (#.091) field of the ACCESSION (#68) file is selected as the reporting facility. (Multiple associated divisions may be defined for an accession area. The facility defined at the lowest IEN (Internal Entry Number) is selected as a default reporting facility.) The facility selected as the reporting facility could be a CBOC (Community Based Outpatient Clinic) location instead of the VAMC or other parent site and fall outside of the Pathology and Laboratory Medicine Program Office clarification. Laboratories are concerned about being cited during JCAHO (Joint Commission on Accreditation of Health Care Organizations) inspections. Inspectors look at this information on patient reports. Resolution: ----------- If the reporting lab being displayed is not the correct facility, the parameter LR POC REPORTING LAB may be defined using 'Define Reporting Lab' under option 'Lab Point of Care Setup' [LA7 POC SETUP]. The option and parameter are included in LA*5.2*104. Routines LRVRPOC and LRVRPOCU (which are included in LR*5.2*568) will determine whether the parameter has been defined at the system or division level when storing a reporting lab designation for Point of Care (POC) results. 2. INC31763570 - Add Display POC Reporting Facility Value Settings option Problem ------- The application coordinator submitted ticket INC31763570 requesting that a menu item, Add Display POC Reporting Facility Value Settings, be added to the Lab Point of Care Setup menu. This option is being added with this patch for easy access to view the already entered POC Reporting Facility Value settings. Resolution ---------- Add Display POC Reporting Facility Value Settings option to the Lab Point of Care Setup menu. Test Sites: ----------- Columbia VA Health Care System (Columbia,SC) Memphis VAMC (Memphis,TN) Test Sites - SNOW Change Order #: -------------------------------- Columbia VA Health Care System: CHG0468522 Memphis VAMC: CHG0468270 Software and 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 can also be obtained at https://download.vista.domain.ext/index.html/SOFTWARE. Documentation Title File Name --------------------------------------------------------------------- Laboratory: POC Interface Installation LAB_POC_IUG.PDF and User Guide 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. *************************************************** * LR*5.2*568 must be installed after LA*5.2*104. * *************************************************** 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. LA*5.2*104). 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 LA*5.2*104. iii. When prompted for the following, enter "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/Rollback Strategy: =========================== Post-Installation Instructions: ------------------------------- Installation Verification: -------------------------- Successful installation can be verified by reviewing the first 2 lines of the routines contained in the patch. The second line will contain the patch number (104) in the [PATCH LIST] section. ;;5.2;AUTOMATED LAB INSTRUMENTS;**[Patch List]**;Sep 27, 1994;Build 4 The option Calculate and Show Checksum Values [XTSUMBLD-CHECK] can be run to compare the routine checksums to what is documented in the patch description. 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 build 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 build 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 build onto the VistA System. The back-out plan is to restore the build from the backup created. No data was modified by this patch. Validation of Back-out Procedure: --------------------------------- The Back-out Procedure can be verified by confirming the checksums have been returned to the pre-patch value using CHECK1^XTSUMBLD. It can also be verified by printing the first 2 lines of the LA routine(s) contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routine(s) contained in this patch have been backed out, the Second line of each routine will no longer contain the designation of patch LA*5.2*104. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.2;AUTOMATED LAB INSTRUMENTS;**[Patch List]**;Sep 27, 1994;Build 4 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: LA7PCFG Before: B85591294 After: B99131253 **67,104** Routine list of preceding patches: 67 ============================================================================= User Information: Entered By : Date Entered : OCT 24, 2023 Completed By: Date Completed: APR 22, 2024 Released By : Date Released : APR 23, 2024 ============================================================================= Packman Mail Message: ===================== $END TXT