$TXT Created by MCCORMACK,JOHN at FS.FO-ALBANY.MED.VA.GOV (KIDS) on Monday, 07/17/06 at 17:31 ============================================================================= Run Date: SEP 11, 2006 Designation: LR*5.2*329 Package : LR - LAB SERVICE Priority: Mandatory Version : 5.2 SEQ #277 Status: Released Compliance Date: OCT 12, 2006 ============================================================================= Associated patches: (v)LR*5.2*121 <<= must be installed BEFORE `LR*5.2*329' (v)LR*5.2*295 <<= must be installed BEFORE `LR*5.2*329' Subject: CLEANUP PURGED ACCESSION'S UID Category: - Routine Description: ============ EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*329 does not contain any changes to the VISTA BLOOD BANK Software as defined by VHA DIRECTIVE 2004-058 titled VISTA BLOOD BANK SOFTWARE VERSION 5.2. EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*329 does not alter or modify any software design safeguards or safety critical elements functions. RISK ANALYSIS: Changes made by patch LR*5.2*329 have no effect on Blood Bank software functionality, therefore RISK is none. 1. Remedy ticket HD0000000088913 reported the Laboratory software was creating Laboratory Unique Identifiers (UID) which used the prefix '00' instead of the site's two character identifier assigned to each accession area. This situation exists when the UIDs from old previously purged accessions are still in the "C" cross-reference of the ACCESSION file (#68), many from when the UID was first implemented in 1995. One of the checks performed during UID creation is to check if the UID being generated exists in the "C" cross-reference. If it does and it is not for the accession being created then the software replaces the accession area identifier the site has specified for the accession area and uses "00" in its place to insure creation of a unique identifier. Example: LRO(68,"C",1550180008,25,2950118,8) Where: LRO = LRO global 68 = ACCESSION file (#68) "C" = cross reference 155018008 = UID 25 = accession area 2950118 = accession date (Jan 18 1995) 8 = accession number portion If the software wanted to assign the normally generated accession UID 1550180008 to accession area 25, accession date of Jan 18 2005, accession number of 18 but found the UID already exist for 1995 accession for the same day and number then UID generating software would replace 15 with 00 to create a UID 0050180008 to allow accessioning to continue. Note: The UID generating software will always produce an unique number. No two accessions will ever have the same UID based on the "C" cross reference. The routine LROC is modified to check for purged accessions and remove purged accession's UID from the "C" and "D" cross reference of the ACCESSION (#68) file. This will correct the problem of 10 year overlapping accession UID. This routine is invoked by Purge old orders & accessions option [LROC]. Note: After installation of this patch the Laboratory software will continue to create UIDs using the "00" prefix when an existing accession is still currently on the system and using the UID. This is to assure that the UID assigned to an accession is unique. The Laboratory software is capable of handling UIDs correctly when the UID has a "00" prefix. There is no inherent requirement that a specific UID conform exactly to its related accession. 2. The check and purge of these cross-references will be tasked by the post-install of this patch to cleanup any existing entries in file #68. The post-install of this patch tasks a back-ground job to cleanup any existing entries in file #68 that have been previously purged. After this back-ground job has run to completion, the "C" and "D" should not contain any UIDs related to purged accessions. 3. As part of developer review, the Purge old orders & accessions option [LROC] has been made 'TaskMan aware'. Stopping of this tasked process can be accomplished using standard TaskMan utilities. ASSOCIATED E3R -------------- None ASSOCIATED REMEDY --------------- HD0000000088913 Duplicates: HD0000000096348 HD0000000141232 HD0000000141237 HD0000000141258 HD0000000141298 HD0000000141977 HD0000000142004 HD0000000142663 HD0000000143065 HD0000000144052 HD0000000145774 HD0000000146357 HD0000000147586 HD0000000147794 HD0000000148645 TEST SITES ---------- ALEXANDRIA, LA BECKLEY, WV BOSTON HCS DURHAM, NC HAMPTON, VA HEARTLAND-EAST HCS HINES, IL LEXINGTON, KY MARYLAND HCS MILWAUKEE, WI NEW YORK HCS PHILADELPHIA, PA PUGET SOUND HCS TAMPA, FL UPSTATE NEW YORK HCS UNOFFICAL TEST SITES -------------------- ALTOONA, PA ANN ARBOR, MI BAY PINES, FL BLACK HILLS HCS BRONX, NY CENTRAL PLAINS HCS CENTRAL TEXAS HCS CLEVELAND, OH DAYTON, OH DETROIT, MI DUBLIN, GA FARGO, ND FRESNO, CA HOUSTON, TX LOMA LINDA, CA LONG BEACH, CA MADISON, WI MANCHESTER, NH MINNEAPOLIS, MN MUSKOGEE, OK NORTH CHICAGO, IL NORTHPORT, NY OKLAHOMA CITY, OK PROVIDENCE, RI RICHMOND, VA SAN FRANCISCO, CA SAN JUAN, PR SHERIDAN, WY SHREVEPORT, LA SIOUX FALLS, SD ST CLOUD, MN TENNESSEE VALLEY HCS WEST PALM BEACH, FL ROUTINE SUMMARY =============== The following routines are included in this patch. The second line of each of these routines now looks like: ;;5.2;LAB SERVICE;;Sep 27, 1994 Checksum Checksum Routine Name Before Patch After Patch Patch List ------------ ------------ ----------- ------------ LR329 N/A 5595661 **329** (Deleted by KIDS) LROC 9241387 7783203 **121,295,329** List of preceding patches: 295 Sites should use CHECK^XTSUMBLD to verify checksums. INSTALLATION INSTRUCTIONS ------------------------- The install time for this patch is less than 5 minute. This patch can be installed when Laboratory users are on the system. Suggested time to install: non-peak requirement hours. NOTE: Kernel patches must be current on the target system to avoid problems loading and/or installing this patch. Patch installation needs to be coordinated with the Laboratory Information Manager (LIM/ADPAC). 1. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This option will load the KIDS package onto your system. 2. On the 'Kernel Installation & Distribution System' Menu (KIDS), select the 'Installation' menu. 3. From this menu, you may then elect to use the following options (when prompted for the INSTALL NAME, enter LR*5.2*329): a. Print Transport Global b. Backup a Transport Global c. Compare Transport Global to Current System d. Verify Checksums in Transport Global Use the 'Verify Checksum in Transport Global' option and verify that all routines have the correct checksums. 4. Use the 'Install Package(s)' option under the 'Installation' menu and select the package 'LR*5.2*329'. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES//' choose 'NO'. Responding 'Yes' to the prompt for rebuilding menu trees can significantly increase install time. When prompted 'Want KIDS to INHIBIT LOGONs during the install? YES// choose 'NO'. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//', choose 'NO'. During install KIDS will place the Purge old orders & accessions option [LROC] out of order. Note: Routine LR329 will be deleted after successful patch installation. INSTALLATION EXAMPLE ==================== Select Installation Option: Select Kernel Installation & Distribution System Option: Installation Select Installation Option: 6 Install Package(s) Select INSTALL NAME: LR*5.2*329 Loaded from Distribution 4/11/05@16:15:44 => LR*5.2*329 This Distribution was loaded on Apr 11, 2005@16:15:44 with header of LR*5.2*329 It consisted of the following Install(s): LR*5.2*329 Checking Install for Package LR*5.2*329 Will first run the Environment Check Routine, LR329 Sending install started alert to mail group G.LMI --- Environment Check is Ok --- Install Questions for LR*5.2*329 Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO Want KIDS to INHIBIT LOGONs during the install? YES// NO Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO Enter the Device you want to print the Install messages. You can queue the install by enter a 'Q' at the device prompt. Enter a '^' to abort the install. DEVICE: HOME// TELNET VIRTUAL Install Started for LR*5.2*329 : Apr 11, 2005@16:16:28 Build Distribution Date: Apr 11, 2005 Installing Routines:... Apr 11, 2005@16:16:28 Running Pre-Install Routine: PRE^LR329. *** Pre install started *** *** No action required *** *** Pre install completed *** Installing PACKAGE COMPONENTS: Installing OPTION.. Apr 11, 2005@16:16:28 Running Post-Install Routine: POST^LR329. *** Post install started *** Running Post-Install Routine: POST^LR329. *** Post install started *** *** Tasking check/cleanup "C" cross reference on ACCESSION file (#68) *** *** Task #XXXX tasked to run *** *** Post install completed *** Sending install completion alert to mail group G.LMI Updating Routine file...... Updating KIDS files....... LR*5.2*329 Installed. Apr 11, 2005@16:16:28 Install Message sent #XXXX Routine Information: ==================== The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: LR329 Before: n/a After: B11411168 **329** Routine Name: LROC Before: B15121360 After: B27696934 **121,295,329** ============================================================================= User Information: Entered By : MCCORMACK,JOHN Date Entered : JAN 21, 2005 Completed By: KIRBY,ROSE Date Completed: SEP 11, 2006 Released By : BELSCHWINDER,MICHAEL Date Released : SEP 11, 2006 ============================================================================= Packman Mail Message: ===================== $END TXT