$TXT Created by . at MNTVBB.DOMAIN.EXT (KIDS) on Friday, 08/15/25 at 09:30 ============================================================================= Run Date: SEP 18, 2025 Designation: SR*3*219 Package : SR - SURGERY Priority: Mandatory Version : 3 SEQ #204 Status: Released Compliance Date: OCT 18, 2025 ============================================================================= Associated patches: (v)SR*3*182 <<= must be installed BEFORE `SR*3*219' (v)SR*3*185 <<= must be installed BEFORE `SR*3*219' Subject: NON-OR PROCEDURE REPORT CANCELED CASES REPORTED AS ABORTED Category: - Routine Description: ============ This patch addresses one issue: INC38166819 -In the Report of Non-O.R. Procedures [SRONOR], procedures that are canceled appear on the report as ABORTED even if they are canceled before the case was started. EHRM Impact Statement: ---------------------- This patch should have no EHRM impact, and can be installed at all sites,including EHRM converted sites. 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 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: ----------------------- N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: INC38166819: Non-OR Procedure Report Canceled cases reported as Aborted Problem: ------ In the Report of Non-O.R. Procedures [SRONOR], procedures that are canceled appear on the report as ABORTED even if they are canceled before the case was started. Resolution: ----------- This patch modifies the report routines SRONOR2, SRONOR3, SRONOR4, SRONOR5, SRONOR7, SRONOR8 (six different sorts) to correctly label procedures as CANCELED when the cancel happens before the procedure begins, and as ABORTED only if canceled after the procedure had been started based on procedure start time or anesthesia being started. Using logic similar to O.R. procedures, which check for an "In-O.R." time, anesthesia start time, and an abort flag/indicator to determine if the procedure is canceled or aborted, the Non-O.R. procedure report will evaluate any procedure that is canceled to determine if it should be reported as canceled or aborted based on the presence of a procedure start time, anesthesia start time, or abort flag indicating case aborted (abort flag may not be present for non-OR cases, but logic checks just like it does for O.R. procedures). If there is a procedure start time, an anesthesia start time, or an abort flag, a canceled Non-O.R. procedure will be flagged as ABORTED on the report. If those time stamps/flags are not present, the procedure will be reported as CANCELED. The logic to return the canceled / aborted designation is built into one function call, CAN^SRONOR2, and the function is called by each of the six report sort routines (SRONOR2, SRONOR3, SRONOR4, SRONOR5, SRONOR7, and SRONOR8). Test Sites: ----------- Minneapolis VAMC (Minnesota MN) Durham VAMC (North Carolina NC) SNOW Change Order Number: ------------------------- Site 1: Minneapolis- CO# CHG0642218 Site 2: Durham - CO# CHG0642781 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Documentation updates are not included in this release. 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. It is not necessary to disable any options. 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. 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 name. (ex. SR*3.0*219). 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*219. 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. 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 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*219b) 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. Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;Surgery;**[Patch List]**;24 Jun 93;Build 2 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: SRONOR2 Before: B18165133 After: B20440143 **50,175,182,219** Routine Name: SRONOR3 Before: B17640494 After: B17570605 **50,175,182,219** Routine Name: SRONOR4 Before: B17758963 After: B17687234 **50,175,182,219** Routine Name: SRONOR5 Before: B17460768 After: B17390879 **50,175,182,219** Routine Name: SRONOR7 Before: B18187654 After: B18115925 **50,175,185,219** Routine Name: SRONOR8 Before: B17802246 After: B17732357 **50,175,182,219** Routine list of preceding patches: 182, 185 ============================================================================= User Information: Entered By : Date Entered : APR 03, 2025 Completed By: Date Completed: SEP 18, 2025 Released By : Date Released : SEP 18, 2025 ============================================================================= Packman Mail Message: ===================== $END TXT