$TXT Created by ALVIN JR at MBOXCACHE.FO-BIRM.DOMAIN.EXT (KIDS) on Monday, 07/18/22 at 11:18 ============================================================================= Run Date: AUG 24, 2022 Designation: PSO*7*684 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #565 Status: Released Compliance Date: SEP 24, 2022 ============================================================================= Associated patches: (v)PSO*7*630 <<= must be installed BEFORE `PSO*7*684' (v)PSO*7*667 <<= must be installed BEFORE `PSO*7*684' Subject: PHARMACY OPERATIONS - DOJ/DEA REFRESH Category: - Routine - Enhancement (Mandatory) Description: ============ ******************************* ATTENTION ****************************** THE INSTALLATION OF THIS PATCH MUST BE QUEUED ************************************************************************** The Pharmacy Operations Project (POP) DEA enhancements provides the ability to support multiple Drug Enforcement Administration (DEA) Numbers for a prescriber. This patch performs a refresh 'migration' of provider DEA information to new data dictionaries introduced by XU*8*688 and initially migrated by PSO*7.0*529. PSO*7*684 is a preliminary patch to prepare for patch PSO*7.0*545. This patch PSO*7*684 corrects the following issues: ---------------------------------------------------- Issue Description ------------------ During the initial DEA migration performed by PSO*7*529, DEA numbers with a Business Activity Code (BAC) of "M" (Mid-Level Practitioner) were incorrectly categorized as Institutional DEA Numbers, causing a fatal exception that prevented them from migrating to the DEA NUMBERS file (#8991.9). Issue Resolution ----------------- This patch migrates DEA numbers using the correct Business Activity Code (BAC) conversion: a) Business Activity Codes of "C" or "M" are interpreted as Individual type DEA numbers. b) All other Business Activity codes are interpreted as Institutional type DEA numbers. Issue Description ------------------ The option DEA Expiration Date Report [PSO EPCS EXPIRE DATE REPORT] option includes DEA numbers that expired in the past when the report is run with the '<30' day and '<90' day search criteria. The '<30' search criteria should only return DEA numbers with an expiration date in the next 30 days (a date that falls between the date the report is run and 30 days into the future from that date. The report incorrectly includes dates in the past. The '<90' search criteria should only return DEA numbers with an expiration date in the next 90 days (a date that falls between the date the report is run and 90 days into the future from that date. The report incorrectly includes dates in the past. Issue Resolution ----------------- Change the DEA Expiration Date Report [PSO EPCS EXPIRE DATE REPORT] option to restrict the results when running the '<30' day search criteria to only include DEA expiration dates in the next 30 days, or between 'today' (the date the report is run) and 30 days into the future. Do not include any DEA expiration dates in the past. Change the DEA Expiration Date Report [PSO EPCS EXPIRE DATE REPORT] option to restrict the results when running the '<90' day search criteria to only include DEA expiration dates in the next 90 days, or between 'today' (the date the report is run) and 90 days into the future. Do not include any DEA expiration dates in the past. This patch PSO*7*684 contains the following enhancements: --------------------------------------------------------- 1. Prior to refreshing the DEA information, all old DEA information will be deleted. 2. A pre-install routine PSO7P684 included in this patch will identify all DEA numbers from the NEW PERSON FILE (#200) and utilize the new PSO DOJ/DEA WEB SERVICE to create entries in the DEA NUMBERS FILE (#8991.9) and migrate or 'link' VistA providers to the corresponding DEA NUMBERS FILE entry. Providers that cannot be linked will be included in the standalone DEA Migration Report as described in item #4 below. Local DEA information from the NEW PERSON file (#200) can be reviewed and corrected, if necessary, using the ePCS GUI application (for VA Prescribers) and the Edit Provider [PSO PROVIDER EDIT] option (for NON-VA Prescribers). The DEA migration may be re-run after making corrections to local DEA information to migrate DEA numbers that had not previously migrated due to an exception. For example, a provider whose DEA number was not migrated due to a name mismatch exception may be migrated by correcting the name and re-running the migration. Successfully migrated provider DEA numbers will create entries in the DEA NUMBERS FILE (#8991.9) marked as USE FOR INPATIENT ORDERS. The Detox Number will be derived from the DEA number if the DEA Number's Business Activity Code (BAC) authorizes a Detox Number. 3. Upon successful installation of this patch, an entry will be logged in the Kernel ^XTMP("PSO70684-INSTALL" global for use by the environment check of the follow-on patch PSO*7.0*545 installation. 4. The DEA Migration Report, available as the standalone DEA Migration Report [PSO DEA MIGRATION REPORT] option, can be used to review the results of the 'refresh migration' of provider DEA information. The following changes have been made to the DEA Migration Report option: a) A new DEA Migration (migration refresh) may optionally be scheduled from the option. b) Exceptions logged during the migration are included to identify issues with local DEA data that may prevent migration. c) The last (most recent) sign-on date of each provider is included. d) The issue date of each provider's last (most recent) prescription is included. e) The provider's Internal Entry Number (IEN) from the NEW PERSON file (#200) is included. 5. Allow non-CPRS users to optionally be included in the DEA Expiration Expiration Date Report [PSO EPCS EXPIRE DATE REPORT]. Prior to this change, providers without an access code were not included the report, regardless of the search criteria selected. This excluded a significant number of Community Care and/or Non-VA providers, who typically are not assigned access codes. With the change, if the ACTIVE or BOTH search criteria are selected at the "CPRS System Access:" prompt, an additional prompt displays, "Type of System Access:", along with the following two choices: Select one of the following: CPRS CPRS Active Providers Only ALL All Eligible Active Providers If CPRS is selected, only CPRS users possessing an access code are displayed. If ALL is selected, access code is not used as a search criteria. 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 --------------- -------------------- 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 -------------- -------------------- 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: INC23277628 - Suggested change for DEA Expiration Date Report -------------------------------------------------------------- Problem The new "DEA Expiration Date Report [PSO EPCS EXPIRE DATE REPORT]" released in Patch PSO*7*667 does not distinguish VA providers from NonVA, making the report excessively long and difficult to use. Solution The report had been modified to include search criteria for CPRS providers only, or ALL providers. INC22899534 - Discrepancy in DEA Expiration Date Report. INC23277628 ------------------------------------------------------------ Problem PSO*7*667 released new DEA Expiration Date Report [PSO EPCS EXPIRE DATE REPORT] option, replacing Print DEA Expiration Date Expires 30 days [XU EPCS XDATE EXPIRES] option. The new option produces different output for the same search criteria. Specifically, the new report incorrectly includes DEA numbers that have already expired when searching for DEA numbers set to expire within the next 30 or 90 days. Solution Modify the output of the report in the DEA Expiration Date Report [PSO EPCS EXPIRE DATE REPORT] option to exclude DEA numbers with expiration dates in the past when searching for DEA numbers that are expiring within the next 30 or 90 days. Test Sites: ---------- Coatesville, PA Heartland-West HCS Tennessee Valley HCS 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 ------------------------------------------------------------------ Deployment, Installation Back-Out PSO_7_0_P684_DIBRG.DOCX and Rollback Guide PSO_7_0_P684_DIBRG.PDF Outpatient Pharmacy Version 7 Technical PSO_7_0_P684_TM.DOCX Manual Security Guide PSO_7_0_P684_TM.PDF Outpatient Pharmacy Version 7 Manager's PSO_7_0_P684_MAN_UM.DOCX User Manual PSO_7_0_P684_MAN_UM.PDF Patch Installation: Pre/Post Installation Overview: ------------------------------- N/A Pre-Installation Instructions: ------------------------------ N/A Installation Instructions: -------------------------- The installation of this patch must be queued and may take up to 12 hours depending on the number of DEA numbers in the NEW PERSON file (#200) to be migrated. If installation is attempted WITHOUT queueing, the installation will be aborted, and the distribution must then be unloaded, reloaded, and reinstalled with queuing. It is recommended that the installation should be queued during non-peak hours. When installation is complete, the installer should confirm a post-install message entitled "DEA Migration Completion MM/DD/YYYY" is sent to all PSDMGR key holders and the patch installer. 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 name, PSO*7.0*684. 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*684. 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. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//', answer . 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'. iv. When prompted 'Delay Install (Minutes): (0 - 60): 0//', answer 0. Back-out Procedures: -------------------- 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 ticket to obtain this concurrence. Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 57 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSO7E684 Before: n/a After: B29068598 **684** Routine Name: PSO7L529 Before: B49721409 After:B140351576 **529,684** Routine Name: PSO7L684 Before: n/a After: B13891166 **684** Routine Name: PSO7P684 Before: n/a After:B121887303 **684** Routine Name: PSODEARP Before: B73463370 After:B128916820 **667,684** Routine Name: PSODEAU0 Before: B18851498 After: B20026869 **529,684** Routine Name: PSODEAUT Before:B201057220 After:B201057220 **529,684** Routine list of preceding patches: 529, 667 ============================================================================= User Information: Entered By : Date Entered : APR 22, 2022 Completed By: Date Completed: AUG 23, 2022 Released By : Date Released : AUG 24, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT