$TXT Created by at MNTVBB.DOMAIN.EXT (KIDS) on Tuesday, 06/13/23 at 13:25 ============================================================================= Run Date: AUG 22, 2023 Designation: SR*3*211 Package : SR - SURGERY Priority: Mandatory Version : 3 SEQ #196 Status: Released Compliance Date: SEP 21, 2023 ============================================================================= Associated patches: (v)SR*3*107 <<= must be installed BEFORE `SR*3*211' Subject: CONCURRENT CASE FIELD NOT CLEARED Category: - Routine Description: ============ The CONCURRENT CASE field (#35) in the SURGERY FILE (#130) in a completed concurrent case is cleared however the CONCURRENT CASE field is not cleared in a cancelled concurrent case. Associated NSR(s): ------------------ N/A 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 Additional Information: ----------------------- New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC27290184 - CONCURRENT CASE Field Not Clear Problem: -------- The CONCURRENT CASE field (#35) in the SURGERY file (#130) in a completed concurrent case is cleared however the CONCURRENT CASE field is not cleared for a cancelled concurrent case. This occurs because the FileMan call (^DIE) to clear the field aborts with an IRIS error because the required DR variable is undefined: Resolution: ----------- This patch modifies routine ^SRSUTL2 to define the variable DR prior to the call to ^DIE. Routine(s): SRSUTL2 Test Sites: ----------- Durham VAMC Durham, NC South Texas VA HCS San Antonio, TX SNOW Change Order #: -------------------- Durham VAMC: CHG0394202 South Texas VA HCS: CHG0392436 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. File Title File Name Format --------------------------------------------------------------------- N/A Documentation Title File Name --------------------------------------------------------- N/A Patch Installation: ------------------- Pre/Post Installation Overview: ------------------------------- Pre-Installation Instructions: ------------------------------ This patch may be loaded with users on the system. You may wish to install it during non-peak hours. Installation will take less than 1 minute. It is not necessary to disable any options/protocols. 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. 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 SR*3.0*211 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: Routines 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 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. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer NO. ii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? 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. Installation Verification: -------------------------- Successful installation can be verified by reviewing the first 2 lines of the routines contained in the patch. The second line will contain the patch number (211) in the [PATCH LIST] section. ;;3.0;Surgery;**[Patch List]**; 24 Jun 93 The Calculate and Show Checksum Values option [XTSUMBLD-CHECK] can be run to compare the routine checksums to what is documented in this patch description. Back-out/Rollback Strategy: --------------------------- Back-out will be done only with the concurrence and participation of the development team and appropriate VA site/region personnel. The decision to back-out or rollback software will be a joint decision between the 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 routines 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 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. If the patch was backed up for the build, from the Kernel Installation and Distribution System Menu, select the Installation Menu. Then select the Install Package(s) option and choose the patch (SR*3.0*211b) to install. The back-out plan is to restore the routines 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 SR 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 SR*3.0*211. Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;Surgery;**[Patch List]**;24 Jun 93;Build 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: SRSUTL2 Before: B7870385 After: B7791170 **34,67,107,211** Routine list of preceding patches: 107 ============================================================================= User Information: Entered By : Date Entered : JUN 07, 2023 Completed By: Date Completed: AUG 22, 2023 Released By : Date Released : AUG 22, 2023 ============================================================================= Packman Mail Message: ===================== $END TXT