$TXT Created by A at CHY0016.FO-BAYPINES.DOMAIN.EXT (KIDS) on Wednesday, 07/29/26 at 16:04 ============================================================================= Run Date: AUG 25, 2026 Designation: GMRC*3*210 Package : GMRC - CONSULT/REQUEST TRACKING Priority: Mandatory Version : 3 SEQ #174 Status: Released Compliance Date: SEP 25, 2026 ============================================================================= Subject: FILE 123 WHO ENTERED ACTIVITY FIELD DATA CLEAN-UP FOR SD APPOINTMENTS Category: - Other - Routine Description: ============ Patch GMRC*3.0*210 contains a post-installation process to fix REQUEST PROCESSING ACTIVITY (#40) sub-file records from the REQUEST/CONSULTATION (#123) file that were created from a SCHEDULING (SD) package process after January 24th, 2024 and up to the date Patch GMRC*3.0*210 is installed. These records have a WHO ENTERED ACTIVITY (#4) field for the REQUEST PROCESSING ACTIVITY (#40) sub-file created during the appointment scheduling process that is different from the actual user who had performed the action based on the associated SDEC APPOINTMENT (#409.84) file record. The functionality that created this data issue has since been corrected on the SD package's side. This clean-up process will look for SDEC APPOINTMENT (#409.84) records created within the aforementioned date range with the APPT REQUEST TYPE (#.22) field value of CONSULT. Of those records, the post-installation will look for REQUEST PROCESSING ACTIVITY (#40) sub-file records in file #123 with a DATE/TIME OF ACTION ENTRY (#.01) field that matches either the DATE APPT MADE (#.09) field, the NOWSHOW DATETIME (#.101) field, or the CANCEL DATETIME (#.12) field from the associated SDEC APPOINTMENT (#409.84) file entry and a WHO ENTERED ACTIVITY (#4) field that is different from either the DATA ENTRY CLERK (#.08) field, the NOSHOW BY USER (#.102) field, or the CANCELLED BY USER (#.121) field, respectively. For any mismatches, the REQUEST PROCESSING ACTIVITY (#40) sub-file's WHO ENTERED ACTIVITY (#4) field will be overwritten with the current user field from the SDEC APPOINTMENT (#409.84) file based on the type of activity, since file #409.84 will be the source of truth. A description of the update and the before/after values will be stored into an ^XTMP global. This data clean-up process will be tasked off to run at midnight on the day it is installed to limit impact on the system. EHRM Impact Statement: ---------------------- This patch should have no EHRM impact, and can be installed at all sites, including EHRM converted sites. 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: ----------------------- Blood Bank Coordination: N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- JIRA tasks: =========== 1) VSE-8729: VistA: Create a Post install to clean up Scheduled user in consults Problem: -------- Due to a leaking variable issue in GMRCGUIB some consults were marked with the wrong Schedule user. A clean up is needed to go through the SDEC APPOINTMENT (#409.84) file for all CONSULT appointments created after January 24, 2024. Resolution: ----------- The GMRC*3.0*210 post-installation process will search for these inaccurate records and update the WHO ENTERED ACTIVITY (#4) field for the appropriate REQUEST PROCESSING ACTIVITY (#40) sub-file entries from the REQUEST/CONSULTATION (#123) file to contain the correct scheduling user. An ^XTMP record will also be generated for each update to contain the before/after values. Test Sites: ----------- Omaha, NE (OMA) Lebanon, PA (LEB) Test Sites - SNOW Change Order #: --------------------------------- Omaha, NE (OMA): CHG0768046 Lebanon, PA (LEB): CHG0769053 Software and Documentation Retrieval Instructions: -------------------------------------------------- This patch is being distributed as a PackMan message. Patch Installation: ------------------- Pre/Post Installation Overview: Pre-Installation Instructions: ------------------------------ The data clean-up process will be tasked off to run at midnight of the day it's installed, so it's okay to install during normal business hours. Installation will take less than 5 minutes. Setup/Configuration Instructions: --------------------------------- This patch may be installed with users on the system and should take less than 5 minutes to install. 1. Choose the PackMan message containing this patch. 2. Choose the INSTALL/CHECK MESSAGE PackMan option. 3. From the KIDS Menu, select the Installation Menu. From this menu, you may elect to use the following options. When prompted for the INSTALL NAME, enter GMRC*3.0*210. a. Backup a Transport Global - This option will create a backup message of any components exported with this patch. You are prompted to select "R" for Routines or "B" for Build. For this patch, backing up the "B"uild is suggested. Select one of the following: B Build R Routines Enter response: Build b. 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 (routines, DDs, templates, etc.). c. Verify Checksums in Transport Global - This option will allow you to ensure the integrity of the routines that are in the transport global. 4. From the Installation Menu, select the Install Package(s) option and when prompted for the INSTALL NAME, enter GMRC*3.0*210. 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. If prompted "Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//" respond NO. 8. If prompted "Delay Install (Minutes): (0 - 60): 0//" respond 0. Post-Installation Instructions ------------------------------ The installer will receive a MailMan message with the results of the data clean-up. No action is required though. Back-Out/Roll Back Plan: ------------------------ Due to the complexity of this patch, it is not recommended for back-out, and a restore from a backup of the Transport Global should not be attempted. In the event that this patch needs to be backed out, the patch installer should enter a ServiceNow Ticket. The development team will need to issue a follow-up patch in order to comprehensively back-out this patch. Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;CONSULT/REQUEST TRACKING;**[Patch List]**;DEC 27, 1997;Build 8 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: GMRCP210 Before: n/a After: B23824902 **210** ============================================================================= User Information: Entered By : Date Entered : NOV 13, 2024 Completed By: Date Completed: AUG 25, 2026 Released By : Date Released : AUG 25, 2026 ============================================================================= Packman Mail Message: ===================== $END TXT