$TXT Created by at CPRSNGUIB.DOMAIN.EXT (KIDS) on Monday, 09/29/25 at 14:42 ============================================================================= Run Date: MAY 06, 2026 Designation: TIU*1*369 Package : TIU - TEXT INTEGRATION UTILITIES Priority: Mandatory Version : 1 SEQ #336 Status: Released Compliance Date: JUN 06, 2026 ============================================================================= Associated patches: (v)TIU*1*110 <<= must be installed BEFORE `TIU*1*369' (v)TIU*1*232 <<= must be installed BEFORE `TIU*1*369' (v)TIU*1*338 <<= must be installed BEFORE `TIU*1*369' (v)TIU*1*346 <<= must be installed BEFORE `TIU*1*369' (v)TIU*1*357 <<= must be installed BEFORE `TIU*1*369' Subject: TIU TEXT ALERT DELETE AND HARD ERROR FIXS Category: - Routine - Data Dictionary Description: ============ This patch addresses the following issues: 1. INC24223358 - TIU-1662 - A defect was found in how VistA handles removing alerts for TIU Text Event Alerts 2. INC39192675 - TIU-2084 - Getting logged off of VistA in the middle of running a report - TIU COPY/PASTE TRACKING REPORT DETAIL1+122^TIUCOPR1 ^DPT("") 3. INC39470303 - TIU-2094 - BLD+7^TIUSRVT3 ^TIU(8927,"") occurring nightly when the auto-deactivate option runs 4. INC39986468 - TIU-2103 - ORPHAN+8^TIUFLF4 *Y error running a FM report from 8925.1 to look for documents with ORPHAN=YES 5. INC34507410 - TIU-2104 - Description discrepancies for START OF ADD SGNR ALERT PERIOD field in TIU BASIC PARAMETERS in Vista 6. N/A - TIU-2095 - ICR 10060 Violation - direct global read ^VA(200,IEN) in TIUSRVT3 7. N/A - TIU-2099 - ICR Violations in TIUCOPR1 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 ------------------ ------------------- -------------------- TIU PARAMETERS (#8925.99) START OF ADD SGNR ALERT Modified PERIOD (#3.1) 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 1. INC24223358 - TIU-1662 - A defect was found in how VistA handles removing alerts for TIU Text Event Alerts Problem: -------- TIU text alerts are being deleted on TIU notes that have an addendum attached that includes the text alert search word. If you create a note with the search word, and attached an addendum with the search term, the alert will be deleted, and no attached team will receive the alert. Resolution: ----------- Mumps code has been modified so that when an addendum is attached, the alert will not be deleted. CPRS users will now be able to have the note and addendum contain the TIU text alert words without risk of the alert being deleted. 2. INC39192675 - TIU-2084 - Getting logged off of VistA in the middle of running a report - TIU COPY/PASTE TRACKING REPORT DETAIL1+122^TIUCOPR1 ^DPT("") Problem: -------- When running the Copy/Paste Tracking Report (Export) [TIU COPY/PASTE TRACKING REPORT] option an error may occur. This is caused by a value that points to a non-existent entry in a file. One potential cause of this has been found to involve the way the Computerized Patient Record System (CPRS) captures and saves copy/paste information. It has been Determined that a user may copy data from one system and paste it into another system. When this occurs, the captured data from the copy from system is stored the same way a local copy would be. This means the copy data would be invalid for the current system and may be identified incorrectly in the Copy/Paste Tracking Report or may point to non-existent entries on the current system which may cause the reported error to occur. Resolution: ----------- This patch only intends to prevent errors from occurring when running the Copy/Paste Tracking Report caused by a pointer to a non-existent entry. As such, routine TIUCOPR1 was modified to include more defensive programming to handle situations such as this. In the future, it is expected a CPRS GUI release will include modifications to correct the way data captured from one system is stored for copy/paste identification to properly indicate where the copied data originated. 3. INC39470303 - TIU-2094 - BLD+7^TIUSRVT3 ^TIU(8927,"") occurring nightly when the auto-deactivate option runs Problem: -------- An error was reported occurring every time the process to deactivate a user was performed. This error was determined to be occurring during the process to remove a user's TIU Templates. During the process to compile a list of the user's templates an error was occurring when a valid input parameter was not present to indicate the appropriate template. Resolution: ----------- This patch only will add defensive coding in routine TIUSRVT3 to stop the lookup of the template information if the input parameter is not valid. This will prevent the error from occurring while allowing the lookup/compiling process to continue which will then allow the appropriate TIU Templates to be removed. 4. INC39986468 - TIU-2103 - ORPHAN+8^TIUFLF4 *Y error running a FM report from 8925.1 to look for documents with ORPHAN=YES Problem: -------- An error was reported when a user attempted to run a FileMan search on the TIU DOCUMENT DEFINITION (#8925.1) file to look for instances where the ORPHAN (#.11) field contained "Y". The error occurs due to a variable not being Newed and instantiated properly within the code which can lead to an Undefined error. Resolution: ----------- This patch modifies the ORPHAN tag code in routine TIUFLF4 to properly New and Instantiate the variable so that the Undefined error no longer occurs. 5. INC34507410 - TIU-2104 - Description discrepancies for START OF ADD SGNR ALERT PERIOD field in TIU BASIC PARAMETERS in Vista Problem: -------- A mismatch in the identified default value for the START OF ADD SGNR ALERT PERIOD (#3.1) field Help Text and Description in the TIU PARAMETERS (#8925.99) file was reported. When the user was utilizing the Basic TIU Parameters [TIU BASIC PARAMETER EDIT] option and typed "?" and "??" at the START OF ADD SGNR ALERT PERIOD prompt, they saw two different default values. The help-prompt (?) indicated 7D (7 Days) while the description (??) indicated 12M (12 Months). Resolution: ----------- This patch modifies the description of the START OF ADD SGNR ALERT PERIOD (#3.1) field in the TIU PARAMETERS (#8925.99) file to indicate the proper default value of 7D (7 Days) so it now matches the help-prompt default value text. 6. N/A - TIU-2095 - ICR 10060 Violation - direct global read ^VA(200,IEN) in TIUSRVT3 Problem: -------- While correcting INC39470303 (item 3 above), it was discovered routine TIUSRVT3 was violating ICR #10060 which allows applications to read data from the NEW PERSON (#200) file using FileMan. TIUSRVT3 was using a direct global read to access the user's name. Resolution: ----------- This patch modifies TIUSRVT3 to access the user's name utilizing the results of a FileMan API and removes the direct global read. 7. N/A - TIU-2099 - ICR Violations in TIUCOPR1 Problem: -------- While correcting INC39192675 (item 2 above), it was discovered routine TIUCOPR1 was violating ICR #10060 which allows applications to read data from the NEW PERSON (#200) file using FileMan. TIUCOPR1 was using a direct global read to access the user's name. Also, it referenced ICR #3162 as support for reading data for REQUEST/ CONSULTATION (#123) file. Unfortunately, that ICR only gave permissions to point to the REQUEST/CONSULTATION (#123) file and not actually read from the file. Resolution: ----------- This patch modifies TIUCOPR1 to access the user's name utilizing the results of a FileMan API and removes the direct global read. It also requested a modification to ICR #2586 to allow Text Integration Utilities (TIU) to access the needed data in the REQUEST/CONSULTATION (#123) file. Test Sites: ----------- Milwaukee VA Medical Center (Milwaukee, WI) Tuscaloosa VA Medical Center (Tuscaloosa, AL) Test Sites - SNOW Change Order#: Milwaukee VA Medical Center - CHG0716728 Tuscaloosa VA Medical Center - CHG0715245 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: This patch contains no pre/post installation routines Pre-Installation Instructions: This patch may be installed with users on the system, although it is recommended that it be installed during non-peak hours to minimize potential disruption to users. This patch should take less than 5 minutes to install. There are no menu options that need to be disabled 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. TIU*1.0*369 or XXXXX BUILD X.X) NOTE: Using will not bring up a Multi-Package build even if it was loaded immediately before this step. It will only bring up the last patch in the build. 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 TIU*1.0*369 iii. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build (including Routines) R Routines Only Backup Type: B// 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. Post-Installation Instructions: There are no post-installation instructions. Back-Out/Roll Back Plan: ------------------------ The decision to back-out or rollback software will be a joint decision between development team, VA site/region personnel and other appropriate VA personnel. The back-out plan is to restore the routines and data dictionary from the backup created. It is imperative that a backup was performed PRIOR to installation. No data was modified by this patch installation and, therefore, no rollback strategy is required. Routine Information: ==================== The second line of each of these routines now looks like: ;;1.0;TEXT INTEGRATION UTILITIES;**[Patch List]**;Jun 20, 1997;Build 4 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: TIUALRT Before: B72816199 After: B78061463 **21,84,79,88,58,61,151,158, 175,221,227,259,355,358,353, 357,369** Routine Name: TIUCOPR1 Before: B90403542 After: B72632551 **290,338,369** Routine Name: TIUFLF4 Before: B17364801 After: B17640909 **11,43,236,232,369** Routine Name: TIUSRVT3 Before: B17514400 After: B18442157 **110,369** Routine Name: TIUSRVT4 Before: B14271945 After: B15256621 **110,369** Routine Name: TIUTIUS Before: B38618925 After: B38637399 **296,324,346,369** Routine list of preceding patches: 110, 232, 338, 346, 357 ============================================================================= User Information: Entered By : Date Entered : JUL 23, 2024 Completed By: Date Completed: MAY 01, 2026 Released By : Date Released : MAY 06, 2026 ============================================================================= Packman Mail Message: ===================== $END TXT