$TXT Created by C32AD.DEVSLC.DOMAIN.EXT (KIDS) on Tuesday, 09/07/21 at 11:46 ============================================================================= Run Date: SEP 27, 2021 Designation: OR*3*568 Package : OR - ORDER ENTRY/RESULTS REPORTING Priority: EMERGENCY Version : 3 SEQ #480 Status: Released Compliance Date: OCT 04, 2021 ============================================================================= Associated patches: (v)OR*3*539 <<= must be installed BEFORE `OR*3*568' Subject: CPRS V32A - NOTES LATENCY ISSUE Category: - Routine Description: ============ Long Beach reported an issue with latency when attempting to load the Computerized Patient Record System (CPRS) Graphical User Interface (GUI) chart for patients with large numbers of notes. To correct an issue with the display of the number of note titles, CPRS v32a had been modified to determine whether or not a user had access to a note before it was counted in the total. This change was causing some issues with latency. For now, this change has been reverted and the issue of note totals will be revisited in the future. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File Number New/Modified/Deleted --------- ----------- -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC19230405 - CPRS Loads slow 2. INC19220185 - CPRS latency issues 3. INC19230403 - CPRS is running very slow. 4. INC19230425 - CPRS is running very slow. 5. INC19234257 - My computer isvery slowand it delayed my work to followup patient care 6. INC19230405 - CPRS loads slow 7. INC19238908 - CPRS is extremely slow Problem: ------- As a part of the resolution to a patient safety New Service Request related to the Notes tab displays, a change was made on how to count the number of notes. The purpose was to make the total county more accurate by taking into consideration which notes were child notes and which notes might not be viewable by the user. However, this change created a latency for patients with large numbers of notes. Resolution: ---------- The updates to the counting logic were removed. Test Sites: ----------- Upstate New York Health Care System Long Beach VAMC, CA Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Patch Installation: ------------------- Pre/Post Installation Overview: 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 OR*3.0*568. 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*568 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 this message? 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 site leadership may make the decision to back-out the patch. There is no data distributed with the patch, so no rollback will be required. To back-out the patch, restore the backup created when the patch was installed. For the back-out to be performed, you must ensure a backup is created. To verify the back-out is successful the routine checksum should be at its pre-patch value. 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: ORCNOTE Before: B77615309 After: B75813697 **22,48,65,104,280,370,539,568** Routine list of preceding patches: 539 ============================================================================= User Information: Entered By : Date Entered : AUG 23, 2021 Completed By: Date Completed: SEP 24, 2021 Released By : Date Released : SEP 27, 2021 ============================================================================= Packman Mail Message: ===================== $END TXT