$TXT Created by DEVCRN.DOMAIN.EXT (KIDS) on Thursday, 01/08/26 at 09:18 ============================================================================= Run Date: FEB 26, 2026 Designation: DG*5.3*1159 Package : DG - REGISTRATION Priority: Mandatory Version : 5.3 SEQ #1012 Status: Released Compliance Date: MAR 29, 2026 ============================================================================= Associated patches: (v)DG*5.3*1055 <<= must be installed BEFORE `DG*5.3*1159' Subject: MASTER VETERAN INDEX VISTA ISSUE - TF SITE LIST Category: - Routine Description: ============ DG*5.3*1055 is the only required build for patch DG*5.3*1159. VistA Imaging Display is encountering issues with erroneous entries being returned in the Treating Facility (TF) List when the Remote Procedure Call (RPC) [VAFCTFU GET TREATING LIST] is executed. Issue The current TF set logic DOT (.) structure in routine VAFCTFU1 ensures that if a Veteran Affairs Medical Center (VAMC) is encountered that the entry is always added to the TF List, even if the TF record is ONLY for a Person (PN) type record. However, TF List entries for this RPC should ONLY ever return VAMCs that are associated with a Patient (PI) type record. To prevent erroneous entries from being added to the TF List when there is ONLY a PN type record associated with it, the Master Patient Index (MPI) team has modified the TF set logic to ensure that only VAMCs associated with a PI type record are actually added to the TF List. EHRM Impact Statement: ---------------------- - This patch will have an intended EHRM impact, and can be installed at all sites, including EHRM converted sites. Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # 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: New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Defect Tracking System Ticket(s) & Overview ------------------------------------------- INC40868401 - HOU/CTX erroneous Treating Facility entries (Parent Ticket) INC41114697 - REN erroneous Treating Facility entries Problem: -------- A few VAMCs utilizing the VistA Imaging Display have reported seeing erroneous entries being returned in the TF List when executing the supported RPC [VAFCTFU GET TREATING LIST]. Resolution: ----------- After analysis, it was determined that these erroneous TF entries are related to VAMCs containing ONLY PN (Person) type records. The RPC [VAFCTFU GET TREATING LIST] should ONLY ever return VAMC sites in the TF List that have PI (Patient) type records. Ultimately, this issue occurs because of how the DOT (.) logic structure was initially set up in routine VAFCTFU1 along with the recent release of the Enterprise User Identity Patch (XU*8.0*799) early this year. Therefore, if ONLY a PN type record is known at a VistA site, even though it was identified and excluded as a PN record it can still be included because the set of the TF List currently always occurs if it encounters a VAMC. To prevent VAMCs with only PN type records from being added to the TF list, MPI has modified the logic of the set to ensure that the site is only added to the TF List if the VAMC site has a PI type record. Test Sites: ---------- Clarksburg (WV) VAMC Martinsburg (WV) VAMC SNOW Change Order #: ------------------- Clarksburg VAMC: CHG0693116 Martinsburg VAMC: CHG0693733 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Documentation Title File Name ------------------------------------------------------------------ N/A Patch Installation: Pre/Post Installation Overview ------------------------------ There are no Pre/Post installation routine processes. Pre-Installation Instructions ----------------------------- This patch takes less than a minute to install. This patch may be installed with users on the system, but it is recommended that installation occurs during off hours to avoid collisions. 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. DG*5.3*1159) 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 DG*5.3*1159 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 Enter response: Routines Only iv. When prompted "Do you wish to secure this message? 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/Roll Back Plan ----------------------- The patch backout procedure would consist of just restoring the original routine using the back-up message created during the patch installation. If assistance is still required to back-out the patch please contact the National Service Desk (NSD) to log a help desk ticket so the development team can assist in the process. Note: This process should only be done with the concurrence and participation of the development team and the appropriate VA Site/Region personnel. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.3;Registration;**[Patch List]**;Aug 13, 1993;Build 1 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: VAFCTFU1 Before: B16172152 After: B18142662 **261,392,448,449,800,856,1042, 1055,1159** ============================================================================= User Information: Entered By : Date Entered : JAN 07, 2026 Completed By: Date Completed: FEB 26, 2026 Released By : Date Released : FEB 26, 2026 ============================================================================= Packman Mail Message: ===================== $END TXT