============================================================================= Run Date: JAN 17, 2025 Designation: MAG*3*335 Package : MAG - IMAGING Priority: Mandatory Version : 3 SEQ #260 Status: Released Compliance Date: FEB 19, 2025 ============================================================================= Associated patches: (v)MAG*3*291 <<= must be installed BEFORE `MAG*3*335' (v)MAG*3*334 <<= must be installed BEFORE `MAG*3*335' Subject: VI CLINICAL CAPTURE - DEFECT PATCH Category: - Routine Description: ============ This document describes MAG*3.0*335, a patch that provides fixes to VistA Imaging Clinical Capture. This patch addresses the following defects: Defect(s): ------------------- 1. INC21218210 - VISTAIS-327 - In VistA Imaging Clinical Capture, when attempting to upload a video, the video does not open with AVI. Location Reporting Incident: Durham Veterans Affairs Medical Center, Durham, NC. 2. INC25317868 - VISTAIS-1356 - VistA Imaging Clinical Capture upload error - TestingWriteAccess.txt error Location Reporting Incident: Portland Veterans Affairs Medical Center, Portland, OR. 3. INC22886590 - VISTAIS-332 - In VistA Imaging Clinical Capture, when a short description has special characters, the patient images become unviewable to the end user on VistA Imaging Clinical Display and JLV (Joint Legacy Viewer). Location Reporting Incident: Veterans Affairs Medical Center, Wade Park Campus, OH. 4. INC29514375 - VISTAIS-2595 - VistA Imaging Clinical Capture Application will not upload JPEG image. Location Reporting Incident: Montgomery County Veterans Affairs Clinic, Salem, VA. Adaptive Maintenance: ===================== 1. VISTAIS-2116 - VistA Imaging Clinical Capture, corrected a defect that can cause the Setting Workstation default Timeout minutes value to change to NULL instead of 6. 2. VISTAIS-3082 - VistA Imaging Clinical Capture, add new file type(s) MP4 and JPEG to the Files of type dropdown. 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 -------------- -------------------- N/A Additional Information: ----------------------- N/A Blood Bank Team Coordination: N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC2128210 - VISTAIS-327 - In VistA Imaging Clinical Capture, when attempting to upload a video, the video does not open with AVI. Location Reporting Incident: Durham Veterans Affairs Medical Center, Durham, NC. Problem: -------- VistA Imaging Clinical Capture not working for video uploads. When videos encoded as MPEG are used, the VistA Imaging Clinical Capture application will display an error that it is unable to display the video. Resolution: ----------- Several code changes were made to the associated Delphi forms to implement the solution: - Deprecated the old Delphi form which contained references to the VCL MediaPlayer that was unable to play videos encoded as AVI/MPEG. - Created a new Delphi form which uses the WMP ActiveX control and is able to play videos encoded as AVI/MPEG. This form is listed in the directory as "Shared\FActiveXTMediaPlayer.pas". - Modified "fmagCapMain.pas": - Added procedure calls to invoke the new Media Player (from "FActiveXTMediaPlayer.pas"). - Removed procedure calls and references to "fmagVideoPlayer.pas" (the legacy problematic video player). - Added logic to run all supported multimedia types (.AVI, .MP3, .MP4, .MPEG) in the new form/ActiveX Media Player. 2. INC25317868 - VISTAIS-1356 - VistA Imaging Clinical Capture upload error- TestingWriteAccess.txt error Location Reporting Incident: Portland Veterans Affairs Medical Center, Portland, OR. Problem: -------- Portland has hired contract scanners to catch up on work, and they have many users trying to work at the same time. When a user tries to test writing to a directory, VistA Imaging Clinical Capture locks a file called TestingWriteAccess for the entire directory. VA wants this file name modified so there is no conflict for users as they try to create the file. This unique number can be determined from the IEN number when the capture process begins, and VistA Imaging Clinical Capture will append the last two (2) characters of the IEN to the end of the TestingWriteAccess file name, causing the filename to be unique in every directory since VistA Imaging Clinical Capture only writes files 00-99 in a directory. Resolution: ----------- Changes were made to VistA Imaging Clinical Capture to append the last two (2) characters of the IEN to the file name to the Tier 1 file location. This results in a unique TestingWriteAccess file for each user within the Tier 1 file directory, helping to prevent contention of resources. Added logging to VistA Imaging Clinical Capture to indicate successful creation/deletion of the file. As a result, we will have file names like TestingWriteAcess00 thru TestingWriteAcess99, which gets temporarily saved to the Tier 1 file location. 3. INC22886590 - VISTAIS-332 - In VistA Imaging Clinical Capture, when a short description has special characters, the patient images become unviewable to the end user on VistA Imaging Clinical Display and JLV. Location Reporting Incident: Louis Stokes Cleveland Veterans Affairs Medical Center, Wade Park Campus, OH. Problem: -------- Delete cache and try again message was displaying when trying to view some images in JLV. Certain situations will prevent captured images from being displayed in JLV and VistA Imaging Clinical Display. The situations in which this defect was experienced are when images with descriptions containing special characters, specifically the up caret (^) and the pipe(|), were attempted to be loaded in the JLV and VistA Imaging Clinical Display. Resolution: ----------- Added new Delphi code to prevent special characters from being saved within image descriptions. The code detects the up-caret (^) and the pipe (|) symbols, flags the entry as an error and disables the Capture button. The error message informs the user that the special characters must be removed. 4. INC29514375 - VISTAIS-2595 - VistA Imaging Clinical Capture application will not upload JPEG image. Location Reporting Incident: Montgomery County Veterans Affairs Clinic, Salem, VA Problem: -------- Washington VAMC Dermatology health techs are reporting an issue with VistA Imaging Clinical Capture in regard to uploading the JPEG images to complete consults. In SNOW ticket INC29514375 and child tickets INC29514492, INC29514662, INC29514665 and INC29509342, it has been shown that TeleReader consults are not capturing correctly when trying to attach JPEG images. Resolution: ----------- Added logic to VistA Imaging Clinical Capture for TeleReader consults to allow capture of JPEGs in addition to JPG and TIF file with complete DICOM data set. Adaptive Maintenance: ===================== 1. VISTAIS-2116 - VistA Imaging Clinical Capture, corrected a defect that can cause the Setting Workstation default Timeout minutes value to change from NULL instead of 6. Problem: -------- VistA Imaging Clinical Capture's MAG.INI Workstation timeout setting does not appear to be working correctly for VistA Imaging Clinical Capture. When any setting other than 0 is entered into the mag.ini - WorkStation Time Out minutes - entry VistA Imaging Clinical Capture goes into a timeout state on startup. If an initial value is not defined in VistA, the timeout should default to 6 minutes, and VistA Imaging Clinical Capture should use this value. Resolution: ----------- The VistA MUMPS MAGGTU6 was changed such that if called from VistA Imaging Clinical Capture when the Windows Timeout is set manually by the user in MAG.INI to 0 and the IMAGING SITE PARAMETER (file #2006.1), TIMEOUT WINDOWS CAPTURE (field #122) value is " " or Null, the routine shall Return a value of 6 minutes. VistA Imaging Clinical Capture will use this value as the default timeout value. 2. VISTAIS-3082 - For VistA Imaging Clinical Capture, add new file type(s) MP4 and JPEG to the Files of type dropdown. Problem: -------- In VistA Imaging Clinical Capture when selecting the file type MP4 and JPEG are not an available Options in the drop down in Files of type while capturing the image. Resolution: ---------- Added the option of type MP4 Files (*.mp4) and JPEG Files (*.jpg, *.jpeg) in the drop down while selecting the Files of type, so that user can select the file type while Capturing in VistA Imaging Clinical Capture. Test Sites - SNOW Change Order #: -------------------------------- Washington Veterans Affairs Medical Center (Washington, DC)- CHG0549009 Spark M. Matsunaga Veterans Affairs Medical Center (Honolulu, HI)- CHG0550596 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released using a host file. The host file is available at the following location: /srv/vista/patches/SOFTWARE/MAG3_0P335.KID Other Software Files: This release also includes other software files. These files can be obtained by accessing the URL: https://download.vista.domain.ext/index.html/SOFTWARE File Title File Name Format -------------------------------------------------------------------------- Kernel Installation and MAG3_0P335.KID ASCII Distribution System (KIDS) build for MAG*3.0*335 VistA Imaging Clinical Capture MAG3_0P335_CLINICAL_ Binary Installation File CAPTURE_INSTALL.MSI VistA Imaging Clinical Capture MAG3_0P335_CLINICAL_ Binary Workstation Installation File. CAPTURE_SETUP.EXE Documentation describing the new functionality that 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 -------------------------------------------------------------------------- Patch Description for MAG*3.0*335 MAG3_0P335_PATCH_DESCRIPTION.PDF Deployment, Installation, Back-Out, MAG3_0P335_DIBRG.PDF and Rollback Guide Patch Installation: ------------------- Pre/Post Installation Overview: ------------------------------- Supported Client Versions: -------------------------- When MAG*3.0*335 is released, the list of supported versions of VistA Imaging Clinical Capture will change: Client Versions Supported: -------------------------- 3.0.335 3.0.291 3.0.321 Client Versions No Longer Supported: ------------------------------------ 3.0.267 3.0.264 3.0.226 Pre-Installation Instructions: ------------------------------ MAG*3.0*335 must be installed on the VistA System on which the VistA Imaging Clinical Capture Application will be used. This patch must be installed by the compliance date. 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. Verify that the previous patch in the Supported Client Versions section has been installed. Note: All released VistA Imaging Clinical Capture patches must be installed on the VistA system before installing MAG*3.0*335. Routine MAGIP335 is an installation routine that is automatically deleted after the KIDS installation. Installation Instructions: -------------------------- 1. Use the Load a Distribution option contained on the Kernel Installation and Distribution System Menu to load the Host file. When prompted to "Enter a Host File:" enter /srv/vista/patches/SOFTWARE/MAG3_0P335.KID 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 (MAG*3.0*335). 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 (MAG*3.0*335). 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. vii. Repeat step ii for each build in the host file. 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. 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. iv. When prompted 'Delay Install (Minutes): (0 - 60): 0//', answer 0. Client Installation Instructions: --------------------------------- For installing or updating VistA Imaging Clinical Capture, refer to the VistA Imaging System Installation Guide on the VA Software Documentation Library at: https://www.domain.ext/vdl/ Post-Installation Instructions: ------------------------------- Post install routine MAGIP335 will automatically run at the end of the installation process. Routine MAGIP335 is automatically deleted after the KIDS installation. For post-installation steps following first-time installation, refer to the VistA Imaging System Installation Guide on the VA Software Documentation Library at: https://www.domain.ext/vdl/ Back-Out/Roll Back Plan: ------------------------ Please refer to the Deployment, Implementation, Back-Out and Rollback Guide (MAG3_0P335_DIBRG.PDF) for Client Installation instructions. Uninstalling the Application: ----------------------------- If it is necessary to uninstall the MAG*3.0*335 client, use the Uninstall option from Programs and Features within Windows Control Panel to Uninstall: VistA Imaging Clinical Capture. Then install the previous version of VistA Imaging Clinical Capture which was included in MAG*3.0*291 or refer to the VistA Imaging System Installation Guide on the VA Software Documentation Library at: https://www.domain.ext/vdl/ Note: There are special installation instructions for MAG*3.0*291. Be sure to review the associated readme file (MAG3_0P291_README.PDF) when reverting to this version. KIDS Uninstall: --------------- If it is necessary to uninstall the MAG*3.0*335 VistA KIDS, the patch backup must be installed. The Kernel Installation & Distribution System menu option, Backup a Transport Global should have been used to create a patch backup of the build prior to installing the patch. (See the Installation Instructions section, step 2B). Administrators will need to check MailMan for the backup message sent by the Backup a Transport Global function executed prior to the patch install. The patch backup must first be loaded from the MailMan backup message, by performing the message action Xtract KIDS, followed by the PackMan function INSTALL/CHECK MESSAGE. The patch may then be installed using the Install Package(s) option in the KIDS Installation menu. 1. Navigate to the Mailman inbox containing the patch backup message. a. Select the MAG*3.0*335 backup message as shown below: * Backup of MAG*3.0*335 install on b. At the "Enter message action:" prompt, select the Xtract PackMan option. c. At the "Select PackMan function:" prompt, select the Install/Check Message option. d. Enter Yes at the prompt "OK to continue with Load?" 2. Navigate to the Kernel Installation and Distribution System Menu and select the Installation Menu. From this menu: a. Select the Install Package(s) option and choose the patch to install. At the "Select INSTALL NAME:" prompt, enter MAG*3.0*335 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. Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;IMAGING;**[Patch List]**;Mar 19, 2002;Build 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: MAGGTU4C Before: B4954042 After: B4957747 **93,94,106,117,122,129,140, 151,178,189,211,215,223,233, 226,264,267,321,291,335** Routine Name: MAGGTU6 Before: B53671836 After: B54483768 **24,8,48,45,20,46,59,72,93, 117,138,334,335** Routine Name: MAGIP335 Before: n/a After: B4076416 **335** Routine list of preceding patches: 291, 334 ============================================================================= User Information: Entered By : Date Entered : JUN 15, 2022 Completed By: Date Completed: JAN 16, 2025 Released By : Date Released : JAN 17, 2025 ============================================================================= Packman Mail Message: ===================== No routines included