$TXT Created by MNTVBB.DOMAIN.EXT (KIDS) on Wednesday, 01/04/23 at 08:40 ============================================================================= Run Date: OCT 04, 2023 Designation: FH*5.5*55 Package : FH - DIETETICS Priority: Mandatory Version : 5.5 SEQ #50 Status: Released Compliance Date: NOV 03, 2023 ============================================================================= Associated patches: (v)FH*5.5*33 <<= must be installed BEFORE `FH*5.5*55' Subject: ALERT FOR WRONG PATIENT DISPLAYS WHEN ACCESSING VIEW ALERTS Category: - Routine Description: ============ This patch addresses the following issue: ALERT FOR WRONG PATIENT DISPLAYS IN VIEW ALERTS Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A 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 New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: =========================================== 1. INC22357619 - ALERT FOR WRONG PATIENT DISPLAYS IN VIEW ALERTS Problem: ------- Alert for wrong patient displayed when accessing View Alerts. A Nutrition and Food alert was selected, and an alert displayed for a different patient. This issue was reviewed by the Kernel Team and their findings were that the application is creating an incorrect Package Identifier (pkgid) (four comma pieces instead of three), so that when the application processes the alert, the patient id or notification id are incorrectly referenced. This was found to be due to the Package Identifier being created using $H which itself contains a comma. Resolution: ---------- The use of $H to create the Package Identifier does allow the creation of a unique identifier but causes problems due to the extra comma. This patch will modify the Package Identifier in FH routines sent to Kernel to conform with Kernel standards. Kernel 8.0 & Kernel Toolkit 7.3 Developer's Guide documents the package id as follows: Paragraph 3.2.1 - The software application identifier for an alert is defined as the original value of the XQAID input variable when the alert is created via the SETUP^XQALERT: Send Alerts API. Typically, the software application identifier should begin with the software application namespace. Paragraph 3.3 - The Computerized Patient Record System (CPRS) software uses a convention for the format of the software application identifier consisting of three comma-delimited pieces: namespace_","_dfn_","_notificationcode Where: ** namespace is the software application namespace. ** dfn is the internal entry number of the patient whom the alert concerns in the PATIENT (#2) file. ** notificationcode is a code maintained by the CPRS software describing the type of alert. Prior to this patch the XQAID variable passed to kernel was created as "FH,"_$J_","_$H ($J is the vista job# for the task & $H is mumps date/time) Technical Resolution: -------------------- The setting of XQAID in routines ALRT^FHCTF5, ALRT^FHASM2A, PHA^FHASM2A and FIL^FHWTRN is changed to use the patient's DFN as the 2nd comma piece and a number identifying the FH alert type in the 3rd piece. "FH,"_DFN_","_TYPE The types are as follows 1 = Food/drug interaction alert 2 = Nutrition Patient assessment alert 3 = Monitor BMI alert 4 = Monitor Tubefeed alert 5 = Monitor Hyperals alert 6 = Monitor Albumin alert 7 = Monitor NPO+Clr alert The TYPE is set into the variable FHCODE in routines FHWTRN & FHCTF5 for each type of alert. During analysis it was also found that routines FHWTRN & FHCTF5 were passing in FHCTF2 in field ENTRY POINT (#.07) in sub file ALERT DATE/TIME (#1) of ALERT file (#8992) for processing the alert but the routine is a standalone process that should not be called to process this alert. The alert is deleted which is correct because these alerts are meant to be informational. Setting an entry point should not have been done and both entry point and routine should not be set. This patch comments out the code S XQAOPT="FHCTF2" at FIL+11^FHWTRN and ALRT+9^FHCTF5. Test Sites: ========== Orlando VA Medical Center (Orlando, FL) VA Western New York Healthcare System (Buffalo, NY) Test Sites - SNOW Change Order #: ================================ ORL - CHG0401053 WNY - CHG0400745 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. 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 FH*5.5*55 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 FH*5.5*55 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. Back-out/Rollback Strategy: --------------------------- 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 an updated KIDS package, the site/region should have saved a backup of the build in a mail message using the Backup a Transport Global [XPD BACKUP] menu option (this is done at time of install). The message containing the backed-up build 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. The back-out plan is to restore the build from the backup created. No data was modified by this patch installation and, therefore, no rollback strategy is required. Validation of Back-out Procedure -------------------------------- The Back-out Procedure can be verified by confirming the checksums have been returned to the pre-patch value using CHECK1^XTSUMBLD. It can also be verified by printing the first 2 lines of the [Namespace] routine(s) contained in this patch using the option: First Line Routine Print [XU FIRST LINE PRINT]. Once the routine(s) contained in this patch have been backed out, the Second line of each routine will no longer contain the designation of patch [Patch name]. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.5;DIETETICS;**[Patch List]**;Jan 28, 2005;Build 7 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: FHASM2A Before: B16654897 After: B17583470 **8,20,27,55** Routine Name: FHCTF5 Before: B41046535 After: B42334358 **4,8,20,55** Routine Name: FHWTRN Before: B37070220 After: B38671911 **4,27,33,55** Routine list of preceding patches: 33 ============================================================================= User Information: Entered By : Date Entered : JUN 02, 2022 Completed By: Date Completed: OCT 04, 2023 Released By : Date Released : OCT 04, 2023 ============================================================================= Packman Mail Message: ===================== $END TXT