$TXT Created by HEV.MYHEALTH.DOMAIN.EXT (KIDS) on Wednesday, 07/19/17 at 11:42 ============================================================================= Run Date: SEP 21, 2017 Designation: MHV*1*29 Package : MHV - MYHEALTHEVET Priority: EMERGENCY Version : 1 SEQ #26 Status: Released Compliance Date: SEP 28, 2017 ============================================================================= Associated patches: (v)DI*22.2*0 <<= must be installed BEFORE `MHV*1*29' (v)MHV*1*24 <<= must be installed BEFORE `MHV*1*29' Subject: EMERGENCY MHV*1*29-FIX USER NAME AND ENHANCE SM USER QUERY Category: - Routine - Informational Description: ============ ************************************************************************ Please note the short install compliance date of Thursday, Sept 28, 2017 for this Emergency Patch. ************************************************************************ * MyHealtheVet patch MHV*1*29, must be installed no later than * Thursday, Sept 28, 2017, because it is a dependency for the * release of the Secure Messaging Web Portal functionality that * will be pushed to sites the evening of Saturday Sept 30th, 2017. ************************************************************************ Secure Messaging (SM) allows patients and clinicians to email each other securely and confidentially, and allows clinicians to post those email threads to the medical record as progress notes. Relationships between patients and clinicians are established based on Primary Care Management Module (PCMM) providers, clinic appointments and Order Entry/Results Reporting (OE/RR) teams. Secure Messaging uses triage groups based on these relationships to manage which patients are able to email which providers. More information on Secure Messaging can be found on the MyHealtheVet (MHV) product web site (intranet) http://vaww1.domain.ext/MYHEALTHEVET/ and MHV web site www.myhealth.domain.ext. Summary ------- This patch addresses the critical issue related to retrieving User Name Components containing special characters (space, apostrophe, single quote and dash/hyphen), and enhances the query response to retrieve additional SM User data fields values from VistA. This has an impact for the SM Providers with special characters in their name. They are prevented from logging into SM and cannot save to CPRS the communication with their patients on an SM Message thread, causing a "Name Mismatch" error. The additional User profile attributes retrieved from VistA will provide enhanced capability for the SM Admin to match the correct provider identity when activating a new SM User, and provide the information needed when debugging Workload Credit and PCMM issues. My HealtheVet (MHV) Emergency VistA Patch (MHV*1.0*29) will address the following: 1. JAZZ 386781:Defect (Prod): Space / Special characters in Clinician's last name or first name in VistA New Person File preventing SM Clinician login. 2. JAZZ 390964:Defect: SM - Messages for users with a blank in first name cannot be saved to CPRS. 3. JAZZ 409966:Story: SM - VistA Patch MHV*1*29 - ENHANCE SM USER QUERY: Add Middle name and other identified attributes (Suffix, Prefix, Title, Phone Number, DISUSER flag, PROVIDER Class, Person Class, Divisions, Service/Section, Specialty, Requires Cosigner flag). Additional Integration Agreement (ICR) MHV package subscribed to: ICR#2533 to extract PROVIDER DIVISIONS. 4. JAZZ 504782:Defect: SM VistA Patch 29- PCMM Flag field displaying incorrect value for the user in SM Admin Portal. 5. JAZZ 550050:Defect: VistA - SM WLC Encounter Filed Triggers CPRS Action Required for Combat Veteran Test Sites: ---------- Cincinnati VA Medical Center - 539 VA Portland Health Care System - 648 Software and Documentation Retrieval Instructions: ---------------------------------------------------- The software for this patch is distributed as KIDS build MHV*1.0*29 via PackMan message. The My HealtheVet documentation describing the new WLC user functionality is available: Secure Messaging User Guide: https://www.myhealth.domain.ext/mhv-portal-web/ShowBinary/BEA%20Repository/pdf /SMUserGuide.pdf The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Hines: domain.ext Salt Lake City: domain.ext Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ Patch Installation: =================== Installation Instructions Overview ---------------------------------- 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. The patch is distributed in KIDS format in a PackMan message. This patch requires MHV*1*24 and VA FileMan 22.2 and installation time is less than 5 minutes. Installation Instructions: 1. LOAD TRANSPORT GLOBAL --------------------- Choose the PackMan message containing this patch and invoke the INSTALL/CHECK MESSAGE PackMan option. 2. START UP KIDS ------------- From the Kernel Installation & Distribution System menu, select the Installation menu 3. Select Installation Option: --------------------------- NOTE: The following are OPTIONAL however it is strongly recommended to be used when installing the MHV*1.0*29 patch - (When prompted for the INSTALL NAME, enter MHV*1.0*29): a. Verify Checksums in Transport Global - This option (#2) will allow you to ensure the integrity of the routines that are in the transport global. b. Compare Transport Global to Current System - This option (#4) will allow you to view all changes that will be made when this patch is installed. It compares all components of this patch (routines, DD's, templates, etc.). c. Backup a Transport Global - This option (#5) will create a backup message of any routines exported with this patch. It will not backup any other changes such as DD's or templates. <<<--This option it is strongly recommended to be used when installing the MHV*1.0*29 patch-->>> 4. Select Installation Option: Install Package(s) ---------------------------------------------- Use the Install Package(s) option and select the package MHV*1.0*29. 5. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO //' respond NO. 6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO //' respond NO. 7. When prompted 'Enter options you wish to mark as 'Out Of Order':' press 8. When prompted 'Enter protocols you wish to mark as 'Out Of Order':' press . Patch Backout Instructions ========================== 1. Go to MailMan menu, choose option Read/Manage Messages and select the backup message that was creating during Installation step 3.c - Backup 2. When prompted 'Type to continue or '^' to exit:' type '^' and then 3. When prompted 'Enter message action (in MHV basket):' type 'Xtract PackMan' and then 4. The following message and the prompt will display: 'Warning: Installing this message will cause a permanent update of globals and routines. Do you really want to do this? NO//' type 'YES' and then 5. When prompted: 'Shall I preserve the routines on disk in a separate back-up message? YES//' type 'NO' and then 6. The system will display the following message confirming that all the routines in the build have been restored to the prior version (unloaded): 'No backup message built. Line 2 Message #147238 Unloading Routine MHV7B1M (PACKMAN_BACKUP) Line 57 Message #147238 Unloading Routine MHV7B9A (PACKMAN_BACKUP) Line 316 Message #147238 Unloading Routine MHV7BU (PACKMAN_BACKUP) Line 500 Message #147238 Unloading Routine MHVUMRPC (PACKMAN_BACKUP) Line 709 Message #147238 Unloading Routine MHVXPRV (PACKMAN_BACKUP) Line 800 Message #147238 Unloading Routine MHVXUSR (PACKMAN_BACKUP) Select PackMan function: and then ' 7. Verify that all six routines are listed as above have been backed out: No backup message built. Routine Information: ==================== The second line of each of these routines now looks like: ;;1.0;My HealtheVet;**[Patch List]**;July 10, 2017;Build 73 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: MHV7B1M Before: B5731809 After: B6609616 **11,29** Routine Name: MHV7B9A Before: B32497735 After: B54975976 **6,10,29** Routine Name: MHV7BU Before: B16434586 After: B23281675 **2,29** Routine Name: MHVUMRPC Before: B53770789 After: B58872124 **11,22,24,29** Routine Name: MHVXPRV Before: B8040639 After: B8530469 **6,29** Routine Name: MHVXUSR Before: B6533332 After: B33090883 **6,29** Routine list of preceding patches: 2, 10, 24 ============================================================================= User Information: Entered By : Date Entered : DEC 02, 2016 Completed By: Date Completed: SEP 21, 2017 Released By : Date Released : SEP 21, 2017 ============================================================================= Packman Mail Message: ===================== $END TXT