============================================================================= Run Date: JUN 27, 2023 Designation: XU*8*689 Package : XU - KERNEL Priority: Mandatory Version : 8 SEQ #627 Status: Released Compliance Date: AUG 11, 2023 ============================================================================= Associated patches: (v)XU*8*548 <<= must be installed BEFORE `XU*8*689' (v)XU*8*551 <<= must be installed BEFORE `XU*8*689' (v)XU*8*688 <<= must be installed BEFORE `XU*8*689' (v)XU*8*751 <<= must be installed BEFORE `XU*8*689' (v)XU*8*765 <<= must be installed BEFORE `XU*8*689' (v)XU*8*774 <<= must be installed BEFORE `XU*8*689' Subject: PHARMACY OPERATIONS - DEA# ENHANCEMENTS Category: - Routine - Enhancement (Mandatory) - Data Dictionary Description: ============ This patch is part of the Pharmacy Operations DEA updates supporting multiple Drug Enforcement Administration (DEA) numbers for a provider. For any Pharmacy issues related to this patch, please submit a yourIT ticket to the Service Now group PLM.HEALTH.ClinicalAncillary.Sub_1. ******* ATTENTION-GUI UPDATE ******** ATTENTION-GUI UPDATE *********** ********************************************************************** This release includes an update to the Electronic Prescribing of Controlled Substances (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. ********************************************************************** Below is a list of all the applications involved in this project along with their patch numbers: APPLICATION/VERSION PATCH --------------------------------------------------------------- OUTPATIENT PHARMACY v7.0 PSO*7.0*545 ORDER ENTRY/RESULTS REPORTING v3.0 OR*3.0*499 INPATIENT MEDICATIONS v5.0 PSJ*5.0*372 KERNEL v8.0 XU*8.0*689 The Kernel patch XU*8.0*689 is being released in a host file as a standalone patch and must be installed before the remaining patches, which are being released in the Kernel Installation and Distribution System (KIDS) multi-package build PSO_545_PSJ_372_OR_499.KID. *********************************************************************** ********* ATTENTION ********* ATTENTION ********* ATTENTION *********** *********************************************************************** The multi-package host file containing PSO*7.0*545, OR*3.0*499, and PSJ*5.0*372 must be installed IMMEDIATELY after installing this patch (XU*8.0*689). After the installation of this patch (XU*8.0*689), Controlled Substance (CS) medication orders are not permitted until the multi-package build PSO_545_PSJ_372_OR_499.KID has been installed. ************************************************************************** ************************************************************************** This group of patches follow an initial release consisting of patches XU*8*688 and PSO*7*529. This patch XU*8*689 has the following enhancements: * Routine XUSER has been updated to support multiple DEA numbers on a provider's profile. * Routine XUSER3 has been updated to include enhanced validation for: 1) The DEA NUMBER field (#.01) and the INDIVIDUAL DEA SUFFIX field (#.02) in the NEW DEA#'S multiple field (#53.21) sub-file (#200.5321) in the NEW PERSON file (#200). 2) The DEA NUMBER field (#.01) in the DEA NUMBERS file (#8991.9). * Environment routine XU8PE689 ensures the DEA Migration has been run within 7 days prior to installation, and does not permit installation until a recent DEA Migration is run. * Routines XUEPCSUT and XUEPCSU1 were created to allow manual entry of DEA number information in the DEA NUMBERS file (#8991.9). * Routine XUEPCSVR was created to allow the ePCS GUI to check the application version running on the VistA server. * Modify the INTEGRATION CONTROL REGISTRATIONS (ICR) #2343 line tags DEA, DETOX, SDEA, VDA and add new line tags PRDEA, PRXDT and PRSCH. * Modify the following routines to use the new Application Program Interface (API) $$PRDEA^XUSER wherever the DEA# field (#53.2) of the NEW PERSON file (#200) is referenced: - XUPSPRA - XUSNPIX1 * Creates or Updates the following APIs: Routine Entry ICR Description ------- -------- ---- ------------------------------------- XUSER $$DEA 2343 Returns a provider's active DEA number. XUSER $$DEAXDT 2343 Returns a DEA number's expiration date. XUSER $$DEASCH 2343 Returns the schedules for a specific DEA number. XUSER $$DETOX 2343 Returns a user's detox number. XUSER $$PRDEA 2343 Returns a prescriber's default DEA number (flagged as USE FOR INPATIENT ORDERS?) XUSER $$PRSCH 2343 Returns DEA schedules for an active DEA number. XUSER $$PRXDT 2343 Returns the expiration date of a prescriber's DEA number flagged as USE FOR INPATIENT ORDERS? XUSER $$SDEA 2343 Returns a value indicating a provider's DEA prescribing privileges for a specific DEA schedule. * The XU EPCS EDIT DATA Remote Procedure Call (RPC) is deprecated indirectly by the marking of the ePCS Edit Prescriber Data [XU EPCS EDIT DATA] option out of order, and the EPCS GUI no longer contains any references to this option. The XU EPCS EDIT DATA RPC is not directly modified by, nor exported in, patch XU*8*689. * A pre-install routine (PRE^XU8P689) will delete FIELD EDITED field (#.03) of the XUEPCS DATA FILE (#8991.6). A modified copy of this field will re-installed by this patch. * The following XU EPCS Kernel namespace options are moved to the PSO EPCS Outpatient Pharmacy namespace, therefore the post-install routine will mark the following XU EPCS name space options as "PLACED OUT OF ORDER BY XU*8*689". - ePCS Edit Prescriber Data [XU EPCS EDIT DATA] - Allocate/De-Allocate of PSDRPH Key [XU EPCS PSDRPH KEY] - Edit Facility DEA# and Expiration Date [XU EPCS EDIT DEA# AND XDATE] - Print Audits for Prescriber Editing [XU EPCS PRINT EDIT AUDIT] - Print DISUSER Prescribers with Privileges [XU EPCS DISUSER PRIVS] - Print PSDRPH Key Holders [XU EPCS PSDRPH] - Print Prescribers with Privileges [XU EPCS PRIVS] - Print Setting Parameters Privileges [XU EPCS SET PARMS] The routine XU8P689 will be automatically deleted upon completion of the installation. Patch Components: ----------------- Files & Fields Associated: -------------------------- File Name (#) Field Name New/Modified/Deleted ------------ ---------- -------------------- XUEPCS DATA FILE (#8991.6) FIELD EDITED (#.03) Modified FILE EDITED (#.07) New DEA NUMBER (#.08) New Forms Associated: ----------------- N/A Mail Groups Associated: ----------------------- N/A Options Associated: Action ------------------- ------------------------ ePCS Edit Prescriber Data Marked Out of Order by Post-Install [XU EPCS EDIT DATA] Print Prescribers with Privileges Marked Out of Order by Post-Install [XU EPCS PRIVS] Print DISUSER Prescribers with Marked Out of Order by Post-Install Privileges [XU EPCS DISUSER PRIVS] Print Setting Parameters Privileges Marked Out of Order by Post-Install [XU EPCS SET PARMS] Print Audits for Prescriber Editing Marked Out of Order by Post-Install [XU EPCS PRINT EDIT AUDIT] Edit Facility DEA# and Expiration Marked Out of Order by Post-Install Date [XU EPCS EDIT DEA# AND XDATE] Print PSDRPH Key Holders Marked Out of Order by Post-Install [XU EPCS PSDRPH] Allocate/De-Allocate of PSDRPH Key Marked Out of Order by Post-Install [XU EPCS PSDRPH KEY] Protocols Associated: --------------------- N/A Security Keys Associated: ------------------------ N/A Templates Associated: --------------------- N/A Remote Procedures Associated: ----------------------------- N/A Parameter Definitions Associated: -------------- -------------------- N/A Additional Information: ----------------------- Blood Bank Team Coordination: EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch XU*8*689 contains changes to a package referenced in VHA OI SEPG SOP 192-023 Review of VISTA Patches for Effects on VISTA Blood Bank Software. This patch does not alter or modify any VistA Blood Bank software design safeguards or safety critical elements functions. RISK ANALYSIS: Changes made by patch XU*8*689 have no effect on Blood Bank software functionality, therefore, RISK is none. New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- N/A Test Sites: ---------- Coatesville VAMC (Coatesville, PA) Kansas City VAMC (Kansas City, MO) Tennessee Valley HCS (Nashville, TN) Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released using a host file. The host file is available at the following location: /srv/vista/patches/SOFTWARE/XU_8_689.KID 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. Documentation Title File Name --------------------------------------------------------------------- Kernel 8.0 and Kernel Toolkit 7.3 KRN8_0TM.DOCX Technical Manual KRN8_0TM.PDF Deployment, Installation, Backout and XU_8_P689_DIBRG.DOCX Rollback Guide (DIBRG) XU_8_P689_DIBRG.PDF Patch Installation: Pre/Post Installation Overview: ------------------------------- 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. This patch contains an environment check routine that ensures the BUSINESS ACTIVITY CODE file (#8991.8) contains the latest codes. If the file is not current, the missing codes are added and the installation aborts. A message is displayed informing the installer the DEA migration must be re-run using the DEA Migration Report [PSO DEA MIGRATION REPORT] option. The loading and installation of the patch may not proceed until the DEA migration is re-run. Pre-Installation Instructions: ------------------------------ N/A Installation Instructions: 1. Use the Load a Distribution option contained on the Kernel Installation and Distribution System Menu to load the Host file. When prompted to "Enter a Host File:" enter /srv/vista/patches/SOFTWARE/XU_8_689.KID A. When prompted "OK to continue with Load?", enter "YES". The message "Distribution OK!" should display. B. When prompted "Want to Continue with Load?", enter "YES". C. If the DEA Migration is not complete or current, the environment check routine displays a message indicating the DEA Migration is outdated and must be re-run, and the installation is aborted. To re-run the migration: i. Navigate to the DEA Migration Report [PSO DEA MIGRATION REPORT] option. ii. When prompted "Do you want to re-run the DEA Migration?" enter "YES". iii. When prompted "Are you sure you want to re-run the DEA Migration?", enter "YES". iv. At the prompt "Date/Time to Queue the DEA Migration", enter a date/time to queue the migration. The default is ten minutes from the date/time the prompt is displayed. a. The DEA migration may take from two hours up to twelve hours to complete. b. The patch XU*8*689 may not be loaded until the migration is complete. c. When the migration is complete, a MailMan message is sent to the user who queued the migration, as well as holders of the PSDMGR key. vii. When the DEA migration is complete, repeat Step 1 to reload the patch and continue the installation. 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 XU*8.0*689. 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 XU*8.0*689. iii. When prompted for the following, enter "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. 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. Post-Installation Instructions: ------------------------------- Successful installation can be verified by reviewing the first 2 lines of the routines contained in the patch. The second line will contain the patch number in the [PATCH LIST] section. ;;8.0;KERNEL;**[PATCH LIST]**;Jul 10, 1995 The option Calculate and Show Checksum Values [XTSUMBLD-CHECK] can be run to compare the routine checksums to what is documented in the patch description. Back-Out/Roll Back Plan: ------------------------ Back-out Procedures are only needed if there are major problems (examples include the KIDS notice of incompletion or hard errors) resulting from the installation of this patch. You must have concurrence from Health Product Support before a rollback can occur. Enter a ServiceNow helpdesk ticket to obtain this concurrence. Prior to installing a patch, 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. The Roll Back Procedure can be verified by printing the first 2 lines of the XU Routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routines contained in the XU*8*689 patch have been rolled back, the first two lines of the Routines will no longer contain the designation of patch XU*8*689 in the patch list section on line 2. Routine Information: ==================== The second line of each of these routines now looks like: ;;8.0;KERNEL;**[Patch List]**;May 17, 2012;Build 113 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: XU8P689 Before: n/a After: B1174266 **689** Routine Name: XU8PE689 Before: n/a After: B13409033 **689** Routine Name: XUEPCSU1 Before: n/a After: B61886394 **689** Routine Name: XUEPCSUT Before: n/a After:B174456386 **689** Routine Name: XUEPCSVR Before: n/a After: B785438 **689** Routine Name: XUPSPRA Before: B921249 After: B7292530 **551,689** Routine Name: XUSER Before: B57408093 After:B135855094 **75,97,99,150,226,267,288,330, 370,373,580,609,642,739,751, 689** Routine Name: XUSER3 Before: B9641979 After: B57231548 **688,689** Routine Name: XUSNPIX1 Before:B169471076 After:B169437094 **438,452,453,481,528,548,774,689** Routine list of preceding patches: 551, 688, 751, 774 ============================================================================= User Information: Entered By : Date Entered : NOV 15, 2017 Completed By: Date Completed: JUN 26, 2023 Released By : Date Released : JUN 27, 2023 ============================================================================= Packman Mail Message: ===================== No routines included