$TXT Created by ALVIN JR at MBOXCACHE.FO-BIRM.DOMAIN.EXT (KIDS) on Thursday, 09/08/22 at 09:34 ============================================================================= Run Date: OCT 05, 2022 Designation: XU*8*775 Package : XU - KERNEL Priority: Mandatory Version : 8 SEQ #616 Status: Released Compliance Date: NOV 05, 2022 ============================================================================= Associated patches: (v)XU*8*490 <<= must be installed BEFORE `XU*8*775' (v)XU*8*552 <<= must be installed BEFORE `XU*8*775' (v)XU*8*765 <<= must be installed BEFORE `XU*8*775' Subject: REMOVE PSDRPH KEY FROM XUKEYALL AND XUKEYDEALL Category: - Routine - Enhancement (Mandatory) Description: ============ ************************************************************************** This patch (XU*8.0*775) is being released with Pharmacy patch PSO*7.0*701 and should be installed immediately after installing PSO*7.0*701. ************************************************************************** The Pharmacy Operational Updates Project implements improvements and enhancements to VistA pharmacy functionality. New and changed functionality delivered by this patch are listed below. Prevent the PSDRPH Key from being allocated via the options: Allocation of Security Keys [XUKEYALL] De-allocation of Security Keys [XUKEYDEALL] Grant Access by Profile [XUSERBLK] Copy One Users Menus and Keys to others [XQSMD COPY USER] Patch PSO*7.0*667 released the Allocate/De-Allocate of PSDRPH Key [PSO EPCS PSDRPH KEY] option, which audits allocation and de-allocation of the PSDRPH key to comply with DEA regulations. This patch, XU*8.0*775, removes the ability to allocate and de-allocate the PSDRPH from options that are not audited. After this patch is installed, if the PSDRPH key is entered at the "Allocate key:" prompt in the Allocation of Security Keys [XUKEYALL] option or the De-allocation of Security Keys [XUKEYDEALL] option, the following message is displayed and the prompt for key is redisplayed: The PSDRPH key cannot be allocated / de-allocated by this option. Please use the option 'Allocate/De-Allocate of PSDRPH Key (Audited)' After this patch is installed, if a user holding the PSDRPH key is selected to copy (or 'clone') using the Grant Access by Profile [XUSERBLK] option or the Copy One Users Menus and Keys to others [XQSMD COPY USER] option, the following message is displayed indicating the PSDRPH key will not be copied to the new user(s): The PSDRPH key cannot be allocated / de-allocated by this option. Please use the option 'Allocate/De-Allocate of PSDRPH Key (Audited)' if necessary. The PSDRPH key will not be copied to the new user. Example: Allocation of Security Keys [XUKEYALL] ========================================================================== Select OPTION NAME: XUKEYMGMT Key Management Select Key Management Option: Allocation of Security Keys Allocate key: PSDRPH The PSDRPH key cannot be allocated / de-allocated by this option. Please use the option 'Allocate/De-Allocate of PSDRPH Key (Audited)'. ========================================================================= Example: De-allocation of Security Keys [XUKEYDEALL] ========================================================================= Select OPTION NAME: XUKEYMGMT Key Management Select Key Management Option: De-allocation of Security Keys De-allocate key: PSDRPH The PSDRPH key cannot be allocated / de-allocated by this option. Please use the option 'Allocate/De-Allocate of PSDRPH Key (Audited)'. ========================================================================== Example: Grant Access by Profile [XUSERBLK] ========================================================================== Select User Management Option: Grant Access by Profile Batch Entry of New Persons -------------------------- Please select a person to copy from Template PERSON: PHARMACIST,SOURCE Type to continue or '^' to exit: ^ Is this the person whose data you want cloned? YES You may enter a date, when the users that are being created/updated will no longer have access to the system. Enter (optional) TERMINATION DATE: The PSDRPH key cannot be allocated / de-allocated by this option. Please use the option 'Allocate/De-Allocate of PSDRPH Key (Audited)'. The PSDRPH key will not be copied to the new user. Press ENTER to continue: ========================================================================== Example: Copy One Users Menus and Keys to others [XQSMD COPY USER] ========================================================================== Select OPTION NAME: XQSMD COPY USER Copy One Users Menus and Keys to others Copy One Users Menus and Keys to others Select the user to be COPIED FROM: PHARMACIST,SOURCE DALLAS TEXAS The PSDRPH key cannot be allocated / de-allocated by this option. Please use the option 'Allocate/De-Allocate of PSDRPH Key (Audited)'. The PSDRPH key will not be copied to the new user. Press ENTER to continue: Select a USER to be COPIED TO: TEST,ABC Select ANOTHER USER: Do you want to QUEUE this job ? Y// N ========================================================================= 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 Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- Additional Information: ----------------------- N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: N/A Test Sites: ----------- Coatesville, PA Heartland West, MO Tennessee Valley HCS Software and 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. Documentation Title File Name ------------------------------------------------------------------ Deployment Installation Back-Out XU_8_0_P775_DIBRG.DOCX and Rollback Guide XU_8_0_P775_DIBRG.PDF Kernel 8.0 & Kernel Toolkit KRN8_0SM.DOCX Systems Management Guide KRN8_0SM.PDF Patch Installation: ------------------- Pre/Post Installation Overview: This patch installs routines only, no non-routine components are installed by this patch. There is no environment check, pre-install, or post-install routine logic executed during the installation of the patch. 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. 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 XU*8.0*775. 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 XU*8.0*775. 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 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: There are no post-installation instructions for this patch. 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 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. To back-out data from a production account could cause errors. Contact the Help Desk to log a ticket. Routine Information: ==================== The second line of each of these routines now looks like: ;;8.0;KERNEL;**[Patch List]**;Jul 10, 1995;Build 11 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: XQ6 Before: B21547163 After: B23651385 **775** Routine Name: XQSMDCPY Before: B12698311 After: B14830157 **19,552,775** Routine Name: XUSERBLK Before: B42943702 After: B50906205 **20,214,230,289,419,490,775** Routine list of preceding patches: 490, 552 ============================================================================= User Information: Entered By : Date Entered : JUL 26, 2022 Completed By: Date Completed: OCT 04, 2022 Released By : Date Released : OCT 05, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT