$TXT Created by DEVCRN.DOMAIN.EXT (KIDS) on Monday, 02/14/22 at 10:01 ============================================================================= Run Date: MAY 31, 2022 Designation: XU*8*767 Package : XU - KERNEL Priority: Mandatory Version : 8 SEQ #610 Status: Released Compliance Date: JUL 01, 2022 ============================================================================= Associated patches: (v)XU*8*744 <<= must be installed BEFORE `XU*8*767' Subject: KERNEL VISTA ENHANCEMENT - PPMS/PIE UPDATE Category: - Enhancement (Mandatory) - Routine Description: ============ XU*8.0*744 is the ONLY required build for patch XU*8.0*767. The following enhancement exported in this patch is needed to support the Master Veteran Index (MVI) continued implementation of Enterprise User Identity as it relates to the Provider Profile Management System (PPMS) / Provider Integration Engine (PIE). Enhancement Currently if PPMS/PIE sends an 'ADD' message for a National Provider Identifier (NPI) that is already KNOWN at the facility, then the traits, check keys and Computerized Patient Record System (CPRS) tab value are subsequently NOT being updated at the facility. Therefore, MVI has made a modification in routine XUMVIENU where if the 'ADD' message is transmitted to a facility that already knows the NPI, then that request will now instead be processed as an 'UPDATE' message and will execute all of the appropriate update rules as if it was initially sent as an 'UPDATE' message. 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: ----------- Anchorage VAMC (AK) Memphis VAMC (TN) 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. 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*767) 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*767 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 XU 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: ;;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: XUMVIENU Before:B211406256 After:B212519191 **711,724,744,767** Routine list of preceding patches: 744 ============================================================================= User Information: Entered By : Date Entered : FEB 03, 2022 Completed By: Date Completed: MAY 31, 2022 Released By : Date Released : MAY 31, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT