$TXT Created by DEVCRN.DOMAIN.EXT (KIDS) on Tuesday, 06/01/21 at 08:21 ============================================================================= Run Date: JUL 14, 2021 Designation: DG*5.3*1050 Package : DG - REGISTRATION Priority: Mandatory Version : 5.3 SEQ #921 Status: Released Compliance Date: AUG 14, 2021 ============================================================================= Associated patches: (v)DG*5.3*981 <<= must be installed BEFORE `DG*5.3*1050' (v)DG*5.3*985 <<= must be installed BEFORE `DG*5.3*1050' (v)DG*5.3*1042 <<= must be installed BEFORE `DG*5.3*1050' Subject: MASTER VETERAN INDEX VISTA ENHANCEMENT - ADDITIONAL TFL UPDATE Category: - Routine - Enhancement (Mandatory) - Other - Data Dictionary Description: ============ NOTE: Master Veteran Index (MVI) enhancements are being distributed in two VistA namespaces: DG and MPIF. Patches DG*5.3*1050 and MPIF*1.0*77 can be installed in any order as there are NO dependencies between these patches. DG*5.3*981, DG*5.3*985 and DG*5.3*1042 are the required builds for patch DG*5.3*1050. The following enhancements exported in this patch are being implemented in continued support of the Master Veteran Index (MVI) Proxy Patient Add and the Enterprise User Identity Treating Facility List (TFL) update processes. Enhancement #1 Enhancements were made in support of MVI's new Enterprise User Identity functionality recently released in DG*5.3*1042 to ensure that when an individual is known as a NEW PERSON (File #200, ie. employee, visitor) and then subsequently becomes a PATIENT (File #2) that their existing Treating Facilities are subsequently removed from the NEW PERSON TREATING FACILITY LIST (#391.92) file. - The processing of the treating facility (correlation) updates on VistA in routine VAFCTFIN was modified to delete all correlations associated with an Integration Control Number (ICN) from the NEW PERSON TREATING FACILITY LIST (#391.92) file when that ICN is known in 'BOTH' the PATIENT (#2) and NEW PERSON (#200) files. - Also, routine VAFCTFNP was modified to perform the actual deletion of the entries in the NEW PERSON TREATING FACILITY LIST (#391.92) file. Enhancement #2 The existing Remote Procedure Call (RPC) [VAFC VOA ADD PATIENT] that is invoked to Proxy Add an entry to the PATIENT (#2) file has been enhanced to properly handle the situation when a 'Postal Code' is passed, but NOT the 'Province'. In this situation, the wrong value (such as 'ZIP+4') can be filed into the POSTAL CODE (#.1172) field which can cause the patient to NOT get added if the data is rejected. Therefore, modifications were made to enhance routine VAFCPTAD to allow the POSTAL CODE (#.1172) value to be validated and filed in the PATIENT (#2) file during creation regardless of whether the PROVINCE (#.1171) value is passed. Finally, the Patient record will be now always be created as long as all of the required identifiers are passed and valid. Optional valid field values will also be added, whereas values that are determined to be invalid will now be ignored. Enhancement #3 MVI has created a new Application Programming Interface (API) in routine VAFCCRNR (ie. $$CRNSITE^VAFCCRNR) that accepts a site's Station Number to determine via a lookup on the "ACRNR" cross-reference (X-REF) in the EHRM MIGRATED FACILITIES (#391.919) file on whether or not that site has migrated to CERNER (ie. Is Cerner Enabled). Therefore, the API call will return a '1' if the site has migrated, else a '0' will be returned. Note: If additional information is required, see REGISTRATION Patch DG*5.3*981 for additional information on how MVI maintains CERNER Enabled sites in VistA. Packages can request access to this interface by creating (if one does not already exist) and/or subscribing to the Controlled Integration Agreement (IA) if they will need to determine if a site has migrated to the CERNER application. Enhancement #4 Upon release of REGISTRATION patch DG*5.3*985, a change was made to the PREFERRED NAME (#.2405) field in the PATIENT (#2) file that prevented this value from being deleted through the setting of the "DEL" node in the Data Dictionary (DD). However, the message displayed which requests the user to contact their MVI Point of Contact (POC) to log a request to delete this value is NOT accurate as MVI can no longer delete this value either due to the DD change implemented to this field. Therefore, MVI has modified the DELETE TEST message by removing the last sentence, as no one or any process will be able to remove/delete this field value. Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- PATIENT (#2) PREFERRED NAME (#.2405) 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 --------------------------- -------------------- VAFC VOA ADD PATIENT 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 ------------------------------------------- 1. INC17273244 / INC17365532 - No Patient record in VistA Problem: -------- A record is being added then subsequently deleted when there is bad data being sent for updating non-required fields in the PATIENT (#2) file during the creation of the file record entry using the Remote Procedure Call (RPC) [VAFC VOA ADD PATIENT]. Resolution: ----------- Software changes were implemented to ensure that the record entry is now created in the PATIENT (#2) file initially using the required fields ONLY. A second subsequent call will then be made to update any additional optional fields sent to the RPC. This will correct the issue of the record being created and then immediately deleted from the PATIENT (#2) file. In addition, another software bug resulting in a data issue where a foreign address is sent, but no province value is passed causing some data to be filed in the wrong fields will also be corrected. 2. INC17983064 - Unable to 'Delete' Preferred Name Problem: -------- After analysis it was determined that an update to the PREFERRED NAME field (#.2405) in the PATIENT (#2) file to prevent the preferred name value from being deleted occurred by setting the 'DEL' node in the DD when this field was distributed in the released REGISTRATION patch DG*5.3*985. This change occurred without MVIs knowledge and/or approval even though the deletion message prompt indicates to contact MVI to create a request to have it removed, which can no longer occur due to this change. Resolution: ----------- The DELETE TEST text in the Data Dictionary (DD) for the PREFERRED NAME (#.2405) field in the PATIENT (#2) file has been updated to remove/delete the last sentence about contacting the MVI Point of Contact (POC) to request they create a Toolkit (TK) request to have this value removed, as the discussions with the business owners led to the decision that no one or process will be allowed to remove this value. Test Sites: ---------- Clarksburg VAMC (Clarksburg WV) Tuscaloosa VAMC (Tuscaloosa AL) 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 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*1050) 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*1050 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, DD and RPC using the back-up message created during the patch installation. Note: The DD and RPC changes were help/description changes ONLY, so backing out isn't critical to restoring system functionality. 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 2 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: VAFCCRNR Before: B4581659 After: B5042521 **981,1050** Routine Name: VAFCPTAD Before:B114621009 After:B162829499 **149,800,876,944,950,955,1033, 1042,1050** Routine Name: VAFCTFIN Before: B94813918 After: B98642902 **428,474,520,639,707,800,821, 837,863,1013,1042,1050** Routine Name: VAFCTFNP Before: B48058643 After: B53250026 **1042,1050** Routine list of preceding patches: 981, 1042 ============================================================================= User Information: Entered By : Date Entered : MAR 24, 2021 Completed By: Date Completed: JUL 14, 2021 Released By : Date Released : JUL 14, 2021 ============================================================================= Packman Mail Message: ===================== $END TXT