$TXT Created by MNTVBB.DOMAIN.EXT (KIDS) on Wednesday, 01/28/26 at 15:57 ============================================================================= Run Date: APR 14, 2026 Designation: PSO*7*751 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #673 Status: Released Compliance Date: MAY 15, 2026 ============================================================================= Associated patches: (v)PSO*7*444 <<= must be installed BEFORE `PSO*7*751' (v)PSO*7*747 <<= must be installed BEFORE `PSO*7*751' (v)PSO*7*777 <<= must be installed BEFORE `PSO*7*751' Subject: RX REFILL STUCK IN SUSPENSE DUE TO VA FILEMAN AUDIT Category: - Routine Description: ============ This patch addresses the following issues: 1. INC35632079 - Rx Refill Stuck In Suspense dup INC40468132 2. INC38652024 - VistA error was caused by TEST PATCH PSO*7.0*751 v2 3. INC40024192 - Non-CS CMOP transmissions failing with TEST PATCH PSO*7.0*751 v3 installed 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. INC35632079 - Rx Refill Stuck In Suspense dup INC40468132 Problem: -------- When VA FileMan Audit is turned on for a sub-field in the REFILL (#52) multiple within the PRESCRIPTION (#52) file followed by a top level field in the PRESCRIPTION (#52) file and a refill is suspended and then deleted, the refill may remain stuck in suspense. If the suspended & deleted refill is a Consolidated Mail Outpatient Pharmacy (CMOP) refill, then it may also reprint every day when the site runs local suspense. Users are unable to refill the prescription (Rx) again since it is stuck in suspense. When a refill is deleted from suspense, routine K52^PSOUTL handles the deletion of the record from the RX SUSPENSE (#52.5) file. However, when a VA FileMan Audit is turned on, the Y variable used by this routine to determine if the refill should be deleted is changed to an unexpected value; this causes the deletion to fail and leaves the refill in the RX SUSPENSE (#52.5) file. Variable X, which contains the value of the field being edited and is used by this routine, may also be changed by the audit. Even though the refill remains in the RX SUSPENSE (#52.5) file, users are unable to delete the suspense record via the Patient Prescription Processing option [PSO LM BACKDOOR ORDERS], so the refill remains stuck. The suspense record can only be deleted via VA FileMan. Resolution: ----------- This patch modifies routine PSOUTLA1 to set variable PSORFKILL at the bottom of WARN^PSOUTLA1, which is called after the user enters @ at the REFILL DATE: prompt. If the user then answers YES to the SURE YOU WANT TO DELETE THE ENTIRE REFILL DATE? prompt, variable PSORFKILL is then used in K52^PSOUTL to set Y=1. This modification accounts for the fact that Y is not always equal to 1 when it gets to K52^PSOUTL while VA FileMan Audit is turned on. Variable PSORFKILL is newed before the call to ^DIE in PSOORED2 where the above mentioned prompts are called as well as the call to K52^PSOUTL. 2. INC38652024 - VistA error was caused by TEST PATCH PSO*7.0*751 v2 Problem: -------- An error, UPDFL+44^PSOBPSU2, occurred during Initial Operating Capability (IOC) testing after PSO*7.0*751 v2 was installed in a Production account. This error led to the discovery that if PAT, CNT & SUB variables exist in the routine symbol table of the calling routine, they are overwritten and killed. Resolution: ----------- This patch modifies the PSOUTL routine to add newing of variables PAT, CNT & SUB. Newing these variables will prevent them from being overwritten & killed, thus preventing the error & other potential errors. 3. INC40024192 - Non-CS CMOP transmissions failing with TEST PATCH PSO*7.0*751 v3 installed Problem: -------- The non-controlled substances (non-CS) CMOP transmission failed during IOC testing after PSO*7.0*751 v3 was installed in a Production account. This transmission failure was accompanied by the following error - CMPRXTYP+3^PSOCMOP ^PS(52.5 It was determined that the initial resolution for Problem #1 that involved Data Dictionary (DD) changes was the cause of this error. These DD changes, specifically PRESCRIPTION (#52) file index modifications, caused the RX SUSPENSE (#52.5) file record to be deleted but then attempted to reference that deleted record in subsequent processing. Resolution: ----------- This version of the patch revises the resolution for Problem #1 to no longer use the PRESCRIPTION (#52) file index modifications, thus preventing the error that accompanied the non-CS CMOP transmission failure. Test Sites: ----------- Hershel "Woody" Williams VAMC (Huntington, WV) Raymond G. Murphy VAMC (Albuquerque, NM) Test Sites - SNOW Change Order #: --------------------------------- Hershel "Woody" Williams VAMC - CHG0701822 Raymond G. Murphy VAMC - CHG0703537 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Documentation describing the new functionality is not included in this release. Documentation Title File Name --------------------------------------------------------------------- N/A 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. It is not necessary to disable any options or protocols. 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 & 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 your build PSO*7.0*751. 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*751. iii. When prompted for the following, enter "R" for Routines or "B" for Build. (We recommend "R" for PSO*7.0*751.) Select one of the following: B Build (including Routines) R Routines Only Backup Type: B// iv. If you select "B", 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. Post-Installation Instructions: N/A Installation Verification: -------------------------- Successful installation can be verified by printing the first 2 lines of the PSO routine contained in this patch using the First Line Routine Print option [XU FIRST LINE PRINT]. The second line of the routine will contain the patch number (751) at the end of the [PATCH LIST] section (as shown in the Routine Information section at the bottom of this patch description). Additionally, the Calculate and Show Checksum Values option [XTSUMBLD-CHECK] can be run to compare the routine checksum to the "After" checksum documented in this patch description. Back-Out/Roll Back Plan: ------------------------ Back-out will be done only with the concurrence and participation of the development team and appropriate VA site/region personnel. The decision to back out or roll back software will be a joint decision between the development team, VA site/region personnel, and other appropriate VA personnel. Prior to installing an updated Kernel Installation & Distribution System (KIDS) package, the site/region should have saved a backup of the build or routine in a mail message using the Backup a Transport Global option [XPD BACKUP] from the Installation menu [XPD INSTALLATION MENU]. The back-out plan is to restore the routine from the backup created. The message containing the backed-up routine 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 routine onto the VistA system. If the patch was backed up for the build, from the Kernel Installation & Distribution System menu [XPD MAIN], select the Installation menu [XPD INSTALLATION MENU]. Then select the Install Package(s) option [XPD INSTALL BUILD] and choose the patch (PSO*7.0*751b) to install. No data was modified by this patch installation and, therefore, no rollback strategy is required. Validation of Back-Out Procedure: --------------------------------- Successful back-out can be verified by confirming the checksum has been returned to the pre-patch value using CHECK1^XTSUMBLD. It can also be verified by printing the first 2 lines of the PSO routine contained in this patch using the First Line Routine Print option [XU FIRST LINE PRINT]. Once the routine contained in this patch has been backed out, the second line of the routine will no longer contain the designation of patch PSO*7.0*751. Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 8 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOORED2 Before: B97018133 After: B97102727 **2,51,46,78,102,114,117,133, 159,148,247,260,281,289,276, 358,251,385,427,538,574,562, 441,703,747,751** Routine Name: PSOUTL Before:B185221257 After:B161242702 **1,21,126,174,218,259,324,390, 313,411,466,477,626,639,692, 777,751** Routine Name: PSOUTLA1 Before: B66629257 After: B89917433 **35,186,218,259,206,388,444,751** Routine list of preceding patches: 444, 747, 777 ============================================================================= User Information: Entered By : Date Entered : JAN 25, 2024 Completed By: Date Completed: APR 14, 2026 Released By : Date Released : APR 14, 2026 ============================================================================= Packman Mail Message: ===================== $END TXT