$TXT Created by CPRS32.DOMAIN.EXT (KIDS) on Friday, 10/27/23 at 09:13 ============================================================================= Run Date: JAN 22, 2024 Designation: GMRA*4*68 Package : GMRA - ADVERSE REACTION TRACKING Priority: Mandatory Version : 4 SEQ #64 Status: Released Compliance Date: FEB 22, 2024 ============================================================================= Associated patches: (v)GMRA*4*63 <<= must be installed BEFORE `GMRA*4*68' Subject: 32A ENTER/EDIT PATIENT REACTION DATA DEFECT AND VDIF ALLERGY UPDATE Category: - Routine Description: ============ This patch addresses the following: 1. When using Enter/Edit Patient Reaction Data [GMRA USER E/E PAT REC DATA] to record a historical reaction, a minimum of four characters needs to be entered as a comment or a sign/symptom needs to be entered for a valid entry to be accepted. However, it was found that if a comment of less than four characters was entered (and a sign/symptom was not entered), an error is displayed to the user, but the comment is still accepted and recorded. This patch fixes that issue, and will not record the comment in that scenario. 2. Allergy data not properly returned under certain instances. Entered in error allergies are not showing up in the reaction results in HealthShare application. This occurs for patients who only have entered in error reactions. Defect exists in VistA in routine GMRAPDT. 3. Adding new protocol event to trigger from an edit to verify allergy and addition of a new observation. This protocol is activated whenever a user edits a verified allergy including adding or editing observations. GMRAPEM0 routine has a code change that triggers this particular event. Patch Components: ----------------- N/A 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 ------------- -------------------- GMRA EDIT VERIFIED DATA NEW 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: 1. NSR #20120404 - Adverse Reaction Reporting File Mods Note: This NSR was addressed in patch GMRA*4*63 and had a defect. Problem: -------- When using ^Enter/Edit Patient Reaction Data [GMRA USER E/E PAT REC DATA], for Historical reactions without any signs/symptom entered, a comment of <4 characters is an invalid entry, and it prompts back until a comment of at least 4 characters are entered. A minimum of 4 characters needs to be entered and a comment or a sign/symptom needs to be entered for a valid entry to be accepted. The issue is it saves the invalid entries which are displayed in VistA and CPRS. Resolution: ----------- The routine GMRAPEH0, was modified to address the issue. The invalid entries will not be stored when it re-prompted. 2. VISTAGMRA-278 - Allergy data not fully/properly returned under certain instances. Problem: -------- VPR "Virtual Patient Record" needs all reactions returned. "Entered In Error" (EIE) reactions are not showing up in results for patients who only have EIE reactions. Resolution: ----------- The routine GMRADPT, was modified to address the issue. User should be able to return all reactions for patients who only have Entered In Error reactions. Test Sites: ----------- DUBLIN VAMC DUBLIN,GA CHILLICOTHE VAMC CHILLICOTHE,OH Test Sites - SNOW Change Order#: -------------------------------- DUBLIN: CHG0438190 CHILLICOTHE: CHG0441075 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Documentation describing the new functionality is included in this release. Documentation can be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/. Documentation can also be obtained at https://download.vista.domain.ext/index.html/SOFTWARE. Documentation Title File Name --------------------------------------------------------------------- Adverse Reaction Tracking 4.0 Technical Manual GMRA_4_0_TM.DOCX GMRA_4_0_TM.PDF Patch Installation: ------------------- Pre/Post Installation Overview: 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 the patch or build name. GMRA*4.0*68 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 GMRA*4.0*68 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. iii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer NO. Post-Installation Instructions: N/A Back-Out/Roll Back Plan: 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. 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. Although this patch does export a new protocol, by restoring the backup created during installation, usage of the new protocol will be removed, so no deletion of the protocol is currently required. Routine Information: ==================== The second line of each of these routines now looks like: ;;4.0;Adverse Reaction Tracking;**[Patch List]**;Mar 29, 1996;Build 5 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: GMRADPT Before: B93897625 After: B93640848 **2,10,46,52,53,63,51,68** Routine Name: GMRAPEH0 Before: B4987029 After: B6132818 **63,68** Routine Name: GMRAPEM0 Before:B103518392 After:B117970016 **2,5,17,21,36,50,58,63,51,68** Routine list of preceding patches: 51 ============================================================================= User Information: Entered By : Date Entered : AUG 31, 2021 Completed By: Date Completed: JAN 16, 2024 Released By : Date Released : JAN 22, 2024 ============================================================================= Packman Mail Message: ===================== $END TXT