$TXT Created by ALVIN JR at DOSP.FO-BIRM.DOMAIN.EXT (KIDS) on Thursday, 10/12/23 at 12:26 ============================================================================= Run Date: DEC 04, 2023 Designation: PSO*7*731 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #610 Status: Released Compliance Date: JAN 04, 2024 ============================================================================= Associated patches: (v)PSO*7*714 <<= must be installed BEFORE `PSO*7*731' (v)PSS*1*261 <<= must be installed BEFORE `PSO*7*731' (v)PSO*7*735 <<= must be installed BEFORE `PSO*7*731' Subject: DETOX/X-WAIVER REMOVAL-DEA WARRANTY Category: - Routine - Enhancement (Mandatory) Description: ============ ******* ATTENTION-GUI UPDATE ******** ATTENTION-GUI UPDATE *********** ********************************************************************** This release includes an update to the ePCS Delphi GUI executable. Shortcuts pointing to ePCS GUI must be updated using the same local, VISN, or Regional processes used to update CPRS GUI shortcuts. ********************************************************************** This patch is one of a series of patches developed to decommission the X-Waiver/Detox Number functionality. Below is a list of all the applications involved in this release along with their patch numbers: APPLICATION/VERSION PATCH --------------------------------------------------------------- ORDER ENTRY/RESULTS REPORTING v3.0 OR*3.0*607 CONTROLLED SUBSTANCES v3.0 PSD*3.0*94 OUTPATIENT PHARMACY v7.0 PSO*7.0*731 PHARMACY DATA MANAGEMENT v1.0 PSS*1.0*261 On December 29, 2022 Congress eliminated the "DATA-Waiver" (or X-Waiver) Program via the Consolidated Appropriations Act of 2023 (the Act). The elimination of the X-Waiver will increase access to buprenorphine for those fighting to overcome opioid use disorder. Upon the passage of the Act, the following changes went into effect: - A DATA-Waiver registration (Detox Number) is no longer required to treat patients with buprenorphine for opioid use disorder. - Going forward, all prescriptions for buprenorphine only require a standard DEA registration number. The previously used DATA-Waiver registration (Detox) numbers are no longer needed for any prescription. - There are no longer any limits or patient caps on the number of patients a prescriber may treat for opioid use disorder with buprenorphine. The Act does not impact existing state laws or regulations that may be applicable. To comply with the Act, this patch (PSO*7.0*731) implements the following changes: 1) No system screens, prompts, or notifications shall display a Detox Number. 2) No reports generated by the system shall include a Detox Number. DEA Warranty 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: INC28252945 - Speed Renew requires a provider DEA# for Non-CS drugs, and duplicative "Return to Continue" INC28334024 - Provider lookup by DEA# displays incorrect provider based on legacy DEA# field 53.2. A post-install routine will remove 'orphaned' DEA numbers that were left in the DEA# field (#53.2) in the NEW PERSON file (#200) at the time the last DEA number in the NEW DEA #'S field (#53.21) was deleted. When finished, the post-install routine will send a MailMan message to the patch installer and holders of the PSDMGR key with the subject "Orphan DEA Cleanup Complete MM/DD/YYYY". The MailMan message will include a list of DEA numbers removed and the providers from which they were removed. 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 ----------- ---- -------------------- PSO EPCS DEA INTEGRITY Run Routine Modified REPORT PSO EPCS GUI CONTEXT Broker (Client/Server) Modified 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. INC28252945 - Speed Renew requires DEA# for Non-CS drugs, and duplicative "Return to Continue". Problem: -------- When certain non-controlled substance drugs are renewed using the Speed Renew action (RN Renew (OP)) in the Outpatient Medication Profile screen, the drug is incorrectly treated as a controlled substance, and the renewing provider is required to have a valid DEA number or VA number and the appropriate DEA schedules. The DEA, SPECIAL HDLG field (#3) in the DRUG file (#50) was incorrectly evaluated by treating all numeric values as controlled substances. Resolution: ----------- The Speed Renew action in the Outpatient Medication Profile screen has been modified to correctly determine the drug's DEA schedule based on the DEA, SPECIAL HDLG field (#3) in the DRUG file (#50). The determination of controlled substance status has been modified to match the logic used throughout Outpatient Medications software, treating values greater than one and less than 6 as controlled substances, and treating any other values as non-controlled substances that do not require a DEA number or VA number to renew. 2. INC28334024 - Provider lookup by DEA# displays incorrect provider, legacy DEA# field 53.2 remains after DEA number deletion. x Problem: -------- The DEA# field (#53.2) in the NEW PERSON file (#200) was replaced by the DEA #'S multiple (#53.21) in patch XU*8.0*689 via an update to Kernel DEA APIs. The legacy field continues to be updated in order to retain backward compatibility with applications performing FileMan or direct global reads. Since a provider may have more than one DEA number in the DEA #'S multiple, a provider's DEA number that has the USE FOR INPATIENT ORDERS? field in the DEA NUMBERS file (#8991.9) set to YES is automatically stored in the provider's legacy DEA# field (53.2) in the NEW PERSON file (#200), and this DEA number is returned by $$DEA^XUSER as the provider's 'default' DEA number. If all DEA numbers are deleted from a provider's profile (leaving the provider with no DEA numbers), the DEA number is not deleted from the legacy DEA# field (#53.2), so that the provider incorrectly displays when the DEA number is used to look up a provider. The legacy DEA# continues to be used by FileMan when performing provider lookups by DEA number because the "PS1" cross reference is retained for backward compatibility. This issue is apparent when a DEA number is mistakenly added to a provider's profile, then deleted from that provider's profile, and finally added to a different provider's profile; in this scenario, the same DEA number is stored in the legacy DEA# field of both providers, causing both to display when provider lookup by DEA number is performed. Resolution: ----------- To keep the legacy DEA# field (#53.2) in the NEW PERSON file (#200) in sync with the NEW DEA #'S subfile (#53.21) in the NEW PERSON file (#200), the PSOPRVW1 routine has been modified to delete the DEA number value in the legacy DEA# field when the last DEA number has been deleted from a provider's profile, preventing the provider from incorrectly displaying if that DEA number is used to perform provider lookups by DEA number. A post-install routine will remove 'orphaned' DEA numbers that were left in the DEA# field (#53.2) in the NEW PERSON file (#200) at the time the last DEA number in the NEW DEA #'S field (#53.21) was deleted. Test Sites: ---------- Coatesville VAMC (Coatesville, PA) Tennessee Valley HCS (Nashville, TN) Kansas City VAMC (Kansas City, MO) Test Sites - SNOW Change Orders: -------------------------------- Coatesville: CHG0423096 Tennessee Valley: CHG0423426 Kansas City: CHG0425021 Documentation Retrieval Instructions: ------------------------------------- The software for this patch is being released in a PackMan message. Other Software Files: This release also includes other software files that may be obtained by accessing the URL: https://download.vista.domain.ext/index.html/SOFTWARE File Name Format -------------------------------------------------------------------- DATA_ENTRY_FOR_PRESCRIBER_PSO_7_731.ZIP Binary The following is a list of the files included in the zip file: File Name Size (Bytes) Date -------------------------------------------------------------------- ePCSDataEntryForPrescriber.exe 7321000 10/05/2023 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 ------------------------------------------------------------------ ePCS User Guide PSO_7_0_EPCS_GUI_UG.DOCX PSO_7_0_EPCS_GUI_UG.PDF Manager's User Manual PSO_7_0_P731_MAN_UM.DOCX PSO_7_0_P731_MAN_UM.PDF Pharmacist's User Manual PSO_7_0_P731_PHARM_UM.DOCX PSO_7_0_P731_PHARM_UM.PDF Technician's User Manual PSO_7_0_P731_TECH_UM.DOCX PSO_7_0_P731_TECH_UM.PDF Technical Manual / Security Guide PSO_7_0_P731_TM.DOCX PSO_7_0_P731_TM.PDF Deployment, Installation Back-Out PSO_7_0_P731_DIBRG.DOCX and Rollback Guide PSO_7_0_P731_DIBRG.PDF 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: Verify the post-install routine sent a MailMan message to the patch installer with the subject "Orphan DEA Cleanup Complete MM/DD/YYYY". The message contains a list of DEA numbers removed and the providers from which they were removed. The message is also sent to holders of the PSDMGR key. 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*731. 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*731. 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. Installation Instructions (ePCS GUI): ------------------------------------- The instructions below may be used to set up the ePCS GUI on a user workstation. For network/server installation, follow the site's local or Veterans Integrated Services Network (VISN) installation procedures. 1. Upon receipt of the file, DATA_ENTRY_FOR_PRESCRIBER_PSO_7_731.ZIP, save into the My Documents folder. 2. Open Windows Explorer 3. Navigate to C:\Program Files (x86)\VistA 4. Right-click on C:\Program Files (x86)\VistA a. If an ePCS folder exists, select the folder b. If an ePCS folder does not already exist 1. Choose New -> Folder 2. ePCS 5. Right-click on My Documents\DATA_ENTRY_FOR_PRESCRIBER_PSO_7_731.ZIP a. Choose Open with -> Windows Explorer 6. Drag the following files to the ePCS folder a. ePCSDataEntryForPrescriber.exe 7. Navigate to the new ePCS folder 8. Right-click on ePCSDataEntryForPrescriber.exe a. Send to -> Desktop (create shortcut) 9. You will find the new shortcut on your Desktop. Select the new shortcut. a. Right-click b. Select Properties i. In Target text box, append to the end of "C:\Program Files (x86)\VistA\ePCS\ePCSDataEntryForPrescriber.exe" 1. s= p= ii. For example "C:\Program Files (x86)\VistA\ePCS\ePCSDataEntryForPrescriber.exe" s=domain.name.server.gov p=0000 c. Click Apply d. Click OK 10. Click the new shortcut to launch the ePCS GUI. Note: To enter data in the ePCS Data Entry for Prescriber application, the user must have the XUEPCSEDIT key and the option EPCS GUI Context version 2.2.2.0 [PSO EPCS GUI CONTEXT] as a secondary menu. A user cannot have both the XUEPCSEDIT key and the ORES key. The two keys are exclusive to one another so that the person prescribing is not also the person controlling authorization for prescribing controlled substances. Post-Installation Instructions: Verify a Mailman message with the subject "Orphan DEA Cleanup Complete MM/DD/YYYY" was received (this may take up to an hour). The MailMan message will include a list of DEA numbers removed and the providers from which they were removed. 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_P731_DIBRG. Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 18 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSO7P684 Before:B121890392 After:B113730763 **684,545,731** Routine Name: PSO7P731 Before: n/a After: B17124259 **731** Routine Name: PSODEADD Before: B55243123 After: B55606496 **545,731** Routine Name: PSODEAED Before: B66234138 After: B62550146 **545,731** Routine Name: PSODEAMA Before:B131428447 After:B125515187 **545,731** Routine Name: PSODEAME Before:B165094907 After:B165660924 **545,731** Routine Name: PSODEARA Before: B28096263 After: B28604449 **545,731** Routine Name: PSODEARB Before: B29088464 After: B29603687 **545,731** Routine Name: PSODEART Before:B235124510 After:B238519708 **667,545,714,731** Routine Name: PSODEARU Before: B21958890 After: B22454311 **667,545,731** Routine Name: PSODEARW Before: B77314191 After: B78808040 **545,731** Routine Name: PSODEARX Before: B52979542 After: B54190445 **545,731** Routine Name: PSODEAU0 Before: B20026869 After: B20331229 **529,684,731** Routine Name: PSODEAU1 Before: B40412013 After: B40808197 **545,731** Routine Name: PSODEAUT Before:B201057220 After:B204522282 **529,684,731** Routine Name: PSODIR5 Before: B84517322 After: B85080523 **545,731** Routine Name: PSOEPU1 Before:B142395125 After:B146118295 **545,731** Routine Name: PSOEPUT Before:B198576957 After:B202139626 **545,731** Routine Name: PSOEPVR Before: B806841 After: B806872 **545,735,731** Routine Name: PSOPRVW Before:B123574637 After:B124320533 **11,146,153,263,268,264,398, 391,450,630,545,731** Routine Name: PSOPRVW1 Before:B164937513 After:B170086304 **545,731** Routine Name: PSORENW4 Before:B124474469 After:B125593603 **11,23,27,32,37,64,46,75,71, 100,130,117,152,148,264,225, 301,390,313,411,444,504,508, 550,457,639,441,683,545,731** Routine Name: PSOUTIL Before:B150112811 After:B150959431 **64,456,444,469,504,651,545,731** Routine list of preceding patches: 714, 735 ============================================================================= User Information: Entered By : Date Entered : JUL 17, 2023 Completed By: Date Completed: NOV 30, 2023 Released By : Date Released : DEC 04, 2023 ============================================================================= Packman Mail Message: ===================== $END TXT