$TXT Created by NNE at MNTVBB.DOMAIN.EXT (KIDS) on Tuesday, 03/31/26 at 11:16 ============================================================================= Run Date: JUN 17, 2026 Designation: PSO*7*810 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #679 Status: Released Compliance Date: JUL 17, 2026 ============================================================================= Associated patches: (v)PSO*7*770 <<= must be installed BEFORE `PSO*7*810' (v)PSO*7*772 <<= must be installed BEFORE `PSO*7*810' Subject: SPMP DISPLAY FIXES Category: - Routine - Other Description: ============ This patch addresses the following issues: Ticket(s): INC39934980/INC39935062/INC39935006/INC40884896 for the State Prescription Monitoring Program (SPMP) Ticket INC39934980: Batch number is not displayed for the TH02 and TT01 elements. Ticket INC39935062: Remove verbiage "and PAT12 through PAT16 are left blank" from PAT22 elements for ASAP versions 4.2 and earlier. Ticket INC39935006: Display issue/Formatting Issue for time field in multiple ASAP versions. Ticket INC40884896: $ZERROR is occurring in option RX [View/Export Single Prescription] at the 'Record Type:' prompt when entering a double question mark for the help menu (i.e. '??'). 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 ------------- -------------------- PSO SPMP4 EXPORT RX Modified PSO SPMP2 BATCH EXPORT Modified 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: ----------------------- N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC39934980 - Batch number is not displayed for the TH02 and TT01 elements. Problem: -------- Batch number is not displayed for the TH02 and TT01 elements. Resolution: ----------- Update the logic to display the Batch number in the TH02 and TT01 elements for the NT [CS Prescriptions Not Transmitted], BP [Export Batch Processing], BAT [View/Export Batch], RX [View/Export Single Prescription], and VD [View/Export Void Prescriptions] options under the State Prescription Monitoring Program (SPMP) Menu [PSO SPMP MENU]. In addition, changes will be made to 2 Protocols, PSO SPMP4 EXPORT RX and PSO SPMP2 BATCH EXPORT. By updating the Protocols, the View/Export Prescription screen will refresh with the new batch number that is generated if the user creates a new batch using the 'EXP' Export action on the View/Export Prescription screen. Technical Resolution: --------------------- Routine PSOASAP0 has been modified in the TH02 tag to determine the batch number. Routine PSOSPML2 has been modified in the PSOSPML2 and BAT tags to add variable BAT which will store the batch number for the TH02 and TT01 elements. In addition, the 'ENTRY ACTION' will be updated for 2 Protocols, PSO SPMP4 EXPORT RX and PSO SPMP2 BATCH EXPORT. This will allow the data to refresh in the temporary global so that the batch number will display correctly for the View/Export Prescription screen if the user creates a new batch using the 'EXP' Export action on the View/Export Prescription screen: Protocol - PSO SPMP4 EXPORT RX: ------------------------------- Old: ENTRY ACTION: D EXPORT^PSOSPML4 New: ENTRY ACTION: D EXPORT^PSOSPML4,INIT^PSOSPML4 Protocol - PSO SPMP2 BATCH EXPORT: ---------------------------------- Old: ENTRY ACTION: D EXP^PSOSPML2("EXPORT") New: ENTRY ACTION: D EXP^PSOSPML2("EXPORT"),INIT^PSOSPML2 2. INC39935062 - Remove verbiage "and PAT12 through PAT16 are left blank" from PAT22 elements for ASAP versions 4.2 and earlier. Problem: -------- Remove verbiage "and PAT12 through PAT16 are left blank" from PAT22 elements for ASAP versions 4.2 and earlier. Resolution: ----------- Update ASAP versions 4.2 and earlier to remove verbiage "and PAT12 through PAT16 are left blank" from PAT22 element description. Update the Outpatient Pharmacy V. 7.0 Technical Manual/Security Guide to reflect the update to PAT22 element descriptions. Technical Resolution: --------------------- New Post Install routine PSO810PI was created to update the PAT22 description for ASAP versions 4.1 and 4.2. A MailMan message is generated with the details of the changes as well as before the changes and after the changes display. 3. INC39935006 - Display issue/Formatting Issue for time field in multiple ASAP versions. Problem: -------- Display issue/Formatting Issue for time field in multiple ASAP versions. Resolution: ----------- Update the logic to fix the display issues/formatting issues for the time field in multiple ASAP versions. Technical Resolution: --------------------- Routine PSOSPML3 has been modified in the SETSEG tag to fix the formatting issue with the "Format: Time" display for multiple ASAP versions. 4. INC40884896 - $ZERROR is occurring in option RX [View/Export Single Prescription] at the 'Record Type:' prompt when entering a double question mark for the help menu (i.e. '??'). Problem: -------- $ZERROR is occurring in option RX [View/Export Single Prescription] at the 'Record Type:' prompt when entering a double question mark for the help menu (i.e. '??'). Resolution: ----------- Update the logic to define the PSOASVER variable so it can be used in the call to the help routine ASAPHELP^PSOSPMU2. By defining the variable, the user can access the help menu at the 'Record Type:' prompt. Technical Resolution: --------------------- Routine PSOSPML4 has been modified in the EXPORT tag to define the PSOASVER variable so the help menu can be accessed at the 'Record Type:' prompt. Test Sites: ----------- Manchester VA Medical Center (Manchester, NH) VA Central Plains Health Care System (Omaha, NE) Test Sites - SNOW Change Order #: Manchester - CHG0725104 Omaha - CHG0725106 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. This patch will also contain updates to the Outpatient Pharmacy V. 7.0 Technical Manual/Security Guide manual only. Documentation describing the new functionality is included in this release. Documentation can be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/. Documentation can also be obtained at https://download.vista.domain.ext/index.html/SOFTWARE. Documentation Title File Name --------------------------------------------------------------------- Outpatient Pharmacy V. 7.0 Technical PSO_7_0_P810_TM.DOCX Manual/Security Guide PSO_7_0_P810_TM.PDF 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*810) 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*810 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: Check MailMan for the Post Install information message. The informational message gives the ASAP version number that was updated, and details the verbiage before the Post Install routine runs and the verbiage after the Post Install routine runs. *NOTE: If there were changes made to the ASAP versions, then the following Mailman message will display: Subj: PSO*7.0*810 Post-Install Information [#564398] 04/21/26@17:29 22 lines From: PSO*7.0*810 Post-Install In 'IN' basket. Page 1 -------------------------------------------------------------------------- ----- ==================== PSO*7.0*810 Summary Report ========================= List of ASAP Versions where PAT22 element description has been corrected. ========================================================================= ASAP Version 4.1 - PAT22 Description Before Post-Install Routine ---------------------------------------------------------------- Used when the patient's address is a foreign country and PAT12 through PAT16 are left blank. This is a freeform text field. ASAP does not provide a list of countries for this field. PMPs may permit some of the other address fields to not be used if this field is populated. ASAP Version 4.1 - PAT22 Description After Post-Install Routine --------------------------------------------------------------- Used when the patient's address is a foreign country. This is a freeform text field. ASAP does not provide a list of countries for this field. PMPs may permit some of the other address fields to not be used if this field is populated. ASAP Version 4.2 - PAT22 Description Before Post-Install Routine ---------------------------------------------------------------- Type to continue or '^' to exit: Subj: PSO*7.0*810 Post-Install Information [#564398] Page 2 -------------------------------------------------------------------------- ----- Used when the patient's address is a foreign country and PAT12 through PAT16 are left blank. ASAP Version 4.2 - PAT22 Description After Post-Install Routine --------------------------------------------------------------- Used when the patient's address is a foreign country. Total ASAP Versions Corrected = 2 *NOTE: If there were no changes made to the ASAP versions, then the following Mailman message will display: Subj: PSO*7.0*810 Post-Install Information [#565494] 11/20/25@15:16 7 lines From: PSO*7.0*810 Post-Install In 'IN' basket. Page 1 -------------------------------------------------------------------------- ----- ==================== PSO*7.0*810 Summary Report ========================= List of ASAP Versions where PAT22 element description has been corrected. ========================================================================= No ASAP Versions Were Corrected. 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 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. To backout the updates to the description verbiage for File #58.4 [SPMP ASAP RECORD DEFINITION] for the PAT22 element only, the following command is performed at the programmer's prompt: D BACKOUT^PSO810PI After backout, users can view the reinstated description changes under the State Prescription Monitoring Program (SPMP) Menu [PSO SPMP MENU] under ASAP [View/Edit ASAP Definitions] for versions 4.1 and 4.2 only, by using the 'SH' Show/Hide Details to verify the description changes for the PAT22 element have been backed out. In addition, a MailMan message is generated with a before changes and after changes display within the mail message. Validation of Back-out Procedure: --------------------------------- The Back-out 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 2 lines of the PSO routine(s) contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once 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 PSO*7.0*810. Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 9 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSO810PI Before: n/a After: B86364442 **810** Routine Name: PSOASAP0 Before:B167408199 After:B170561288 **408,451,496,504,625,630,659, 705,772,810** Routine Name: PSOSPML2 Before: B70853943 After: B70903929 **408,451,625,810** Routine Name: PSOSPML3 Before: B69444134 After: B72359356 **408,451,625,772,810** Routine Name: PSOSPML4 Before:B116681933 After:B120767917 **408,451,625,659,662,770,810** Routine list of preceding patches: 770, 772 ============================================================================= User Information: Entered By : Date Entered : SEP 26, 2025 Completed By: Date Completed: JUN 16, 2026 Released By : Date Released : JUN 17, 2026 ============================================================================= Packman Mail Message: ===================== $END TXT