============================================================================= Run Date: FEB 19, 2021 Designation: MAG*3*256 Package : MAG - IMAGING Priority: Mandatory Version : 3 SEQ #198 Status: Released Compliance Date: MAR 19, 2021 ============================================================================= Subject: Clinical Display Defect Fix Category: - Routine Description: ============ MAG*3.0*256, a patch that provides fixes to the VistA Imaging Clinical Display. This patch addresses the following issues: INC5914206 - Clinical Display not displaying MUSE study type EVR INC8579324 - Unable to copy images from VistA Imaging Display INC9031004 - OS Version for file 2006.81 and 2006.82 not showing in Windows 10. INC5809011 - BSE LOGIN ERROR The VistA error trap has many "BSE LOGIN ERROR" for about two weeks now. Reference discussion on related ServiceNow ticket. 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: Defect 1082742 (Trouble Ticket INC5914206) - Clinical Display not displaying MUSE study type EVR Problem -------- Clinical Display MUSE viewer message log shows Format ID = 1 Resolution ----------- Instructed the reporting site to set up their MUSE system with the correct information to allow the Vista Display application to use Format Type Name (Abbreviation) to cross reference the correct Report ID number. Issue resolved when the site made this change. Second condition: If the MUSE system has a default Format type of "General," this will cause a no match condition setting the Format ID = 1. This condition is resolved in Code to display a valid Format ID. Defect 1194687 (Trouble Ticket #INC8579324) Salt Lake City - Unable to copy images from VistA Imaging Display Problem: -------- While testing MAG*3.0*225, the test team discovered they cannot copy images from VistA Imaging to a new directory assigned by the patch. Attempts to do so result in an Access Denied message. Note: MAG*3.0*225 successfully creates a new local directory as designed. The 'Copy Image (before delete) for Re-Association in Clinical Display' creates the ReAssociate folder under >\My Documents\> when Clinical Display is launched. Resolution: ----------- Created a "CopyTheFile" routine that works like the private one used elsewhere in the system (Display, Capture, and BP processor). The new routine logs in using the "2006.1" file's "Net Username" and "Net Password" variables (which is a privileged account such as the IU Account or the IA Account). This network user account has permissions to source and destination folders that the logged-in user may not have. Defect 1208495 (INC9031004) - OS Version for file 2006.81 and 2006.82 is not showing Windows 10 (6.3) Problem: -------- The entry is updated with every session for Imaging Capture and Display. The only OS versions showing are 6.1 (Windows 7) and 6.2 (Windows 8, which VA never used). The Windows 10 PCs are having entries stored as 6.2. Gary Egli researched this and reported the following in an email: "I have identified a number of places where the check for Windows 10 is not being done. The Windows 10 check will have to be added to the OS checks and we will also have to verify the correct information is being passed to the RPC writing the OS version to files 2006.81 and 2006.82." Priority: 8, Nuisance Problem, Workaround (looking at 6.2 as if it is Windows 10). Resolution: ----------- A code change has been made to use the latest Windows API to return the valid OS system name. Thus Windows 10 will be logged as Windows 10.0. If the MS OS System is upgraded in the future, the correct definition will be displayed in the logs. Defect 1078472 (INC5809011) - BSE LOGIN ERROR Problem: -------- The XUCODE variable contains what the kernel BSE code receives from the application using the BSE token. The format expected is: "Calling application^BSE token^calling site^calling site's RPC broker port". In this case, for release of information requests, the broker port was being incorrectly set to "0". VistA can't login with a "0" port number, which is considered invalid. Resolution: ----------- For the Release of Information print form, in the FormCreate method, we added the SetLocalBrokerPort call and pass in the VistaPort parameter. We do this right after the creation of the ROIRestUtlity object. This is being done correctly elsewhere throughout Display for all other Release of Information forms, but it had been missed for this particular form. Test Sites: ----------- VA Eastern Colorado Health Care System (Denver, CO) San Diego VA Medical Center (San Diego, CA) 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_0P256.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_0P256.KID Distribution System (KIDS) build for MAG*3.0*256 VistA Imaging Clinical Display MAG3_0P256_Clinical_Display_Setup.exe client installation file - New VistA Imaging Clinical MAG3_0P256_Clinical_Display_Install.msi Display push installation file Documentation Title File Name --------------------------------------------------------------------- Patch Description for MAG*3.0*256 MAG3_0P256_Patch_Description.pdf Deployment, Installation, Back-Out, MAG3_0P256_DIBORG.pdf and Rollback Guide MAG*3.0*256 Clinical Display MAG3_0P_256_CLINICAL_DISPLAY_README.txt README Patch Installation: ------------------- Supported Client Versions: When MAG*3.0*256 is released, the list of supported versions of Clinical Display will change: Client Versions Supported: 3.0.256 3.0.225 3.0.234 Client Versions No Longer Supported: 3.0.216 3.0.188 3.0.191 3.0.181 3.0.167 3.0.161 Pre/Post Installation Overview: MAG*3.0*256 must be installed on the VistA System on which the VistA Imaging Applications will be used. This patch must be installed by the compliance date. This patch should take less than five minutes to install. Note: All released VistA Imaging patches must be installed on the VistA system before installing MAG*3.0*256. 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_0P256.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. 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 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. VistA Imaging Clinical Display Client Installation Instructions Note: The Clinical Display Application is only supported on Windows 10 operating systems. Other operating systems are not officially supported. Clinical Display is distributed as an MSI and EXE installation. The MSI is intended for sites that want to do a push installation (using SCCM or another tool). The EXE is intended for use to install on a single workstation. The MAG3_0P256_Clinical_Display_Setup.exe file can be installed manually on workstations as described in the Single Workstation Installation section in the VistA Imaging System Installation Guide. Post-Installation Instructions: N/A Back-Out/Roll Back Plan: ------------------------ Uninstalling the Application: If it is necessary to uninstall the MAG*3.0*256 client, use the Uninstall option from Programs and Features within Windows Control Panel to Uninstall: VistA Imaging Clinical Display. Then install the previous version of Clinical Display which was included in MAG*3.0*225. KIDS Uninstall: If it is necessary to uninstall the MAG*3.0*256 VistA KIDS, then select the Kernel Installation & Distribution System menu option, Backup a Transport Global, see the Installation Steps section where step 4c 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. Select the message shown below: Backup of MAG*3.0*256 install on Select the Xtract PackMan option. Select the Install/Check Message option. Enter Yes at the prompt. Enter No at the backup prompt. There is no need to back up the backup. Enter message action (in IN basket): Ignore// Xtract PackMan Select PackMan function: ? Answer with PackMan function NUMBER, or NAME Choose from: 1 ROUTINE LOAD 2 GLOBAL LOAD 3 PACKAGE LOAD 4 SUMMARIZE MESSAGE 5 PRINT MESSAGE 6 INSTALL/CHECK MESSAGE 7 INSTALL SELECTED ROUTINE(S) 8 TEXT PRINT/DISPLAY 9 COMPARE MESSAGE Select PackMan function: Select PackMan function: 6 INSTALL/CHECK MESSAGE Warning: Installing this message will cause a permanent update of globals and routines. Do you really want to do this? NO// YES Routines are the only parts that are backed up. NO other parts are backed up, not even globals. You may use the Summarize Message option of PackMan to see what parts the message contains. Those parts that are not routines should be backed up separately if they need to be preserved. Shall I preserve the routines on disk in a separate back-up message? YES// NO No backup message built. Line 2 Message #43934 Unloading Routine MAGXXXX (PACKMAN_BACKUP) Select PackMan function: Routine Information: This section lists modified routines for the VistA KIDS build. For each routine, the second line will contain the following information: ;;3.0;IMAGING;**[Patch List]**; Mar 19, 2002;Build 1;Feb 15, 2017 CHECK1^XTSUMBLD is used to generate the checksums. Routine Checksums Routine Checksum Checksum Patch List Before After MAGGTU4D 4954163 4951761 **93,94,106,117,122,131,149, 138,156,161,167,181,191,188, 216,234,225,256** MAGIP256 New 4110431 **256** Routine MAGIP256 is an installation routine automatically deleted after the KIDS installation. Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;IMAGING;**[Patch List]**;Mar 19, 2002;Build 9 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: MAGGTU4D Before: B4954163 After: B4951761 **93,94,106,117,122,131,149, 138,156,161,167,181,191,188, 216,234,225,256** Routine Name: MAGIP256 Before: n/a After: B4110431 **256** Routine list of preceding patches: 225 ============================================================================= User Information: Entered By : Date Entered : JAN 28, 2020 Completed By: JR Date Completed: FEB 17, 2021 Released By : Date Released : FEB 19, 2021 ============================================================================= Packman Mail Message: ===================== No routines included