$TXT Created by L at MNTVBB.DOMAIN.EXT (KIDS) on Friday, 04/17/26 at 09:34 ============================================================================= Run Date: JUL 02, 2026 Designation: PSO*7*827 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #681 Status: Released Compliance Date: AUG 02, 2026 ============================================================================= Associated patches: (v)PSO*7*763 <<= must be installed BEFORE `PSO*7*827' (v)PSO*7*768 <<= must be installed BEFORE `PSO*7*827' (v)PSO*7*780 <<= must be installed BEFORE `PSO*7*827' Subject: UNPARKED REFILL NOT SUSPENDING TO CMOP AND UNHOLD/PARK ISSUE Category: - Routine Description: ============ This patch addresses the following issues: 1. Prescriptions removed from park status are routing to local suspense instead of Consolidated Mail Outpatient Pharmacy (CMOP) suspense. 2. A prescription will become "incompletely parked" if it is placed in a park status during an "unholding" action. 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. INC41904667: Unparked CMOP Rx Suspending Locally Problem: ------- A prescription refill initially suspended for CMOP is later parked and refilled again but is then incorrectly suspended for local print. In this scenario, the refill should suspend for CMOP, not local print. Resolution: ---------- Some modifications to routines PSOCMOPA and PSOPRKA will ensure that a parked refill previously suspended to CMOP will suspend to CMOP again upon a refill action. 2. INC41379591: Unhold and then Park Issue INC42665644 (duplicate) Problem: ------- A prescription will become "incompletely" parked during the following scenario: (1) A prescription is placed on hold; (2) Later when it is "unheld", a future fill date is specified and the prescription is placed on park during the unhold action. In Computerized Patient Record System (CPRS), the prescription does not indicate a parked status. In VistA, the medication profile view and the activity log do not indicate a parked status. However, the detail view of the prescription displays that it is parked. Other downstream issues occur in dispensing functions, etc. The root cause in the downstream issues is that the "PARK" subscript in the PRESCRIPTION (#52) file is not set. Resolution: ---------- Modify routine PSOHLD to correctly file the prescription if is parked with a future fill date during the unhold action. The views in CPRS and VistA will all indicate that the prescription is parked. The code change involved moving the line at EN+67^PSOHLD to EN+63^PSOHLD. The logic had been branching off when checking the fill date against "today" and thus not checking whether the routing of "PARK" was specified. Test Sites: ----------- VA Central Plains Health Care System (Iowa City, IA) Manchester VA Medical Center (Manchester, NH) Test Sites - SNOW Change Order #: -------------------------------- Iowa City - CHG0744956 Manchester - CHG0744353 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 or build name (ex. PSO*7.0*827) 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*827. iii. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build R Routines 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 Back-out/Rollback Strategy: --------------------------- 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 build 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 build 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. The back-out plan is to restore the build from the backup created. 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: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 4 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOCMOPA Before: B22326197 After: B23007627 **61,76,443,508,441,768,827** Routine Name: PSOHLD Before:B105565408 After:B106003356 **1,16,21,24,27,32,55,82,114, 130,166,148,268,281,298,358, 353,385,386,370,488,562,441, 712,780,827** Routine Name: PSOPRKA Before: B78603877 After: B84532828 **441,712,763,827** Routine list of preceding patches: 763, 768, 780 ============================================================================= User Information: Entered By : Date Entered : MAR 20, 2026 Completed By: Date Completed: JUL 02, 2026 Released By : Date Released : JUL 02, 2026 ============================================================================= Packman Mail Message: ===================== $END TXT