$TXT Created by DEVCRN.DOMAIN.EXT (KIDS) on Monday, 03/22/21 at 07:45 ============================================================================= Run Date: APR 27, 2021 Designation: DG*5.3*1042 Package : DG - REGISTRATION Priority: Mandatory Version : 5.3 SEQ #914 Status: Released Compliance Date: MAY 28, 2021 ============================================================================= Associated patches: (v)DG*5.3*856 <<= must be installed BEFORE `DG*5.3*1042' (v)DG*5.3*1013 <<= must be installed BEFORE `DG*5.3*1042' (v)DG*5.3*1026 <<= must be installed BEFORE `DG*5.3*1042' (v)DG*5.3*1033 <<= must be installed BEFORE `DG*5.3*1042' Subject: MASTER VETERAN INDEX VISTA ENHANCEMENTS - TFL UPDATES Category: - Enhancement (Mandatory) - Routine - Data Dictionary - Other Description: ============ DG*5.3*856, DG*5.3*1013, DG*5.3*1026 and DG*5.3*1033 are the required builds for patch DG*5.3*1042. The following enhancements exported in this patch are being implemented in continued support of the Master Patient Index (MPI). Enhancement #1 MPI has enhanced the existing Remote Procedure Call (RPC) [VAFCTFU GET TREATING LIST] in routine VAFCTFU1 to ensure that ONLY VistA treating facilities are now returned for the specified Patient DFN (Data File Number). Treating facilities containing any of the following conditions will now be skipped/ignored and NOT returned in the call: - FACILITY TYPE (#13 INSTITUTION (#4) file) of "OTHER" - STATION NUMBER (#99 INSTITUTION (#4) file) of 200 or 200M - SOURCE ID TYPE (#.09 TREATING FACILITY LIST (#391.91) file) has a value other than PI (Patient Internal Identifier) Enhancement #2 MPI has enhanced the existing RPC [VAFC VOA ADD PATIENT] in routine VAFCPTAD to ensure that when a Zip Code is passed to the site that MPI will automatically retrieve the County value using the supported KERNEL Application Programming Interface (API) call POSTAL^XIPUTIL and store the resulting County value in the COUNTY (#.117) field in the PATIENT (#2) file. NOTE: COUNTY (Field #.117) will only be added to the PATIENT (#2) file when the State value passed into the RPC is also defined, which is due to the requirements dictated in the input transform of the COUNTY (#.117) field. Enhancement #3 The following changes detailed below are in support of the impending release of Enterprise User Identity functionality in a future patch to allow MPI to handle persons similarly to patients. - Creation of the new file NEW PERSON TREATING FACILITY LIST (#391.92) to store the list of treating facilities where the NEW PERSON (#200) is known. Specifically, it will store the treating facility when there is ONLY a local NEW PERSON (File #200) entry and NOT a local PATIENT (File #2) entry in the Treating Facility Update (MFN) Health Level Seven (HL7) message. GLOBAL MAP DATA DICTIONARY #391.92 -- NEW PERSON TREATING FACILITY LIST FILE CROSS REFERENCED BY: PERSON(B) INDEXED BY: SOURCE ID & SOURCE ID TYPE & ASSIGNING AUTHORITY & INSTITUTION (AISS), PERSON & INSTITUTION (APAT) ^DGCN(391.92,D0,0)=(#.01) PERSON [1P:200] ^ (#.02) INSTITUTION [2P:4] ^ (#.03) SOURCE ID [3F] ^ (#.04) SOURCE ID TYPE [4S] ^ (#.05) ASSIGNING AUTHORITY [5F] ^ (#.06) IDENTIFIER STATUS [6S] ^ NOTE: Should the NEW PERSON (#200) entry later become a PATIENT (#2) (ie. goes to Employee Health for instance), then the incoming Treating Facility Update (MFN) HL7 messages will be filed into the TREATING FACILITY LIST (#391.91) file instead. Any existing information for this individual in the NEW PERSON TREATING FACILITY LIST (#391.92) file will then be ignored and may be targeted for clean-up in a future release. - Processing of the broadcasted Treating Facility Update (MFN) HL7 messages on VistA will be modified to ensure that the facility is processed into the correct treating facility list file. Therefore if the incoming Integration Control Number (ICN) is known in the PATIENT (#2) file then it will continue to process into the TREATING FACILITY LIST (#391.91) as before (Routine VAFCTFIN), else it will process into the NEW PERSON TREATING FACILITY LIST (#391.92) through the new capabilities (File/Update/Delete) introduced in the new routine VAFCTFNP when ONLY known to the NEW PERSON (#200) file. - Finally, the existing RPC [VAFC LOCAL GETCORRESPONDINGIDS] has been augmented to also retrieve/return the treating facilities from the NEW PERSON TREATING FACILITY LIST (#391.92) file when the requested identifier values are NOT known in the TREATING FACILITY LIST (#391.91) file, which indicates that this individual is ONLY known to the NEW PERSON (#200) file. Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- NEW PERSON TREATING N/A *NEW FILE FACILITY LIST (#391.92) 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 --------------------------- -------------------- VAFC LOCAL GETCORRESPONDINGIDS Modified 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 ------------------------------------------- N/A Test Sites: ---------- Hampton VAMC (Hampton VA) Northport VAMC (Northport NY) Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. 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. MPI/PD VistA Documentation can also be found on the VA Software Documentation Library at: http://www.domain.ext/vdl/application.asp?appid=16 Documentation Title File Name --------------------------------------------------------------------- MPI/PD VISTA Technical Manual DG_5_3_P1042_TM.PDF DG_5_3_P1042_TM.DOC 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. 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. DG*5.3*1042) 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 DG*5.3*1042 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: Build 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 ------------------------------ 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 routines and RPC using the back-up message created during the patch installation. The NEW routine (VAFCTFNP) and FILE (NEW PERSON TREATING FACILITY LIST (#391.92)) 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: ;;5.3;Registration;**[Patch List]**;Aug 13, 1993;Build 5 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: VAFCPTAD Before:B109307880 After:B114621009 **149,800,876,944,950,955,1033,1042** Routine Name: VAFCTFIN Before: B89934930 After: B94813918 **428,474,520,639,707,800,821, 837,863,1013,1042** Routine Name: VAFCTFNP Before: n/a After: B48058643 **1042** Routine Name: VAFCTFU1 Before: B11999906 After: B15999262 **261,392,448,449,800,856,1042** Routine Name: VAFCTFU2 Before: B50067513 After: B59958600 **821,856,863,981,1026,1042** Routine list of preceding patches: 1013, 1026, 1033 ============================================================================= User Information: Entered By : Date Entered : DEC 10, 2020 Completed By: Date Completed: APR 27, 2021 Released By : Date Released : APR 27, 2021 ============================================================================= Packman Mail Message: ===================== $END TXT