$TXT Created by CMLCACHE.FO-BIRM.DOMAIN.EXT (KIDS) on Monday, 04/22/24 at 10:08 ============================================================================= Run Date: MAY 21, 2024 Designation: PSO*7*743 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #623 Status: Released Compliance Date: JUN 21, 2024 ============================================================================= Associated patches: (v)PSO*7*700 <<= must be installed BEFORE `PSO*7*743' (v)PSO*7*731 <<= must be installed BEFORE `PSO*7*743' Subject: DEA USABILITY IMPROVEMENTS Category: - Routine - Enhancement (Mandatory) Description: ============ This patch contains several Drug Enforcement Agency (DEA) changes, consisting of three defect fixes and one enhancement. ************************************************************************ * INC29308190 - Fix for defect in VA# DEA Schedule Display. * INC29308282 - Fix for Duplicate DEA# defect. * INC28438197 - Original DEA# displayed when finishing renewal. * Inbound eRx - Search multiple DEAs assigned to a prescriber for match. ************************************************************************ This patch implements the following enhancement: Inbound eRx shall check all VistA provider DEAs when matching to eRx DEA ------------------------------------------------------------------------- After the release of PSO*7*545, more than one DEA number could be added to a provider's VistA profile. However, inbound eRx continued to check for one VistA DEA number (the DEA number marked as USE FOR INPATIENT), so that if the inbound eRx DEA number existed on the provider's profile but it was not marked USE FOR INPATIENT, a DEA mismatch error would occur and the eRx order failed validation. With this patch, all the DEA numbers on the provider's VistA profile are checked when attempting to match the inbound eRx DEA number to the VistA provider's DEA number. If a match is found, the matching VistA DEA number is used for provider validation and drug validation. ************************************************************************* DEA Warranty Defect Fixes ------------------------- Pharmacy Operational Updates (POU) Drug Enforcement Agency (DEA) patch PSO*7*545 introduced several issues related to the display of DEA number. This patch addresses the following warranty issues: INC29308190 - When a provider has an expired DEA # and a VA#, the VA# is showing schedules 2-5 (YES/NO). When the VA# is removed, the schedules on the VA# continue to display in the Edit Provider [PSO PROVIDER EDIT] option and the View Provider [PSO PROVIDER INQUIRE] option. INC29308282 - Duplicate DEA# cannot be removed from VistA, cannot be re-added to EPCS GUI. INC28438197 - When processing Controlled Substance outpatient prescriptions under option Complete Orders from OERR for which the renewal provider is different than the original provider, the original (incorrect) provider is displayed, along with the original provider's DEA number. When processing of the Rx is complete, the renewed order's provider reverts to the correct renewal provider and the issue is resolved. It does not appear to break the digital signature. 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 Procedure Calls: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A Additional Information: ----------------------- Blood Bank Team Coordination: N/A New Service Requests (NSRs): ------------------------------ N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: 1. INC29308190 - When a provider has an expired DEA # and a VA#, the VA# is showing schedules 2-5 (YES/NO). When the VA# is removed, the schedules on the VA# continue to display in the Edit Provider [PSO PROVIDER EDIT] option and View Provider [PSO PROVIDER INQUIRE] option. Problem: -------- When a provider has an expired DEA # field (#53.2) in the NEW PERSONS file (#200) and a VA# field (#53.3) in the NEW PERSONS file (#200), the VA# is showing schedules field (#55.1 - #55.6) from the NEW PERSONS file (#200). When the VA# is removed, the schedules on the VA# continue to display in the Edit Provider [PSO PROVIDER EDIT] option and the View Provider [PSO PROVIDER INQUIRE] option. Resolution: ----------- Suppress the VA# schedules when there is no VA#. 2. INC29308282 - Duplicate DEA# cannot be remove from VistA, cannot be added to EPCS GUI. Problem: -------- When a duplicate DEA number is added to a provider's profile, removing it from the provider's profile also removes it from the DEA NUMBERS file (#8991.9), leaving the remaining DEA number on the provider's profile in the NEW DEA #'S multiple (#53.21) in the NEW PERSON file (#200) pointing to a non-existent entry in the DEA NUMBERS file (#8991.9) and leaving the provider's profile in a corrupted state. VistA impact: The remaining DEA number is displayed on the provider's profile with the message "**ERROR-MISSING FROM DEA NUMBERS FILE**". The number may be selected and updated, correcting the problem. EPCS GUI impact: Both of the duplicate DEA numbers are removed from the provider's list of DEA numbers, but the number cannot be re-assigned to the provider because the corrupted DEA value remains in the NEW DEA #'S multiple (#53.21) in the NEW PERSON file (#200) and EPCS GUI treats the re-assignment of the DEA number a duplicate and prevents it from being added. Resolution: ---------- The VistA code used by the Add New Providers [PSO PROVIDER ADD] option, the Edit Provider [PSO PROVIDER EDIT] option, the View Provider [PSO PROVIDER INQUIRE] option, and the EPCS GUI Remote Procedure Call (RPC) to allow a duplicate DEA number to be removed from a provider's profile without affecting the remaining/original DEA number. The resolution for the legacy VistA options Add New Providers [PSO PROVIDER ADD], Edit Provider [PSO PROVIDER EDIT], and View Provider [PSO PROVIDER INQUIRE] is the same as the EPCS GUI are the same: The deletion of a duplicate DEA number from a provider's profile removes the deleted duplicate but leaves the remaining original DEA number on the provider's profile unchanged. Code was removed which deleted the entry from the DEA NUMBERS file (#8991.9); records in that file will persist after the entries are deleted from the NEW PERSON file (#200). No changes to the EPCS GUI Delphi code were necessary. 3. INC28438197 - Original DEA# displayed when finishing renewal. Problem: -------- The original Rx order's provider and DEA number is displayed in the Complete Orders from OERR option when finishing an order that was renewed by a different provider. When processing of the Rx is complete, the renewed order contains the correct renewal provider and DEA number and the issue is resolved. It does not appear to break the digital signature. Resolution: ---------- Modify the routines used to retrieve the DEA number during the finishing of a pending renewal (routines PSOORFI5 and PSOORNE4) to retrieve the DEA# from the pending CPRS renewal order rather than the original pharmacy order. This will correct the issue by displaying the correct renewal provider and renewal provider's DEA number. This patch also addresses the following internally discovered issue: A: Multiple DEA message still displays when DEA# expired more than 366 days ago without showing the expired DEA#. Problem: -------- When provider has 2 DEAs and 1 has an expiration date more than 366 days ago, the multiple DEA message still displays without showing the expired DEA#. Resolution: ----------- Count the number of DEA# available to be displayed. Only display them if there is more than 1 number. Test Sites: ---------- Kansas City VAMC (Kansas City, MO) Tennessee Valley HCS (Nashville, TN) Test Sites - SNOW Change Orders: -------------------------------- Tennessee Valley: CHG0477534 Kansas City: CHG0477561 Documentation Retrieval Instructions: ------------------------------------- The software for this patch is being released in a PackMan message. 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. Title File Name ------------------------------------------------------------------ Inbound ePrescribing User Manual PSO_7_0_P743_UM_32.DOCX (Unit 3 Part 2) Inbound ePrescribing User Manual PSO_7_0_P743_UM_72.DOCX (Unit 7 Part 2) PSO*7.0*743 Deployment, Installation, PSO_7_0_P743_DIBRG.DOCX Backout, Rollback Guide Patch Installation: ------------------- Pre/Post Installation Overview: Pre-Installation Instructions: The installation of this patch can be queued. 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. Post-Installation Instructions: 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 PSO*7.0*743. 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 build PSO*7.0*743. 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 this message? 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? 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: Back-Out/Roll Back Plan: ------------------------ Please refer to the "Deployment, Installation, Back-Out, and Rollback Guide" for installation, post-install instructions and back-out procedures. This document is exported as PSO_7_0_P743_DIBRG. Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 24 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSODEAUT Before:B204522282 After:B194691482 **529,684,731,743** Routine Name: PSODIR5 Before: B85080523 After: B86717249 **545,731,743** Routine Name: PSOEPUT Before:B202139626 After:B196499658 **545,731,743** Routine Name: PSOEPUT2 Before: B10145072 After: B13509843 **545,743** Routine Name: PSOERUT1 Before: B49401821 After: B49736643 **700,743** Routine Name: PSOERX1A Before:B238628329 After:B239268682 **467,527,508,551,581,617,669, 700,743** Routine Name: PSOERX1G Before:B173422954 After:B173619495 **617,646,689,700,743** Routine Name: PSOERXA0 Before: B38571988 After: B49117769 **467,586,617,651,545,743** Routine Name: PSOERXA1 Before:B135954657 After:B136282665 **467,520,508,551,581,617,743** Routine Name: PSOERXI1 Before: B47133714 After: B47618274 **581,617,692,706,700,743** Routine Name: PSOERXU8 Before: B17242344 After: B47470441 **581,617,700,743** Routine Name: PSOERXUT Before:B153985248 After:B157298883 **617,667,651,718,700,743** Routine Name: PSOORFI5 Before: B84747678 After: B86172264 **225,315,266,391,372,416,504, 505,557,617,441,545,743** Routine Name: PSOORNE4 Before:B106064020 After:B106286207 **11,27,32,36,46,75,96,103,99, 117,131,225,386,390,391,313, 411,661,441,700,743** Routine Name: PSOPRVW Before:B124320533 After:B122136866 **11,146,153,263,268,264,398, 391,450,630,545,731,743** Routine Name: PSOPRVW1 Before:B170086304 After:B169859240 **545,731,743** Routine list of preceding patches: 700, 731 ============================================================================= User Information: Entered By : Date Entered : OCT 12, 2023 Completed By: Date Completed: MAY 21, 2024 Released By : Date Released : MAY 21, 2024 ============================================================================= Packman Mail Message: ===================== $END TXT