============================================================================= Run Date: FEB 04, 2026 Designation: MAG*3*333 Package : MAG - IMAGING Priority: Mandatory Version : 3 SEQ #271 Status: Released Compliance Date: MAR 09, 2026 ============================================================================= Associated patches: (v)MAG*3*196 <<= must be installed BEFORE `MAG*3*333' (v)MAG*3*208 <<= must be installed BEFORE `MAG*3*333' (v)MAG*3*305 <<= must be installed BEFORE `MAG*3*333' Subject: VI-LDGW REAL-TIME MONITOR OF RETRIEVAL OF MISSING IMAGES Category: - Routine - Data Dictionary - Other Description: ============ This document describes the MAG*3.0*333 changes to VistA and the Legacy DICOM Gateway (LDGW). The primary changes are updates to Study Tracker. The VA requires all digital medical images for the patient to be stored in VistA Imaging. Study Tracker provides both an automatic and manual mechanism to identify missing images in VistA and retrieve them from a PACS. Study Tracker will be used for retrieving Radiology, Dental, Eye Care, and other clinical specialty images. The migration to Oracle Cerner expects all digital medical images (except Cardiology) to be in VistA Imaging. Oracle Cerner will be obtaining the VA images from VistA Imaging and not the site PACS. Adaptive Maintenance ======================= VISTAIS-4150 - Real-Time Automatic Monitor of Image Retrieval VISTAIS-4151 - Study Tracker Excel Comma-Separated Value File VISTAIS-4160 - Chronological Ordering of Radiology Automatic Compare/Retrieve VISTAIS-4143 - Header display of Encapsulated Encoded Pixel Data Segments VISTAIS-4141 - Manifest Files for Batch Export of Images VISTAIS-4146 - Removing Scratch files from Image Output folder VISTAIS-4152 - DICOM Gateway/VistA Routine Checksums Defects ======================= VISTAIS-3507 - Diâ Division is Undefined for Queued Jobs (INC34386963, INC38357561) VISTAIS-4148 - DICOM Gateways VistA Q/R Surrogates are not Division specific VISTAIS-3495 - Router Evaluation Processor date format (INC38881977) VISTAIS-3501 - Validate Access/Verify Codes for Background Task Usage (INC28769269) VISTAIS-3393 - Legacy DICOM Gateway Install Process Needs Longer Pause (INC36250927) VISTAIS-4140 - Improved C:\DICOM\DATA1 Deletion Technique (INC30616458) VISTAIS-4144 - Automatic Handling of RPC Errors for Batch Export VISTAIS-4153 - Correction of MAGDOUTP Piece-4 Counter Problem (INC23350751, INC24440368, INC23530064) VISTAIS-4159 - Problem with Terminated RPC Session (INC23857017, INC26509974, INC25925960, INC24638776, INC23713380) VISTAIS-4161 - Maintain Processing Lock When Error-Initiated Restart Occurs (INC23599225) EHRM Impact Statement: ---------------------- This patch should have no EHRM impact, and can be installed at all sites, including EHRM converted sites. ` Patch Components: ---------------- VistA Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- IMAGING SITE PARAMETERS Q/R CHECK DIVISION(#211) New (#2006.1) STUDY TRACKER REPORT New FOLDER (#212) STUDY TRACKER REPORT New FILENAME (#213) SAVE Q/R REPORT IN EXCEL New FILE (#214) AUTO Q/R MANUAL/AUTO New SCROLL (#215) DICOM VISTA Q/R REQUEST DIVISION (#.01) New QUEUE (#2006.541) LDGW Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- Show-menu.ps1 New VIMfunctions.ps1 New VI Maintenance.LNK New Forms Associated: Form Name File Number New/Modified/Deleted --------- ----------- -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A VistA Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- MAG SYS MENU Menu Modified Display Routine Checksums Routine New MAGD RAD STUDY TRACKER Menu Modified MAGD CON STUDY TRACKER Menu Modified MAGD AUTO RETRIEVE MONITOR Routine New LDGW Options Associated: Option Name ----------- 4-1-10 Display Routine Checksums 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 --------------------- -------------------- MAG DICOM GET NEXT QUEUE ENTRY Modified 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: -------------------------------------------- Adaptive Maintenance ======================= VISTAIS-4150 - Real-Time Automatic Monitor of Image Retrieval Problem: -------- When running the Automatic Query and Retrieve on VistA, the user is unable to see if the retrieves are failing unless they have access to the DICOM Gateway where 2-14-2 Execute C-MOVE Request to Retrieve Images is running. If for some reason the 2-14-2 window is not running the retrieve on VistA looks like it is running without error. Resolution: ----------- The option MON Real-Time Monitor of Retrieval of Missing Images was added on VistA under both the Radiology and Consult Study Tracker Menus. This option is run in tandem with Automatic Retrieve of Missing Images and provides information on each retrieve request. VISTAIS-4151 - Study Tracker Excel Comma-Separated Value File Problem: -------- The Study Tracker Automatic Compare and Retrieve in VistA does not create a log file when running. Sites queue the output to a MailMan message, but it is very difficult to find and sum up information about the number of studies and images in VistA and PACS. Resolution: ----------- An option was added when running the Study Tracker Automatic Compare and Retrieve to log the information to the XTMP global. This information can then be exported to a local workstation as a comma-separated value file (*.CSV) under the current Display stats for automatic Q/R runs for both Radiology and Consults. The .csv file can be easily opened in Excel. VISTAIS-4160 - Chronological Ordering of Radiology Automatic Compare/Retrieve Problem: -------- The Radiology Automatic Compare and Retrieve options on VistA list the radiology exams in order of their verification date. Since the time to verify a radiology study can vary somewhat from the actual study date, the accession numbers in the report were not in absolute chronological order. Resolution: ----------- The Radiology Automatic Compare and Retrieve options on VistA were changed to traverse the examination date and times in the RAD/NUC MED PATIENT file (#70) (^MAGDSTA5). The records in the report are in the chronological order of the examination date and times. VISTAIS-4143 - Header display of Encapsulated Encoded Pixel Data Segments Problem: -------- Option 2-9 Display a DICOM Image Header on the LDGW does not show the encapsulation sequences for Pixel Data. Resolution: ----------- Added the option to display encapsulation sequences for Pixel Data when viewing the DICOM Header of an image based on the DICOM Standard. The display of the Pixel Sequences can be turned off and on at the command prompt by running DEBUG^MAGDDR2 subroutine. VISTAIS-4141 - Manifest Files for Batch Export of Images Problem: -------- When running Batch Export of Images by Accession Number List there was no log that showed success or failures of the images being sent. If the export run got interrupted with VistA RPC failure there was no record of where in the list of accession numbers the export left off. Resolution: ----------- A modification was added when exporting a set of DICOM objects by a list of accession numbers. The user now has the option to create a study manifest file and a separate image manifest file. Both manifest files contain Comma-Separated Value data that can easily be imported into EXCEL and/or be read with custom computer applications. The user also has the option to create both the study and image manifest files without doing any image transfers (INFO option). This is useful for planning purposes. The Study Manifest contains one record per study and consists of the following fields: 1. Accession Number 2. Study Problem (if there is one) 3. Description 4. File Type (the extension(s) like DCM, JPG, PDF 5. Count of images in study 6. Count of images transferred (for SEND and COPY options) 7. Count of failed image transfers 8. Count of missing image files 9. Size of the study (sum of all the image file sizes) 10. Image Date 11. Image Time The Image Manifest contains one record per image file and consists of the following fields: 1. Accession Number 2. File Name 3. Image Problem (if there is one) 4. File size (bytes) 5. Image Date 6. Image Time VISTAIS-4146 - Removing Scratch files from Image Output folder Problem: -------- The DICOM Export application creates two sets of scratch files in the Image Output folder. The first set of files contain the parameters for the Laurel Bridge storage SCP DCF_STORE_SCU.EXE. These files are named DCFâDCF_STORE_SCU_.CFG. The second set of scratch files are the DICOM files that are produced from converting a TGA files before export. Neither of these two sets of scratch files need to be kept, but there is no option to clean up these files. Resolution: ----------- A PowerShell script was added that can be run from a Windows Desktop shortcut that will delete the contents of the C:\DICOM\IMAGE_OUT folder. Show-menu.ps1 - C:\Program Files (x86)\VistA\Imaging VIMfunctions.ps1 - C:\Program Files (x86)\VistA\Imaging VI Maintenance.LNK - placed in C:\users\Public\Desktop VISTAIS-4152 - DICOM Gateway/VistA Routine Checksums Problem: -------- LDGW patches update MUMPs routines on both VistA and on the LDGW. The patch documentation for the LDGW includes MUMPS routine checksums, however, ther is no LDGW option that is provided for users to display routine checksums. Resolution: ----------- An option was added to the LDGW System Operation menu and the VistA MAG SYS MENU to Display Routine Checksum. These options use the KIDS algorithm for checksums for a set of routines either by name or by patch number. In addition to displaying the checksum for a routine, the last edit date and time (from the routine's fâs first line) and the patch list string (from the routine's sâs second line) are also shown. Defects ======================= VISTAIS-3495 - Router Evaluation Processor date format Problem: -------- When the Routing Evaluation Processor is started and stopped, the start and stop times are output in an internal MUMPS date format. Waiting for task #29576 to start. Tue 15:05 Started at 66260,55195 Tue 15:06 Stopped at 66260,55246- Remote process has ended. Resolution: ----------- Updated the output format to show month, day, year and time. Waiting for task #29576 to start. Tue 15:05 Started at May 31, 2022@15:05:30 Tue 15:06 Stopped at May 31, 2022@15:06:18- Remote process has ended. VISTAIS-3501 - Validate Access/Verify Codes for Background Task Usage Problem: -------- If a bad Access or Verify code is entered 4-2-2 Update Gateway Configuration Parameters, the 4-2-11 Validate Access/Verify Codes for Background Task Usage still says the codes are valid. The test of the Access/Verify codes is using the existing RPC connection from logon instead of using the background Access/Verify codes. Resolution: ----------- Close the existing RPC connection in 4-2-11 before trying the background Access/Verify codes. VISTAIS-3507 Diâ Division is Undefined for Queued Jobs Problem: -------- When running a Study Tracker Automatic Query Retrieve or Compare and trying spooling the output to a Mailman Message, sites are getting the error message. If the Query/Retrieve Site Parameter 'Select only studies for the current division for auto compare/retrieve?' was set to Yes and setting output QUEUE TO PRINT ON, the mail message would show an error and not output. Resolution: ----------- MAGDSTA1 was modified to pass DIVISION to a queued job. VISTAIS-3393 - Legacy DICOM Gateway Install Process Needs Longer Problem: -------- Sometimes when installing MAG*3.0*333 LDGW not all the updated routines were being installed. During the installation, there is a hardcoded pause while the routines are being uploaded. The pause was set to 6 seconds which was not always enough time for the upload to complete. Resolution: ----------- Updated the PAUSE line in MAGDCM_update.scr install routine from 6 seconds to 20. VISTAIS-4140 - Improved C:\DICOM\DATA1 Deletion Technique Problem: -------- The init_dicom.bat file which is distributed with the DICOM Gateway is used to reinitialize the pointer files and delete the DICOM communication log files from the C:\DICOM\DATA1 folder. The batch file recursively deletes all subdirectories in the folder. The batch file must be run as administrator and if the batch file is not run from the C:\DICOM\DATA1 directory it will delete items from the C:\WINDOWS\SYSTEM32 directory rendering the operating system unusable. Resolution: ----------- A PowerShell script was added that can be run from a Windows Desktop shortcut that will delete the contents of the C:\DICOM\DATA1 folder. Show-menu.ps1 - C:\Program Files (x86)\VistA\Imaging VIMfunctions.ps1 - C:\Program Files (x86)\VistA\Imaging VI Maintenance.LNK - placed in C:\users\Public\Desktop VISTAIS-4144 - Automatic Handling of RPC Errors for Batch Export Problem: -------- If a batch export for Radiology, Consults or Lab encountered an RPC error, the batch export would terminate, and the remaining images would not transfer. The exports would have to be restarted at the point that it failed. Resolution: ----------- The code was updated to record the progress of an export making it possible to restart exports from the point of an RPC error. If a large export is being done overnight and VistA shuts down RPCs and then restarts them, the export will continue from the point of the interruption. VISTAIS-4148 - DICOM Gateways VistA Q/R Surrogates are not Division specific Problem: -------- When Study Tracker was released in MAG*3.0*231 the DICOM Gateway Surrogate for VistA Q/R Clients (2-14-1) could service requests for VistA for any division. This causes a problem at consolidated sites when a DICOM Gateway in one division was the surrogate for a VistA Q/R client request for another division. The retrieve request goes to the DICOM Gateway that the surrogate runs on, so gateway either cannot access the share or sends the images to the wrong compass for storage. Resolution: ----------- The DICOM Gateway VistA Q/R Surrogates can only service the VistA Q/R client requests for the same division. The DUZ(2) value of the VistA account running the VistA Q/R must be the same as the DUZ(2) value of the account that started the DICOM Gateway where the 2-14-1 Surrogate for VistA Q/R Client is running. VISTAIS-4153 - Correction of MAGDOUTP Piece-4 Counter Problem Problem: -------- Could not run the Display DICOM OBJECT EXPORT file entries option in VistA or 2-8-5 (Re)Initialize Image Transmission Queue option on the DICOM gateway. Entries in MAGDOUTP had a negative number in piece 4 of the zero node. ^MAGDOUTP(2006.574,0)="DICOM OBJECT EXPORT^2006.574^238178^-187643" The MAG DICOM GET NEXT QUEUE ENTRY RPC updates the image state (from XMIT to SUCCESS for example) was part of a bigger subroutine that removes old studies which are more than 15 days old. Occasionally the update of the image state caused the removal of an old study, even though it had been removed before. This caused the counter to be erroneously decremented. Resolution: ----------- The functions to update the images state and remove old studies are now in separate subroutines. VISTAIS-4159 - Problem with Terminated RPC Session Problem: -------- When starting the Modality Worklist Status (1_4) window, error, *** Error: WRITE+5^MAGM2VCU *** is displayed and forces an exit back to the menu. On the second attempt, the option will open/start as expected. Prior to P305, a new RPC session was made for every DICOM Gateway menu option. In P305 this was changed so that the existing RPC session was reused for the different menu options, however this created a problem when the RPC session was terminated while in the menu itself. Resolution: ----------- An automatic RPC Broker restart capability was added to the menu routine (^MAGDMENU) itself. Now before launching an option, the menu routine will check the RPC session and start a new one if necessary. An error message will be displayed if an RPC error occurs, a new RPC session will be established, and the selected menu option will be launched. Furthermore, the menu routine (^MAGDMENU) was modified so that when it is waiting for the user to select an option, it will periodically check the RPC Broker connection (once every 100 seconds) and restart it if necessary. INC23599225 - VISTAIS-4161 - Maintain Processing Lock When Error-Initiated Restart Occurs Problem: -------- The DICOM Gateway 1-1 Start Processing Text Messages from HIS and 2-3 Process DICOM Images processes are only allowed to run one instance at a time. After MAG*3.0*305 multiple 1-1 and 2-3 sessions could be started if the original session errored out. Resolution: ----------- Modified code to reestablish the menu option lock when the process is restarted. Test Sites: ----------- Denver VA Medical Center (Denver, CO) Topeka VA Medical Center (Topeka, KS) Test Sites - SNOW Change Order #: --------------------------------- Denver VA Medical Center (Denver, CO) T1-CHG679326 T2-CHG687534 Topeka VA Medical Center (Topeka, KS) T1-CHG0679491 T2-CHG0684915 Software and Documentation Retrieval Instructions: -------------------------------------------------- All patch files can be obtained from the SOFTWARE library by accessing the URL: https://download.vista.domain.ext/index.html/SOFTWARE. The software for this patch is being released using a host file. File Title File Name Format -------------------------------------------------------------------------- Kernel Installation and MAG3_0P333.KID ASCII Distribution System (KIDS) Build for MAG*3.0*333 Legacy DICOM Gateway MAG3_0P333_DICOM_Setup.exe Binary Installation File Documentation describing the new functionality is included in this release. Documentation can be found on the VA Software Documentation Library at: //www.domain.ext/vdl/. Documentation can also be obtained at https://download.vista.domain.ext/index.html/SOFTWARE Documentation Title File Name -------------------------------------------------------------------------- README file for MAG*3.0*.333 MAG3_0P333_README.PDF Patch Description for MAG*3.0*333 MAG3_0P333_PATCH_DESCRIPTION.PDF Deployment, Installation, Back-Out, MAG3_0P333_DIBRG.PDF and Rollback Guide VistA Imaging DICOM Gateway User MAG_DICOMUG.PDF Manual Patch Installation: ------------------- Pre/Post Installation Overview: ------------------------------- N/A Supported Versions: -------------------------- When MAG*3.0*333 is released, the list of supported versions of LDGW will change: LDGW (Server) Versions Supported: ---------------------------------------------- 3.0.333 3.0.350 3.0.319 LDGW (Server) Versions No Longer Supported: ------------------------------------------------------------ 3.0.305 3.0.274 3.0.257 Installation Instructions: -------------------------- Pre-Installation Instructions: ------------------------------- All released VistA Imaging patches must be installed on the VistA system before installing MAG*3.0*333. MAG*3.0*333 must be installed on the VistA System. This patch must be installed by the compliance date. All sites running VistA Imaging 3.0 must install the KIDS portion of this patch on the VistA System. This patch can be loaded while the VistA Imaging System is active, and users are on the system. Installing the MAG*3.0*333 KIDS takes 2-5 minutes. Note: The MAG*3.0*333 KIDS should be installed on VistA first and then the DICOM Gateway updated. KIDS 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_0P333.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*333). 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*333 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 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. If prompted 'Want KIDS to INHIBIT LOGONs during the install?,' answer NO. iii. If prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols?,' answer NO. Installing and Updating the LDGW: --------------------------------- For installing the DICOM Gateway, refer to Section 3, Installing the VistA Imaging DICOM Gateway in the VistA Imaging DICOM Gateway Installation Guide. NOTE: When uninstalling MAG*3.0*350, do NOT stop the IRIS service. Use these following steps to upgrade the software on an existing Legacy DICOM Gateway installation from a previous patch. 1. Log into the DICOM Gateway. 2. Back up the DICOM Dictionaries (the master file directory). The DICOM dictionary directory is usually on a shared network system and is used to hold DICOM master files. F:\DICOM is typically the DICOM dictionary directory. Note: The installation will not overwrite site-configurable master files. 3. Using a LDGW Terminal session, run option 4-2-1 Display Gateway Configuration Parameters. Review the general setup of the DICOM Gateway (number of text data directories, mapped drives for components such as dictionary files, and so on.) and record the location of these directories here: ⢠The local directory for images queued for processing IMAGE INPUT PATH=.................... ⢠The local directory for images that have been processed IMAGE OUTPUT PATH=.................. â¦â¦â¦â¦â The directory for data dictionaries DICT PATH=.......................... 4. Stop and close all active IRIS terminal windows on the LDGW. 5. Make a backup copy of the current LDGW database. C:\DICOM\IRIS\Iris.dat. (This can be done without stopping IRIS). 6. Copy the MAG3_0P333_DICOM_SETUP.EXE file to a local folder on the computer on which you will install the DICOM Gateway. 7. Go to the Control Panel, choose Uninstall a program, and remove the VistA DICOM Gateway (Patch 350). 8. When the message "Cannot delete file C:\DICOM\IRIS\iris.dat" is shown, click OK button to proceed with the uninstall. 9. Install the DICOM Gateway by following the steps in section 3.4.1 Installing the DICOM Gateway and 3.4.2 Installing IRIS for Health in the VistA Imaging DICOM Gateway Installation Guide. 10. Verify that security settings are correct. Refer to section 4 Securing the Gateway and IRIS in the VistA Imaging DICOM Gateway Installation Guide. 11. Verify DICOM Gateway Installation. Refer to section 5.3 Verify the DICOM Gateway Installation in the VistA Imaging DICOM Gateway Installation Guide. Post-Installation Instructions: ------------------------------- Routine MAGIP333 is an installation routine that is automatically deleted after the KIDS installation. ALL DICOM Gateways, including Legacy, Text and Routing, as well as HDIGs, need to be upgraded with the installation of MAG3_0P333_DICOM_Setup.exe at your earliest convenience. Refer to the VistA Imaging DICOM Gateway Installation Guide for details. Verify DICOM_INIT.BAT was removed 1. Navigate to the \DICOM\Data1 folder and verify that DICOM_INIT.BAT is removed, if not, delete the file. 2. Check any other \DICOM\Data folders for the DICOM_INIT.BAT is removed, if not, delete the file. Reinitialize the DICOM VistA Q/R Request Queue 1. In VistA, navigate to the Study Tracker Menu 2. Select Option: QDEL Delete the DICOM VISTA Q/R REQUEST QUEUE 3. At 'Do âDo you want to remove t' tyâ t"Y" âYâ and press 4. Verify entries have been removed The DICOM VISTA Q/R REQUEST QUEUE file has been truncated. Back-Out/Roll Back Plan: ------------------------ Please refer to the Deployment, Implementation, Back-Out and Rollback Guide (MAG3_0P333_DIBRG.PDF) for Server Installation instructions. Uninstalling the Application: ----------------------------- If it is necessary to uninstall the MAG*3.0*333 DICOM Gateway, use the Uninstall option from Programs and Features within Windows Control Panel to Uninstall the VistA Imaging DICOM Gateway. Then install the previous version of LEGACY DICOM Gateway. KIDS Uninstall: --------------- If it is necessary to uninstall the MAG*3.0*333 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 Installation Steps 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*333 backup message as shown below: * Backup of MAG*3.0*333 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. 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. Legacy DICOM Gateway (LDGW) Routine Information: ================================================ This section lists modified routines for the LDGW build. Routine Name: MAGDAUD1 Before: B21787487 After: B21934087 **10,11,333** Routine Name: MAGDDEL2 Before: B33576522 After: B20615911 **10,11,51,69,54,274,333** Routine Name: MAGDDR1 Before: B65150778 After: B60532808 **10,11,30,51,54,231,333** Routine Name: MAGDDR2 Before: B36802868 After: B44252372 **10,11,30,54,110,156,305,333** Routine Name: MAGDDR2A Before:B168859333 After:B169557353 **1,10,51,54,99,110,190,218, 231,305,333** Routine Name: MAGDDR3 Before: B79517273 After: B79475650 **1,10,51,50,110,190,231,274, 305,333** Routine Name: MAGDFCNS Before: B89968928 After: B98579195 **9,10,11,30,50,333** Routine Name: MAGDHRC Before: B96676069 After: B93391685 **11,30,51,49,123,110,138, 231,333** Routine Name: MAGDHRCP Before: B44418147 After: B45008527 **11,54,49,110,183,333** Routine Name: MAGDIR6 Before: B95113006 After: B89268673 **11,30,51,54,53,49,138,166, 231,333** Routine Name: MAGDIWB0 Before: B21322194 After: B27535093 **11,51,305,333** Routine Name: MAGDIWB1 Before:B187718620 After:B187709487 **11,30,51,50,54,138,156,190, 305,333** Routine Name: MAGDIWB2 Before:B107127730 After:B114565017 **11,30,51,50,54,99,110,138, 305,333** Routine Name: MAGDIWB4 Before:B107735367 After:B119041040 **305,333** Routine Name: MAGDIWBA Before:B113456242 After:B137246470 **30,50,54,305,333** Routine Name: MAGDIWBE Before: B94799901 After: B100500941 **305,333** Routine Name: MAGDBIWBF Before: 80407293 After: B97092381 **305,333** Routine Name: MAGDIWBH Before: B28701977 After: B33570433 **305,333** Routine Name: MAGDIWBJ Before:B231203377 After:B171149173 **305,333** Routine Name: MAGDIWBM Before: B21985495 After: B27268079 **305,333** Routine Name: MAGDIWBN Before: n/a After:B171409078 **333** Routine Name: MAGDIWBP Before: n/a After: B20018334 **333** Routine Name: MAGDIWDG Before: B8522275 After: B8737856 **110,305,333** Routine Name: MAGDMENA Before: B56295725 After: B59202626 **9,21,10,11,30,69,54,110, 305,333** Routine Name: MAGDMENO Before: B58925350 After: B60009932 **11,30,51,50,69,54,53,118, 110,231,305,319,350,333** Routine Name: MAGDMENU Before: B79859663 After: B79497068 **9,21,11,30,51,69,54,53,118, 110, 231,305,319,333** Routine Name: MAGDMLOG Before: B32785216 After: B33527327 **9,10,30,51,54,110,333** Routine Name: MAGDSTQ8 Before: B36279345 After: B41372450 **231,333** Routine Name: MAGDSTR2 Before:B200352080 After:B200370079 **231,305,333** Routine Name: MAGDSTRT Before: B56444115 After: B65730158 **21,11,30,51,69,54,305,333** Routine Name: MAGDVRSN Before: B21494340 After: B63031763 **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,274,305,319,333** Routine Name: MAGM2VC Before: B59848201 After: B64359772 **11,30,51,69,103,54,110,333** Routine Name: MAGOSDIR Before: B21221028 After: B22324468 **10,51,69,162,166,231,333** Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;IMAGING;**[Patch List]**;Mar 19, 2002;Build 2 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: MAGBRTE4 Before: B76402670 After: B74330617 **11,30,51,85,54,39,156,196,333** Routine Name: MAGDFCNV Before: B20613077 After: B64117589 **11,51,141,138,231,333** Routine Name: MAGDHOW4 Before: B34588912 After: B32845780 **138,208,333** Routine Name: MAGDRPC4 Before:B163913734 After:B173706658 **11,30,51,50,54,49,138,156, 180,305,333** Routine Name: MAGDRPCE Before: B42732687 After: B40916332 **305,333** Routine Name: MAGDSTA0 Before: n/a After: B23232412 **333** Routine Name: MAGDSTA1 Before:B169506557 After:B167043273 **231,306,305,333** Routine Name: MAGDSTA2 Before: B85486784 After:B124908020 **231,333** Routine Name: MAGDSTA5 Before: B25524370 After: B27915125 **231,305,333** Routine Name: MAGDSTA7 Before: B46290220 After: B46973414 **231,305,333** Routine Name: MAGDSTA8 Before:B156327044 After:B153842563 **231,305,333** Routine Name: MAGDSTA9 Before: B26490456 After: B27102159 **231,306,333** Routine Name: MAGDSTAA Before: B98491722 After:B121857916 **231,306,305,333** Routine Name: MAGDSTAG Before: n/a After: B19613551 **333** Routine Name: MAGDSTAS Before:B136206196 After:B138461889 **231,306,305,333** Routine Name: MAGDSTAX Before: n/a After: B19962373 **333** Routine Name: MAGDSTQ8 Before: B36279345 After: B39540551 **231,333** Routine Name: MAGDSTQ9 Before: B10301034 After: B9380247 **231,305,333** Routine Name: MAGDSTV1 Before: B43298920 After: B50964023 **231,305,333** Routine Name: MAGDSTV2 Before: B25168899 After: B27402791 **231,333** Routine Name: MAGIP333 Before: n/a After: B7254475 **333** Routine list of preceding patches: 196, 208, 305 ============================================================================= User Information: Entered By : Date Entered : APR 04, 2022 Completed By: Date Completed: FEB 03, 2026 Released By : Date Released : FEB 04, 2026 ============================================================================= Packman Mail Message: ===================== No routines included