$TXT Created by NNE at MNTVBB.DOMAIN.EXT (KIDS) on Wednesday, 05/11/22 at 12:13 ============================================================================= Run Date: AUG 17, 2022 Designation: PSO*7*662 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #564 Status: Released Compliance Date: SEP 17, 2022 ============================================================================= Associated patches: (v)PSO*7*659 <<= must be installed BEFORE `PSO*7*662' (v)PSO*7*630 <<= must be installed BEFORE `PSO*7*662' Subject: SPMP MULTI-STATE HANDLING FIXES Category: - Routine Description: ============ It was reported that the Meds by Mail logic added to the State Prescription Monitoring Program (SPMP) patch, PSO*7.0*630, was not working correctly for some of the SPMP options. This patch will resolve the following SPMP issues: 1. INC19848427 - The same RX fills are being transmitted in multiple batches and also to states not associated with the patient or dispensing pharmacy 2. INC19848615 - View/Export Single Prescription [PSO SPMP SINGLE RX VIEW/EXPORT] option only sends to state of dispensing pharmacy 3. INC19851935 - Export Batch Processing [PSO SPMP BATCH PROCESSING] option only displays ASAP version of the dispensing state 4. INC21661107 - Manual Voids sent to state of dispensing pharmacy, not patient's home state Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: 1. INC19848427 - the Scheduled SPMP Data Export [PSO SPMP SCHEDULED EXPORT] option and CS Prescriptions Not Transmitted [PSO SPMP RX NOT TRANSMITTED] option are both gathering prescriptions for incorrect states. Problem: -------- A single prescription can incorrectly be sent to multiple states. This happens if the state being transmitted has a state IEN which is a single digit, and the patient's home state has a state IEN that contains that transmitting state's IEN. This will affect both the transmission for the previous day (including return to stock) and the 30 day look back. Resolution: ----------- Fix the logic for the Scheduled SPMP Data Export [PSO SPMP SCHEDULED EXPORT] option and CS Prescriptions Not Transmitted [PSO SPMP RX NOT TRANSMITTED] option to look at the dispensing pharmacy state and the patient state, and then look at the SEND EXPORT STATE PARAMETER (#21) field in the SPMP STATE PARAMETERS (#58.41) file to determine what state(s) the batch needs to be sent. Technical Resolution: --------------------- Routine PSOSPMU1 in the GATHER tag, change the contains from "'[STATE" to "'[("^"_STATE_"^")" when checking for the STATE variable. This will fix the issue with the prescriptions being sent to incorrect states. 2. INC19848615 - the View/Export Single Prescription [PSO SPMP SINGLE RX VIEW/EXPORT] option only transmits to the dispensing pharmacy's state. Problem: -------- Patch PSO*7.0*630 added functionality to allow Meds By Mail to transmit control substance prescriptions to the SPMP state of the patient's geographic state. However, when using View/Export Single Prescription [PSO SPMP SINGLE RX VIEW/EXPORT] option to send a single RX, it will only send to the state of the dispensing pharmacy and cannot be changed to transmit to the patient's geographical state. Resolution: ----------- Fix the logic for the View/Export Single Prescription [PSO SPMP SINGLE RX VIEW/EXPORT] option to look at the dispensing pharmacy state and the patient state, and then look at the SEND EXPORT STATE PARAMETER (#21) field in the SPMP STATE PARAMETERS (#58.41) file to determine what state(s) the batch needs to be sent. Technical Resolution: --------------------- Routine PSOSPML4 in the EXPORT tag, look at the dispensing pharmacy state and the patient state, and then look at the SEND EXPORT STATE PARAMETER (#21) field in the SPMP STATE PARAMETERS (#58.41) file to determine what state(s) the batch needs to be sent. 3. INC19851935 - the Export Batch Processing [PSO SPMP BATCH PROCESSING] option reverts to dispensing pharmacy's state. Problem: -------- Patch PSO*7.0*630 added functionality to allow Meds By Mail to transmit control substance prescriptions to the SPMP state of the patient's geographic state. However, when using Export Batch Processing [PSO SPMP BATCH PROCESSING] option to view transmissions for states other than the dispensing pharmacy's state, then the prescription details will display the ASAP version for the dispensing pharmacy's state. As the user backs out of the option, the state changes away from what the state the user initially picked and instead changes to the dispensing pharmacy's state. Resolution: ----------- Fix the logic for the Export Batch Processing [PSO SPMP BATCH PROCESSING] option to display the appropriate state. Technical Resolution: --------------------- Routine PSOSPML4 in the EN tag, change the STATEIEN variable lookup so the appropriate state displays. 4. INC21661107 - the View/Export Void Prescriptions [PSO SPMP VOID RX VIEW/EXPORT] option only transmits to the dispensing pharmacy's state. Problem: -------- The View/Export Void Prescriptions [PSO SPMP VOID RX VIEW/EXPORT] option only transmits to the dispensing pharmacy's state. Resolution: ----------- Fix the logic for the View/Export Void Prescriptions [PSO SPMP VOID RX VIEW/EXPORT] option to look at the dispensing pharmacy state and the patient state, and then look at the SEND EXPORT STATE PARAMETER (#21) field in the SPMP STATE PARAMETERS (#58.41) file to determine what state(s) the batch needs to be sent. Technical Resolution: --------------------- Routine PSOSPMV in the RXLOOP tag, change the logic to look at the dispensing pharmacy state and the patient address state, and then look at the SEND EXPORT STATE PARAMETER (#21) field in the SPMP STATE PARAMETERS (#58.41) file to determine what state(s) the batch needs to be sent. Test Sites: ----------- VA Gulf Coast Healthcare (Biloxi, MS) Meds by Mail 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. It is not necessary to disable any options. 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*662) 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*662. 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: ------------------------ 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 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 and Distribution System Menu, select the Installation Menu. Then select the Install Package(s) option and choose the patch (PSO*7.0*662b) to install. The back-out plan is to restore the routine from the backup created. No data was modified by this patch installation and, therefore, no rollback strategy is required. Validation of Back-out Procedure: --------------------------------- The Back-out Procedure can be verified by printing the first two lines of the routines contained in this patch using the First Line Routine Print [XU FIRST LINE PRINT] option. After the routines contained in this patch have been backed out, the second line of the routines will no longer contain the designation of this patch in the patch list section. 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: PSOSPML4 Before:B103397398 After:B109923547 **408,451,625,659,662** Routine Name: PSOSPMU1 Before:B142399204 After:B142616954 **408,437,451,625,630,662** Routine Name: PSOSPMV Before: B37836041 After: B40484462 **625,662** Routine list of preceding patches: 630, 659 ============================================================================= User Information: Entered By : Date Entered : OCT 27, 2021 Completed By: Date Completed: AUG 17, 2022 Released By : Date Released : AUG 17, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT