============================================================================= Run Date: SEP 10, 2021 Designation: MAG*3*257 Package : MAG - IMAGING Priority: Mandatory Version : 3 SEQ #207 Status: Released Compliance Date: OCT 12, 2021 ============================================================================= Subject: VISTA Imaging - HDIG Defect(s) Fix Category: - Routine Description: ============ This document describes MAG*3.0*257, a patch that addresses the following issues: 1. INC10929224 - Unable to get a patient's outside diagnostic imaging to import to Vista imaging due to the patient having two last names. There are 4 additional tickets all related to the same issue: (INC11038264, INC12322606, INC16675462, INC15412222) 2. INC10091921 - Issue after Importing an old SOP class image. Images with Study ID tag (0020,0010) of no more than four characters in the image header prior to importing through the VI DICOM Importer III application, was modified to a value of greater than 48 characters after completing the import process. 3. INC13054429 - #2006.9421 'MAGV IMPORT STUDY LOG' not recording accession number properly. 4. INC6228060 - VistA creates duplicate patient record entries and logs multiple threads for the same patient. There are 2 additional tickets all related to the same issue: (INC7481655; INC6484886) 5. INC7909232 - HDIG is hanging because the Image_In folder was filling up and the hard drive was full. There is another ticket that is related to the same issue: (INC8122278) 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: ----------------------- 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. INC10929224 - Unable to get a patient's outside diagnostic imaging to import to Vista imaging due to the patient having two last names. There are 4 additional tickets all related to the same issue: (INC11038264, INC12322606, INC16675462, INC15412222) Problem: -------------------- The Knoxville Tennessee Community-Based Outpatient Clinic (CBOC) site reported an issue of not being able to successfully import patient's outside images to VistA Imaging (VI). Analysis by a CLIN3 specialist revealed the issue occurs when there is a space in the patient's name. The issue started after the MAG*3.0*239 update. Resolution: ----------- HDIG application was replacing space in the Patient's Name with comma and hence the error. Removed the code that replaces space with comma. 2. INC10091921 - Issue after Importing an old SOP class image. Images with Study ID tag (0020,0010) of no more than four characters in the image header prior to importing through the VI DICOM Importer III application, was modified to a value of greater than 48 characters after completing the import process. Problem: -------------------- The DICOM Importer is inserting the new Study Instance UID into the incorrect Study ID. It is inserting the Study Instance UID into the Study ID (0020,0010) data element instead of the correct Study Instance UID (0020,000D) data element. This causes problems with other systems when the image is exported. MAG3_0P231 is adding a check to the Legacy DICOM gateway to verify length of data elements. These images are unable to be processed since the Study ID with the Study instance UID in it violates the length outlined by the DICOM standard. This new check will have an option to turn it on and off. It will remain off until this issue with the Importer is corrected. Resolution: ----------- HDIG is putting the new Study Instance UID into the Study ID (0020,0010) data element instead of the Study Instance UID (0020,000D) data element. During the setting of the Study Instance UID value, (0020,0010) tag is replaced with (0020,000D) tag. 3. INC13054429 - #2006.9421 'MAGV IMPORT STUDY LOG' not recording accession number properly. Problem: -------------------- A large number of entries in #2006.9421 'MAGV IMPORT STUDY LOG' do not contain an accession number value. Despite the availability of the accession number value during the HDIG process, the value is not always made available as part of the RPC 'MAGV IMPORT STUDY LOG STORE' to VistA. Accession Number is Null. Imported successfully, Login to Importer and create a new Radiology Order and Import. Import goes through successfully, however Accession Number is Null. Resolution: ----------- The issue happens while creating new order. After creating new order, the Accession number is updated with new value. 4. INC6228060 - VistA creates duplicate patient record entries and logs multiple threads for the same patient. There are 2 additional tickets all related to the same issue: (INC7481655; INC6484886) Problem: -------------------- The HDIG application is creating duplicate entries in the Imaging Patient Reference (#2005.6) and Procedure References (#2005.61) files in Vista. Resolution: ----------- On the Java side, the application is coded to check whether duplicate records in the Patient Reference (#2005.6) or Procedure Reference (#2005.61) files already exist or need to be created. Accordingly, the appropriate exception is thrown. On the MUMPS side, applied a lock on the Patient Reference (#2005.6) and Procedure Reference (#2005.61) files, so that only one thread makes an entry in a file. If the error occurs due to a race condition, then the HDIG traps the error and once again makes a call to Vista to get the reference from the corresponding file. 5. INC7909232 - HDIG is hanging because the Image_In folder was filling up and the hard drive was full. There is another ticket that is related to the same issue: (INC8122278) Problem: -------------------- HDIG is creating files of zero bytes in the Image_In folder and making an entry in the 2006.571. Resolution: ----------- During normal workflow of transferring previously supported SOP Class images, the HDIG makes a call to Legacy DICOM Gateway (LDGW) to create a queue entry and return temporary filename. During this request to the LDGW, if the space in the disk where Image_In folder is located is below the threshold set in the LDGW configuration, then the MUMPS routine in LDGW instead of returning a queue entry and return temporary filename, LDGW returns "NOT ENOUGH DISK SPACE TO STORE IMAGES" message. The message will be written to the ImagingExchangeWebApp log file on the HDIG stats page. And an email will be sent to the Administrator similar to this: Failed to store DICOM object with SOP Instance UID 1.2.840.113663.1500.1.430065718.3.2.20190617.144917.889.5: Processing Error [P116_SCU->60200/188] gov.va.med.imaging.core.interfaces.exceptions.MethodException: gov.va.med.imaging.core.interfaces.exceptions.MethodException: -2 ERROR -- NOT ENOUGH DISK SPACE TO STORE IMAGES ON D: Submitted by: Mon Feb 03 10:17:25 CST 2020 Hostname: VHAXXXYourHDIGNameHere SiteId: 660 Timestamp: Feb 3, 2020 10:17:49 AM Test Sites: ----------- VA Eastern Colorado Health Care System (Denver, CO) Veterans Health Care System of the Ozarks (Fayetteville, AR) Jesse Brown VAMC (Chicago) St Louis VAMC 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_0P257.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 ------------------------------------------------------------------ Kernel Installation and MAG3_0P257.KID Distribution System (KIDS) Hybrid DICOM Gateway MAG3_0P257_HDIG_SETUP.MSI Installation File LDGW Installation File MAG3_0P257_DICOM_SETUP.EXE Documentation Title File Name ------------------------------------------------------------------ Patch Description for MAG3_0P257_PATCH_DESCRIPTION.PDF MAG*3.0*257 Deployment, Installation, MAG3_0P257_DIBORG.PDF Back-Out, and Rollback Guide Patch Installation: ------------------- Supported Client Versions: -------------------------- When MAG*3.0*257 is released, the list of supported versions of HDIG will change: Client Versions Supported: -------------------------- 3.0.257 3.0.239 3.0.204 Client Versions No Longer Supported: ------------------------------------ 3.0.194 3.0.192 3.0.172 Pre/Post Installation Overview: ------------------------------- MAG*3.0*257 must be installed on the VistA System and on 64-bit HDIG servers. This patch must be installed by the compliance date. All sites running VistA Imaging 3.0 must install the KIDS portion of this patch. This patch can be loaded while the VistA Imaging System is active and users are on the system. Installing the MAG*3.0*257 KIDS takes 2-5 minutes. Note: The MAG*3.0*257 KIDS should be installed on VistA first and then the DICOM Gateway updated. The VistA DICOM Gateway query/retrieve capabilities require DICOM Gateway services and will not be operational until MAG*3.0*257 is installed on the DICOM Gateways. Note: For a fresh installation, remove all installed Java applications before the installation of MAG*3.0*257. Verify that the patches listed in the Associated Patches section of this document have been previously installed. Note: If setting up a new server, please follow the steps below to permit installation of Microsoft Visual C++ when LDGW is installed. 1. Right click on the DICOM_setup application 2. Select Properties 3. Select the Compatibility tab 4. Check the box for Compatibility mode 5. Click Apply and select OK Note: To avoid losing configuration changes, sites with a modified HDIG Listen file will need to save a copy of the file before installing this patch. After the installation is complete, compare the backed up Listen file with new Listen file, make appropriate changes to the new Listen file. and restart the Tomcat service. The listen file contains new SOP classes. These SOP classes will be disabled and should not be enabled until MAG*3.0*271 is released. C:\DCF_RunTime\cfg\apps\defaults\LISTEN 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_0P257.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 (ex. MAG*3.0*257). 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 of any routines exported with this patch. It will not backup any other changes such as DDs or templates. 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?,' answer NO. ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install?,' answer NO. Installing and Updating the HDIG: --------------------------------- For installing or updating the HDIG, refer to the Hybrid DICOM Image Gateway (HDIG) Installation Guide. Post-Installation Instructions: ------------------------------- ALL DICOM Gateways, including Legacy, Text and Routing, as well as HDIGs, need to be upgraded with the installation of MAG3_0P257_DICOM_Setup.exe at your earliest convenience. Refer to the VistA Imaging DICOM Gateway Installation Guide for details. Note: Backup the DICOM dictionary directory. Typically, the DICOM Dictionaries are installed in the \DICOM\Dict directory on a network drive. IMPORTANT: The Caché Service must be stopped before upgrading the DICOM Gateway. Note: When Caché is installed, it will automatically install Adobe SVG Viewer 3.0 which is not approved for use and must therefore be uninstalled using Add/Remove programs. Note: If installing the LDGW on a new server, the latest 2008 C++ Redistributables must be downloaded and installed prior to running the install of the LDGW. The latest version can be downloaded at: https://www.microsoft.com/en-us/download/details.aspx?id=26368 Note: After the patch installation, Telnet needs to be disabled. Refer to the VistA Imaging DICOM Gateway Installation Guide for details. (section 4.7.3) LDGW: ------ Verify the checksums of the added/updated routines. Routine Checksum Before Checksum After Patch List ------- --------------- -------------- ----------- MAGDVRSN 21494340 21494340 **1,7,9,26, 21,10,36,3, 11,30,5,51, 50,52,69,75, 102,103,54, 53,66,49,99, 123,118,87, 110,138,156, 160,162,174, 166,183,190, 218,231,257** MAGVCSTR 11185442 11878763 **118,110, 257** VistA KIDS: ------------ 1. Verify the checksums of the added/updated routines. Routine Checksum Before Checksum After Patch List ------- --------------- -------------- ---------- MAGIP257 New 4110440 ***257*** MAGVRS06 4241857 6283965 **118,257** Routine MAGIP257 is an installation routine that is automatically deleted after the KIDS installation. 2. Review the HDIG Statistics page for each Image Gateway a. If not opened already, then access the HDIG Statistics Home page or http://:8080/HDIGManagementWebApp/ViewHDIGStats.jsp. b. Check for proper values in the basic information fields Hostname, Site Number, Site Name and Version <30.257.1.7004>. c. Review the Inbound Activity section of the HDIG Statistics page to ensure all instruments on each specific gateway are listening on the proper ports as indicated in the INSTRUMENT.DIC file. Back-out and Rollback: ---------------------- Uninstalling Client: -------------------- For uninstalling the HDIG and instructions on reinstalling the previous patch (MAG*3.0*239 for HDIG and MAG*3.0*231 for LDGW), refer to the Hybrid DICOM Image Gateway (HDIG) Installation Guide. KIDS Uninstall: --------------- If it is necessary to uninstall the MAG*3.0*257 VistA KIDS, then select the Kernel Installation & Distribution System menu option, Backup a Transport Global (see the Installation Instructions section) where step 2b must be done before installing the patch. Administrators will need to use the PackMan function INSTALL/CHECK MESSAGE. Check the MailMan messages for the backup message sent by the Backup a Transport Global function executed prior to the patch install. 1. Select the message shown below: 2. Backup of MAG*3.0*257 install on 3. Select the Xtract PackMan option. 4. Select the Install/Check Message option. 5. Enter Yes at the prompt. 6. Enter No at the backup prompt. There is no need to back up the backup. Back-out Verification: ---------------------- 1. Review the HDIG Statistics page for each Image Gateway. a. If not opened already, then access the HDIG Statistics Home page or http://:8080/HDIGManagementWebApp/ViewHDIGStats.jsp. b. Check that proper values for the previous patch (MAG*3.0*239) are in the basic information fields: Hostname, Site Number, Site Name and Version <30.239.5.8001>. c. Review the Inbound Activity section of the HDIG Statistics page to ensure all instruments on each specific gateway are listening on the proper ports as indicated in the INSTRUMENT.DIC file. 2. Perform site-specific testing appropriate to the areas where the catastrophic failure was identified. LDGW Back-out Verification: ---------------------- 1. Log into the Legacy DICOM Gateway 2. Start the 2-3 process (Process DICOM Images) 3. Verify that images are being processed Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;IMAGING;**[Patch List]**;Mar 19, 2002;Build 20 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: MAGIP257 Before: n/a After: B4110440 **257** Routine Name: MAGVRS06 Before: B4241857 After: B6283965 **118,257** Routine list of preceding patches: 118 ============================================================================= User Information: Entered By : Date Entered : FEB 04, 2020 Completed By: Date Completed: SEP 10, 2021 Released By : Date Released : SEP 10, 2021 ============================================================================= Packman Mail Message: ===================== No routines included