============================================================================= Run Date: APR 16, 2024 Designation: IVM*2*214 Package : IVM - INCOME VERIFICATION MATCH Priority: EMERGENCY Version : 2 SEQ #179 Status: Released Compliance Date: APR 17, 2024 ============================================================================= Associated patches: (v)IVM*2*204 <<= must be installed BEFORE `IVM*2*214' (v)IVM*2*210 <<= must be installed BEFORE `IVM*2*214' Subject: CHANGES FOR PHONE NUMBER [WORK] Category: - Enhancement (Emergency) - Routine - PATCH FOR A PATCH Description: ============ ************************************************************************** ************************************************************************** IMPORTANT NOTE: Due to the Service Now Ticket INC31532264, an emergency defect fix is included in the IVM*2.0*214 patch. DG*5.3*1111 is also being released as an emergency patch. This defect impacts Registration (DG) options and causes the Z05 and Z07 ORU/ORF HL7 message transmission to error. Please read the Pre- and Post-Installation Instructions carefully since this is not a regular DG and Income Verification Match (IVM) patch. See the DG*5.3*1111 patch description for details. The national release date is April 16, 2024, with a one-day compliance period. This patch must be installed at all VistA sites by close of business on Tuesday, April 17, 2024. ************************************************************************** ************************************************************************** Veterans Health Information Systems and Technology Architecture (VistA) Registration, Eligibility & Enrollment (REE) patch IVM*2.0*214 is being released to support enhancements for the Eligibility and Enrollment (E&E) program. Patch IVM*2.0*214 is also being released in support of the Veterans Health Administration (VHA) Enrollment System (VES) 6.9 release. IVM*2.0*214 is being released with DG*5.3*1111 in Host File DG_53_P1111.KID. Patch IVM*2.0*214 disables the PHONE NUMBER [WORK] data elements in the Income Verification Match (IVM) Demographics Upload [IVM UPLOAD DEM] option and directly uploads the PHONE NUMBER [WORK] field (#.132) and the PHONE [WORK] CHANGE DT/TM field (#.1326) to the PATIENT file (#2). Patch IVM*2.0*214 fixes a defect where the FATHER'S NAME (SEQ 6) and MOTHER'S NAME (SEQ 7) in the ZPD segment of ORF/ORU-Z05 Health Level 7 (HL7) message were not being transformed from HL7 format to FileMan format prior to being stored in the database. Listing of Updates: =================== This patch makes the following enhancements to VistA REE: 1. Disable Work Phone data elements in the IVM Demographics Upload [IVM UPLOAD DEM] option as the application will not allow VistA to automatically file the PHONE NUMBER [WORK] field (#.132) and the PHONE [WORK] CHANGE DT/TM field (#.1326) to the PATIENT file (#2) when processing ORU~Z05 Health Level 7(HL7) messages from VES. 2. Directly upload the Work Phone data elements PHONE NUMBER [WORK] field (#.132) and PHONE [WORK] CHANGE DT/TM field (#.1326) into the PATIENT file (#2) when received ORU~Z05 Health Level 7(HL7) messages from VES if the conditions listed below are met: a. The Change Date/Time of the incoming Work Phone Number is not null. b. The Change Date/Time of the incoming Work Phone Number from VES is more recent than the VistA Change Date/Time of the Work Phone Number. 3. Add a new record to the IVM DEMOGRAPHIC UPLOAD FIELDS file (#301.92). The new record will contain the following data: NUMBER: 231 DHCP FIELD NAME: WORK NUMBER CHANGE DT/TM HL7 LOCATION: RF171PW UPLOADABLE DEMOGRAPHIC FIELD: YES DHCP FILE: PATIENT DHCP FIELD NUMBER: .1326 TRANSFORM IVM DATA: YES TRANSFORM DHCP DATA: YES ADDRESS FIELD?: YES DHCP LOCATION LOGIC: S DR=.1326 D LOOK^IVMPREC9 DHCP OUTPUT LOGIC: S DR=.1326 D LOOK^IVMPREC9 4. Changed a record in IVM DEMOGRAPHICS UPLOAD FIELDS file (#301.92). The modified record will contain the following data: NUMBER: 150 DHCP FIELD NAME: PHONE NUMBER [WORK] HL7 LOCATION: PID13W UPLOADABLE DEMOGRAPHIC FIELD: YES DHCP FILE: PATIENT DHCP FIELD NUMBER: .132 ADDRESS FIELD?: YES DHCP LOCATION LOGIC: S DR=.132 D LOOK^IVMPREC9 DHCP OUTPUT LOGIC: S DR=.132 D LOOK^IVMPREC9 Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File Number 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: ----------------------- N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- Jira VES-40655: Z07's failing with generic 'null' exception. Problem: ------- INC31532264 Hot Springs reported on 2/21/2024 that the Catastrophic Disability data did not transmit to the Health Eligibility Center (HEC). Further analysis and investigation found that the ZPD segment of the Z05 and Z07 HL7 messages had the FATHER'S NAME and MOTHER'S NAME in the wrong format. The following line in routine IVMPREC8 was accidentally removed in a previous patch release (DG*5.3*1085 and IVM*2.0*210, nationally released 2/27/2023): I IVMXREF["ZPD06"!(IVMXREF["ZPD07") S IVMFLD=$$FMNAME^HLFNC(IVMFLD) This line calls Application Program Interface (API) FMNAME^HLFNC to convert the name component from the Z05 HL7 message in the HL7 format that has the "~" delimiter to FileMan format with the "," and space delimiter. The missing line of code caused the name component of the Father's and Mother's name to be filed in the HL7 format in the FATHER'S NAME field (#.2401) and MOTHER'S NAME field (#.2402) of the Patient file (#2). Example screen capture of wrong format: FATHER'S NAME: DOE~JOE~N~~~~~~~ MOTHER'S NAME: DOE~JANE~MARY~REEVES~~~REEVES~~~REEVES Correct FileMan DHCP format should be: FATHER'S NAME: DOE, JOSEPH N MOTHER'S NAME: DOE, JANE MARY REEVES Z07 from VistA should be in FileMan format with "," and " " delimiter: ZPD^1^^^^^TEST,FATHER MIDDLE SUFFIX^TEST,MOTHER MIDDLE SUFFIX^""^""^^0^""^""^^^^""^^0^^^^^^^^^^^X^""^""^""^""^""^^^^^""^""^""^""^ ""^"" Z07 from VistA that is in the incorrect HL7 format with the "~" delimiter: ZPD^1^^^^^TEST~FATHER~MIDDLE^SUFFIX~~^TEST~MOTHER~MIDDLE~SUFFIX~~^""^""^^0 ^""^""^^^^""^^0^^^^^^^^^^^X^""^""^""^""^""^^^^^""^""^""^""^""^" Options Impacted: Register a Patient [DG REGISTER PATIENT] Load/Edit Patient Data [DG LOAD PATIENT DATA] Preregister a Patient [DGPRE PRE-REGISTER OPTION] Eligibility Verification [DG ELIGIBILITY VERIFICATION] Enter a Request/Notification [FBCH ENTER REQUEST] Sample screen capture that displays the Father's Name and Mother's Name: PATIENT DATA, SCREEN <2> RHHQHT,ZDJELHA I #### ##,#### NON-VETERAN (OTHER) ========================================================================== ===== [1] Marital: MARRIED POB: CHARLSTON, SOUTH CAROLINA Religion: UNKNOWN/NO PREFERENCE Father: DOE~JOHN~N~~~~~~~ SCI: NOT APPLICABLE Mother: DOE~JANE~SMITH~REEVES~ Mom's Maiden: MPIMMW, Any user entering data in any of the options that triggers a Z07 HL7 message would be impacted if there are values in the Father's and Mother's name fields. Since the format of the names are wrong in the outgoing Z07 HL7 message, this causes issues in VES. If the VES HL7 message builder looks for the delimiter of a ",", it would keep concatenating a "~" after the name since no comma "," is found. In some cases, this caused an exceeding character limit errors, thus preventing the Z07 message from being filed. This caused an infinite loop between Z07/Z05 message due to the wrong format being filed and stored from the Z05 HL7 message and the wrong name format to be sent in the outgoing Z07 message. The API OPD^VADPT, a supported API, was impacted since this returned the other patient information. Screen capture sample: >D OPD^VADPT >ZW VAPD VAPD(1)="CHARLSTON" VAPD(2)="45^SOUTH CAROLINA" VAPD(3)="DOE~JOHN~N~~~~~~~" VAPD(4)="DOE~JANE~MARY~REEVES~~~REEVES~~~REEVES" Resolution: ----------- With patch IVM*2.0*214 the processing of the FATHER'S NAME and MOTHER'S NAME fields of the ZPD segment of the ORF/ORU-Z05 message will be restored to transform the data from HL7 format to FileMan format. The fix in IVM*2.0*214 is to restore the missing line of code and add a minor change to retrieve the first four pieces of the name component: LAST NAME~FIRST NAME~MIDDLE^SUFFIX for the conversion. Once the patches DG*5.3*1111 and IVM*2.0*214 are installed and compliant at all 130 facilities on 4/16/2024, VHA ENROLLMENT SYSTEM (VES) will execute a script that will generate Z05 HL7 messages to do a mass cleanup of the values in the FATHER'S NAME field (#.2401) and MOTHER'S NAME field (#.2402) in the Patient file (#2) for all 130 facilities. Test Sites: ----------- VA Tennessee Valley Health Care System (Nashville, Murfreesboro) Edward Hines Jr. VA Hospital Hines, IL Boise VA Medical Center, ID Test Sites - SNOW Change Order #: --------------------------------- VA Tennessee Valley Health Care System: CHG0469954 Edward Hines Jr. VA Hospital: CHG0469775 Boise VA Medical Center: CHG0470193 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released using a host file. The host file is available at the following location: /srv/vista/patches/SOFTWARE/DG_53_P1111.KID Documentation describing the new functionality is included in this release. Documentation can be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/. Documentation can also be obtained at https://download.vista.domain.ext/index.html/SOFTWARE Documentation Title File Name --------------------------------------------------------------------- DG_53_P1111.KID Release Notes DG_5_3_P1111_RN.PDF IVM Version 2 Technical Manual IVM_2_TM.PDF Patch Installation: ------------------- Pre/Post Installation Overview: ------------------------------- The post-install routine POST^IVM20214P performs the following action: - Queues off a background job to delete replace all instances of PHONE NUMBER [WORK] entries from IVM PATIENT (#301.5) file. - Upon successful completion of the job, a MailMan message is sent to the Postmaster. This message contains statistics of the job, including Number of PHONE NUMBER [WORK] entries deleted from IVM PATIENT (#301.5) file. - The statistics as well as the list of DFNs of the records that were modified is captured in the ^XTMP("IVM20214P" global. The MailMan message will include information on where to view that list. See an example of the message in the 'Post-Installation Instructions' section. The data in the ^XTMP("IVM20214P" global will be purged after 60 days. Pre-Installation Instructions: ------------------------------ Please refer to the DG*5.3*1111 patch description for pre-installation instructions. Installation Instructions: -------------------------- Please refer to the DG*5.3*1111 patch description for installation instructions. Post-Installation Instructions: ------------------------------- IMPORTANT NOTE: Do not do the following step until you have received the MailMan message indicating the successful completion of the IVM20214 post-installation background job. A sample of that message is shown below. - The post-installation routine IVM20214P should be manually deleted from your system using the KERNEL option Delete Routines [XTRDEL]. Below is a sample of the MailMan message upon the completion of the post-installation job which is sent to the patch installer. Subj: IVM*2.0*214-CLEANUP OF PHONE NUMBER [WORK] ENTRIES IN (#301.5) [#508088] 01/17/24@09:10 14 lines From: POSTMASTER In 'IN' basket. Page 1 ----------------------------------------------------------------------- The job completed to clean PHONE NUMBER [WORK] records in the IVM PATIENT (#301.5) File. ^XTMP("IVM20214P" global contains deleted records for reference and the format is DFN^IEN OF #301.5^IEN OF SUBFILE #301.501^IEN OF SUBFILE #301.511 ^PHONE NUMBER[WORK]. Job Results: ------------ Facility Name: ZZ DUP ALBANY.DOMAIN.EXT Station Number: 500 The process statistics: Job Start Date/Time: JAN 17, 2024@09:10:10 Job End Date/Time: JAN 17, 2024@09:10:10 Total PHONE NUMBER [WORK] records deleted: 391 NOTE: The global ^XTMP("IVM20214P") will be purged after 60 days. Please refer to the additional Post VES Data Cleanup instructions in the patch description of patch DG*5.3*1111. Back-Out/Roll Back Plan: ------------------------ Please refer to the DG*5.3*1111 patch description for the Back-Out/Roll Back Plan. Routine Information: ==================== The second line of each of these routines now looks like: ;;2.0;INCOME VERIFICATION MATCH;**[Patch List]**;21-OCT-94;Build 15 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: IVM20214P Before: n/a After: B29536287 **214** Routine Name: IVMPREC6 Before:B206466106 After:B214040173 **3,4,12,17,34,58,79,102,115, 140,144,121,151,152,165,167, 171,164,188,192,193,204,214** Routine Name: IVMPREC8 Before:B298899885 After:B286209815 **5,6,12,58,73,79,102,115,121, 148,151,152,168,167,171,164, 188,187,210,214** ============================================================================= User Information: Entered By : Date Entered : DEC 18, 2023 Completed By: Date Completed: APR 16, 2024 Released By : Date Released : APR 16, 2024 ============================================================================= Packman Mail Message: ===================== No routines included