$TXT Created by at MNTVBB.DOMAIN.EXT (KIDS) on Monday, 09/27/21 at 14:28 ============================================================================= Run Date: JAN 11, 2022 Designation: MD*1*80 Package : MD - CLINICAL PROCEDURES Priority: Mandatory Version : 1 SEQ #64 Status: Released Compliance Date: FEB 11, 2022 ============================================================================= Associated patches: (v)MD*1*29 <<= must be installed BEFORE `MD*1*80' Subject: MUSE ENCOUNTER COMPLETION ISSUE Category: - Routine Description: ============ This patch addresses the following issue: Encounters for procedures that are read and completed in the MUSE system are not crossing over correctly which causes the encounters to remain open. Defect Tracking System Ticket(s) & Overview: =========================================== INC18271595: MUSE Completed Procedure / Encounter Issue INC19903830 (d) Issue: ----- The MUSE system sends a value of "0" (zero) for the variable DUZ to VistA. "DUZ" is used by VistA to designate a user's (or proxy user's) internal entry number (IEN) in the NEW PERSON (#200) file. No users can be defined with a DUZ of zero. Because upstream MUSE logic sends a value of zero for DUZ, VistA will generate a processing error and will not automatically complete the associated encounter for a completed procedure. Resolution: ---------- Modify routines MDPCE, MDPCE1, and MDPCE2 to evaluate the DUZ variable which has been sent from upstream processing logic. If the DUZ value is not valid (i.e. zero, null, or undefined) retrieve the NEW PERSON (#200) internal entry number (IEN) for the proxy user "CLINICAL,DEVICE PROXY SERVICE". Test Sites: ----------- Boise VA Medical Center (Boise, Idaho) Captain James A. Lovell Federal Health Care Center (North Chicago, Illinois) Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Patch Instructions: ------------------ 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 name. (ex. MD*1.0*80). NOTE: Using will not bring up a Multi-Package build even if it was loaded immediately before this step. It will only bring up the last patch in the build. 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 MD*1.0*80. 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 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 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. 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. Example - load the backup build: Enter message action (in IN basket): Ignore// Xtract KIDS Select PackMan function: 6 INSTALL/CHECK MESSAGE Line 8 Message #169519 Unloading KIDS Distribution MD*1.0*80b MD*1.0*80b Want to Continue with Load? YES// Loading Distribution... MD*1.0*80b Example - install the backup build: Select Installation Option: Install Package(s) Select INSTALL NAME: MD*1.0*80b 9/7/21@11:37:39 => Backup of MD*1.0*80 on Aug 18, 2021. Build [Answer subsequent prompts in usual manner.] The back-out plan is to restore the routines from the backup created. No data was modified by this patch installation and, therefore, no rollback strategy is required. Validation of Back-out Procedure: --------------------------------- The Back-out Procedure can be verified by printing the first 2 lines of the routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routines contained in MD*1.0*80. patch have been backed out, the first two lines of the routines will no longer contain the designation of this patch in the patch list section. Routine Information: ==================== The second line of each of these routines now looks like: ;;1.0;CLINICAL PROCEDURES;**[Patch List]**;Apr 01, 2004;Build 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: MDPCE Before: B4196998 After: B5046292 **5,21,80** Routine Name: MDPCE1 Before: B5009420 After: B5500566 **6,80** Routine Name: MDPCE2 Before: B24838118 After: B25529924 **6,21,29,80** Routine list of preceding patches: 29 ============================================================================= User Information: Entered By : Date Entered : SEP 21, 2021 Completed By: Date Completed: JAN 11, 2022 Released By : Date Released : JAN 11, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT