$TXT Created by MNTVBB.DOMAIN.EXT (KIDS) on Friday, 10/22/21 at 13:41 ============================================================================= Run Date: JAN 10, 2022 Designation: OR*3*572 Package : OR - ORDER ENTRY/RESULTS REPORTING Priority: Mandatory Version : 3 SEQ #487 Status: Released Compliance Date: FEB 10, 2022 ============================================================================= Associated patches: (v)OR*3*563 <<= must be installed BEFORE `OR*3*572' (v)PSJ*5*419 <<= must be installed BEFORE `OR*3*572' Subject: MEDICATION RELEASED FROM HOLD NOT SHOWING NURSE VERIFIED IN BCMA Category: - Routine Description: ============ This patch addresses the following issues: 1. INC19397308 - MEDICATION RELEASED FROM HOLD NOT SHOWING NURSE VERIFIED IN BCMA Defect Tracking System Ticket(s) & Overview: 1. INC19397308 - MEDICATION RELEASED FROM HOLD NOT SHOWING NURSE VERIFIED IN BCMA duplicate: INC19389775 - When provider places an order 'on hold' CPRS creates another order, nurse must verify again BCMA Problem: -------- After a medication is released from hold (in CPRS) and is verified by a nurse (in CPRS), the medication is not showing in BCMA as being nurse verified. In BCMA, after being nurse verified, the medication is still showing *** in the Ver column of the Coversheet, Unit Dose, and IV tabs. Resolution: ----------- The issue is due to not sending an HL7 message for nurse verification. This occurs because the processing quits out when the order action is not a change (XX) or new (NW). When the medication has put on hold and then released off hold, the action of the nurse to verify it is a Release Hold (RL) action and fails to continue to the code that sends the message. The correction is to modify routine ORCSEND to move the quit logic to after the message is sent for the pharmacy package. This patch is only addressing the nurse verification sync issue from CPRS processing. Issues with keeping the nurse verification in sync during Pharmacy processing will be addressed with the future patch PSJ*5.0*426. Technical Resolution: --------------------- Routine ORCSEND is modified to move the quit logic and conditionally call VER^ORMBLDPS for package PS only when the action is NW, XX, or RL. The quit in line VR+6^ORCSEND is commented out, that quit is then added after line VR+9^ORCSEND. Line VR+9^ORCSEND is changed from 'I $$NMSP^ORCD(ORPKG)="PS" D VER^ORMBLDPS(ORIFN) Q' to 'I $$NMSP^ORCD(ORPKG)="PS"&(ORX="NW!(ORX="XX")!(ORX="RL")) D VER^ORMBLDPS(ORIFN) Q' Patient Safety Issues (PSIs) ---------------------------- HITPS-8206 Test Sites: ----------- Bedford VAMC, Bedford MA VA Hudson Valley HCS, Montrose NY 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 loaded with users on the system. You may wish to install it during non-peak hours. Installation will take less than 1 minute. 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*3.0*572) 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 OR*3.0*572. 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: Build 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. 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 routines contained in the OR*3.0*572 patch have been backed out, the first two lines of the routines 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;ORDER ENTRY/RESULTS REPORTING;**[Patch List]**;Dec 17, 1997;Build 4 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: ORCSEND Before: B67866193 After: B69452365 **4,27,45,79,92,141,165,195, 228,243,303,296,390,563,572** Routine list of preceding patches: 563 ============================================================================= User Information: Entered By : Date Entered : SEP 16, 2021 Completed By: Date Completed: JAN 06, 2022 Released By : Date Released : JAN 10, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT