$TXT Created by at MNTVBB.DOMAIN.EXT (KIDS) on Tuesday, 09/24/24 at 12:43 ============================================================================= Run Date: SEP 25, 2024 Designation: DG*5.3*1130 Package : DG - REGISTRATION Priority: EMERGENCY Version : 5.3 SEQ #984 Status: Released Compliance Date: SEP 27, 2024 ============================================================================= Associated patches: (v)DG*5.3*964 <<= must be installed BEFORE `DG*5.3*1130' Subject: SENSITIVE FLAG WARNING MESSAGE UPDATE Category: - Routine Description: ============ Patch DG*5.3*1130 updates the message that is displayed when accessing a patient that is marked as having a sensitive patient record. Office of General Council (OGC) has approved a revised Sensitive Flag Warning Message to be applied to all Application User Interfaces (UIs) which currently employ and display the Security Patient Flag (SPF) warning message. Apps/UIs that employ the Registration RPC/API SPF message (in full) will benefit from patch DG*5.3*1130 to fully comply with the new OGC language. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File # 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 -------------- -------------------- N/A Additional Information: ----------------------- Blood Bank Coordination: N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC35142798 - SENSITIVE FLAG WARNING MESSAGE UPDATE Problem: -------- When accessing a patient with a sensitive record, a warning message is displayed stating that the patient has a sensitive patient record. This message text will be updated. Resolution: ----------- Modify routines DGSEC and DGSEC4 to update the message that displays when a user is trying to access a patient that is marked as having a sensitive patient record. PLEASE NOTE: ============ Routine DGSEC, distributed in this patch, references routines A7RDPACT, MPRCHK and GMRPNCW. These routines are no longer part of the national Class I routine set but may still be in use at some sites. If DG*5.3*796 is installed in an account where those routines are not present, XINDEX may display this message: "Reference to routine (one of the above). That isn't in this UCI." This alert message can be ignored. Old --- ***WARNING*** ***RESTRICTED RECORD*** * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This record is protected by the Privacy Act of 1974 and the Health * * Insurance Portability and Accountability Act of 1996. If you elect * * to proceed, you will be required to prove you have a need to know. * * Accessing this patient is tracked, and your station Security Officer * * will contact you for your justification. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Do you want to continue processing this patient record? No// ? Enter 'YES' to continue processing, or 'NO' to quit processing this record. New --- ***WARNING*** ***RESTRICTED RECORD*** * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ** * 1. STOP * * 2. Confirm you need access to this Restricted patient record * * * * This record is protected by the Privacy Act of 1974 and the Health * * Insurance Portability and Accountability Act (HIPAA) Privacy Rule. * * * Access to this patient record is tracked and monitored. * * * You must have need for this record to accomplish officially * * authorized and assigned duties, such as direct patient care, to * * proceed. * * * You must provide justification for your access upon request. * * * Failure to comply may result in disciplinary or adverse action up to* * and including removal from Federal service, and civil and criminal * * penalties. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ** Do you want to continue accessing this patient record? No// ? Enter 'YES' to continue accessing, or 'NO' to quit accessing this record. Do you want to continue accessing this patient record? No// (No) Test Sites: ----------- VA Pittsburgh HCS SNOW Change Order #: -------------------------------- VA Pittsburgh HCS - CHG0524309 Software and Documentation Retrieval Instructions: -------------------------------------------------- This patch is being distributed as a PackMan message. Patch Installation: ------------------- Pre/Post Installation Overview: Pre-Installation Instructions: ------------------------------ It is recommended that this patch be installed outside of normal business hours to avoid any complications resulting from users on the system. Installation will take less than 2 minutes. Installation Instructions: 1. Choose the PackMan message containing this patch and invoke the INSTALL/CHECK MESSAGE PackMan option. 2. From the Kernel Installation & 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 DG*5.3*1130. 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 your build DG*5.3*1130. iii. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build (including Routines) R Routines Only Enter response: B iv. When prompted "Do you wish to secure your build? 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 the components of this patch, such as routines, DDs, templates, etc. D. Select the Install Package(s) option and choose the patch to install, DG*5.3*1130. i. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer NO. ii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer NO Post-Installation Instructions ------------------------------ N/A 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 routine in a mail message using the Backup a Transport Global [XPD BACKUP] menu option from the Kernel Installation and Distribution System Menu and selecting the Installation Menu. The back-out plan is to restore the routine from the backup created. The message containing the backed-up routine 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 routine onto the VistA System. If the patch was backed up for the build, from the Kernel Installation and Distribution System Menu, select the Installation Menu. Select the Install Package(s) option and choose the patch (DG*5.3*1130b) to install. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.3;Registration;**[Patch List]**;Aug 13, 1993;Build 7 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: DGSEC Before: B44965286 After: B69401551 **32,46,197,214,249,281,352, 391,425,582,769,796,964,1130** Routine Name: DGSEC4 Before: B44665082 After: B52433846 **249,281,391,471,684,699,964,1130** Routine list of preceding patches: 964 ============================================================================= User Information: Entered By : Date Entered : SEP 12, 2024 Completed By: Date Completed: SEP 25, 2024 Released By : Date Released : SEP 25, 2024 ============================================================================= Packman Mail Message: ===================== $END TXT