$TXT Created by M at MNTVBB.DOMAIN.EXT (KIDS) on Friday, 09/06/24 at 14:24 ============================================================================= Run Date: NOV 13, 2024 Designation: LR*5.2*575 Package : LR - LAB SERVICE Priority: Mandatory Version : 5.2 SEQ #474 Status: Released Compliance Date: DEC 14, 2024 ============================================================================= Associated patches: (v)LR*5.2*568 <<= must be installed BEFORE `LR*5.2*575' Subject: POC PROVIDER ISSUE Category: - Routine Description: ============ This patch addresses one issue: Point of care results might have a non-provider assigned as the ordering provider. 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 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): N/A Defect Tracking System Ticket(s) & Overview: =========================================== INC33388072: Point of Care Results Assigned Non-Provider as Provider Issue: -------- It is possible that a Point of Care (POC) order might have a "non-provider" assigned as the ordering provider. This scenario occurs when the POC logic has not been able to determine the patient's physician. If the patient has had a recent appointment with a non-provider (such as an Imaging Technologist), that non-provider will be filed on the POC order as the ordering provider. Resolution: ----------- Routine LRVRPOC has been modified to validate whether the provider holds the PROVIDER security key in the NEW PERSON (#200) file. If a provider does not hold the PROVIDER security key, results will not file and an interface error of "No valid provider found" will be generated. Test Sites: ----------- Michael E. DeBakey VA Medical Center (Houston, TX) James A. Haley Veterans Hospital (Tampa, FL) SNOW Change Order #: ------------------- Houston - CHG0534419 Tampa - CHG0536408 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 --------------------------------------------------------------------- N/A Patch Installation: ------------------- Pre/Post Installation Overview: There is a post installation routine included in this patch which will run automatically when the patch is installed. The post install routine will not be deleted and should remain on the system for backout purposes. 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. 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 LR*5.2*575. 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*575. iii. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build (including Routines) R Routines Only Backup Type: B// 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. Post-Installation Instructions: N/A Back-out/Rollback Strategy: -------------------------- 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 routine 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 1 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: LRVRPOC Before: B97615991 After: B98122434 **290,350,468,454,568,575** Routine list of preceding patches: 568 ============================================================================= User Information: Entered By : Date Entered : AUG 14, 2024 Completed By: Date Completed: NOV 12, 2024 Released By : Date Released : NOV 13, 2024 ============================================================================= Packman Mail Message: ===================== $END TXT