$TXT Created by at CPRSNGUIB.DOMAIN.EXT (KIDS) on Friday, 10/03/25 at 11:41 ============================================================================= Run Date: JAN 15, 2026 Designation: OR*3*625 Package : OR - ORDER ENTRY/RESULTS REPORTING Priority: Mandatory Version : 3 SEQ #537 Status: Released Compliance Date: FEB 15, 2026 ============================================================================= Associated patches: (v)OR*3*405 <<= must be installed BEFORE `OR*3*625' (v)OR*3*461 <<= must be installed BEFORE `OR*3*625' Subject: CPRS CLINIC INFUSION, VIS SHEET ISSUE & INCOMPLETE OUTPATIENT ORDERS Category: - Routine Description: ============ This patch addresses the following issues: 1.INC29145882 -VISTAOR-37982 -Clinic Infusion Medications are displayed in the "Infusions" package as opposed to "Clinic Infusions" in CPRS 2. INC26174672 - VISTAOR-33937 - Multiple VIS Sheets Not Showing. 3.INC28822263 -VISTAOR-35454 -Mumps error OUT+5^ORMPS1 4.INC31681077 -VISTAOR-37164 -R3 -(CMS)Bug in Medication Package. Inpatient Medications not displaying as an Inpatient Medication in CPRS. Duplicate(s): INC32306932, INC32507532, INC33118775, INC33589172, INC35017564, INC37580925. EHRM Impact Statement: ---------------------- -This patch should have no EHRM impact, and can be installed at all sites, including EHRM converted sites. 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): HITPS-10825 HITPS-11291 HITPS-12321 Defect Tracking System Ticket(s) & Overview: 1.INC29145882 -VISTAOR-37982 -Clinic Infusion Medications are displayed in the "Infusions" package as opposed to "Clinic Infusions" in CPRS. Problem: -------- Infusion orders in CPRS are not updated to a Clinic Infusion package whenever processing a location change (to a clinic location). When prompted, the provider clicks the clinic location and signs the infusion order in the location change dialog box. After signing, the order is dropped into the "infusions" package (with the outpatient clinic location on the order) rather than the "clinic infusions." Resolution: ----------- Changes made to address this issue were in ORWDX1. The fix ensures that whenever a location change is made, the Order Display Group is updated to match the new location. The medication will be displayed in the correct package. 2.INC26174672 - VISTAOR-33937 - Multiple VIS Sheets Not Showing. Problem: --------- Provider selects two separate vaccines; Hepatitis A and Hepatitis B in the Vaccine Information Statement via VIMM form. Once the form is completed, Hep A only appears under the Vaccine Information Statement section in the progress note. Resolution: ----------- Fix was made in ORFEDT routine to address the Vaccine Information Statement (VIS) section. All selected vaccines from the VIMM form should appear in progress notes under the VIS section. 3.INC28822263 -VISTAOR-35454 -Mumps error OUT+5^ORMPS1 Problem: -------- Hard error caused by existing code oversite (quit condition in a function without a return value). Calls to ISSUPPLY^ORUTL3 quit without a return if no information is found in the Drug file. Resolution: ----------- Added return of 0 to prevent error. 4.INC31681077 -VISTAOR-37164 -R3 -(CMS)Bug in Medication Package. Inpatient Medications not displaying as an Inpatient Medication in CPRS. Problem: -------- In CPRS, an order is currently being displayed as Inpatient Medications in the Meds tab and Outpatient Medications in the Orders tab. This issue occurred when the provider sets a Non-Imo clinic location in CPRS for the patient. Then the patient is admitted in VistA without refreshing CPRS, an Inpatient Medication order was placed. The provider signs the order under File > Review / Sign Changes. After completing the Change Location process, the medication still appears as Outpatient Medications instead of Inpatient Medications in the Orders tab. This is causing confusion amongst staff when the order displays correctly under Inpatient Meds in the Medications tab and Unit Dose from the Vista Order. The order can't be processed in BCMA and staff cannot scan against it. Resolution: ----------- ORWDX1 routine was modified to make sure the package reflects the dialog in CPRS. The fix is made within the CHANGE tag, which processes the Change Location requests on medications orders. Once the desired location is set, the fix ensures the proper information on the Order file (#100) is updated and the medication is displayed in the correct package in the Orders tab in CPRS. Test Sites: ----------- ORLANDO VAMC BOISE VAMC Test Sites - SNOW Change Order#: ORLANDO VAMC - CHG0669858 BOISE VAMC - CHG0670229 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Patch Installation: ------------------- Pre-Installation Instructions: N/A 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*625) 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*625. 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 10 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: ORFEDT Before: B36843407 After: B38334703 **405,625** Routine Name: ORUTL3 Before: B4735089 After: B4739537 **111,397,405,625** Routine Name: ORWDX1 Before: B58032777 After: B52863372 **85,187,195,215,243,296,341, 350,461,625** Routine list of preceding patches: 405, 461 ============================================================================= User Information: Entered By : Date Entered : AUG 29, 2024 Completed By: Date Completed: JAN 12, 2026 Released By : Date Released : JAN 15, 2026 ============================================================================= Packman Mail Message: ===================== $END TXT