$TXT Created by DEVCRN.DOMAIN.EXT (KIDS) on Wednesday, 08/17/22 at 13:11 ============================================================================= Run Date: OCT 05, 2022 Designation: MPIF*1*79 Package : MPIF - MASTER PATIENT INDEX VISTA Priority: Mandatory Version : 1 SEQ #75 Status: Released Compliance Date: OCT 17, 2022 ============================================================================= Associated patches: (v)MPIF*1*67 <<= must be installed BEFORE `MPIF*1*79' (v)MPIF*1*74 <<= must be installed BEFORE `MPIF*1*79' Subject: MASTER VETERAN INDEX VISTA ISSUE - REGISTER A PATIENT Category: - Routine Description: ============ NOTE: To prevent legacy systems ending up as Treating Facilities, MPIF* patches should NOT be installed on legacy systems or the FORUM CLAIMS system (since it is NOT a Veterans Affair Medical Center (VAMC) VistA system). MPIF*1.0*67 and MPIF*1.0*74 are the only required builds for patch MPIF*1.0*79. NOTE: Do NOT install MPIF*1.0*79 on legacy sites or on the FORUM CLAIMS system. The following issue being addressed in this patch is needed to correct a hard error from occurring when registering a new patient in the Veterans Health Information Systems and Technology Architecture (VistA) system where the newer types of addresses (Correspondence/Work) and/or phone numbers (Work/Cell) are the ONLY types included in the response from the Person Service Identity Management (PSIM) system for that record. Issue When executing the Register a Patient menu option [DG REGISTER PATIENT] and the response that is received from PSIM only contains the newer types of Addresses and/or Phone Numbers and NOT an original address or phone type then a hard system crash/error can occur as the current software logic doesn't know how to correctly parse/label/display these new field types. In addition, it was also determined that if both a new and old address and/or phone type are returned in the response from PSIM then the data may be labeled/displayed incorrectly. Therefore, the Master Patient Index (MPI) team has modified the parsing logic in routine MPIFXMLP and the display logic in MPIFVER to account for these new address and phone types so that when the data in the response from registering a patient is received from PSIM that it doesn't cause a hard error/crash to occur and that all the data for that patient record is labeled/displayed correctly, even if other unexpected types are received. 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 ------------------------------------------- INC23717314 - Vista issues- stack code error Problem: -------- Upon trying to register a certain patient in VistA a hard stack error occurs ($ZE= VALUE+1^MPIFXMLP *RETURN()) resulting in a crash/termination of the user's VistA instance session. Resolution: ----------- After analysis it was determined that the parsing logic hadn't been updated to handle the new address (Correspondence/Work) and phone (Work/Cell) types that could be received in the response from PSIM. If only new types were sent then an error could occur, but if both new and old types were sent then the fields could be labeled and displayed incorrectly. Therefore, MPI has updated the parsing logic in routine MPIFXMLP and the display logic in MPIFVER to account for these new address and phone types to prevent errors from occurring and ensuring the data is labeled/displayed correctly, even if unexpected types are received. Test Sites: ---------- Bronx VAMC (NY) Clarksburg VAMC (WV) 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, but it is recommended that installation occur during off hours to avoid collisions. The following OPTIONs should be disabled during installation: Load/Edit Patient Data [DG LOAD PATIENT DATA] Register a Patient [DG REGISTER PATIENT] Preregister a Patient [DGPRE PRE-REGISTER OPTION] Electronic 10-10EZ Processing [EAS EZ 1010EZ PROCESSING] UPDATE BATCH JOB FOR HL7 v2.3 [VAFC BATCH UPDATE] MPI/PD Patient Admin Coordinator Menu [RG ADMIN COORD MENU] Local/Missing ICN Resolution Background Job [MPIF LOC/MIS ICN RES] The HL7 incoming filers should be stopped. Use the Monitor, Start, Stop Filers [HL FILER MONITOR] option on the Filer and Link Management Options [HL MENU FILER LINK MGT] menu on the HL7 Main Menu [HL MAIN MENU]. 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. MPIF*1.0*79) 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 MPIF*1.0*79 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? Yes//', answer YES a. When prompted 'Enter options you wish to mark as 'Out Of Order':', select the following option: Option Name Menu Text ----------- --------- [DG LOAD PATIENT DATA] Load/Edit Patient Data [DG REGISTER PATIENT] Register a Patient [DGPRE PRE-REGISTER OPTION] Preregister a Patient [EAS EZ 1010EZ PROCESSING] Electronic 10-10EZ Processing [VAFC BATCH UPDATE] UPDATE BATCH JOB FOR HL7 v2.3 [RG ADMIN COORD MENU] MPI/PD Patient Admin Coordinator Menu [MPIF LOC/MIS ICN RES] Local/Missing ICN Resolution Background Job Press the Enter key when you are done selecting options. b. When prompted 'Enter protocols you wish to mark as 'Out Of Order':', press the Enter key. c. When prompted 'Delay Install (Minutes): (0 - 60): 0//', answer 0. Post-Installation Instructions ------------------------------ After patch installation has completed, restart the HL7 incoming filers. Use the Monitor, Start, Stop Filers [HL FILER MONITOR] option on the Filer and Link Management Options [HL MENU FILER LINK MGT] menu on the HL7 Main Menu [HL MAIN MENU]. Back-Out Plan ------------- This 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;MASTER PATIENT INDEX VISTA;**[Patch List]**;30 Apr 99;Build 2 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: MPIFVER Before: B62395107 After: B91571550 **61,62,65,66,67,79** Routine Name: MPIFXMLP Before:B106881898 After:B113981059 **61,67,74,79** Routine list of preceding patches: 74 ============================================================================= User Information: Entered By : Date Entered : JAN 19, 2022 Completed By: Date Completed: OCT 05, 2022 Released By : Date Released : OCT 05, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT