$TXT Created by at CLN1G1.AAC.DOMAIN.EXT (KIDS) on Monday, 06/17/19 at 07:44 ============================================================================= Run Date: NOV 06, 2019 Designation: MD*1*73 Package : MD - CLINICAL PROCEDURES Priority: Mandatory Version : 1 SEQ #57 Status: Released Compliance Date: DEC 09, 2019 ============================================================================= Associated patches: (v)MD*1*34 <<= must be installed BEFORE `MD*1*73' (v)MD*1*65 <<= must be installed BEFORE `MD*1*73' Subject: ELIMINATE ALERTS FOR RETRACTED NOTES AND CORRECT HIGH VOLUME SETUP ISSUES Category: - Routine Description: ============ This patch will resolve the following 2 issues in the Clinical Procedures package: 1. INC5256127 - Multiple Procedure Alerts on Retracted Note 2. INC6092268 - High Volume bugs discovered New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC5256127 - Multiple Procedure Alerts on Retracted Note Problem 1: ---------- Placing a Text Integration Utility (TIU) note in 'Retracted' status in Clinical Procedures causes a repeating "procedure ready for interpretation" alert to be sent each time the MD PROCESS RESULTS background job runs. This could generate hundreds/thousands of alerts depending on how often this background job runs. Resolution 1: ------------- A modification will be made in routine MDHL7XXX to not send the alert if the note is in a 'Retracted' Status. 2. INC6092268 - High Volume bugs discovered Problem 2A: ----------- When using the menu option High Volume Procedure Setup [MD HIGH VOLUME PROCEDURE SETUP], the software would allow a Clinical procedure to be setup for High Volume without the associated note title's technical fields COMMIT ACTION and POST-SIGNATURE CODE fields being set to "Q(UIT)" as required by the application setup. Resolution 2A: -------------- Routine MDARSET is modified to skip the prompt asking the user if they want to set the technical fields when entering a new procedure setup. The routine will refuse to set up the new procedure if the note title is in an ACTIVE status. The user MUST set the note title to INACTIVE to add the new procedure to the High Volume setup. If deleting a procedure setup from High Volume, they are still prompted if they want to update the technical fields (delete the 'Q's), as it is possible for multiple procedures to share a note title. Problem 2B: ----------- When using the menu option High Volume Procedure Setup [MD HIGH VOLUME PROCEDURE SETUP] for a Muse Procedure and the 'Use Interpreter to close note?' prompt is answered 'YES', the user is not prompted to set the associated note title's technical fields COMMIT ACTION and POST-SIGNATURE CODE to 'Q(uit)'. Resolution 2B: -------------- Routine MDARSET is modified, when adding a new Muse procedure to High Volume setup, the routine automatically sets the associated note title's technical fields to a 'Q' on a Muse Procedure when the 'Use Interpreter to close note?' is set to 'YES'. It no longer asks to set the technical fields and it reminds the user to REACTIVATE the NOTE TITLE. Test Sites: ----------- Fayetteville VA Medical Center (NC) Veterans Health Care System of the Ozarks (Fayetteville, AR) Patch Installation: =================== Pre-Installation Instructions: ------------------------------ If installed during the normal workday, it is recommended that the Clinical Procedures users be off the system. Other VISTA users will not be affected. It is also recommended that Background Task MD PROCESS RESULTS be halted during installation of the patch. Install Time - less than 2 minutes (unless otherwise indicated). Installation Instructions: -------------------------- 1. Load Transport Global --------------------- Choose the PackMan message containing this patch and invoke the INSTALL/CHECK MESSAGE PackMan option. 2. Start Up KIDS -------------- Start up the Kernel Installation and Distribution System Menu [XPD MAIN]: Edits and Distribution ... Utilities ... Installation ... Select Kernel Installation & Distribution System Option: Installation --- Load a Distribution Print Transport Global Compare Transport Global to Current System Verify Checksums in Transport Global Install Package(s) Restart Install of Package(s) Unload a Distribution Backup a Transport Global 3. Select Installation Option: --------------------------- NOTE: When prompted for the INSTALL NAME, enter MD*1.0*73: a. Backup a Transport Global - This option will create a backup message of any routines exported with this patch. It will not backup any other changes such as DD's or templates. b. 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 components of this patch (routines, DD's, templates, etc.). c. Verify Checksums in Transport Global - This option will allow you to ensure the integrity of the routines that are in the transport global. 4. Select Installation Option: Install Package(s) ---------------------------------------------- a. Choose the Install Package(s) option to start the patch install. b. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer NO. c. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer NO. Back-out/Rollback Strategy: =========================== In the event of a catastrophic failure, the Facility CIO may make the decision to back-out the patch. It is imperative that you have performed a backup of the routine included in this patch prior to installation. The back-out plan is to restore the routine from the backup created. No data was modified by this patch installation and, therefore, no rollback strategy is required. To verify the back-out completed successfully, ensure the checksum matches the pre-patch checksum from the patch descriptions. Post-Installation Instructions: ------------------------------- This patch does not modify existing High Volume Procedures technical fields of those procedures that are currently defined at the site. It is strongly recommended that each procedure setup be examined and corrected if they do not show 'Q' as shown below: (example:) Procedure: CP PROCEDURE This procedure has note title CP TEST NOTE TITLE associated with it. The current setup is as follows: STATUS: ACTIVE COMMIT ACTION: Q POST-SIGNATURE CODE: Q When a procedure is setup for High Volume, the COMMIT ACTION and POST-SIGNATURE CODE fields must contain a 'Q'. If you need to update these fields, the title (CP TEST NOTE TITLE) must be inactivated first. At the "Procedure:" prompt, when you enter a '?', all existing High Volume Procedures are listed. Edit each one to verify the technical fields are 'Q' and not . IMPORTANT NOTE: Before you can make changes in the setup, the associated note title needs to be INACTIVE first. This is listed when you edit the procedures as: This procedure has note title ############# associated with it. After editing, DON'T FORGET TO REACTIVATE YOUR NOTE TITLES. Routine Information: ==================== The second line of each of these routines now looks like: ;;1.0;CLINICAL PROCEDURES;**[Patch List]**;Apr 01, 2004;Build 2 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: MDARSET Before: B45042455 After: B52267997 **21,65,73** Routine Name: MDHL7XXX Before: B28032567 After: B29356870 **21,34,73** Routine list of preceding patches: 34, 65 ============================================================================= User Information: Entered By : Date Entered : JUN 03, 2019 Completed By: Date Completed: NOV 05, 2019 Released By : Date Released : NOV 06, 2019 ============================================================================= Packman Mail Message: ===================== $END TXT