$TXT Created by DEVCRN.DOMAIN.EXT (KIDS) on Thursday, 01/30/20 at 11:14 ============================================================================= Run Date: MAR 23, 2020 Designation: XU*8*724 Package : XU - KERNEL Priority: Mandatory Version : 8 SEQ #561 Status: Released Compliance Date: APR 02, 2020 ============================================================================= Associated patches: (v)XU*8*711 <<= must be installed BEFORE `XU*8*724' Subject: KERNEL VISTA ISSUE - NATIONAL PROVIDER IDENTIFIER Category: - Routine - Data Dictionary Description: ============ XU*8.0*711 is the only required build for patch XU*8.0*724. The following issue resolutions exported in this patch will address problems related to the National Provider Identifier (NPI) updates that were previously released in patch XU*8.0*711 in support of the Provider Profile Management System (PPMS) / Provider Integration Engine (PIE) updates for Mission Act. Issue #1 After extensive review of the NEW PERSON File (#200) and the related NPI fields, it was determined that the initial information provided to the Master Veteran Index (MVI) on which NPI fields to populate (or NOT) and those fields that would be populated by the PERSON CLASS (#8932.1) multiple in support of PPMS/PIE was unfortunately not completely accurate. MVI will address this issue of unusable NPI values, by making changes to how these NPI entries are created in the loading process. Therefore, MVI will now populate the EFFECTIVE DATE/TIME (#42) multiple in the NEW PERSON (#200) file, which will involve creating/setting the following values in the multiple: - EFFECTIVE DATE/TIME (#.01) : NOW (Current Date/Time) - STATUS (#.02) : 1 (Active) - NPI (#.03) : NPI value passed into process When the NPI (#.03) field in the EFFECTIVE DATE/TIME (#42) multiple is set it will then automatically trigger the 'AC' cross-reference (X-Ref) to make the following additional changes in the NEW PERSON (#200) file for the record: - AUTHORIZE RELEASE OF NPI (#41.97) : 1 (YES) - NPI ENTRY STATUS (#41.98) : D (DONE) - NPI (#41.99) : Same NPI value populated in EFFECTIVE DATE/TIME (#42) multiple above. Finally, as part of the post-install process for this patch, MVI will address the existing entries in the NEW PERSON (#200) file at the site that were loaded with ONLY the NPI field populated. MVI will now populate the EFFECTIVE DATE/TIME (#42) multiple fields, which will in turn automatically correct the other NEW PERSON (#200) fields as detailed above to make the NPI value usable. Upon completion, an email will be generated to the installer and MVI development detailing the statistics of the cleanup. ** NOTE: This will NOT address any duplicates already created or the DEA# (#53.2) NEW PERSON (#200) file issue. ** Issue #2 It was determined that the [XUS MVI ENRICH NEW PERSON] remote procedure (RPC), which is used to remotely add and/or update entries in the NEW PERSON (#200) file including the automatic assignment of the PROVIDER and XUORES security keys when the user is added and/or reactivated, was NOT accurately filing these security keys into the KEYS (#51) multiple. This unfortunately resulted in the system thinking that the user in fact possessed two entirely different keys. Therefore, routines XUMVIENU and XUMVINPA have been modified to ensure that the security keys are appropriately DINUM'd when entered into the KEYS (#51) multiple for the record entry in the NEW PERSON (#200) file, which will allow them to be correctly identified and displayed using the USER INQUIRY [XUSERINQ] menu option. Finally, as part of the post-install background process for this patch, MVI will also clean-up any existing erroneous 'PROVIDER' and 'XUORES' key entries currently found in the KEYS (#51) multiple in the NEW PERSON (#200) file. Issue #3 A problem was reported by the HealthShare Referral Management (HSRM) group that consults were NOT always being scheduled. After much research it was discovered that the "ADUPN" cross-reference (X-REF) on the ADUPN (#205.5) field in the NEW PERSON (#200) file was incorrectly defined to only capture the initial 30 characters of the ADUPN value instead of the entire defined field length maximum of 50 characters. The data dictionary (DD) for this field (#205.5) has now been updated to: 1. Capture the complete/entire "ADUPN" value in the "ADUPN" X-REF. 2. Standardize the ADUPN value when entered to lowercase. Finally, as part of the post-install background process, MVI will clean up the "ADUPN" X-REF so the correct values are represented and will also standardize the current ADUPN (#205.5) values in the NEW PERSON (#200) file so that they are now stored only as lowercase. UPDATED ADUPN DD: DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE ------------------------------------------------------------------------ 200,205.5 ADUPN 205;5 FREE TEXT Active Directory UPN INPUT TRANSFORM: K:$L(X)>50!($L(X)<3) X I $D(X) S X=$$LOW^XLFSTR (X) MAXIMUM LENGTH: 50 LAST EDITED: JAN 29, 2020 HELP-PROMPT: Answer must be 3-50 characters in length. This field should never be edited directly. DESCRIPTION: Identity and Access Management Active Directory User Principle Name (AD UPN) field. WRITE AUTHORITY: ^ NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER CROSS-REFERENCE: 200^ADUPN 1)= S ^VA(200,"ADUPN",$E(X,1,50),DA)="" 2)= K ^VA(200,"ADUPN",$E(X,1,50),DA) Index of entries by Active Directory UPN. Will be used by Identity and Access Management (IAM) Provisioning application when searching for and provisioning a VistA user to match the user with an Active Directory account. Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- NEW PERSON (#200) ADUPN (#205.5) MODIFIED 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*724 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*724 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 ------------------------------------------- 1. INC7642708 - Issue with NPI displaying for File 200 entries for Non-VA Provider import 2. INC7481785 - Key information missing when NON-VA Provider accounts are created by PSUSER,APPLICATION PROXY 3. INC9023514 - Provider data imported into VISTA, 7-30/8-17-19 by PSUSER,APPLICATION PROXY - duplicates 4. INC7957392 - e/ NON-VA PROVIDERS BEING DOWNLOADED WITH INCOMPLETE INFOMRATION BY PSUSER,APPLICATION PROXY 5. INC8428630 - Non-VA provider PIE/PPMS import issue (MVI team) 6. INC9398788 - PSUSER,APPLICATION PROXY created NON-VA PROVIDER accounts causing duplicates in the system - can't write med orders due to this Problem: -------- Several sites have logged tickets indicating that the NPI data that MVI was creating/storing for PPMS/PIE starting with the release of patch XU*8.0*711 is causing impacts/issues at their sites. **Note: Only around 50+ sites have currently had NPI data sent to them from PPMS/PIE. Resolution: ----------- Routine XUMVINPA has been updated to change the process of how NPI data is created/stored in the NEW PERSON (#200) file. As indicated above MVI will now update the EFFECTIVE DATE/TIME (#42) multiple, which then automatically triggers the 'AC' X-Ref that will then update additional NPI related NEW PERSON (#200) fields. In addition, MVI will address the existing entries at the sites by setting the EFFECTIVE DATE/TIME (#42) multiple and allowing the 'AC' X-Ref to execute making these NPIs now usable. ** NOTE: This will NOT address any duplicates already created or the DEA# (#53.2) NEW PERSON (#200) file issue. ** 7. INC9161486 - VISTA: SDAM APPT MGT -PSUSER,APPLICATION PROXY has automatically? assigned thousands of users access to an security key that is restricted Problem: -------- As part of supporting the PPMIS/PIE process in VistA, the Master Veteran Index (MVI) created the [XUS MVI ENRICH NEW PERSON] RPC so that NEW PERSON (#200) records could be added and/or updated, which includes assigning of the 'PROVIDER' and 'XUORES' security keys when the user is added and/or reactivated. Unfortunately, when these security keys were added to the KEYS (#51) multiple for the record in the NEW PERSON (#200) file the entries were NOT DINUM'd, causing the wrong keys to be displayed when viewed in the USER INQUIRY [XUSERINQ] menu option. Resolution: ----------- Routines XUMVIENU and XUMVINPA have been updated to ensure that when the 'PROVIDER' and 'XUORES' security keys are added to the KEYS (#51) multiple in the NEW PERSON (#200) file for the record that they are properly DINUM'd, which will allow them to be correctly identified and displayed when viewed using the USER INQUIRY [XUSERINQ] menu option. In addition, MVI will address any existing erroneous 'PROVIDER' and 'XUORES' key entries currently found in the KEYS (#51) multiple in the NEW PERSON (#200) file. 8. INC8765177 - HSRM Consults not going into scheduled status ADUPN Mis-Match Problem: -------- This issue was discovered by the HealthShare Referral Management (HSRM) group as their consults were NOT always being scheduled. It was determined that the "ADUPN" X-REF on the ADUPN (#205.5) field which their application relies on was incorrectly defined to capture only 30 characters instead of the entire maximum DD defined field length of 50 characters. Resolution: ----------- DD changes were made to the ADUPN (#205.5) field in the NEW PERSON (#200) file to capture the entire ADUPN (#205.5) field value of 50 characters when creating the "ADUPN" X-REF for the record entry. In addition, MVI will address/correct any existing erroneous entries currently stored in the "ADUPN" X-REF. Test Sites: ----------- Pittsburgh (PA) VAMC Tomah (WI) VAMC Patch Installation: Pre/Post Installation Overview ------------------------------ The post-installation process will task off the following clean-up processes to the background: - MVI will populate the EFFECTIVE DATE/TIME (#42) multiple field for existing entries in the NEW PERSON (#200) file, which will then automatically correct the associated NPI fields to make the NPI value usable. - MVI will clean-up existing erroneous 'PROVIDER' and 'XUORES' security key entries for records currently found in the KEYS (#51) multiple in the NEW PERSON (#200) file that have NOT been DINUM'D. - MVI will clean-up the existing 'ADUPN' cross-reference (X-REF) entries now that the X-REF will capture the entire 'ADUPN' value. In addition, existing ADUPN (Field #205.5) stored values will also be standardized to be [Lower Case]. Task Description: XU*8*724 post-install process for updating NPI in NEW PERSON (#200) file. Note: A single Mailman message will be generated to the installer and MVI developers to detail the results of the clean-up processes once they have all completed. 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 patch. 2. Choose the INSTALL/CHECK MESSAGE PackMan option. 3. From the Kernel Installation and Distribution System Menu, select the Installation Menu. From this menu, you may elect to use the following options. When prompted for the INSTALL enter the patch number (i.e. XU*8.0*724): a. Verify Checksums in Transport Global - This option will allow you to ensure the integrity of the routines that are in the transport global. b. Print Transport Global - This option will allow you to view the components of the KIDS build. c. 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 components of this patch, such as routines, DDs, templates, etc. d. Backup a Transport Global - This option will create a backup message of any routines exported with this patch. It will not backup any other changes such as DDs or templates. 4. From the Installation Menu, select the Install Package(s) option and choose the patch to install. 5. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//', respond NO. 6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', respond NO. 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO// respond NO. Post-Installation Instructions ------------------------------ Routine XU8P724 can be deleted once the tasked post-installation process to clean-up the several fields/X-REF in the NEW PERSON (#200) file has been completed. Back-Out Plan ------------- The back-out procedure for this KERNEL (XU) patch would consist of restoring the original routines using the back-up message created during the patch installation. The Data Dictionary (DD) changes are compatible with existing functionality in production and can remain there. 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 2 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: XU8P724 Before: n/a After: B32237361 **724** Routine Name: XUMVIENU Before:B277994868 After:B280103209 **711,724** Routine Name: XUMVINPA Before: B8194513 After: B9033340 **711,724** Routine list of preceding patches: 711 ============================================================================= User Information: Entered By : Date Entered : JAN 14, 2020 Completed By: Date Completed: MAR 16, 2020 Released By : Date Released : MAR 23, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT