$TXT Created by at CDVF.DEVSLC.DOMAIN.EXT (KIDS) on Monday, 04/08/24 at 12:04 ============================================================================= Run Date: MAY 30, 2024 Designation: PXRM*2*86 Package : PXRM - CLINICAL REMINDERS Priority: EMERGENCY Version : 2 SEQ #69 Status: Released Compliance Date: JUN 05, 2024 ============================================================================= Associated patches: (v)PXRM*2*42 <<= must be installed BEFORE `PXRM*2*86' (v)PXRM*2*85 <<= must be installed BEFORE `PXRM*2*86' Subject: REMINDER DIALOG B INDEX REPAIR Category: - Routine - Data Dictionary Description: ============ At some point in the past there was an unknown issue that caused the "B" index of file #801.41 to become corrupted. That issue appears to have been corrected. Running a FileMan Verify fields on the .01 field can show the corruption. There may be entries that are not properly indexed and duplicate entries that violate the uniqueness key. In addition to the corrupted "B" index, there are .01s that have trailing non-printing characters. Because these characters are not visible, their presence can lead to apparent duplicates, an entry with the trailing non-printing characters and one without them. This patch repairs the "B" index in four steps. 1. Find all entries that have a .01 field with trailing non-printing characters and rename them, so the trailing non-printing characters are removed. The renaming will be recorded in the EDIT HISTORY. For example: EDIT DATE: JAN 22, 2024@11:11:24 EDIT BY: TESTMASTER,USER EDIT COMMENTS: PXRM*2.0*86 renamed: "WOUND TYPE-CHAR " To: "WOUND TYPE-CHAR" During this search if a corrupted entry (missing the .01 or the entire 0 node) is encountered it will be handled as follows: The number of references to the entry will be determined. If the number is 0 the entry is not being used and it will be deleted. If the number is greater than 0 a message will be displayed on the screen and included in the Install file to the effect that a corrupted entry, that is in use, was found and it needs to be repaired by hand. The message includes the internal entry number of the entry so it can be easily located. 2. Rebuild the "B" index. 3. Using the rebuilt "B" index build a list of duplicates. 4. For each set of duplicates, group them by TYPE and rename them by appending -TYPE. If there are multiple entries for a TYPE, search the EDIT HISTORY of the entries in the set to find the most recently edited one. Repoint the other entries to it and delete the repointed entries. The renaming and repointing will be recorded in the EDIT HISTORY. For example: EDIT DATE: JAN 22, 2024@11:11:26 EDIT BY: TESTMASTER,USER EDIT COMMENTS: PXRM*2.0*86 repointed the following IENs to this entry: 47276 The input transform for the NAME field was updated to not allow trailing non-printing characters. This will prevent the creation of new Reminder Dialog entries with trailing non-printing characters. This patch also updates the national computed finding VA-ELIGIBILITY, adding secondary eligibilities by name to the VAEL array, i.e., VAEL("SE",ELIGIBILITY), where ELIGIBILITY is an eligibility (.01) from file #8. This allows secondary eligibilities to be used in Conditions. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- REMINDER COMPUTED FINDINGS N/A N/A (811.4) Update the description of VA-ELIGBILITY. 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 Test Sites: ----------- Carl Vinson VAMC Dublin, GA Fort Harrison VAMC Fort Harrison, MT Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Documentation of the new functionality is included in the patch description. There are no formal documents being distributed with this release. Patch Installation: ------------------- Pre/Post Installation Overview: The required builds are: PXRM*2.0*42 and PXRM*2.0*85. The initializing routine PXRMP86I can be deleted after a successful installation. 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 1 minute to install. This patch must not be queued, the installer will be prompted to select an output device when the repointing is done. No options or protocols need to be disabled; it will be done automatically. 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. PXRM*2.0*86) 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 PXRM*2.0*86 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 this message? 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//', NO. iii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer NO. iv. When prompted 'Enter the Device you want to print the Install messages. Enter a '^' to abort the install.' Enter your output device. Do not queue the install, when the repointing is done an output device will need to be selected. DEVICE: HOME// Post-Installation Instructions: After a successful installation, the initializing routine PXRMP86I can be deleted. Back-Out/Roll Back Plan: ------------------------ If back-out is needed, install the backup build created in step 2B iii. Back-out will be done only with the concurrence and participation of development team and appropriate VA site/region personnel. 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. Prior to installing the updated KIDS package, the site/region should have saved a backup of the routines in a mail message using the Backup a Transport Global [XPD BACKUP] menu option. The message containing the backed up routines can be loaded with the "Xtract PackMan" function at the Message Action prompt. The PackMan function INSTALL/CHECK MESSAGE is then used to install the backed-up routines onto the VistA system outlined in step 2B Section iii. Note: In the event of a catastrophic failure, the final decision to back out this patch will be up to the site management. To backout the patch, it is imperative that the backup was performed as specified above. Routine Information: ==================== The second line of each of these routines now looks like: ;;2.0;CLINICAL REMINDERS;**[Patch List]**;Feb 04, 2005;Build 9 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PXRMCLEH Before: n/a After: B13194965 **86** Routine Name: PXRMDLGBREPAIR Before: n/a After: B60030606 **86** Routine Name: PXRMINTR Before: B45764043 After: B56109900 **4,12,16,18,26,45,86** Routine Name: PXRMMSER Before:B133664475 After:B141557445 **11,12,21,24,26,42,86** Routine Name: PXRMP86I Before: n/a After: B711651 **86** Routine list of preceding patches: 42, 45 ============================================================================= User Information: Entered By : Date Entered : JAN 18, 2024 Completed By: Date Completed: MAY 30, 2024 Released By : Date Released : MAY 30, 2024 ============================================================================= Packman Mail Message: ===================== $END TXT