$TXT Created by CPRSNGUIB.DOMAIN.EXT (KIDS) on Monday, 06/24/24 at 12:46 ============================================================================= Run Date: AUG 28, 2024 Designation: OR*3*610 Package : OR - ORDER ENTRY/RESULTS REPORTING Priority: Mandatory Version : 3 SEQ #525 Status: Released Compliance Date: SEP 30, 2024 ============================================================================= Associated patches: (v)OR*3*245 <<= must be installed BEFORE `OR*3*610' (v)OR*3*603 <<= must be installed BEFORE `OR*3*610' Subject: PERSONAL QUICK ORDER,LAB REPORT PARAMS FIXES Category: - Routine Description: ============ This patch addresses the following issues: 1. In CPRS, personal quick order processed a prescription order on an inactivated drug for outpatient. 2. In CPRS, Lab Overview, Pending Lab Orders, and Lab Orders (All) Exceed Max Occurrence Limit. 3. In CPRS, Lab Overview, Pending Lab Orders, and Lab Orders (All) return results outside of given date range. 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 Additional Information: ----------------------- New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: 1. INC24298435 -- CPRS: Personal Quick Order pushed in prescription on an inactivated drug for outpatient. Problem: -------- If a provider creates a quick order a medication in CPRS and then later the DRUG is unmarked for use in Outpatient on the Pharmacy side, CPRS is allowing the medication to be entered and placed with no indication that it should not be ordered now. There needs to be a check when a medication quick order is used for ordering to see if the medication is still marked for use in Pharmacy. This would be for any type of medication quick order to prevent it from being ordered and signed if no longer marked for use in Pharmacy. This issue actually happened at a site using the current CPRS v32a software. I did check with CPRS v32b and it still happens there also. Resolution: ----------- Modified routine ORWUL and ORWDXQ to check if the orderable item within the personal quick order is marked for a specific package. If the orderable item is not marked for the package, then the personal quick order will not be available in CPRS. The check prevents users from processing personal quick orders for specific pharmacy package. 2. INC31277951 -- CPRS: Lab Overview Reports Exceed Max Occurrence Limit Problem: -------- The VistA/CPRS reports do not appear to respect the record limit (max occurrence). They seem to always return all records (more than the promised maximum of 100) from the start date (alpha) until now, which could be very slow if the start date is far in the past. The result is a blocked/frozen CPRS GUI from a long network delay followed by a long rendering time. In addition, Lab Product Support agrees that Labs in general should honor max occurrence. The same issue is also occurring in Pending Lab Orders and Lab Orders All. Resolution: ----------- ORDV02B and ORDV02C routines are updated to honor max occurrence value. ORDV02B routine covers Lab Orders All and Pending Lab Orders. ORDV02C routine covers Lab Overview Collected Specimen. The GUI block occurs whenever the customer has an RPC Broker Call open while attempting to run Lab Orders Overview. Customer agreed to run Lab Orders Overview without opening RPC Broker call as a solution to prevent GUI (Graphical User Interface) freeze in CPRS. 3. INC31277211 -- CPRS: Lab Overview Reports Date Range Not Honored. Problem: -------- The VistA/CPRS reports do not appear to respect the end date (omega) parameters. The expected behavior is to return only the records within the specified alpha-omega date range (unless either alpha or omega were -1). In addition, Lab Product Support agrees that Labs in general should honor date range input from users. The same issue is also occurring in Pending Lab Orders and Lab Orders All. Resolution: ----------- ORDV02B and ORDV02C routines are updated to honor date range input from users. ORDV02B routine covers Lab Orders All and Pending Lab Orders. ORDV02C routine covers Lab Overview Collected Specimen. Test Sites: ----------- ORLANDO,FL VAMC NORTHPORT, NY VAMC 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 name. (OR*3.0*610) 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*610. 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: ------------------------ 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. The back-out plan is to restore the routines from the backup created. It is imperative that a backup was performed PRIOR to installation. No data was modified by this patch installation and, therefore, no rollback strategy is required. 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 11 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: ORDV02B Before: B42196710 After: B47355768 **350,423,377,534,610** Routine Name: ORDV02C Before: B23821276 After: B25820877 **350,423,377,534,603,610** Routine Name: ORWDXQ Before: B14448552 After: B15648782 **10,85,245,610** Routine Name: ORWUL Before: B51080306 After: B69475646 **85,117,131,132,164,215,245,610** Routine list of preceding patches: 245, 603 ============================================================================= User Information: Entered By : Date Entered : SEP 25, 2023 Completed By: Date Completed: AUG 28, 2024 Released By : Date Released : AUG 28, 2024 ============================================================================= Packman Mail Message: ===================== $END TXT