$TXT Created by DEVCRN.DOMAIN.EXT (KIDS) on Monday, 03/01/21 at 16:38 ============================================================================= Run Date: MAR 13, 2023 Designation: RG*1*75 Package : RG - CLINICAL INFO RESOURCE NETWORK Priority: Mandatory Version : 1 SEQ #76 Status: Released Compliance Date: MAR 28, 2023 ============================================================================= Associated patches: (v)RG*1*34 <<= must be installed BEFORE `RG*1*75' Subject: MASTER VETERAN INDEX VISTA ENHANCEMENTS - ENTERPRISE USER IDENTITY Category: - Enhancement (Mandatory) - Routine Description: ============ NOTE: Master Patient Index (MPI) 'Enterprise User Identity' enhancements are being distributed in two VistA namespaces: RG and XU. Patches RG*1.0*75 and XU*8.0*663 can be installed in any order as there are NO direct dependencies between these patches. (Do NOT install RG*1.0*75 on legacy sites or on the FORUM CLAIMS system) NOTE: Legacy sites and the FORUM CLAIMS system can install just the XU*8.0*663 patch. The RG*1.0*75 patch should NOT be installed on legacy sites or on the FORUM CLAIMS system. RG*1.0*34 is the only required build for patch RG*1.0*75. The following enhancement exported in this patch is needed to support the Master Veteran Index (MVI) implementation of Enterprise User Identity when adding or editing entries in the NEW PERSON (#200) file in VistA. Enhancement In support of the new Enterprise User Identity functionality being released in KERNEL patch XU*8.0*663, MVI has updated its existing monitoring process in the 'Link and Process Status Display' [RG LINKS & PROCESS DISPLAY] menu option, which is executed by routine RGMTMONT, to now also include/display the following additional monitoring information: - Whether the 'XUS IAM NPFM BATCH UPDATE' menu option exists in the OPTION (#19) file, if it has been scheduled to run (if so the next date/time it is scheduled to run) and the number of NEW PERSON (File #200) updates that are waiting to be processed at the site. - Whether the 'XUS IAM NPFM PURGE' menu option exists in the OPTION (#19) file, if it has been scheduled to run (if so the next date/time it is scheduled to run) and the number of NEW PERSON (File #200) updates that are waiting to be purged at the site. 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: ---------- Miami VAMC (Miami FL) Texas Valley Coastal Bend HCS (Harlingen TX) Tomah VAMC (Tomah WI) Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. 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. 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*75) 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*75 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: Routines 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 ------------------------------ N/A Back-Out Plan ------------- The RG patch backout procedure would consist of 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 1 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: RGMTMONT Before: B37393019 After: B73383877 **20,30,31,34,75** Routine list of preceding patches: 34 ============================================================================= User Information: Entered By : Date Entered : JUN 01, 2020 Completed By: Date Completed: MAR 13, 2023 Released By : Date Released : MAR 13, 2023 ============================================================================= Packman Mail Message: ===================== $END TXT