$TXT Created by at MNTVBB.DOMAIN.EXT (KIDS) on Wednesday, 12/08/21 at 17:03 ============================================================================= Run Date: APR 11, 2022 Designation: OR*3*578 Package : OR - ORDER ENTRY/RESULTS REPORTING Priority: Mandatory Version : 3 SEQ #493 Status: Released Compliance Date: MAY 12, 2022 ============================================================================= Associated patches: (v)OR*3*481 <<= must be installed BEFORE `OR*3*578' Subject: CLINIC MED DUPLICATE ORDER CHECKING ISSUE Category: - Routine Description: ============ This patch addresses the following issue: Duplicate order checking might display an incorrect dispense drug against pending clinic medications. Defect Tracking System Ticket(s) & Overview: =========================================== INC20107634: Clinic Med Order Checking Issue in CPRS Issue: ----- Duplicate order checking might display an incorrect dispense drug in both CPRS and VistA option "Patient Prescription Processing (PSO LM BACKDOOR ORDERS)" when checking against pending clinic medications orders which have free text dosages. Resolution: ---------- In CPRS, routine ORKPS1 has been modified to ensure that the duplicate order checking display will not indicate a dispense drug when checking against pending Clinic Medication orders with free text dosages. Note: Order Checks between Non-VA Meds and Outpatient Meds are not addressed with this patch. This is not an enhancement to the current Medication Order Check functionality. Patch PSO*7.0*663 addresses the same issue in VistA option "Patient Prescription Processing (PSO LM BACKDOOR ORDERS)". The two patches do not have to be installed at the same time. Test Sites: ----------- Martinsburg VAMC (Martinsburg,WV) Miami VAMC (Miami,FL) Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Patch Instructions: ------------------ 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 name. (ex. OR*3.0*578). 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*578. 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/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. Example - load the backup build: Enter message action (in IN basket): Ignore// Xtract KIDS Select PackMan function: 6 INSTALL/CHECK MESSAGE Line 8 Message #169519 Unloading KIDS Distribution OR*3.0*578b OR*3.0*578b Want to Continue with Load? YES// Loading Distribution... OR*3.0*578b Example - install the backup build: Select Installation Option: Install Package(s) Select INSTALL NAME: OR*3.0*578b 9/7/21@11:37:39 => Backup of OR*3.0*578 on Aug 18, 2021. Build [Answer subsequent prompts in usual manner.] 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. 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*578 build 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. 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 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: ORKPS1 Before:B110514189 After:B119007398 **232,272,346,352,345,311,402, 457,469,481,578** Routine list of preceding patches: 481 ============================================================================= User Information: Entered By : Date Entered : NOV 15, 2021 Completed By: Date Completed: APR 07, 2022 Released By : Date Released : APR 11, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT