$TXT Created by L. at MNTVBB.DOMAIN.EXT (KIDS) on Thursday, 09/21/23 at 13:40 ============================================================================= Run Date: DEC 07, 2023 Designation: GMRA*4*70 Package : GMRA - ADVERSE REACTION TRACKING Priority: Mandatory Version : 4 SEQ #63 Status: Released Compliance Date: JAN 07, 2024 ============================================================================= Associated patches: (v)GMRA*4*63 <<= must be installed BEFORE `GMRA*4*70' Subject: LONG REMOTE ALLERGY LIST ERROR ON DRUG ORDER Category: - Routine Description: ============ This patch will resolve the following issue: It was reported that a hard error was encountered when the reporting site, using CPRS, placed an inpatient medication order for hydroxyzine for a patient that has noted severe allergic reactions to hydroxyzine. The error caused CPRS to shut down and prevented the user from further processing the order. The error encountered is as follows: DRUG+95^GMRAOR *ITEMS() Subscript 1 > 511 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.INC27445347-Error Ordering Hydroxyzine Problem: -------- The error occurs due to the large number of remote allergies for the patient. The reported error is as follows: DRUG+95^GMRAOR *ITEMS() Subscript 1 > 511 Resolution: ----------- The api ADDCOMMA^GMRAOR was added to insert a comma(s) before the 512th position in the source array to prevent the subscript error from occurring. Technical Resolution: --------------------- Upon researching, it was discovered that the ITEMS array in api DRUG^GMRAOR was designed to store each symptom individually as an index of the ITEMS array. The source that provides all the symptoms are stored in a separate array that contains each symptom, separated by commas. This in turn, would indicate to the process to assign each symptom, the value that is between the commas, as an index to the ITEMS array. However, in the case of the error, there were no commas in the source array to indicate each separate symptom and the length of the symptoms list was greater than 511 characters, thus creating the error. The following call was added to call the api ADDCOMMA^GMRAOR at DRUG+95^GMRAOR. ....I $L($G(@RETURN)) S @RETURN=$$ADDCOMMA(@RETURN) ;p70 The ADDCOMMA^GMRAOR() function will take a text string of symptoms and determine if the total length is greater than 511. If is less than 512 it will keep the passed text string intact. If it is greater than 511 characters, then the process will use the array GMRAOUT() to store up to 200 characters for each index in the array. It will then substitute the last space within each array index with a comma. It will then append all of the array indexes into the variable GMRAFOUT, which is returned to the $$ADDCOMMA call to be further processed. Participating Test Sites: ========================= Charleston VAMC Charleston, SC Jesse Brown VAMC Chicago, IL SNOW Change Order #: =================== Charleston - CHG0425510 Chicago (Jesse Brown) - CHG0425779 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Patch 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 2 minutes to install. For this install there are no options that are required 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 GMRA*4.0*70. 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*70. 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. a. When prompted 'Enter options you wish to mark as 'Out Of Order':', press the Enter key. b. When prompted 'Enter protocols you wish to mark as 'Out Of Order':', press the Enter key. c. When prompted 'Delay Install (Minutes): (0 - 60): 0//', answer 0. 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 an updated KIDS package, the site/region should have saved a backup of the routine in a mail message using the Backup a Transport Global [XPD BACKUP] menu option from the Kernel Installation and Distribution System Menu and selecting the Installation Menu. The back-out plan is to restore the routine from the backup created. The message containing the backed-up routine 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 routine onto the VistA System. If the patch was backed up for the build, from the Kernel Installation and Distribution System Menu, select the Installation Menu. Select the Install Package(s) option and choose the patch (GMRA*4.0*70b) to install. 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 GMRA 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 GMRA*4.0*70. 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: GMRAOR Before:B164773411 After:B186206489 **2,13,26,37,41,42,44,46,52, 53,63,70** Routine list of preceding patches: 63 ============================================================================= User Information: Entered By : Date Entered : AUG 31, 2023 Completed By: Date Completed: DEC 06, 2023 Released By : Date Released : DEC 07, 2023 ============================================================================= Packman Mail Message: ===================== $END TXT