$TXT Created by DEVCRN.DOMAIN.EXT (KIDS) on Monday, 02/08/21 at 11:36 ============================================================================= Run Date: APR 21, 2021 Designation: XU*8*744 Package : XU - KERNEL Priority: Mandatory Version : 8 SEQ #591 Status: Released Compliance Date: MAY 22, 2021 ============================================================================= Associated patches: (v)XU*8*724 <<= must be installed BEFORE `XU*8*744' Subject: KERNEL VISTA ENHANCEMENT - PPMS/PIE SUPPORT Category: - Enhancement (Mandatory) - Routine Description: ============ XU*8.0*724 is the only required build for patch XU*8.0*744. The following enhancements exported in this patch are needed to support the Master Veteran Index (MVI) continued implementation of Enterprise User Identity. Enhancement #1 Currently the Computerized Patient Record System (CPRS) application is NOT able to sufficiently differentiate between Veteran Affairs (VA) and Non-VA Providers added by the Provider Profile Management System (PPMS) / Provider Integration Engine (PIE). Therefore, MVI has enhanced the PPMS/PIE process of adding Non-VA providers through the population of the following CPRS TAB (#101.13) multiple fields below in the NEW PERSON (#200) file to allow CPRS to correctly identify/differentiate between these types of Providers: CPRS TAB (#.01) - "NVA" EFFECTIVE DATE (#.02) - Date MVI adds record into file EXPIRATION DATE (#.03) - Inactivation Date MVI receives from PPMS/PIE Finally, to address the records that currently exist in the NEW PERSON (#200) file, MVI has created a post-install routine (XUP744) to populate the following CPRS TAB (#101.13) multiple fields below in the NEW PERSON (#200) file if the record contains a National Provider Identifier (NPI Field #41.99) value and the REMARKS (#53.9) and TITLE (#8) fields are set to 'Non-VA Provider': CPRS TAB (#.01) - "NVA" EFFECTIVE DATE (#.02) - Date MVI adds record into file EXPIRATION DATE (#.03) - Update with the INACTIVE DATE (#53.4) if it exists else leave blank (null). NOTE: POST-INSTALL will automatically queue itself and transmit an email to the user with a process summary report once completed. Enhancement #2 MVI has updated the Remote Procedure Call (RPC) [XUS MVI ENRICH NEW PERSON] to restrict updates to the NEW PERSON (#200) file for 'Dual Providers' when their Primary Menu is populated. In addition, if their Primary Menu is NOT populated, but the CPRS TAB (#101.13) multiple in the NEW PERSON (#200) file is populated with a value other than 'NVA', then the record will also be considered as 'Dual Provider' and the update will be prevented from occurring. 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: Blood Bank Team Coordination ---------------------------- EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch XU*8.0*744 contains changes to a package referenced in Process Asset Library standard titled: BBM Team Review of VistA Patches. This patch does not alter or modify any VistA Blood Bank software design safeguards or safety critical elements functions. RISK ANALYSIS: Changes made by patch XU*8.0*744 have no adverse effect on Blood Bank software functionality, therefore RISK is none. New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A Defect Tracking System Ticket(s) & Overview ------------------------------------------- N/A Test Sites: ----------- Las Vegas VAMC (Las Vegas NV) Robley Rex VAMC (Louisville KY) 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 ------------------------------ The post-installation process (XUP744) will task off the following clean-up processes for the NEW PERSON (#200) file to the background: The post-init process will run through the existing NPI entries in the NEW PERSON (#200) file looking for records where the REMARKS (#53.9) and TITLE (#8) fields are set to 'Non-VA Provider'. If found, then MVI will update the following fields in the CPRS TAB (#101.13) multiple for that record: CPRS TAB (#.01) - "NVA" EFFECTIVE DATE (#.02) - Date MVI adds record into file EXPIRATION DATE (#.03) - Update with the INACTIVE DATE (#53.4) if it exists else leave blank (null). 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*744) 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*744 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 ------------------------------ Post-Init routine XUP744 can be deleted once the tasked post-installation process has completed. 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. The NEW routines (XUMVIEU1 and XUP744) should then be deleted from the system. 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:B280103209 After:B211406256 **711,724,744** Routine Name: XUMVIEU1 Before: n/a After: B24824276 **744** Routine Name: XUP744 Before: n/a After: B9079060 **744** Routine list of preceding patches: 724 ============================================================================= User Information: Entered By : Date Entered : DEC 10, 2020 Completed By: Date Completed: APR 21, 2021 Released By : Date Released : APR 21, 2021 ============================================================================= Packman Mail Message: ===================== $END TXT