$TXT Created by at MNTVBB.DOMAIN.EXT (KIDS) on Wednesday, 05/06/20 at 09:23 ============================================================================= Run Date: NOV 19, 2020 Designation: SR*3*201 Package : SR - SURGERY Priority: Mandatory Version : 3 SEQ #186 Status: Released Compliance Date: DEC 19, 2020 ============================================================================= Associated patches: (v)SR*3*188 <<= must be installed BEFORE `SR*3*201' Subject: DELETED POSTOP OCCURRENCE & OR SCHEDULING BLOCKED Category: - Routine - Input Template Description: ============ The patch addresses two issues: 1. When a POSTOP OCCURRENCE for "OUT-OF-OR UNPLANNED INTUBATION W/IN 30 DAYS" is entered and then deleted, the printed risk assessment improperly displays "NO DATE" rather than "NO" for the occurrence. 2. When two users attempt to schedule or reschedule an operation for the same patient, they can inadvertently schedule the same case for different times or rooms and block those resources from other users. Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- SRO-NOCOMP input SURGERY (#130) Modified Defect Tracking System Ticket(s) & Overview: 1. INC9151043 - Deleted Postop Occurrence Problem: -------- When a POSTOP OCCURRENCE for "OUT-OF-OR UNPLANNED INTUBATION W/IN 30 DAYS" is entered and then deleted, the printed risk assessment improperly displays "NO DATE" rather than "NO" for the occurrence. A map of the entered occurrences is maintained in the SURGERY FILE (#130) node 205 as "Y" or "N". The defect is that the entry for "OUT-OF-OR UNPLANNED INTUBATION W/IN 30 DAYS" is not being reset to "N" when it is deleted. Resolution: ----------- Entries are deleted (or marked "N") in the occurrence map via the INPUT TEMPLATE [SRO-NOCOMP]. There was no line item for the "OUT -OF-OR UNPLANNED INTUBATION W/IN 30 DAYS" occurrence. The patch updates the template to include the missing occurrence. Routines: N/A Input Template: [SRO-NOCOMP] 2. INC9442240 - OR Scheduling Blocked Problem: -------- When two (2) users accidently attempt to schedule or reschedule an operation for the same patient, they can inadvertently schedule the same case for different times or rooms and block those resources from other users. Resolution: ----------- Routine ^SRSCHD1 is modified to check whether the case has been scheduled after the case is LOCKed just before the case is scheduled. The routine ^SRSUP1 is modified to recheck to determine if the operating room or scheduled time have been changed by another user after the case is LOCKed just before the case is scheduled. Additionally, the LOCK performed by the Scheduling options is modified to only LOCK the case number that is being edited. Routines: SRSCAN, SRSCAN0, SRSCHD1, SRSCHDA, SRSUP1, SRSUPC Test Sites: ----------- Memphis VAMC (Memphis, TN) VA Heartland - East (St. Louis, MO) 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 5 minutes to install. NOTE : Kernel patches must be current on the target system to avoid problems loading and/or installing this patch. 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 SR*3.0*201. B. From the Installation Menu, select the Backup a Transport Global option and when prompted for the INSTALL NAME enter the patch SR*3.0*201. This option will create a backup message of any routines exported with this patch. It will not backup any other changes such as DDs or templates. 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. From the Installation Menu, select the Install Package(s) option and enter the patch SR*3.0*201. 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/Roll Back Plan: ------------------------ 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 development team, VA site/region personnel and other appropriate VA personnel. It is imperative that you have performed a backup of the routines included in this patch prior to installation. The back-out plan is to restore the routines from the backup created and to restore the input template SRO-NOCOMP. Assistance with the input template restore can be provided upon request. Please call the National Help Desk or enter a Help Desk ticket, if required. No data was modified by this patch installation and, therefore, no rollback strategy for data is required. To verify the routine back-out completed successfully, ensure the checksums match the pre-patch checksums from this patch description. To verify the input template back-out completed successfully, ensure template SRO-NOCOMP no longer matches the patch version. Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;Surgery ;**[Patch List]**;24 Jun 93;Build 5 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: SRSCAN Before: B10909174 After: B10971522 **100,201** Routine Name: SRSCAN0 Before: B27843088 After: B28162341 **34,42,67,103,107,114,100,144, 175,176,182,184,188,201** Routine Name: SRSCHD1 Before: B8338471 After: B21408876 **37,100,201** Routine Name: SRSCHDA Before: B15325707 After: B15369435 **77,50,100,201** Routine Name: SRSUP1 Before: B27897479 After: B30135770 **7,16,19,47,58,67,77,50,93, 107,114,100,131,177,184,201** Routine Name: SRSUPC Before: B7886388 After: B7967550 **100,175,182,201** Routine list of preceding patches: 188 ============================================================================= User Information: Entered By : Date Entered : FEB 25, 2020 Completed By: Date Completed: NOV 18, 2020 Released By : Date Released : NOV 19, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT