$TXT Created by CLN1G2.AAC.DOMAIN.EXT (KIDS) on Friday, 06/26/20 at 12:42 ============================================================================= Run Date: SEP 14, 2020 Designation: OR*3*521 Package : OR - ORDER ENTRY/RESULTS REPORTING Priority: Mandatory Version : 3 SEQ #446 Status: Released Compliance Date: OCT 15, 2020 ============================================================================= Associated patches: (v)OR*3*377 <<= must be installed BEFORE `OR*3*521' Subject: ORDER DETAILS DISPLAYING INCORRECT DRUG Category: - Routine Description: ============ This patch will resolve the following issue: INC8143873 - OEL^PSOORRL Application Programmer Interface (API) used incorrectly Defect Tracking System Ticket(s) & Overview: INC8143873 - OEL^PSOORRL API used incorrectly Rational Defect - 1154608 Problem: -------- The Order Detail screen in Computerized Patient Record System (CPRS) is displaying the Inpatient medication order incorrectly. This display issue is due to incorrect usage of API OEL^PSOORRL (Integration Agreement 2400). Resolution: ----------- A modification has been made in routine ORQ21 to assure the proper data is passed to the OEL^PSOORRL API so the medication data is processed correctly. Test Sites: ----------- Bath VAMC (Bath, NY) Orlando VAMC (Orlando, FL) Western Colorado HCS (Grand Junction, CO) 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. (OR*3.0*521) 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 of any routines exported with this patch. It will not backup any other changes such as DDs or templates. 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. Post-Installation Instructions: NONE Back-Out/Roll Back Plan: ------------------------ 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. Validation of Back-out Procedure: --------------------------------- The Back-out Procedure can be verified by printing the first 2 lines of the routine contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routine contained in the OR*3.0*521 patch has 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 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: ORQ21 Before: B39169290 After: B43976767 **141,190,195,215,243,361,350, 417,377,521** Routine list of preceding patches: 377 ============================================================================= User Information: Entered By : Date Entered : DEC 03, 2019 Completed By: Date Completed: SEP 14, 2020 Released By : Date Released : SEP 14, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT