$TXT Created by DESMOND,LINDA at MNTVMM.FO-ALBANY.MED.VA.GOV (KIDS) on Tuesday, 01/18/05 at 16:59 ============================================================================= Run Date: JAN 20, 2005 Designation: DG*5.3*626 Package : DG - REGISTRATION Priority: Mandatory Version : 5.3 SEQ #553 Status: Released Compliance Date: FEB 20, 2005 ============================================================================= Associated patches: (v)DG*5.3*451 <<= must be installed BEFORE `DG*5.3*626' (v)DG*5.3*603 <<= must be installed BEFORE `DG*5.3*626' Subject: COMBAT OVERLAP FIX Category: - Routine Description: ============ 1. Based on a business decision by the Central Business office, the Combat and Conflict fields on Registration screen 6 should not allow overlapping dates to be entered. Although the HVE Phase II patch prevented the entry of an overlapping conflict when it overlapped with an already defined period of Combat, it did not prevent users from entering the Conflict information first, and then entering the overlapping period of Combat. This patch will resolve this issue, by checking for overlapping date ranges on the Combat fields, as well as the Conflict fields. 2. Another reported issue had to do with Conflict From and To Dates not being checked appropriately. This issue allows a user to enter a To date before a From Date, and/or disallows the entry of a valid date when the software thought it was outside the range of the conflict. This issue is being resolved with this patch. 3. The third issue being resolved with this patch, involves the Combat Location field. If a user enters information for one patient using the combat fields, and then immediately edits data on another patient's combat from/to dates (without entering a new Combat Location), then the previous patient's combat location is used to determine the appropriate date range for the combat period. This issue has been resolved with a modification to the ^DGRPE and ^DGRPCE routines. 4. The fourth is based on a business decision by the Central Business Office that the Combat From and To fields can now equal (i.e., be the same date). In addition, the Conflict To date may be equivalent to the Combat From date or another Conflict From date without causing an inconsistency. 5. Sites that did not clean up the combat and/or conflict dates to reflect at a minimum of a month and a year were unable to update the imprecise "year-only" date. This fifth issue is being resolved by allowing a user to change an imprecise date to a more precise date of either a month/year or day/month/year. This patch addresses the following E3R(s): ------------------------------------------ There are no E3Rs associated with this patch. This patch addresses the following NOIS message(s): --------------------------------------------------- FNC-0904-31074 HVE PHASE II - MSE Inconsistencies MWV-0904-21191 HVE PHASE II - Screen 6 issues BEC-0904-21350 HVE PHASE II - Screen #6 issues ALT-0904-21361 HVE PHASE II - Screen 6 Issues FAV-0904-71485 HVE PHASE II NHM-0904-11706 HVE PHASE II - MSE Inconsistencies BAC-0904-41710 HVE PHASE II - Screen 6 issues MON-0904-51777 HVE PHASE II - MSE Inconsistencies MAD-0904-41587 HVE PHASE II - MSE Inconsistencies CPH-1004-40203 HVE PHASE II - Combat Dates. ================INSTALLATION INSTRUCTIONS ================= This patch can be loaded with users on the system. Install Time - 1 minute 1. LOAD TRANSPORT GLOBAL --------------------- Choose the PackMan message containing this patch and invoke the INSTALL/CHECK MESSAGE PackMan option. 2. DISABLE ROUTINE MAPPING (DSM for Open VMS sites only) ----------------------- Disable routine mapping on all systems for the routines listed in step 3 below. NOTE: If the routines included in this patch are not currently in your mapped routine set, please skip this step. 3. COMPONENTS SENT WITH PATCH ------------------------ The following is a list of the routines included in this patch. The second line of each of these routines now looks like: ;;5.3;Registration;**[patch list]**;Aug 13, 1993 CHECK^XTSUMBLD results Routine name Before Patch After Patch Patch List ============ ============ =========== ========== DGRPCE 11721106 11614281 121,122,175,297,342 451,626 DGRPDT 13945001 15682627 562,603,626 DGRPE 26703993 26743702 32,114,139,169,175 247,190,343,397,342 454,415,489,506,244 547,522,528,555,508 451,626 DGRPMS 9056450 9466001 451,626 4. START UP KIDS ------------- Start up the Kernel Installation and Distribution System Menu [XPD MAIN]: Edits and Distribution ... Utilities ... Installation ... Select Kernel Installation & Distribution System Option: INStallation --- Load a Distribution Print Transport Global Compare Transport Global to Current System Verify Checksums in Transport Global Install Package(s) Restart Install of Package(s) Unload a Distribution Backup a Transport Global Select Installation Option: 5. Select Installation Option: -------------------------- NOTE: The following are OPTIONAL - (When prompted for the INSTALL NAME, enter DG*5.3*626): a. Backup a Transport Global - This option 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. b. 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 (routines, DD's, templates, etc.). c. Verify Checksums in Transport Global - This option will allow you to ensure the integrity of the routines that are in the transport global. 6. Select Installation Option: Install Package(s) ---------------- **This is the step to start the installation of this KIDS patch: a. Choose the Install Package(s) option to start the patch install. b. When prompted 'Want KIDS to INHIBIT LOGONs during the install? YES//' answer NO (unless otherwise indicated) c. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//' answer NO (unless otherwise indicated) 7. REBUILD MAPPED ROUTINE(S) (DSM for Open VMS sites only) ------------------------- Optional - Include the routines distributed with this patch in the mapped routine set. NOTE: This step is only necessary if you performed step 2 or if you wish to include the routines in your mapped set. Routine Information: ==================== Routine Name: - DGRPDT Routine Checksum: Routine Name: - DGRPMS Routine Checksum: Routine Name: - DGRPCE Routine Checksum: Routine Name: - DGRPE Routine Checksum: ============================================================================= User Information: Entered By : MORGAN,BRIAN Date Entered : OCT 04, 2004 Completed By: DESMOND,LINDA Date Completed: JAN 19, 2005 Released By : GROOMS,ANTHONY E Date Released : JAN 20, 2005 ============================================================================= Packman Mail Message: ===================== $END TXT