$TXT Created by K at DEVFEX.DOMAIN.EXT (KIDS) on Friday, 08/19/22 at 08:27 ============================================================================= Run Date: AUG 22, 2022 Designation: DVBA*2.7*245 Package : DVBA - AUTOMATED MED INFO EXCHANGE Priority: EMERGENCY Version : 2.7 SEQ #206 Status: Released Compliance Date: AUG 23, 2022 ============================================================================= Associated patches: (v)DVBA*2.7*238<<= must be installed BEFORE `DVBA*2.7*245' Subject: CLINICAL DOCUMENTS 401 ERROR UPDATE Category: - Routine Description: ============ Patch DVBA*2.7*245 will fix the following issue: CAPRI GUI VBA Users are receiving a 401 error when sending documents using the Send to VBA eFolder Option. 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: N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1.) INC23855232: capri transfer of document issue INC23855099: CAPRI will not let me send documents to VBMS - seems to be a certificate issue. INC23832201: CAPRI will not allow upload to VBMS INC23849031: Capri error - unable to send records to VBMS eFolder Problem: -------- Some users are experiencing an issue with sending Clinical Documents to the VBA eFolder when switching sites. Resolution: ----------- Removed security check on security key return as this is causing the issue for remote users. Test Sites: ---------- Tampa VA Medical Center (Tampa, FL) Software and Documentation Retrieval Instructions: ---------------------------------------------------- The software for this patch is being released in a PackMan message Documentation describing the new functionality is not included in this release. Documentation Title File Name ---------------------------------------------------------------------- N/A Patch Installation: Pre/Post Installation Overview: ------------------------------- N/A 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. (ex. ) 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 DVBA*2.7*245 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 Enter response: Build (including Routines) 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 . iii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer . Post-Installation Instructions ------------------------------ N/A Back-Out 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. Log a ServiceNow helpdesk ticket so the development team can assist in this process. Prior to installing a patch, the site/region should have saved a back-up 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. Routine Information: ==================== The second line of each of these routines now looks like: ;;2.7;AMIE;**[Patch List]**;Apr 10, 1995;Build 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: DVBABURL Before: B12675140 After: B11691305 **104,136,143,149,168,181,186, 192,205,237,240,238,245** Routine list of preceding patches: 238 ============================================================================= User Information: Entered By : Date Entered : AUG 18, 2022 Completed By: Date Completed: AUG 22, 2022 Released By : Date Released : AUG 22, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT