$TXT Created by FMB.FO-OAKLAND.DOMAIN.EXT (KIDS) on Friday, 12/13/19 at 10:55 ============================================================================= Run Date: DEC 17, 2019 Designation: VPR*1*19 Package : VPR - VIRTUAL PATIENT RECORD Priority: Mandatory Version : 1 SEQ #16 Status: Released Compliance Date: DEC 21, 2019 ============================================================================= Associated patches: (v)VPR*1*17 <<= must be installed BEFORE `VPR*1*19' Subject: HEALTH CONCERNS Category: - Routine - Other Description: ============ This patch to the Virtual Patient Record (VPR) application will address an issue occurring in the HealthShare operational mode updates. The V Health Factors file currently populates the Health Concerns container in HealthShare. Sites that are heavy users of health factors are seeing significant delays in update queue processing. No HealthShare clients are pulling this data yet, so this patch will stop populating this container until further analysis can be done. The VPR event listeners for the Patient Care Encounter (PCE) and Text Integration Utilities (TIU) applications have also been streamlined to reduce the number of tasks created to collect and post encounter related patient data. Patch Components: ----------------- Entities Associated: N/A Files & Fields Associated: N/A Forms Associated: N/A Mail Groups Associated: N/A Options Associated: N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- VPR PCE EVENTS Modified Remote Procedure Calls Associated: N/A Security Keys Associated: N/A Templates Associated: N/A Blood Bank Team Coordination: N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- N/A Test Sites: ----------- North Chicago, IL Tuscaloosa, AL Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released as a KIDS build via 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 1 minute to install. Installation Instructions: -------------------------- 1. Choose the PackMan message containing this patch. 2. Choose the INSTALL/CHECK MESSAGE PackMan option. 3. From the Kernel Installation and Distribution System Menu, select the Installation Menu. From this menu, you may elect to use the following options. When prompted for the INSTALL NAME, enter VPR*1.0*19. a. Backup a Transport Global - This option will create a backup message of any routines exported with this patch. It will not backup any other changes such as DDs or templates. b. 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 components of this patch (routines, DDs, templates, etc.). c. Verify Checksums in Transport Global - This option will allow you to ensure the integrity of the routines that are in the transport global. 4. From the Installation Menu, select the Install Package(s) option and choose the patch to install. 5. When prompted Want KIDS to INHIBIT LOGONs during the install? NO// enter NO. 6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO// enter NO. 7. If prompted Delay Install (Minutes): (0 60): 0// respond 0. Post-Installation Instructions: ------------------------------- N/A Backout Procedures: ------------------- During the VistA Installation Procedure of the KIDS build, the installer should use the 'Backup a Transport Global' action (step 3a in the Installations Instructions below). If rollback/backout is required, the installer can use the MailMan message to restore routines that were saved prior to installing the patch. The PROTOCOL (#101) file entry modified by this patch would also need to be reverted; this can be done via FileMan: VA FileMan 22.2 Select OPTION: 1 ENTER OR EDIT FILE ENTRIES Input to what File: ENTITY// 101 PROTOCOL (6166 entries) EDIT WHICH FIELD: ALL// ENTRY ACTION THEN EDIT FIELD: Select PROTOCOL NAME: VPR PCE EVENTS PCE events for VPR ENTRY ACTION: D PX^VPRENC// D PCE^VPREVNT Select PROTOCOL NAME: Routine Information: ==================== The second line of each of these routines now looks like: ;;1.0;VIRTUAL PATIENT RECORD;**[Patch List]**;Sep 01, 2011;Build 5 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: VPRENC Before: n/a After: B55221135 **19** Routine Name: VPREVNT Before:B123819975 After:B120515239 **8,10,15,17,19** Routine Name: VPRHS Before: B80485929 After: B80745038 **8,10,15,16,17,19** Routine list of preceding patches: 17 ============================================================================= User Information: Entered By : Date Entered : NOV 19, 2019 Completed By: Date Completed: DEC 17, 2019 Released By : Date Released : DEC 17, 2019 ============================================================================= Packman Mail Message: ===================== $END TXT