$TXT Created by DEVCRN.DOMAIN.EXT (KIDS) on Wednesday, 04/01/26 at 14:41 ============================================================================= Run Date: JUL 20, 2026 Designation: XU*8*844 Package : XU - KERNEL Priority: Mandatory Version : 8 SEQ #666 Status: Released Compliance Date: JUL 30, 2026 ============================================================================= Associated patches: (v)XU*8*799 <<= must be installed BEFORE `XU*8*844' (v)XU*8*819 <<= must be installed BEFORE `XU*8*844' Subject: KERNEL VISTA ENHANCEMENTS - ENTERPRISE USER XML PARSING Category: - Routine - Other - Enhancement (Mandatory) Description: ============ XU*8.0*799 and XU*8.0*819 are the required builds for patch XU*8.0*844. The following enhancements/issue exported in this patch are needed to support the Master Patient Index (MPI) implementation of Enterprise User Identity and the sites transition/migration to the CERNER application by the Electronic Health Record Modernization (EHRM) team. In addition, these enhancements will work in conjunction with the MPI changes that have been exported in patch MPI*1.0*165. Note: Patch MPI*1.0*165 is NOT a VistA patch. Enhancement #1 -------------- EHRM has requested that DIVISION multiple (#16) information in the NEW PERSON file (#200) be exported in the Asynchronous Report to CERNER. MPI verified that the DIVISION information was already being transmitted to the MPI in the response for the site, but lacked inclusion of the Station Number. Although the Division Name is currently being returned in the response it is NOT always 100% reliable to do a look up on to retrieve the Station Number value. Therefore, the Station Number has now been appended to the end of the DIVISION information in the array that is transmitted to MPI for the user's record. Enhancement #2 -------------- Due to the issue identified below, it was determined that the MPI would create the Remote Procedure Call (RPC) [XUS MVI NEW PERSON FLD MNTR] to allow access to the NEW PERSON FIELD MONITOR file (#8933.1) to view, modify or add an entry for a given Designated User ID (DUZ). This RPC will allow the MPI to execute the following processes on the NEW PERSON FIELD MONITOR file (#8933.1) at the requested site: - Retrieve the FIRST Pending entry to be transmitted. - Retrieve the LAST entry for a DUZ, regardless of transmission state - Retrieve ALL Pending entries for a DUZ - Flip the REQUIRES TRANSMISSION (#.03) flag for the FIRST Pending entry for a DUZ - Flip the REQUIRES TRANSMISSION (#.03) flag for ALL Pending entries for a DUZ - Add a NEW Pending entry for a DUZ for today (if applicable) Note: A new entry will ONLY be added for the DUZ if one doesn't already exist there for today. The ability to add a Pending entry will also allow MPI to automatically update the VistA IDs List for the user by removing their terminated and/or disusered historical entries. Issue -------------- It was reported by the national operations staff at several sites that ZSOAP errors were being logged for parsing errors related to the MPI's background job option [XUS IAM NPFM BATCH UPDATE]. After analysis, it was determined that these parsing errors were being generated because of '&' characters in the SITE NAME field (#1) in the VISITED FROM field (#8910) in the NEW PERSON file (#200) that were being transmitted to the Person Service Identity Management (PSIM) system. The '&' character is a defined delimiter for the Extensible Markup Language (XML)/Service Provisioning Markup Language (SPML) and if it is included in any data element then it needs to be escaped to prevent parsing issues. It was noted that several fields passed into the XML/SPML builder were already being checked for these conditions. Therefore, MPI updated the builder to also check and handle these types of characters in SITE NAME as well. 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 --------------------------- -------------------- XUS MVI NEW PERSON FLD MNTR New 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 ------------------------------------------- INC41818298 - R3 - (WPB) Please investigate these ZSOAP errors in ATG Production system. Problem: -------- A few sites have noticed increased ZSOAP errors being logged into their production error trap. After analysis, the majority of them are timeout issues which will be automatically retried. However, some were shown to be parsing errors that are triggered when the XUS IAM NPFM BATCH UPDATE background job runs every 5 minutes. The parsing error is causing the background job to fail on that record every time it runs. Resolution: ----------- After analysis of the parsing error, it was determined that the SITE NAME (#1) in the VISITED FROM field (#8910) in the NEW PERSON file (#200) contained '&' characters which is a defined delimiter in the XML/SPML document. To prevent parsing from being thrown off by these characters in the data, MPI has updated the XML/SPML builder to escape these characters in SITE NAME as is already being accomplished on several other free text fields being sent in the document to PSIM. Test Sites: ---------- Alexandria (LA) VAMC Butler (PA) VAMC George E. Wahlen (Salt Lake City, UT) VAMC SNOW Change Order #: ------------------- Alexandria VAMC: CHG0745499 Butler VAMC: CHG0738670 George E. Wahlen VAMC: CHG0739548 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 and the installation may be queued. The background job MPI NEW PERSON FIELD MONITOR BATCH UPDATE [XUS IAM NPFM BATCH UPDATE] should be unscheduled. Use the Schedule/Unschedule Options [XUTM SCHEDULE] option on the TaskMan Management [XUTM MGR] 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. XU*8.0*844) 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*844 iii. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build R Routines Enter response: Build 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 ------------------------------ The background job MPI NEW PERSON FIELD MONITOR BATCH UPDATE [XUS IAM NPFM BATCH UPDATE] is required to be rescheduled. Use the Schedule/Unschedule Options [XUTM SCHEDULE] option on the TaskMan Management [XUTM MGR] menu and enter a date/time of at least 5 minutes from now. Back-Out/Roll Back Plan ----------------------- This patch contains routines and an RPC. In the event that it is determined that this patch should be backed out, the site should install the back-up build 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: ;;8.0;KERNEL;**[Patch List]**;Jul 10, 1995;Build 1 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: XUIAMNPB Before:B108825472 After:B110515518 **799,844** Routine Name: XUIAMRPC Before: n/a After: B27513052 **844** Routine Name: XUMVINPB Before:B149133444 After:B153031034 **710,725,733,819,844** Routine list of preceding patches: 799, 819 ============================================================================= User Information: Entered By : Date Entered : MAR 16, 2026 Completed By: Date Completed: JUL 16, 2026 Released By : Date Released : JUL 20, 2026 ============================================================================= Packman Mail Message: ===================== $END TXT