$TXT Created by NNE at MNTVBB.DOMAIN.EXT (KIDS) on Tuesday, 11/15/22 at 14:24 ============================================================================= Run Date: MAR 15, 2023 Designation: PSO*7*705 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #586 Status: Released Compliance Date: APR 15, 2023 ============================================================================= Associated patches: (v)PSO*7*659 <<= must be installed BEFORE `PSO*7*705' Subject: SPMP DEA NUMBER MISSING OR WRONG WHEN EXPIRED Category: - Routine Description: ============ This patch will resolve the following issue: 1) INC23385693 - HAC VistA SPMP issue: DEA # (#10) field in the ORDER DEA ARCHIVE INFO (#101.52) file is null on eRx Controlled substance eRx prescriptions can be finished in VistA on a day after the authorizing provider's Drug Enforcement Administration (DEA) Number expires as long as the Issue/Written Date of the eRX is before or equal to the provider's DEA expiration date. This is by design. However, when this happens, it causes the DEA # (#10) field to be null or to store the facility's DEA number in the ORDER DEA ARCHIVE INFO (#101.52) file. This will have side effects in functionality that uses this field. In particular, this affects State Prescription Monitoring Program (SPMP) functionality. When the DEA # (#10) field in the ORDER DEA ARCHIVE INFO (#101.52) file is null, this may cause the Vista SPMP transmissions to submit an incorrect DEA Number for the provider. A future CPRS patch will also address the problem for these situations so that the correct DEA number is stored into ORDER DEA ARCHIVE INFO (#101.52) file. The related CPRS ticket is INC24400778. 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 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 ------------- ---- ------------ N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1) INC23385693 - HAC VistA SPMP issue: DEA # (#10) field in the ORDER DEA ARCHIVE INFO (#101.52) file is null on eRx Problem: -------- It was discovered that when a provider's DEA number expires on the same date as the issue/written date, the DEA # (#10) field can be null or may store the facility's DEA number in the ORDER DEA ARCHIVE INFO (#101.52) file. When this happens, the SPMP transmission should still send the provider's DEA number, but instead it will send either null or the Facility DEA# which is incorrect. Resolution: ----------- To fix the issue for the SPMP transmission, the routine PSOASAP0 tag PRE02 will be modified so that in the event the ORDER DEA ARCHIVE INFO (#101.52) file does not have a DEA # (#10) field value, then it does a second look up that passes the issue/written date to the $$DEA^XUSER call so the provider's DEA number will be sent even though it expires on the same day as the RX issue/written date. In the case where the ORDER DEA ARCHIVE INFO (#101.52) file incorrectly captured the facility DEA Number, this patch will still send that value in the SPMP transmission and will not override it. That issue will be corrected by a future CPRS patch (INC24400778). Test Sites: ----------- Meds by Mail Pacific Islands HCS (Honolulu, HI) 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*705) 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*705. 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*705b) 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 routine contained in this patch has been backed out, the second line of the routine 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 5 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOASAP0 Before:B175437386 After:B178203552 **408,451,496,504,625,630,659,705** Routine list of preceding patches: 659 ============================================================================= User Information: Entered By : Date Entered : SEP 27, 2022 Completed By: Date Completed: MAR 15, 2023 Released By : Date Released : MAR 15, 2023 ============================================================================= Packman Mail Message: ===================== $END TXT