$TXT Created by at MNTVBB.DOMAIN.EXT (KIDS) on Saturday, 07/11/20 at 15:06 ============================================================================= Run Date: SEP 24, 2020 Designation: OR*3*534 Package : OR - ORDER ENTRY/RESULTS REPORTING Priority: Mandatory Version : 3 SEQ #450 Status: Released Compliance Date: OCT 25, 2020 ============================================================================= Associated patches: (v)OR*3*377 <<= must be installed BEFORE `OR*3*534' Subject: NOTIFICATION LISTING AND LAB CRITICAL FLAG ISSUES Category: - Routine Description: ============ This patch addresses two (2) issues: 1. The "Display the Notifications a User Can Receive" option does not display the ORB PROCESSING FLAG parameter edits based on Team when they are set to Mandatory. 2. Results might erroneously flag as "critical" in two CPRS reports on the Labs tab. Options Associated: Option Name Type New/Modified/Deleted ------------------------ ----------- -------------------- ORB3 RECIP NOTIFICATIONS run routine Modified Associated NSR(s): ================== N/A Patient Safety Issues (PSIs): ============================ N/A Defect Tracking System Ticket(s) & Overview: ============================================ 1. INC5295661: Team Member Display Issue in Notification Listing Problem: ------- The "Display the Notifications a User Can Receive [ORB3 RECIP NOTIFICATIONS]" option does not display the ORB PROCESSING FLAG parameter settings based on Team when they are set to Mandatory. Resolution: ---------- The option "Display the Notifications a User Can Receive [ORB3 RECIP NOTIFICATIONS]" will now display the ORB PROCESSING FLAG parameter edits based on Team when they are set to Mandatory. Since the "Condensed" format of the "new" option is in the same format as the "old" option's report, it was decided by Tier 2, CPRS development, and HPS Sustainment to replace the program call in the "old" option with the program call of the "new" option. The option is now available under both the "old" and "new" notification menu trees. Before install: NAME: ORB3 RECIP NOTIFICATIONS MENU TEXT: Display the Notifications a User Can Receive TYPE: run routine CREATOR: xxxx,xxxx PACKAGE: ORDER ENTRY/RESULTS REPORTING DESCRIPTION: This option prompts for a user/recipient then processes each notification to determine if and why the user will receive the notification. This information is then displayed. ROUTINE: USRNOTS^ORB3MGR2 UPPERCASE MENU TEXT: DISPLAY THE NOTIFICATIONS A US After install: NAME: ORB3 RECIP NOTIFICATIONS MENU TEXT: Display the Notifications a User Can Receive TYPE: run routine CREATOR: xxxx,xxxx PACKAGE: ORDER ENTRY/RESULTS REPORTING X ACTION PRESENT: YES DESCRIPTION: This option prompts for a user/recipient then processes each notification to determine if and why the user will receive the notification. This information is then displayed. EXIT ACTION: W @IOF ROUTINE: DETV^ORPARMG1 UPPERCASE MENU TEXT: DISPLAY THE NOTIFICATIONS A US 2. INC9398056: Critical Result Flag Issue on CPRS Lab Reports Problem: ------- Results might erroneously flag as "critical" in two CPRS reports on the Labs tab. The two reports are "Lab Overview (Collected Specimens)" and "Lab Orders (All)". The root cause of the issue is that any comment lines containing "H*" and/or "L*" are causing the results to flag as critical. Resolution: ---------- Modify routines ORDV02B and ORDV02C to only determine critical flags from the test result flag - not from comment text. Routines: ORDV02B and ORDV02C Test Sites: =========== Altoona - VA Medical Center (Altoona, PA) San Diego - VA Medical Center (San Diego, CA) Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Patch Instruction: ----------------- 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. NOTE: CPRS 31b must be installed before this patch is installed. OR*3.0*377 is a required build and is a component of CPRS31b. NOTE: If XINDEX is performed both pre- and post-install on this build, a known error/warning might display: ORDV02B * * 119 Lines, 7312 Bytes, Checksum: B43440865 LO+2 F - Reference to routine '^OMGCOAS1'. That isn't in this UCI. ORDV02C * * 80 Lines, 5177 Bytes, Checksum: B22901238 OV+2 F - Reference to routine '^OMGCOAS1'. That isn't in this UCI. The routine line LO+2^ORDV02B checks to see if routine OMGCOAS1 exists in the environment before proceeding. If the routine does not exist, XINDEX generates a warning, which is of no concern in this case. 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*534) 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. Back-out/Rollback Strategy: -------------------------- 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 routines included in this patch prior to installation. The option "Display the Notifications a User Can Receive" option can be restored to the original pre-install state by editing the option: Select OPTION NAME: MENU MANAGEMENT XUMAINT Menu Management Edit options Key Management ... Restrict Availability of Options Option Access By User List Options by Parents and Use Fix Option File Pointers Help Processor ... OPED Screen-based Option Editor Display Menus and Options ... Menu Rebuild Menu ... Out-Of-Order Set Management ... See if a User Has Access to a Particular Option Show Users with a Selected primary Menu Select Menu Management Option: EDit options Select OPTION to edit: DISPLAY THE NOTIF 1 DISPLAY THE NOTIFICATIONS A US ORB3 RECIP NOTIFICATIONS Display th e Notifications a User Can Receive 2 DISPLAY THE NOTIFICATIONS A US ORB3 LM 14 NOTS FOR USERS Display the Notifications a User Can Receive [NEW] CHOOSE 1-2: 1 ORB3 RECIP NOTIFICATIONS Display the Notifications a User Can Receive NAME: ORB3 RECIP NOTIFICATIONS Replace MENU TEXT: Display the Notifications a User Can Receive Replace PACKAGE: ORDER ENTRY/RESULTS REPORTING// OUT OF ORDER MESSAGE: LOCK: REVERSE/NEGATIVE LOCK: DESCRIPTION: 1>This option prompts for a user/recipient then processes each notification 2>to determine if and why the user will receive the notification. This 3>information is then displayed. EDIT Option: TYPE: run routine// HEADER: ENTRY ACTION: EXIT ACTION: W @IOF// @ SURE YOU WANT TO DELETE? Y (Yes) ROUTINE: DETV^ORPARMG1// USRNOTS^ORB3MGR2 CREATOR: xxxx,xxxx// HELP FRAME: PRIORITY: Select TIMES PROHIBITED: Select TIME PERIOD: RESTRICT DEVICES?: Select PERMITTED DEVICE: 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. To verify the back-out completed successfully, ensure the checksum matches the pre-patch checksum from the 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: ORDV02B Before: B43440865 After: B42196710 **350,423,377,534** Routine Name: ORDV02C Before: B23842995 After: B22901238 **350,423,377,534** Routine list of preceding patches: 377 ============================================================================= User Information: Entered By : Date Entered : JUN 22, 2020 Completed By: Date Completed: SEP 24, 2020 Released By : Date Released : SEP 24, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT