$TXT Created by . at MNTVBB.DOMAIN.EXT (KIDS) on Wednesday, 10/22/25 at 10:38 ============================================================================= Run Date: MAY 01, 2026 Designation: PSO*7*812 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #675 Status: Released Compliance Date: JUN 01, 2026 ============================================================================= Associated patches: (v)PSO*7*770 <<= must be installed BEFORE `PSO*7*812' Subject: ERX HOLD QUEUE ISSUE Category: - Routine Description: ============ This patch addresses one issue. Under certain circumstances, an ePrescribing (eRx) change request in the eRx Holding Queue Processing [PSO ERX QUEUE PROCESSING] option, can end up in a status of "HC" (Hold due to change) or "I" In Progress status (if removed from hold) and no further action can be taken on that prescription (Rx) entry. This patch enables the RM (Remove) option to be used in this scenario. 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): N/A Defect Tracking System Ticket(s) & Overview: 1. INC40018386 - Needs to remove an order from pharmacy VistA eRX Queue INC40107715 - duplicate INC40120066 - duplicate Problem: -------- When an original eRx order has a change request entered (for any reason), the original order goes to a status of HC (hold due to change), and a new entry with a V number is created for the change. Additional changes can be requested on the original order. If, however, a change is requested on the V number (the replacement order), the first V number will go to status of HC (hold due to change) and a new (second) V number is created. The original/first V number can be removed from hold, and go to status "I" (In Progress), but other than that, no other action can be performed on that entry in the eRx Holding Queue Processing [PSO ERX QUEUE PROCESSING] option, and the order will be stuck in queue in either I or HC status. Resolution: ----------- This patch will enable the RM (ERX Remove) option for eRx Change requests that are stuck in HC or I status. This will enable the users to remove the entry from the holding queue. Test Sites: ----------- South Texas VHCS (STX) VA Long Beach Health Care (LON) SNOW Change Order #: ------------------- South Texas VHCS (STX): CO # CHG0712175 VA Long Beach Health Care (LON): CO # CHG0720581 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Documentation updates are not included in this release. Patch Installation: ------------------- Pre/Post Installation Overview: This patch is installed using typical PackMan procedures. There are no unique pre installation or post installation steps required 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. ) 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 PSO*7.0*812 iii. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build (including Routines) R Routines Only Backup Type: B// 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. Post-Installation Instructions: There are no specific post-installation steps. Back-Out/Roll Back Plan: ------------------------ Back-out will be done only with the concurrence and participation of development team and appropriate VA site/region personnel. 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. Prior to installing an updated KIDS package, the site/region should have saved a backup of the routines in a mail message using the Backup a Transport Global [XPD BACKUP] menu option (this is done at time of install). The message containing the backed-up routines can be loaded with the "Xtract PackMan" function at the Message Action prompt. The Packman function "INSTALL/CHECK MESSAGE" is then used to install the backed up routines onto the VistA System. If the patch was backed up for the build, from the Kernel Installation and Distribution System Menu, select the Installation Menu. Then select the Install Package(s) option and choose the patch (PSO*7.0*812b) to install. The back-out plan is to restore the routines from the backup created. No data was modified by this patch installation and, therefore no additional rollback strategy is required. Validation of Backout Procedure: --------------------------------- The Backout Procedure can be verified by confirming the checksums have been returned to the pre-patch value using CHECK1^XTSUMBLD. It can also be verified by printing the first two lines of the routine(s) contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. After the routine(s) contained in this patch have been backed out, the second line of each routine will no longer contain the designation of patch [812]. Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 1 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOERXU7 Before:B129576560 After:B130767717 **581,617,700,746,769,770,812** Routine list of preceding patches: 770 ============================================================================= User Information: Entered By : Date Entered : SEP 29, 2025 Completed By: Date Completed: MAY 01, 2026 Released By : Date Released : MAY 01, 2026 ============================================================================= Packman Mail Message: ===================== $END TXT