$TXT Created by DEVCRN.DOMAIN.EXT (KIDS) on Tuesday, 07/07/20 at 14:58 ============================================================================= Run Date: AUG 20, 2020 Designation: XU*8*732 Package : XU - KERNEL Priority: Mandatory Version : 8 SEQ #575 Status: Released Compliance Date: SEP 04, 2020 ============================================================================= Associated patches: (v)XU*8*710 <<= must be installed BEFORE `XU*8*732' Subject: KERNEL VISTA ISSUES - NPI DUPLICATES Category: - Routine - Other Description: ============ XU*8.0*710 is the only required build for patch XU*8.0*732. The following items exported in this patch will assist with supporting / addressing the National Provider Identifier (NPI) and any existing duplicates that may exist in the NEW PERSON (#200) file. Issue #1 The existing Remote Procedure Calls (RPCs) [XUS MVI NEW PERSON GET] and [XUS MVI NEW PERSON UPDATE] and the corresponding routine 'XUMVINPU' were modified to offer MVI the ability to retrieve the DOB (#5) field and also retrieve/update the following fields for the EFFECTIVE DATE/TIME (#42) multiple in the NEW PERSON (#200) file: - EFFECTIVE DATE/TIME (.01) - STATUS (.02) - NPI (.03) NOTE: The RPC [XUS MVI NEW PERSON UPDATE] will now look at the value passed in for the NPI (#41.99) field from the NEW PERSON (#200) file, if it is NOT already one of the NPI (#.03) entries in the EFFECTIVE DATE/TIME (#42) multiple, then a new entry in the multiple will be created with the following values: EFFECTIVE DATE/TIME (.01) - NOW STATUS (.02) - 1 ('Active') NPI (.03) - Value passed from #41.99 The 'AC' X-REF will then trigger and update the following single-value fields in the NEW PERSON (#200) file: AUTHORIZE RELEASE OF NPI (41.97) NPI ENTRY STATUS (41.98) NPI (41.99) The [XUS MVI NEW PERSON GET] RPC now also allows retrieval by MVI of the NPI ENTRY STATUS (#41.98) field in the NEW PERSON (#200) file. Finally, the [XUS MVI NEW PERSON UPDATE] RPC has been enhanced to also be able to handle NPI deletions, including the EFFECTIVE DATE/TIME (#42) multiple related to that NPI, the NPI (#41.99) and the NPI ENTRY STATUS (#41.98) from the NEW PERSON (#200) file. Issue #2 Sites may have encountered multiple entries for Non-VA Providers, which there should NEVER be more than one, under the same NPI value from a previous issue that has now been corrected in patch XU*8.0*724. Therefore, the post-init process (XUP732) in this patch will process the NEW PERSON (#200) file for NPI entries and correct any duplicate NPI entries related to a NON-VA Provider (ie. Remarks="Non-VA Provider" and Title="Non-VA Provider") by keeping the 1st record, updating any subsequent record (ie. Having a higher internal entry number) by removing all NPI related fields and changing the NAME (#.01) field to have a 'ZZ' pre-pended to the last name (ie. JONES, JIM will become ZZJONES, JIM). NOTE: Any other NPI duplicates found that don't meet the criteria will NOT be updated, but WILL be included in the email report sent to the installer and development team. Also included in the report will be the following statistics: - How many were found - How many were updated successfully - How many were NOT updated successfully and what issues were encountered with them. 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 GET Modified 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*732 contains changes to a package referenced in ProPath 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*732 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: ----------- Anchorage VAMC (Anchorage, AK) Boston HCS (Jamaica Plain, MA) 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 (XUP732) will task off the following clean-up processes to the background: The post-init process will run thru the existing NPI entries in the NEW PERSON (#200) file looking for any duplicate NPI entries that are related to a NON-VA Provider (ie. remarks="Non-VA Provider" and Title="Non-VA Provider"). If found the 1st record will be kept and the subsequent record (with higher internal entry number) will be updated by removing all of the NPI related fields and updating the NAME (#.01) field to pre-pend a 'ZZ' to the last name. ie. 'JONES, JIM' will now become 'ZZJONES, JIM' NOTE: Any other NPI duplicates found that don't meet the criteria will NOT be updated, but WILL be included in the email report sent to the installer and development team. 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*732) 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 of any routines exported with this patch. It will not backup any other changes such as DDs or templates. 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 XUP732 can be deleted once the tasked post-installation process has completed. Back-Out Plan ------------- This patch contains a routine and RPC change. In the event that it is determined that this patch should be backed out, the site should submit a ServiceNow (SNOW) ticket so that the development team can evaluate and assist in the restoration process. Note: During installation, if the option to back-up the routine was executed as directed, "Backup a Transport Global" (Step 2B.), then the routine will have the ability to be restored from the 'backup' MailMan message that was generated. However, the Kernel Installation and Distribution System (KIDS) process does NOT perform a back of the other VistA software components, such as RPCs. 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 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: XUMVINPU Before:B125047049 After:B148889034 **691,711,710,732** Routine Name: XUP732 Before: n/a After: B8347138 **732** Routine list of preceding patches: 710 ============================================================================= User Information: Entered By : Date Entered : JUN 18, 2020 Completed By: Date Completed: AUG 20, 2020 Released By : Date Released : AUG 20, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT