$TXT Created by CLN2G2.AAC.DOMAIN.EXT (KIDS) on Thursday, 12/24/20 at 16:06 ============================================================================= Run Date: APR 22, 2021 Designation: OR*3*544 Package : OR - ORDER ENTRY/RESULTS REPORTING Priority: Mandatory Version : 3 SEQ #461 Status: Released Compliance Date: MAY 23, 2021 ============================================================================= Associated patches: (v)OR*3*519 <<= must be installed BEFORE `OR*3*544' Subject: RECEIVED WHEN TRYING TO ACCESS A PATIENT IN CPRS Category: - Routine Description: ============ This patch addresses the following issue: 1. A hard Mumps (M) error is generated during a patient lookup in the Computerized Patient Record System (CPRS) graphical user interface (GUI). Defect Tracking System Ticket(s) & Overview: 1. INC13999003: Received LAST5+4^ORWPT when trying to access a patient in CPRS Problem: -------- A hard M error is generated during the patient lookup in the CPRS GUI. This occurs when the clinician is using the last four digits of the social security number lookup or the first letter of the last name with the last four digits of the social security number lookup. The routine ORWPT reads the BS (last four digits) index or the BS5 (first letter of last name, last four digits) index for the patient lookup. Some records in either or both indexes may point to a PATIENT (#2) file record that does not exist. Resolution: ----------- The routine ORWPT has been modified to confirm the record in either the BS or BS5 index does point to an existing PATIENT (#2) file record. Test Sites: ----------- Hunter Holmes McGuire VAMC (Richmond, VA) Roseburg VA HCS (Roseburg, OR) 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. or XXXXX BUILD X.X) 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*544. 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: ------------------------ 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 this patch description. 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 1 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: ORWPT Before: B80612428 After: B81289007 **10,85,132,149,206,187,190, 215,243,280,306,311,441,528, 519,544** Routine list of preceding patches: 519 ============================================================================= User Information: Entered By : Date Entered : DEC 15, 2020 Completed By: Date Completed: APR 21, 2021 Released By : Date Released : APR 22, 2021 ============================================================================= Packman Mail Message: ===================== $END TXT