$TXT Created by A. at KRNDEV.FO-OAKLAND.DOMAIN.EXT (KIDS) on Thursday, 04/30/26 at 07:19 ============================================================================= Run Date: JUL 23, 2026 Designation: XU*8*838 Package : XU - KERNEL Priority: Mandatory Version : 8 SEQ #667 Status: Released Compliance Date: AUG 23, 2026 ============================================================================= Associated patches: (v)XU*8*759 <<= must be installed BEFORE `XU*8*838' Subject: IMPROVE HL7 LOCKING - ADDING NEW USERS Category: - Routine - Other Description: ============ This patch improves how the HL7 interface handles locking when adding new users in VistA. Previously, there were occasional issues where the system would remain locked, causing delays. Key Enhancements 1. Retry Limit: The system will try up to 3 times to add a new user, with a 3-second pause between attempts. 2. Automatic Unlock: After 3 attempts, the lock will be released whether successful or not. 3. Error Logging: If all attempts fail, the error will be recorded in Kernel Standard Error Logging. - Possible errors recorded in Kernel Standard Error Logging: * HL7 Interface Lock failed * HL7 Interface Unlock failed * HL7 Interface FIND/ADD failed : Unmanaged error - review the stack trace - sample of error trap log Date ErrNum $ZE Time UCI/VOL $J T-9 #110) HL7 Interface Lock failed 15:15:23 ROU:PTHR4PA01 83781 $I |TCP|1|83781 Which error? > 110 Process ID: 83781 (83781) JUN 01, 2026 15:15:23 UCI/VOL: [ROU:PTHR4PA01] $ZA: 2,4,5,7,6 $ZB: \004 Current $IO: |TCP|1|83781 Current $ZIO: REDACTED^0^1^|TCP|1|83781 $ZE= HL7 Interface Lock failed Last Global Ref: ^XTMP("HL7DELAY 3260601",0) S @%ZTERRT@("LINE")=$STACK(%2,"MCODE") 4. Notification: If all attempts fail, a message will be sent to the newly established HL7 INTERFACE DELAY MailMan group. - You can self-subscribe to this group if you want to receive these alerts. - sample message: Subj:HL7 Interface Delay Notification [#203109] 07/02/26@07:41 From: POSTMASTER In 'IN' basket. Page 1 *New* -------------------------------------------------------------------- The HL7 Interface is experiencing delays in processing XUSER, ONE due to locking issues. 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 Number New/Modified/Deleted --------- ----------- -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- HL7 INTERFACE DELAY New 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: INC40276949 - Bad User returned from RPC, appears to be lock can't be gotten, no retry. Problem ------- We use a process that relies on a remote system, and sometimes it returns a 'Bad User' error. This error is happening more often and prevents patients from being added automatically, forcing manual processing. Resolution ---------- Kernel Patch XU*8.0*838 introduces enhanced error tracking capabilities for the process that adds users to VistA. Any runtime errors that occur during this process are now automatically recorded in the standard Kernel error log for further analysis. In addition, users may receive error notifications by subscribing to the newly established MailMan mail group designated for this purpose. Routine Name: XUESSO1 Description of Changes: Add new enhanced error handling to capture runtime error and log it in the Standard Kernel Error logging. Error notification email can also be sent to anyone subscribing to the new MailMan mail group described in this patch description. Test Sites: SNOW Change Order #: ----------- -------------------- Hampton VAMC CHG0736156 Phoenix VAMC CHG0734635 Pittsburgh VAMC CHG0731582 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 describing the new functionality is not included in this release but will be included in a future release of the Kernel Technical Manual. Patch Installation: ------------------- Pre/Post Installation Overview: ------------------------------ There are no Pre/Post installation routine processes. 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. 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 XU*8.0*838 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 XU*8.0*838 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. When prompted "Enter the Coordinator for Mail Group 'HL7 INTERFACE DELAY':", press . ii. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//', answer . iii. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer . iv. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer . Post-Installation Instructions: ------------------------------- None Back-Out/Roll Back Plan: ------------------------ Perform a restore using the backup of the BUILD created in the Installation Instruction Step 2B above. Note: This process should only be done with the concurrence and participation of the development team and the appropriate VA Site/Region personnel. If rollback/backout is required, perform the steps below: Step 1 - Install the Backup a. Use MailMan [XMUSER] menu to locate the PackMan message containing the backup build. The subject of the PackMan message begins with "Backup of XU*8.0*838". b. At the Enter message action prompt, enter XTRACT KIDS c. At the Select PackMan function prompt, enter INSTALL/CHECK MESSAGE d. If prompted OK to continue with Load?, enter YES e. If prompted Want to Continue with Load?, enter YES f. Use KIDS [XPD MAIN] menu to install the backup KIDS distribution using the Install Package(s) [XPD INSTALL BUILD] option. g. At the Select INSTALL NAME prompt, enter XU*8.0*838b h. At the Want KIDS to Rebuild Menu Trees Upon Completion of Install prompt, enter NO i. At the Want KIDS to INHIBIT LOGONs during the install prompt, enter NO j. At the Want to DISABLE Scheduled Options, Menu Options, and Protocols prompt, enter NO Step 2 - Remove Mail Group HL7 INTERFACE DELAY Select Systems Manager Menu Option: FM Select VA FileMan Option: Enter or Edit Input to what File: NAME COMPONENTS// MAIL GROUP EDIT WHICH FIELD: ALL// Select MAIL GROUP NAME: HL7 INTERFACE DELAY NAME: HL7 INTERFACE DELAY// @ SURE YOU WANT TO DELETE THE ENTIRE 'HL7 INTERFACE DELAY' MAIL GROUP? Y SINCE THE DELETED ENTRY MAY HAVE BEEN 'POINTED TO' BY ENTRIES IN THE 'BULLETIN' FILE, ETC., DO YOU WANT THOSE POINTERS UPDATED (WHICH COULD TAKE QUITE A WHILE)? No// If assistance is still required, then submit a ServiceNow (SNOW) ticket so that the development team can evaluate and assist in this restoration process. Routine Information: ==================== The second line of each of these routines now looks like: ;;8.0;KERNEL;**[Patch List]**;Jul 10, 1995;Build 4 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: XUESSO1 Before:B106736265 After:B129227787 **165,183,196,245,254,269,337, 395,466,523,655,659,771,759, 838** Description of Changes: Add new functionality to capture runtime error and log it in the Standard Kernel Error logging. Error notification email can also be sent to anyone subscribing to the new MailMan mail group described in this patch description. Routine list of preceding patches: 759 ============================================================================= User Information: Entered By : Date Entered : NOV 07, 2025 Completed By: Date Completed: JUL 22, 2026 Released By : Date Released : JUL 23, 2026 ============================================================================= Packman Mail Message: ===================== $END TXT