$TXT Created by KOPP,TERRY at DEVFEY.FO-ALBANY.MED.VA.GOV (KIDS) on Wednesday, 07/28/04 at 16:15 ============================================================================= Run Date: OCT 06, 2004 Designation: IB*2*232 Package : IB - INTEGRATED BILLING Priority: Mandatory Version : 2 SEQ #256 Status: Released Compliance Date: NOV 06, 2004 ============================================================================= Subject: EDI/HIPAA ENHANCEMENTS Category: - Enhancement (Mandatory) - Data Dictionary - Input Template - Routine Description: ============ **************************** IMPORTANT NOTE **************************** Patch IB*2.0*280 MUST be installed IMMEDIATELY after installing this patch. Failure to do so may cause data problems with E_claims that will bring the wrath of the clearinghouse down on you. IRM ... Review the patch instructions prior to the install. There are pre-installation and post-installation functions that require your attention. Coordinate the install of patches IB*2.0*232 and IB*2.0*280 with your billing department. Ensure that the IB ADPAC/Billing Supervisor has a copy of the patch descriptions and the EDI Billing User Guide. ************************************************************************* Associated patches: (v) IB*2.0*184 IB*2.0*196 IB*2.0*245 IB*2.0*239 Background: =========== In order to meet federally mandated HIPAA (Health Information Portability and Accountability Act) compliant regulations, this patch has altered the EDI (Electronic Data Interchange) flat file map that is sent for electronic claims to contain all the information that is required to generate an industry standard (X.12 compliant) claim. HIPAA EDI requirements significantly alter the data the V.A. transmits in an attempt to eliminate the individual requirements dictated by individual payers. The overall concept of the HIPAA EDI guidelines is that "all data should be sent all the time" and the payers then can select which data is important to them. As a result, the EDI data is now required to be 'standardized' and as long as all HIPAA required fields are transmitted, then a claim is not supposed to be rejected based on payer specific data requirements. In order to 'standardize' the electronic claim, the HIPAA guidelines require changing some basic characteristics of the electronic claim, specifically related to provider ID's. The file of data that is sent for electronic claims submission has been changed drastically. The specific changes are not included in this patch description, but the new flat file layout document is available on the following website: http://tspr.vista.med.va.gov/warboard/anotebk.asp?proj=717&Type=Active - Functional change summary: Because of the standardization of data, the Output Formatter overrides will only be available now for the ADMISSION HOUR and DISCHARGE HOUR fields on the bill transmission form. All other local overrides found for the transmission form will be deleted. With the new requirements, there is a new primary ID transmitted for a performing provider. This is either a Social Security Number (for a person) or a Federal Tax ID number (for a non-person such as a group of providers). This is NOT an optional ID. All performing providers must be assigned this ID in order to bill for their services. Previously, you were required to have a primary performing ID type for each insurance company, for each form type (HCFA 1500 or UB-92). These IDs are no longer required for ALL insurance companies as the primary ID will be the SSN/tax ID as described above. HIPAA has allowed individual insurance companies to require sites to provide an additional ID, however. This is now called the secondary performing provider ID and these are the ID's you can enter on Screen 8 when you add the performing provider to the claim. This does NOT mean you HAVE to enter an ID on Screen 8 for the insurance company. There are specific conditions that will require an entry here and these are discussed in the user document in detail. Briefly, however, here are the 'rules' for deciding the appropriate performing provider ID that will be pulled for a claim: A maximum of one ID of each provider ID type from provider ID maintenance is allowed to be included on the claim. The first ID of each ID type that is found according to the list below is the one that is sent: 1. The ID and ID type found on screen 8, if any, for the provider. 2. If an ID exists for the individual provider without a care unit, the ID is sent. 3. If an ID exists for ALL providers for the insurance company, the ID is sent. 4. If an ID exists for the facility, the ID is sent. The definition of billing facility ID's have been changed so the site can define them by division. These are the ID's on billing Screen 3. Care units used for performing provider ID's have been modified to be a little easier to understand and use. 1. Care unit set up has been simplified. You no longer need to create the care unit, then assign a combination. The option for care unit maintenance now assumes you want to add a care unit if it doesn't already exist for an insurance company and automatically prompts you for a 'combination'. The following prompts have been removed: ADD (I)NS. CO. CARE UNIT OR CARE UNIT (C)OMBINATION?: DO YOU WANT TO ADD A COMBINATION FOR THIS CARE UNIT NOW?: 2. There is no longer a requirement that a care unit be entered for a claim if the insurance company uses care units for the provider ID. 3. A care unit is no longer EVER required when adding an ID. If a care unit is entered when defining an ID, it is simply attached to the ID and displayed in the list of choices for valid ids when entering the ID on screen 8 of the billing screens. If no care unit is assigned to a performing provider ID, the ID simply exists and is displayed without the care unit. Note that if an ID exists with and without a care unit, when a default ID is determined for the secondary ID for a provider on a claim, the system will default to the id without the care unit because when determining a default provider id, it always ignores any IDs with care units. 4. The only place a care unit description is used now is on the provider ID screen that is displayed on screen 8, when the list of valid IDs are displayed for the provider/form type. Supervising Provider has been added as a new Provider Function on billing screen 8. As a result of the provider ID changes, it is essential that the insurance files be set up correctly. This patch deletes the data in the old primary performing provider ID parameters to accommodate the new definition of performing provider ID's. It copies the billing facility ID's for each insurance company to new fields for the default facility's division so additional ones can be defined for other divisions, if necessary. It also deletes any performing provider ID's for insurance companies that have been deleted. This patch addresses the following New Service Request (NSR): ------------------------------------------------------------- No new service requests are associated with this patch. This patch addresses the following NOIS message(s): --------------------------------------------------- There are no NOIS messages associated with this patch. The following is a list of Input templates included in this patch: ------------------------------------------------------------------ Template Name Type File Name (Number) ------------- ---- ------------------ IB SCREEN8H INPUT BILL/CLAIMS (#399) IB SCREEN82 INPUT BILL/CLAIMS (#399) IBEDIT INS CO1 INPUT INSURANCE COMPANY (#36) The following is a list of files included in this patch: --------------------------------------------------------- UP SEND DATA DATE SEC. COMES FILE # NAME DD CODE W/FILE ------------------------------------------------------ 2 PATIENT Y N N INSURANCE TYPE (#.3121 - subfile #2.312) PT. RELATIONSHIP TO INSURED (#16) 36 INSURANCE COMPANY Y N N DELETE 2006 4.04 (#4.04) DELETE 2006 4.05 (#4.05) DELETE 2006 4.06 (#4.06) DELETE 2006 4.07 (#4.07) DELETE 2006 4.08 (#4.08) DELETE 2006 4.1 (#4.1) DELETE 2006 4.11 (#4.11) PERF PROV SECOND ID TYPE HCFA (#4.02) PERF PROV SECOND ID TYPE UB (#4.01) SECONDARY ID REQUIREMENTS (#4.03) 364.5 IB DATA ELEMENT DEFINITION N N Y 364.6 IB FORM SKELETON DEFINITION N N Y 364.7 IB FORM FIELD CONTENT N N Y 355.9 IB BILLING PRACTITIONER ID Y N N PROVIDER ID CARE UNIT (#.03) 355.91 IB INSURANCE CO LEVEL BILLING Y N N PROV ID PROVIDER ID CARE UNIT (#.03) 355.92 FACILITY BILLING ID Y N N 355.97 IB PROVIDER ID # TYPE Y N Y 355.93 IB NON VA BILLING PROVIDER Y N Y NAME (#.01) PROVIDER TYPE (#.02) STATE LICENSE # (#.12) STREET ADDRESS LINE 2 (#.1) X12 TYPE OF FACILITY (#.11) 399 BILL/CLAIMS Y N N DEFAULT DIVISION (#.22) NON-VA FACILITY (#232) PRIMARY INSURANCE CARRIER (#122) SECONDARY INSURANCE CARRIER (#123) TERTIARY INSURANCE CARRIER (#124) PROVIDERS (#222 - subfile #399.0222) DELETE 2006 .09 (#.09) DELETE 2006 .1 (#.1) DELETE 2006 .11 (#.11) DELETE 2006 1.01 (#1.01) DELETE 2006 1.02 (#1.02) DELETE 2006 1.03 (#1.03) FUNCTION (#.01) PERFORMED BY (#.02) PRIM INS PROVIDER ID TYPE (#.12) PRIMARY INS CO ID NUMBER (#.05) SEC INS PROVIDER ID TYPE (#.13) SECONDARY INS CO ID NUMBER (#.06) TERT INS PROVIDER ID TYPE (#.14) TERTIARY INS CO ID NUMBER (#.07) The following is a list of LIST TEMPLATES included in this patch: ----------------------------------------------------------------- IBCE PRVFAC MAINT The following is a list of OPTIONS included in this patch: ---------------------------------------------------------- Provider ID Query [IBCE PROVIDER ID QUERY] DESCRIPTION: This option allows the site to run or re-run the provider id query report to report some of the invalid provider id set ups for insurance companies. The following is a list of PROTOCOLS included in this patch: ------------------------------------------------------------ IBCE PRVFAC EDIT The following fields for the provider ID parameters in the INSURANCE COMPANY file (#36) have been renamed/redefined. Note fields 4.04-4.11 below are no longer in use: FLD # OLD NAME NEW NAME ----- -------------------------------- -------------------- 4.01 PERFORMING PROVIDER ID TYPE PERF PROV SECOND ID TYPE HCFA 4.02 PERFORMING PROV ID SOURCE PERF PROV SECOND ID TYPE UB 4.03 DEFAULT PERF ID IF MISSING? SECONDARY ID REQUIREMENTS 4.04 NETWORK ID SOURCE DELETE 2006 4.04 4.05 DEFAULT NETWORK ID IF MISSING? DELETE 2006 4.05 4.06 EMC ID SOURCE DELETE 2006 4.06 4.07 DEFAULT EMC ID IF MISSING? DELETE 2006 4.07 4.08 EMC CARE UNIT PROMPT DELETE 2006 4.08 4.1 ALTERNATE PERF PROV ID TYPE DELETE 2006 4.1 4.11 ALTERNATE PERF PROV ID SOURCE DELETE 2006 4.11 The following fields for the provider ID in the BILL/CLAIMS (#399) file, subfile PROVIDER (#399.0222) have been renamed/redefined as they are no longer used: FLD # OLD NAME NEW NAME ------ -------------------------- ------------------- .09 PRIMARY PROV ID CARE UNIT DELETE 2006 .09 .1 SECONDRY PROV ID CARE UNIT DELETE 2006 .1 .11 TERTIARY PROV ID CARE UNIT DELETE 2006 .11 1.01 PRIMARY EMC ID CARE UNIT DELETE 2006 1.01 1.02 SECONDARY EMC ID CARE UNIT DELETE 2006 1.02 1.03 TERTIARY EMC ID CARE UNIT DELETE 2006 1.03 PRE-INSTALLATION FUNCTIONS: 1. The four files (IB BILLING PRACTITIONER ID (#355.9), IB INSURANCE CO level BILLING PROV ID (#355.91), IB PROVIDER ID CARE UNIT (#355.95), IB INS CO PROVIDER ID CARE UNIT (#355.96)) where provider IDs stored are searched and if any IDs are found for insurance companies that have been deleted, the ID entries are deleted from the file. 2. The definition and the data in the following fields in the INSURANCE COMPANY file (#36) are deleted to ensure all cross references and descriptions are fully removed before the newly defined fields are loaded with the install: 4.01 PERFORMING PROVIDER ID TYPE 4.02 PERFORMING PROV ID SOURCE 4.03 DEFAULT PERF ID IF MISSING? 3. For all entries in the INSURANCE COMPANY file (#36), the data for the following fields is deleted to clean up the file: 4.02 PERFORMING PROV ID SOURCE 4.03 DEFAULT PERF ID IF MISSING? 4.04 NETWORK ID SOURCE 4.05 DEFAULT NETWORK ID IF MISSING? 4.06 EMC ID SOURCE 4.07 DEFAULT EMC ID IF MISSING? 4.08 EMC CARE UNIT PROMPT 4.1 ALTERNATE PERF PROV ID TYPE 4.11 ALTERNATE PERF PROV ID SOURCE 4. The data in field PERFORMING PROVIDER ID TYPE (#4.01) is saved and becomes the default provider secondary ID for the HCFA 1500 form for the insurance company. 5. The definition of the following fields in the BILL/CLAIMS (#399) file, subfile PROVIDER (#399.0222) are deleted to ensure all cross references and descriptions are fully removed before the newly defined fields are loaded with the install: .05 PRIMARY INS CO ID NUMBER .06 SECONDARY INS CO ID NUMBER .07 TERTIARY INS CO ID NUMBER .09 PRIMARY PROV ID CARE UNIT .1 SECONDRY PROV ID CARE UNIT .11 TERTIARY PROV ID CARE UNIT 1.01 PRIMARY EMC ID CARE UNIT 1.02 SECONDARY EMC ID CARE UNIT 1.03 TERTIARY EMC ID CARE UNIT 6. The mail group MCH is created. It should contain the same remote members as the old MCR mail group it is replacing. 7. Six new provider ID types have been added to the IB PROVIDER ID # TYPE file (#355.97). They are: PPO NUMBER HMO NUMBER SOCIAL SECURITY NUMBER STATE INDUSTRIAL ACCIDENT PROV LOCATION NUMBER BILLING FACILITY PRIMARY ID In addition, the X12 qualifiers for all provider ID types are updated according to the HIPAA standards. 8. The entry IB315 is deleted from the IB ERROR (#350.8) file 9. A check is made to insure the domain Q-MCH.VA.GOV has been added to the DOMAIN (#4.2) file only if the patch is being loaded in a production account. The domain needs to be set up as follows or the patch will not be installed: NAME: Q-MCH.VA.GOV FLAGS: S RELAY DOMAIN: FOC-AUSTIN.VA.GOV If you do not have the domain set up correctly, refer to patch XMB*DBA*162 for specifics on its set up. 10. The provider id for CHAMPUS ID has been renamed TRICARE ID. 11. All local override fields for the transmission fields included in this patch are deleted for the IB 837 TRANSMISSION FORM (for electronic claim submission) in the IB FORM FIELD CONTENT (#364.7) file. Before deletion, the format code for each field is written to the install file for the patch. If this data ever needs to be recovered, the data can be found here and manually re-entered. If the build does not find any local fields, there will be no output referencing this in the install file. Note that the overrides for ADMISSION HOUR and DISCHARGE HOUR on the IB 837 TRANSMISSION FORM are NOT removed by this install. POST-INSTALLATION FUNCTIONS: 1. A mail message is sent to a special mail group at the Albany OIFO confirming the site has installed the new version of the software. This mail group name is ZZ_EDIENHANCE@FO-ALBANY.MED.VA.GOV. If, for any reason, the mail message cannot be successfully created and sent, a bulletin will be sent to the members of the IB EDI SUPERVISOR mail group advising them to contact EVS to report this problem immediately. EVS can then send a manual confirmation to this mail group to advise them the site is running the EDI Enhancements software. 2. The data in the HOSPITAL PROVIDER NUMBER (#.11) and PROFESSIONAL PROVIDER NUMBER (#.17) fields in the INSURANCE COMPANY file (#36) are copied as entries in the new facility ID file (FACILITY BILLING ID #355.92). 3. Three cross references are deleted from the BILL/CLAIMS file that reference CARE UNITS as they are no longer needed or used: PRIMARY INSURANCE CARRIER (#101) Trigger cross reference #4 Deletes the PRIMARY EMC ID CARE UNIT field when the PRIMARY INSURANCE CARRIER field changes. SECONDARY INSURANCE CARRIER (#102) Trigger cross reference #5 Deletes the SECONDARY EMC ID CARE UNIT field when the SECONDARY INSURANCE CARRIER field changes. TERTIARY INSURANCE CARRIER (#103) Trigger cross reference #4 Deletes the TERTIARY EMC ID CARE UNIT field when the TERTIARY INSURANCE CARRIER field changes. Test Sites: ----------- CENTRAL PLAINS HCS CENTRAL TEXAS HCS EASTERN COLORADO HCS INDIANAPOLIS Other 'add-on' pilot sites also tested the software. DOCUMENTATION RETRIEVAL ======================= The changes to the Integrated Billing software have been detailed in the updated EDI Billing user's guide. This guide is available for download at the following website: http://vaww.vistau.med.va.gov/vistau/e-bp/e-claims.htm The user's guide may also be retrieved from the following OI Field Offices' Anonymous.Software Directories. Use the appropriate FTP capability to retrieve the files and use BINARY format. 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 ftp.fo-slc.med.va.gov anonymous.software FIRST AVAILABLE SERVER download.vista.med.va.gov anonymous.software FILE NAME ============== IB_2_232UG.PDF ================INSTALLATION INSTRUCTIONS ================= It is recommended this patch be installed outside of normal business hours to avoid any complications resulting from Integrated Billing users on the system. Installation will take less than 30 minutes. Other VISTA users will not be affected. The following menus/options should be disabled to prevent possible conflicts while running the KIDS install. Billing Supervisor Menu [IB BILLING SUPERVISOR] Billing Clerk's Menu [IB BILLING CLERK MENU] Integrated Billing Master Menu [IB MANAGER MENU] In addition this patch should not be installed at the times when queued claims are sent to the Austin FSC (Financial Services Center). The IB personnel set this time, so they should be aware of what times queued claims are sent to Austin. Install Time: less than 30 minutes ************** PRE-INSTALLATION INSTRUCTIONS ************** Nightly jobs: DO NOT install this patch while the nightly IB MT NIGHT COMP job is running. *********************************************************** 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 routine(s) included in this patch. The second line of each of these routine(s) will look like: ;;2.0;INTEGRATED BILLING;**[patch list]**;21-MAR-94 CHECK^XTSUMBLD results Routine name Before Patch After Patch Patch List ============ ============ =========== ========== IBCBB1 11866588 16120102 27,52,80,93,106 51,151,148,153,137 232 IBCBB2 16377709 17364901 51,137,210,245,232 IBCBB21 6826047 6642591 51,137,210,232 IBCE837 26625512 26776750 137,191,197,232 IBCE837A 10309494 10486796 137,191,211,232 IBCEF2 10582330 14296373 52,85,51,137,232 IBCEF4 8108477 8857760 51,137,232 IBCEF7 N/A 11650571 232 IBCEF71 N/A 20195434 232 IBCEF72 N/A 11695414 232 IBCEF73 N/A 10577143 232 IBCEF74 N/A 19367427 232 IBCEFG1 9320615 10283839 52,51,137,181,197 232 IBCEP 16086162 10144684 137,232 IBCEP0 21510008 21546622 137,191,239,232 IBCEP0A 13040260 13120940 137,232 IBCEP2 15856525 16361218 137,181,232 IBCEP2A 5909026 6129528 137,232 IBCEP2B N/A 18937107 232 IBCEP3 10299570 9164022 137,207,232 IBCEP4A 24140485 18271696 137,232 IBCEP5 13458822 14765789 137,232 IBCEP5A 5283539 8951005 137,232 IBCEP5B 24388459 23533206 137,239,232 IBCEP5C 17283897 18414796 137,239,232 IBCEP6 5453460 4559530 137,232 IBCEP7 4538401 25321200 137,232 IBCEP7A N/A 2291408 232 IBCEP8 3622459 8307023 51,137,232 IBCEQ1 N/A 9869244 232 IBCEQ1A N/A 20136790 232 IBCESRV 14441806 15671023 137,181,196,232 IBCEU 13254284 14054971 51,137,207,232 IBCEU5 21365069 21845934 51,137,232 IBCNSC01 14639853 14777443 52,137,191,184,232 IBCNSC1 7689226 6463359 62,137,232 IBCNSCD 8457816 10297337 28,46,232 IBCSC3 17003524 17527793 8,43,52,80,82 51,137,232 IBCSC82 9846140 9331591 51,137,210,232 IBCSC8H 12652084 11875031 51,137,207,210,232 IBCSCH 28881055 30141913 52,80,106,124,138 51,148,137,161,245 232 IBCU 14077097 14555083 52,106,51,191,232 IBEFUNC 8203989 8200161 55,91,106,139,51 153,232 IBY232PO N/A 14498180 232 IBY232PR N/A 18790924 232 Total number of routines: 45 (INCLUDING PRE AND POST PROCESSORS) # New routines: 11 # Modified routines: 34 # Deleted routines: 0 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 5. Select Installation Option: -------------------------- NOTE: The following are OPTIONAL 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. When prompted for the INSTALL NAME, enter IB*2.0*232 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 YES (unless otherwise indicated) d. When prompted 'Enter options you wish to mark as 'Out Of Order':' Enter the following options: Billing Supervisor Menu [IB BILLING SUPERVISOR] Billing Clerk's Menu [IB BILLING CLERK MENU] Integrated Billing Master Menu [IB MANAGER MENU] e. When prompted 'Enter protocols you wish to mark as 'Out Of Order':. press . f. You MAY be asked if you wish to overwrite data dictionary files, depending on your system settings. You need to answer 'YES' to all overwrite requests. g. You will be asked to supply a coordinator for the MCH mail group. You should enter the person that is the currently the coordinator for the MCR mail group. 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. ************** POST-INSTALLATION INSTRUCTIONS************** Using Fileman Inquiry, verify the following: 1. Ensure the patch has changed the IB SITE PARAMETER File (#350.9) LIVE TRANSMIT 837 QUEUE (#8.01) to: MCH 2. Ensure the entry MCH in the MAIL GROUP file (#3.8) has the following as a REMOTE MEMBER (#12): S.IBCE MESSAGES SERVER@XXX.MED.VA.GOV where XXX is the site domain. 3. Check with your Billing ADPAC/Supervisor to see who should be assigned the new PROVIDER ID QUERY option [IBCE PROVIDER ID QUERY] as a secondary menu option. Then make the appropriate assignments for this option. 4. You may delete the pre and post installation routines IBY232PR and IBY232PO. ***************** SPECIAL NOTE *************** This patch makes substantial modification to the 837 format. Any local fields in file 364.7 that reference the new 837 format will be DELETED as part of the install process. This was done because the flat file was reorganized and so many fields were moved and deleted that it was not possible to code a fix to allow local fields to continue to exist in this file. Only local override fields for TRANSMISSION are deleted. The override fields for transmission data ADMISSION HOUR and DISCHARGE HOUR will not be deleted and all local print overrides are still functional. Routine Information: ==================== Routine Name: - IBCE837 Routine Checksum: Routine Name: - IBCE837A Routine Checksum: Routine Name: - IBCBB1 Routine Checksum: Routine Name: - IBCBB21 Routine Checksum: Routine Name: - IBCEF2 Routine Checksum: Routine Name: - IBCEF4 Routine Checksum: Routine Name: - IBCEF7 Routine Checksum: Routine Name: - IBCEF71 Routine Checksum: Routine Name: - IBCEF72 Routine Checksum: Routine Name: - IBCEF73 Routine Checksum: Routine Name: - IBCEFG1 Routine Checksum: Routine Name: - IBCEP2 Routine Checksum: Routine Name: - IBCEP2A Routine Checksum: Routine Name: - IBCEP5 Routine Checksum: Routine Name: - IBCEP5A Routine Checksum: Routine Name: - IBCEP6 Routine Checksum: Routine Name: - IBCEP8 Routine Checksum: Routine Name: - IBCESRV Routine Checksum: Routine Name: - IBCEU Routine Checksum: Routine Name: - IBCEU5 Routine Checksum: Routine Name: - IBCSC3 Routine Checksum: Routine Name: - IBCSC82 Routine Checksum: Routine Name: - IBCSC8H Routine Checksum: Routine Name: - IBCBB2 Routine Checksum: Routine Name: - IBEFUNC Routine Checksum: Routine Name: - IBCSCH Routine Checksum: Routine Name: - IBCEF74 Routine Checksum: Routine Name: - IBCEP2B Routine Checksum: Routine Name: - IBCEP3 Routine Checksum: Routine Name: - IBCEP4A Routine Checksum: Routine Name: - IBCEP7 Routine Checksum: Routine Name: - IBCNSC1 Routine Checksum: Routine Name: - IBY232PO Routine Checksum: Routine Name: - IBY232PR Routine Checksum: Routine Name: - IBCNSCD Routine Checksum: Routine Name: - IBCEP Routine Checksum: Routine Name: - IBCEP5B Routine Checksum: Routine Name: - IBCEP5C Routine Checksum: Routine Name: - IBCEP7A Routine Checksum: Routine Name: - IBCNSC01 Routine Checksum: Routine Name: - IBCU Routine Checksum: Routine Name: - IBCEP0A Routine Checksum: Routine Name: - IBCEQ1 Routine Checksum: Routine Name: - IBCEQ1A Routine Checksum: Routine Name: - IBCEP0 Routine Checksum: ============================================================================= User Information: Entered By : LORD,BRIAN Date Entered : JUL 15, 2003 Completed By: TORRANCE,LORI Date Completed: OCT 05, 2004 Released By : JACKSON,SHERYL Date Released : OCT 06, 2004 ============================================================================= Packman Mail Message: ===================== $END TXT