$TXT Created by MNTVBB.DOMAIN.EXT (KIDS) on Thursday, 08/14/25 at 12:01 ============================================================================= Run Date: DEC 02, 2025 Designation: SR*3*223 Package : SR - SURGERY Priority: Mandatory Version : 3 SEQ #206 Status: Released Compliance Date: JAN 01, 2026 ============================================================================= Associated patches: (v)SR*3*200 <<= must be installed BEFORE `SR*3*223' Subject: NURSE INTRAOPERATIVE REPORT COMMENTS Category: - Routine Description: ============ This patch addresses the following issues: 1. NURSE INTRAOPERATIVE REPORT WOUND SWEEP COMMENTS 2. NURSE INTRAOPERATIVE REPORT INTRA-OPERATIVE X-RAY COMMENTS 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 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): ----------------------------- Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC39864368 - NURSE INTRAOPERATIVE REPORT WOUND SWEEP COMMENTS Problem: -------- WOUND SWEEP COMMENTS that are added/edited/deleted in the VistA Surgery package after the nurse intraoperative report is completed/electronically signed do not force the creation of an addendum to the nurse intraoperative report. This leaves the VistA Surgery package and nurse intraoperative report out of sync. This word processing field should function the same as other word processing fields captured in the completed/electronically signed nurse intraoperative report (e.g. NURSING CARE COMMENTS (#.29), SPECIMENS (#49), CULTURES(#64) etc. Resolution: ----------- Modify routine SROESNR0 to add WOUND SWEEP COMMENTS field to the list of Surgery (#130) fields for comparison. Technical Resolution: --------------------- Add the following line in the FIELD label in routine SROESNR0: KFCCC ;;^Wound Sweep Comments-130,635;W^53;0 2. INC39707539 - NURSE INTRA-OPERATIVE X-RAY COMMENTS Problem: -------- INTRA-OPERATIVE X-RAY COMMENTS that are added/edited/deleted in the VistA Surgery package after the nurse intraoperative report is completed/electronically signed do not force the creation of an addendum to the nurse intraoperative report. This leaves the VistA Surgery package and nurse intraoperative report out of sync. This word processing field should function the same as other word processing fields captured in the completed/electronically signed nurse intra-operative report (e.g. NURSING CARE COMMENTS (#.29), SPECIMENS (#49), CULTURES(#64) etc. Resolution: ----------- Modify routine SROESNR0 to add INTRA-OPERATIVE X-RAY COMMENTS field to the list of Surgery (#130) fields for comparison. Technical Resolution: --------------------- Add the following line in the FIELD label in routine SROESNR0: KFCFC ;;^Intraoperative XRay Comments-130,637;W^54;0 Test Sites: ----------- Minneapolis VAMC Minneapolis, MN Lebanon VAMC Lebanon, PA Test Sites - SNOW Change Order #: -------------------------------- Minneapolis - CHG0654794 Lebanon - CHG0655264 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. 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. SR*3.0*223) 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*223 iii. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build R Routines 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/Rollback Strategy: --------------------------- 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 build 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 build 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*223b) to install. The back-out plan is to restore the build 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 printing the first 2 lines of the routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the build contained in the SR*3.0*223 patch has been backed out, the first two lines of the routine will no longer contain the designation of this patch in the patch list section on line 2. 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: SROESNR0 Before: B59624124 After: B61380734 **100,129,147,153,175,176,182, 184,200,223** Routine list of preceding patches: 200 ============================================================================= User Information: Entered By : Date Entered : AUG 13, 2025 Completed By: Date Completed: DEC 01, 2025 Released By : Date Released : DEC 02, 2025 ============================================================================= Packman Mail Message: ===================== $END TXT