$TXT Created by L at DOSP.FO-BIRM.DOMAIN.EXT (KIDS) on Monday, 03/08/21 at 14:20 ============================================================================= Run Date: APR 01, 2021 Designation: PSO*7*625 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #521 Status: Released Compliance Date: MAY 01, 2021 ============================================================================= Associated patches: (v)PSO*7*504 <<= must be installed BEFORE `PSO*7*625' (v)PSO*7*549 <<= must be installed BEFORE `PSO*7*625' Subject: PHARMACY SAFETY UPDATES (COV19) - SPMP Enhancements Category: - Routine - Data Dictionary - Other - Enhancement (Mandatory) Description: ============ In response to the COVID-19 pandemic, the Pharmacy Safety Updates (PSU) project will simplify retransmission to State Prescription Drug Monitoring Program (PDMP) of rejected prescriptions. It also adds the following features: - Allow VOIDS to be submitted to the State PDMP to correct duplicate records (transmitted to state on different days) without requiring them to be returned to stock. - Users can resend corrected records to PDMP in a batch rather than one at a time. - Sites can identify and transmit records that were missed in previous nightly transmissions. - The nightly batch job will send a zero report to State PDMPs when no Controlled Substances were dispensed during a reporting period eliminating the need for follow-up. This improved functionality to identify, correct and transmit CS prescription records will ensure that they are reported to the State PDMPs with as little intervention by Pharmacy staff as possible. FEATURES: 1. Resend a Group of Selected Prescriptions in a batch The Manual Export/Prescription Correction [PSO SPMP MANUAL EXPORT/RX FIX] option has been added to the State Prescription Monitoring Program (SPMP) [PSO SPMP MENU] Menu. This new option provides the capability to resend one or many previously submitted, corrected prescriptions to the state using filtering criteria such as patient, provider, location of patient, drug, or list of prescription numbers. 2. Send Void Record for Released Rx's or Batch of Rx's The new View/Export Void Prescriptions [PSO SPMP VOID RX VIEW/EXPORT] option has been added to the State Prescription Monitoring Program (SPMP) Menu [PSO SPMP MENU]. This new option allows batches of one or more prescriptions to be exported with the VOID record type to remove duplicate records from the state database. This may now be done without having to mark the prescription as Returned to Stock, which was the basis for a generating a void record prior to this patch. The new option is only accessible to holders of the PSO SPMP ADMIN key. This option also allows selection of record types NEW and REVISED as well. The View/Export Single Prescription [PSO SPMP SINGLE RX VIEW/EXPORT] option has also been enhanced to prompt for the VOID record type for released prescriptions when the user holds the PSO SPMP ADMIN key, allowing released prescriptions to be exported with the VOID record type without having to mark the prescriptions as Returned to Stock. 3. Change SSH Key Default from DSA to RSA This patch changes the default SSH key from DSA to RSA when creating new keys using the "Create New SSH Key Pair" selection of the Manage Secure SHell (SSH) Keys [PSO SPMP SSH KEY MANAGEMENT] option. New DSA keys can no longer be created with this option because they are no longer supported by the most recent version of the operating system. 4. Zero Report if No Prescriptions Meet Transmission Criteria This patch adds functionality to build and transmit a Zero Report during the Scheduled SPMP Data Export [PSO SPMP SCHEDULED EXPORT] process if there are no controlled substances to send for a given site. 5. Flush Key fingerprint command in Debug Mode This patch updates the View/Export Batch [PSO SPMP BATCH VIEW/EXPORT] and the Export Batch Processing [PSO SPMP BATCH PROCESSING] options to allow holders of the PSO SPMP ADMIN key to clear the old known host file if the vendor server changes its host key. The following two prompts are displayed if the batch export is selected to run in debug mode and it is not a single RX batch: - "Do you want to flush the known hosts key? N//". If this prompt is answered with "Yes", the software performs the flush of the known host keys before the export starts. - "Reason for Debug:". The user will be prompted to enter a reason if the previous prompt 'flush host keys' was answered with "Yes". User entry is required. The two options have been modified to display the latest "Debug Reason" entered in the header section of the ListMan screen for batches where the known host key was flushed. 6. CS Prescriptions Not Transmitted Option This patch also adds a new option CS Prescriptions Not Transmitted [PSO SPMP RX NOT TRANSMITTED]. This new option is manually run and reports controlled substance prescriptions by date range that were not transmitted to the state but meet the criteria to be sent. When using this option, date ranges should be small enough to limit a batch to less than 10,000 records. This new option also provides the ability to transmit records that were not previously transmitted to the state. 7. Check for CBOC division that isn't transmitting data This patch provides the ability to check for CBOC divisions that aren't transmitting to SPMP because the division is in a different state than the VAMC and that state hasn't been set up to transmit. This functionality has been added to the Scheduled SPMP Data Export [PSO SPMP SCHEDULED EXPORT] option. An email is sent to members of PSO SPMP NOTIFICATIONS mailgroup notifying them that the site did not transmit CS records because it is in a state that does not have the state parameters defined in VistA. 8. Delete batch if it has not been exported This patch includes a new action protocol to delete a batch if the batch has not been previously exported. The Delete Batch [PSOSPMP1 DELETE BATCH] action has been added to the Export Batch Processing [PSO SPMP BATCH PROCESSING] option. 9. Automate transmission of CS prescriptions not transmitted (skipped) This patch automates the identification and transmission of released controlled substance prescriptions in the last 30 days that have not been transmitted to the state. This functionality has been added to the Scheduled SPMP Data Export [PSO SPMP SCHEDULED EXPORT] option. When un-transmitted RXs are found during the 30 day lookback, a separate SCHEDULED batch is created with the released date range of the missed prescriptions. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Mod/Del ------------------ ------------------- ------------ SPMP EXPORT BATCH (#58.42) EXPORT TYPE (#2) Modified CREATED BY (#10) New DEBUG REASON (#58.42102) New DEBUG REASON (#.01) RUN BY (#1) DEBUG EXPORT DATE/TIME (#3) ZERO REPORT SITES (#58.42201) New OUTPATIENT SITE (#.01) SITE DEA NUMBER (#1) SPMP STATE PARAMETERS (#58.41) ZERO REPORT ASAP VERSION (#20) New SPMP ASAP RECORD DEFINITION (#58.4) VERSION (#58.4001) ZERO REPORT ASAP VERSION (#.05) New 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 ------------ ---- -------------------- PSO SPMP MANUAL EXPORT/RX FIX run routine New PSO SPMP VOID RX VIEW/EXPORT action New PSO SPMP MENU menu Modified PSO SPMP DISCLOSURE REPORT action Modified PSO SPMP RX NOT TRANSMITTED run routine New PSO SPMP SSH KEY MANAGEMENT action Modified PSO SPMP UNMARK ADMIN CLINIC action Modified PSO SPMP SINGLE RX VIEW/EXPORT action Modified PSO SPMP STATE PARAMETERS action Modified PSO SPMP BATCH VIEW/EXPORT action Modified PSO SPMP BATCH PROCESSING action Modified PSO SPMP ASAP DEFINITIONS action Modified Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- PSO SPMP1 MANUAL BATCH EXPORT Modified PSO SPMP1 DELETE BATCH New PSO SPMP1 MENU Modified PSO SPMP1 STATE PARAMETERS Modified Security Keys Associated: Security Key Name ----------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A List Templates Associated: Template Name Type New/Modified/Deleted ------------- ---- ------------ PSO SPMP VIEW/EXPORT BATCH PROTOCOL Modified Test Sites: ----------- Boise VAMC Tennessee Valley HCS Robley Rex VA Medical Center White River Junction VAMC Software and Documentation Retrieval Instructions: -------------------------------------------------- The software is released as a PackMan message and is distributed from FORUM. 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. File Description File Name ----------------------------------------------------------------- Outpatient Pharmacy V. 7.0 Manager's User Manual pso_7_0_p625_man_um.pdf pso_7_0_p625_man_um.docx Outpatient Pharmacy V. 7.0 Technical Manual/Security Guide pso_7_0_p625_tm.pdf pso_7_0_p625_tm.docx Pharmacy Safety Updates Deployment, Installation, Backout Rollback Guide pso_7_0_p625_dibrg.pdf pso_7_0_p625_dibrg.docx Patch Installation: ------------------- Pre/Post Installation Overview: It is not necessary to disable any options. 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. Please avoid scheduling this patch to install at 1:00 AM local time. 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*625) 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*625 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. When Prompted "Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES//" respond Yes ii. When Prompted "Want KIDS to INHIBIT LOGONs during the install? NO//" respond NO. iii. When Prompted "Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//" respond NO. iv. If prompted 'Delay Install (Minutes): (0-60): 0//' respond 0. 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 then from the Kernel Installation and Distribution System Menu, select the Installation Menu. Select the Install Package(s) option and choose the patch (xxx*x.x*xxxb) to install. This may only do a partial back out of the patch; a follow up backout patch or manual steps may need to be performed to complete the backout. The back-out plan is to restore the routines 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 2 lines of the routine contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routine contained in the PSO*7.0*625 patch has been backed out, the first two lines of the routine will no longer contain the designation of this patch in the patch. Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 42 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSO625P2 Before: n/a After:B127012102 **625** Routine Name: PSO625P3 Before: n/a After:B121818662 **625** Routine Name: PSO625P4 Before: n/a After:B103777900 **625** Routine Name: PSO625P5 Before: n/a After: B58973892 **625** Routine Name: PSO625PI Before: n/a After:B118726275 **625** Routine Name: PSOASAP Before: B85756536 After: B88963366 **451,496,625** Routine Name: PSOASAP0 Before:B165083587 After:B167986109 **408,451,496,504,625** Routine Name: PSOSPMA3 Before:B171421989 After:B171617912 **451,625** Routine Name: PSOSPMDL Before: n/a After: B4441399 **625** Routine Name: PSOSPMKY Before:B101316264 After:B102749976 **451,625** Routine Name: PSOSPML0 Before: B32864109 After:B101233344 **408,451,625** Routine Name: PSOSPML1 Before: B47175688 After: B48377186 **408,451,625** Routine Name: PSOSPML2 Before: B55672544 After: B70853943 **408,451,625** Routine Name: PSOSPML3 Before: B57979959 After: B58248609 **408,451,625** Routine Name: PSOSPML4 Before: B93991952 After:B103195106 **408,451,625** Routine Name: PSOSPML7 Before: n/a After: B86592473 **625** Routine Name: PSOSPML8 Before: n/a After: B12757535 **625** Routine Name: PSOSPMSP Before:B106425657 After:B125009898 **408,451,625** Routine Name: PSOSPMU0 Before: B23897100 After: B33044815 **451,625** Routine Name: PSOSPMU1 Before:B128483290 After:B137687998 **408,437,451,625** Routine Name: PSOSPMU2 Before: B10133979 After: B20209131 **451,625** Routine Name: PSOSPMU3 Before:B137219252 After:B138473139 **451,625** Routine Name: PSOSPMUT Before:B182085156 After:B204967908 **408,451,549,625** Routine Name: PSOSPMV Before: n/a After: B37836041 **625** ============================================================================= User Information: Entered By : Date Entered : SEP 09, 2020 Completed By: Date Completed: APR 01, 2021 Released By : Date Released : APR 01, 2021 ============================================================================= Packman Mail Message: ===================== $END TXT