$TXT Created by DEVCRN.DOMAIN.EXT (KIDS) on Wednesday, 07/29/26 at 14:34 ============================================================================= Run Date: SEP 17, 2026 Designation: RG*1*80 Package : RG - CLINICAL INFO RESOURCE NETWORK Priority: Mandatory Version : 1 SEQ #79 Status: Released Compliance Date: OCT 18, 2026 ============================================================================= Associated patches: (v)RG*1*76 <<= must be installed BEFORE `RG*1*80' Subject: MASTER VETERAN INDEX VISTA ENHANCEMENT - PREFERRED NAME HL7 ACK Category: - Routine - Enhancement (Mandatory) Description: ============ NOTE: To prevent legacy systems ending up as Treating Facilities, RG* patches should NOT be installed on legacy systems or the FORUM CLAIMS system (since it is NOT a Veterans Affair Medical Center (VAMC) VistA system). RG*1.0*76 is the only required build for patch RG*1.0*80. NOTE: Do NOT install RG*1.0*80 on legacy sites or on the FORUM CLAIMS system. The Master Patient Index (MPI) has made an enhancement to ensure that it is notified in the Application Acknowledgement (APP ACK) when an error occurs updating the Preferred Name on a Patient's record at a site. Enhancement Previously the Data Dictionary (DD) Input Transforms for Preferred Name were identical on the MPI and at the VAMCs. Over time, changes have been made to the input transform at the VAMCs for the PREFERRED NAME (.2405) field in the PATIENT (2) file that has put more constraints on what values can be stored which can cause the MPI to get out of sync with the site. It was discovered that if an invalid Preferred Name value is transmitted down to the site from the MPI in the Update Person (A31) Health Level Seven (HL7) messages that an appropriate error message indicating this issue is not being returned for that field in the APP ACK to MPI. This error occurs because the Preferred Name value sent does not pass the DD input transform check at the site, thereby causing the MPI to assume that the update was successful and update the value on the correlation record when in fact no update should have occurred as it wasn't a valid value. To prevent MPI from updating Preferred Name on the Correlation record when it is rejected at the site, a change in routine RGADTP2 was necessary to transmit back the appropriate error information related to updating PREFERRED NAME (.2405) in the PATIENT (2) file. Previously this wasn't required and therefore not implemented when the field was initially introduced as the DD's were initially identical. EHRM Impact Statement: ---------------------- - This patch should have no 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 ------------------------------------------- N/A Test Sites: ---------- Butler VAMC (PA) Huntington VAMC (WV) SNOW Change Order #: ------------------- Butler VAMC: CHG0777655 Huntington VAMC: CHG0776421 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Documentation describing the new functionality is not included in this release. 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. The HL7 incoming filers should be stopped. Use the Monitor, Start, Stop Filers [HL FILER MONITOR] option on the Filer and Link Management Options [HL MENU FILER LINK MGT] menu on the HL7 Main Menu [HL MAIN MENU]. 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. RG*1.0*80) 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 RG*1.0*80 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 ------------------------------ After patch installation has completed, restart the HL7 incoming filers. Use the Monitor, Start, Stop Filers [HL FILER MONITOR] option on the Filer and Link Management Options [HL MENU FILER LINK MGT] menu on the HL7 Main Menu [HL MAIN MENU]. *Note: Do NOT start the HL7 filers as POSTMASTER as they don't have the required privileges to execute all of the processes that come through messaging. In addition, it is a violation of multiple standards and policies to modify your DUZ under any circumstances. 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: ;;1.0;CLINICAL INFO RESOURCE NETWORK;**[Patch List]**;30 Apr 99;Build 2 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: RGADTP2 Before: B87694121 After: B94674949 **27,20,45,44,47,48,49,52,54, 58,59,64,66,67,71,72,76,80** Routine list of preceding patches: 76 ============================================================================= User Information: Entered By : Date Entered : JUL 08, 2026 Completed By: Date Completed: SEP 17, 2026 Released By : Date Released : SEP 17, 2026 ============================================================================= Packman Mail Message: ===================== $END TXT