$TXT Created by DAVIS,PAULETTE T at DEVCRN.FO-ALBANY.MED.VA.GOV (KIDS) on Friday, 04/09/10 at 08:43 ============================================================================= Run Date: AUG 17, 2010 Designation: RG*1*57 Package : RG - CLINICAL INFO RESOURCE NETWORK Priority: Mandatory Version : 1 SEQ #56 Status: Released Compliance Date: SEP 17, 2010 ============================================================================= Associated patches: (v)RG*1*52 <<= must be installed BEFORE `RG*1*57' (v)RG*1*54 <<= must be installed BEFORE `RG*1*57' Subject: REMOVE POTENTIAL MATCHES RETURNED EXCEPTION REFERENCES Category: - Routine Description: ============ NOTE: RG* and MPIF* patches should NOT be installed on legacy systems to avoid issues with the legacy systems ending up as Treating Facilities. RG*1.0*52 and RG*1.0*54 are required builds for patch RG*1*57. The Potential Matches Returned (218) exceptions in the VistA MPI/PD Exception Handling [RG EXCEPTION HANDLING] option are obsolete. As of VistA patch MPIF*1*52, the logging of Potential Matches Returned exceptions was removed from the VistA HL7 message processor routines. Although the exceptions no longer occur, some references remained that will be cleaned up in this patch. Issue #1: Upon log in, members of the RG CIRN DEMOGRAPHIC ISSUES Mail Group see a notification regarding exceptions to process. Previously, two different notifications existed. Since only one exception type (234 - Primary View Reject) remains in the MPI/PD Exception Handling [RG EXCEPTION HANDLING] option, only one notification is needed. This was reported in Remedy Ticket HD0000000383093. Issue #2: In the MPI/PD Exception Handling [RG EXCEPTION HANDLING] option, after choosing an exception, "PMR Potential Match Rev" was displayed as one of the selectable actions at the bottom of the screen. This action item has been removed. Issue #3: Post-init routine, RGP57PST, will examine the NOT PROCESSED exceptions listed under the MPI/PD Exception Handling [RG EXCEPTION HANDLING] option. If there are any NOT PROCESSED exceptions for exception type Potential Matches Returned (218), they will be marked as PROCESSED, since this type is obsolete. Some code references to the Potential Matches Returned (218) exception type are not obvious to the user, as they are involved in behind-the-scenes processing. Those references have also been cleaned up. The Potential Matches Returned (218) entry in the CIRN HL7 EXCEPTION TYPE (#991.11) file remains, but is no longer used. Issue #4: Remedy Ticket HD0000000224941 reported the following problem. After selecting an exception in the VistA MPI/PD Exception Handling [RG EXCEPTION HANDLING] option, and choosing the UPD Update to Processed action item, the user observed an unexpected result when taking the default answer to the prompt, "Are you sure you want to change the status? YES//". After answering YES, the user saw "??" (two question marks) displayed, which caused questions about whether or not the answer was processed correctly. The next screen of the VistA MPI/PD Exception Handling [RG EXCEPTION HANDLING] option indicated that the exception was processed. However, upon further investigation, it was found that the WHO MARKED PROCESSED (#8) field in the EXCEPTION (#2) multiple of the CIRN HL7 EXCEPTION LOG (#991.1) file was not updated with the user name. When the above sequence of actions is taken, the code should store the DUZ (internal entry number) of the user into the WHO MARKED PROCESS (#8) field. If by chance, the user has a 4 digit DUZ and there are other users on the system who have those same 4 digits as the last four digits of their Social Security Numbers, then FileMan's lookup by cross-reference does not know which entry to file into the field. This issue has been corrected in routine RGEX03. Because enhancements are being made to the MPI/PD Exception Handling [RG EXCEPTION HANDLING] option, ALL of the related protocols are included in the build to ensure that this List Manager application exports correctly. Documentation Update: ===================== The following MASTER PATIENT INDEX/PATIENT DEMOGRAPHICS (MPI/PD) VISTA documentation is available, updated for patch RG*1.0*57. Facilities should download the revised documentation listed as follows: Exception Handling RG1_0_P57EH.PDF User Manual RG1_0_P57UM.PDF The preferred retrieval method is to FTP from the ANONYMOUS.SOFTWARE directory at: DOWNLOAD.VISTA.MED.VA.GOV This transmits the file from the first available FTP server. Sites may also elect to retrieve software directly from one of the following servers. OI Field Office FTP Address Directory ------------------------------------------------------------------ Albany ftp.fo-albany.med.va.gov ANONYMOUS.SOFTWARE Hines ftp.fo-hines.med.va.gov ANONYMOUS.SOFTWARE Salt Lake City ftp.fo-slc.med.va.gov ANONYMOUS.SOFTWARE Note: These files must be transferred in binary or IMAGE, not ASCII, mode. The documents can also be downloaded from the VistA Documentation Library (VDL) Web page in both Acrobat PDF and MS-Word DOC formats: http://www.va.gov/vdl/application.asp?appid=16 Associated Remedy Ticket(s): ============================ HD0000000383093 - Sign On Message HD0000000224941 - Are you sure you want to change the status? YES//YES?? Associated New Service Request (NSR): ===================================== There is no associated NSR with the patch. Test Sites: =========== Louisville, KY Oklahoma City, OK Puget Sound HCS Post-Install Routine: ===================== The logging of Potential Matches Returned (218) exceptions was removed from the VistA HL7 message processor routines in VistA patch MPIF*1*52 which was released on Nov 30, 2009. Any Potential Matches Returned exceptions remaining in the CIRN HL7 EXCEPTION LOG (#991.1) file will be marked as processed by post-init routine RGP57PST. Routine RGP57PST will be automatically deleted from your system after successful installation of the patch. Installation Instructions: ========================== This patch takes less than 5 minutes to install. This patch should be loaded during non-peak hours to minimize disruption to the users. 1. Users are allowed on the system during patch installation. 2. The HL7 incoming filers should be stopped. Use the Monitor, Start, Stop Filers [HL FILER MONITOR] option on the Filer and Link Management Options [HL MENU FILER LINK MGT] menu on the HL7 Main Menu [HL MAIN MENU]. 3. Use the INSTALL/CHECK MESSAGE option on the PackMan menu. Note: TEXT PRINT/DISPLAY option in the PackMan menu will display the patch text only. 4. From the Kernel Installation and Distribution System Menu, select the Installation menu. 5. From this menu, you may elect to use the following options: (a) Backup a Transport Global. (b) Compare Transport Global to Current System. (c) Verify Checksums in Transport Global. (d) Print Transport Global. 6. Use the Install Package(s) option and select the package RG*1.0*57. 7. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//', respond NO 8. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', respond NO. 9. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//', respond YES. The following OPTIONS should be disabled during the installation. MPI/PD Master Menu [RGMGR] MPI/PD Exception Handling [RG EXCEPTION HANDLING] MPI/PD Exception Purge [RG EXCEPTION PURGE] 10. After patch installation has completed, restart the HL7 incoming filers. Use the Monitor, Start, Stop Filers [HL FILER MONITOR] option on the Filer and Link Management Options [HL MENU FILER LINK MGT] menu on the HL7 Main Menu [HL MAIN MENU]. 11. The RGP57PST routine is automatically deleted from your system after successful installation of the patch. Routine Information: ==================== The second line of each of these routines now looks like: ;;1.0;CLINICAL INFO RESOURCE NETWORK;**[Patch List]**;30 Apr 99;Build 2 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: RGEX01 Before: B26588821 After: B22714339 **3,12,19,23,43,45,47,48,52,57** Routine Name: RGEX03 Before: B81303188 After: B81177461 **3,12,19,23,27,30,38,39,43, 44,48,54,57** Routine Name: RGEXHND1 Before: B37317689 After: B37400054 **3,12,19,23,43,45,52,57** Routine Name: RGHLLOG Before: B23997530 After: B24264633 **1,3,11,13,18,19,25,45,52,57** Routine Name: RGMTETOT Before: B27906188 After: B13022179 **20,30,43,45,52,57** Routine Name: RGP57PST Before: n/a After: B5113070 **57** Routine Name: RGRSUTIL Before: B14283785 After: B11788298 **1,3,19,45,57** Routine Name: RGSYSTAT Before: B9080377 After: B9266591 **16,19,23,25,20,43,45,52,57** Routine list of preceding patches: 52, 54 ============================================================================= User Information: Hold Date : AUG 08, 2010 Entered By : CHESNEY,CHRISTINE M Date Entered : JAN 05, 2010 Completed By: ALDERMAN,MATT S Date Completed: JUL 21, 2010 Released By : HEUER,CINDY Date Released : AUG 17, 2010 ============================================================================= Packman Mail Message: ===================== $END TXT