============================================================================= Run Date: OCT 22, 2007 Designation: SD*5.3*495 Package : SD - SCHEDULING Priority: Mandatory Version : 5.3 SEQ #424 Status: Released Compliance Date: NOV 22, 2007 ============================================================================= Associated patches: (v)SD*5.3*466 <<= must be installed BEFORE `SD*5.3*495' (v)DVB*4*58 <<= must be installed BEFORE `SD*5.3*495' (v)IB*2*369 <<= must be installed BEFORE `SD*5.3*495' (v)PRCA*4.5*250<<= must be installed BEFORE `SD*5.3*495' Subject: AUTOMATED SERVICE CONNECTED DESIGNATION - SD Category: - Enhancement (Mandatory) - Routine - Data Dictionary - Informational Description: ============ I M P O R T A N T ************************************************************************* This Scheduling Application System patch, SD*5.3*495, along with the Hospital Inquiry (HINQ) patch, DVB*4.0*58, and the Patient Care Encounter (PCE) patch, PX*1.0*184, is being released in a single KIDS software distribution (host file) DVB_4_P58.KID. This patch description includes only the Informational portion of SD*5.3*495. Also as part of this project are patches PRCA*4.5*250 and IB*2.0*369. These patches must be installed before the host file DVB_4_P58.KID. Please refer to the "Software Retrieval" and "Installation Instructions" sections of the DVB*4.0*58 patch description for instructions on how to acquire, install, and implement the patch software. ************************************************************************* This patch addresses the Automated Service Connected Designation (ASCD) project which will automate the Service Connected (SC) decision for outpatient encounters using mapped ICD9/Rated Disability Codes at the time the clinician enters the ICD9 code for the encounter within the Patient Care Encounter (PCE) and Scheduling packages ONLY. In the current clinical work environment providers are requested to designate, at the point of care, if a specific patient care encounter is service connected based on available disability rating information. This software will computerize the clinician's process at each encounter, i.e. mark the encounter service connected (SC) or non-service connected (NSC) as appropriate via the PCE & Scheduling packages. Thus, when a provider or clinician chooses the diagnosis code within one of these packages for the encounter, the system will automatically determine if the diagnosis is related to the veteran's established SC conditions, and will likewise automatically make the proper SC/NSC determination. Additionally, the Class III Service Connection Objective Update Tool (SCOUT) software has been converted and implemented as Class I Automated Service Connected Designation (ASCD). This software recognizes potentially billable encounters for SC veterans that cannot be automatically matched to rated disability codes as well as potentially non-billable encounters which were designated NSC but should be SC. These encounters are displayed in reports for coders and/or utilization review staff to review the patient visit information and change the incorrect SC/NSC designation so they can be billed appropriately. Patch SD*5.3*495 addresses the following changes/enhancements: o Modifications were made to the outpatient encounter checkout process to determine if the encounter needs additional review for final service connected designation. o A scheduling API was created to automate and flag checked-out outpatient encounters for review. o The SCOUT application was converted and modified for processing and reporting of encounters that have been set for review. MODIFICATIONS TO OUTPATIENT CHECKOUT Technical: ---------- o Routine SDCOM was modified to call the Scheduling API routine SDSCAPI to check if the encounter needs additional review for final service connected designation. o A new routine, SDSCAPI, was created to automate and review an encounter and determine if the patients rated disabilities match or partially match the new RATED DISABILITIES (VA)/ICD9 code mapping. Functional: ----------- o During the Check Out process, if the encounter's primary diagnosis code does not match the mapping of the patients rated disabilities and ICD9 codes then the encounter will be flagged for review. o The response to the question "Was treatment for SC Condition?" will be automated for each encounter based on the patients rated disabilities and each ICD9 code. Automated Service Connected Designation (ASCD) Application Technical: ---------- o The following new menu options have been created: Automated Service Connected Designation Menu [SDSC MENU] ASCD Compile Parameter [SDSC SITE PARAMETER] ASCD Reports ... [SDSC REPORTS] Clinic Service Total Summary Report [SDSC SERVICE TOTAL REPORT] Compile Results Report [SDSC CHECK COMPILE] Estimated Recovered Costs Report [SDSC RECOVERED REPORT] First Party Billable Service Connected Report [SDSC FIRST PARTY REPORT] Manager Summary Report [SDSC MANAGER SUMMARY REPORT] Provider Service Connected Encounters [SDSC PROVIDER REPORT] Provider Total Summary Report [SDSC PROVIDER TOTAL REPORT] Service Connected Encounters Report [SDSC ENC REPORT] Third Party Billable Service Connected Report [SDSC THIRD PARTY REPORT] Unbilled/Billable Amount Report [SDSC UNBILL AMT REPORT] User Service Connected Encounters Report [SDSC USER REPORT] User Total Summary Report [SDSC USER TOTAL REPORT] Compile ASCD Encounters by Date Range [SDSC COMPILE] Edit ASCD Encounters by Date Range [SDSC EDIT BY DATE] Edit ASCD Encounters by ListMan [SDSC EDIT LISTMAN] Edit Single ASCD Encounter [SDSC SINGLE EDIT] Purge ASCD NSC Encounters [SDSC PURGE NSC ENC] o Two (2) new DBIAs were created and 7 DBIAs were subscribed to in support of this project. New --- 4990 SERVICE CONNECTED AUTOMATION 4991 PCE PRIMARY PROVIDER Subscribing ----------- 643 DBIA186-C 733 READ ACCESS TO ICD9 CODE INFORMATION 767 DBIA268-C 2602 READING AUDIT FILE 3857 PATIENT SECURITY CHECK 4370 AR API to return Billing Data 4987 IB BILLING DATA API Functional: ----------- o The following new application menu options have been created: Select OPTION NAME: Automated Service Connected Designation Menu ASCD Compile Parameter ASCD Reports ... Compile ASCD Encounters by Date Range Edit ASCD Encounters by Date Range Edit ASCD Encounters by ListMan Edit Single ASCD Encounter Purge ASCD NSC Encounters o This software recognizes potentially billable encounters for SC veterans that cannot be automatically matched to Rated Disability codes. These encounters are displayed in reports for coders and/or utilization review staff who then review the patient visit information, edit incorrect SC designated encounters, and release them to Claims Tracking for billing where appropriate. SCHEDULING MANAGER'S MENU MODIFICATION Technical: ---------- o The Scheduling Manager's Menu [SDMGR] option will have the new Automated Service Connected Designation Menu [SDSC MENU] option module added to the current ITEM list. OPTION NAME: SDMGR MENU TEXT: Scheduling Manager's Menu TYPE: menu CREATOR: POSTMASTER PACKAGE: SCHEDULING E ACTION PRESENT: YES DESCRIPTION: This is the primary menu option which allows the user access to all options of the scheduling module. ITEM: SDAPP ITEM: SDOUTPUT ITEM: SDSUP ITEM: SCDX AMBCAR REPORTING SYNONYM: ACR ITEM: SDSC MENU Functional: ----------- o The Scheduling Manager's Menu [SDMGR] option will now provide access to the following application modules: Select OPTION NAME: SDMGR Scheduling Manager's Menu Scheduling Version 5.3 ACR Ambulatory Care Reporting Menu ... Appointment Menu ... Automated Service Connected Designation Menu ... Outputs ... Supervisor Menu ... This patch addresses the following New Service Request (NSR): ------------------------------------------------------------- Request ID: 20050705 Request Name: Automated Service Connected Designation Product Name: SCOUT and VBA/ICD mapping This patch addresses the following Remedy Ticket(s): ---------------------------------------------------- There are no Remedy tickets associated with this patch. Components Sent With Patch: --------------------------- ROUTINE, FILE, MAIL GROUP, OPTION, SECURITY KEY, PROTOCOL, LIST TEMPLATE, PARAMETER DEFINITION ROUTINE SUMMARY: ================ 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: ;;5.3;Scheduling;**[patch list]**;Aug 13, 1993 CHECK^XTSUMBLD results Routine name Before Patch After Patch Patch List ============ ============ =========== ========== SD53P495 N/A 17052827 495 SDCOM 3581556 3870697 15,60,105,132,466 495 SDSCAPI N/A 4890152 495 SDSCCHK N/A 12562660 495 SDSCCLM N/A 807240 495 SDSCEDT N/A 14963185 495 SDSCINS N/A 4394965 495 SDSCLM N/A 3606888 495 SDSCLM1 N/A 442198 495 SDSCLST N/A 2013059 495 SDSCMSR N/A 13760559 495 SDSCNSCP N/A 5697380 495 SDSCOMP N/A 12109889 495 SDSCPRG N/A 5179008 495 SDSCPRM N/A 652551 495 SDSCPRV N/A 7693494 495 SDSCRP1 N/A 10017525 495 SDSCRP2 N/A 11697469 495 SDSCRPT1 N/A 11329051 495 SDSCRPT2 N/A 8000312 495 SDSCSSD N/A 6360121 495 SDSCUSR N/A 7607646 495 SDSCUTL N/A 6356862 495 Number of Routines = 23 Total number of routines modified: 1 Total number of new routines: 22 CHECK1^XTSUMBLD (new method) results Routine name Before Patch After Patch Patch List ============ ============ =========== ========== SD53P495 N/A 87466494 495 SDCOM 5826254 6631731 15,60,105,132,466 495 SDSCAPI N/A 21470995 495 SDSCCHK N/A 39800348 495 SDSCCLM N/A 1275412 495 SDSCEDT N/A 76725826 495 SDSCINS N/A 11936927 495 SDSCLM N/A 8362461 495 SDSCLM1 N/A 677645 495 SDSCLST N/A 5358321 495 SDSCMSR N/A 50399971 495 SDSCNSCP N/A 15365722 495 SDSCOMP N/A 63599781 495 SDSCPRG N/A 10441801 495 SDSCPRM N/A 856844 495 SDSCPRV N/A 25452487 495 SDSCRP1 N/A 37970877 495 SDSCRP2 N/A 51118024 495 SDSCRPT1 N/A 49147516 495 SDSCRPT2 N/A 34356180 495 SDSCSSD N/A 17495006 495 SDSCUSR N/A 25529113 495 SDSCUTL N/A 29887017 495 Number of Routines = 23 Total number of routines modified: 1 Total number of new routines: 22 The following is a list of files included in this patch: -------------------------------------------------------- UP SEND DATA USER DATE SEC. COMES SITE RSLV OVER FILE # NAME DD CODE W/FILE DATA PTS RIDE ----------------------------------------------------------------------- 409.48 SDSC SERVICE CONNECTED CHANGES YES YES NO The following is a list of fields included in this patch: --------------------------------------------------------- Field Name (Number) File Name (Number) -------------------------- ---------------------------------------- OUTPATIENT ENCOUNTER (#.01) SDSC SERVICE CONNECTED CHANGES (#409.48) DATE LAST EDITED (#.02) SDSC SERVICE CONNECTED CHANGES (#409.48) LAST EDITED BY (#.03) SDSC SERVICE CONNECTED CHANGES (#409.48) DATE CREATED (#.04) SDSC SERVICE CONNECTED CHANGES (#409.48) STATUS (#.05) SDSC SERVICE CONNECTED CHANGES (#409.48) SERV. CONNECT (OK BY USER?) (#.06) SDSC SERVICE CONNECTED CHANGES (#409.48) DATE OF ENCOUNTER (#.07) SDSC SERVICE CONNECTED CHANGES (#409.48) PRIMARY PROVIDER (#.08) SDSC SERVICE CONNECTED CHANGES (#409.48) SERV. CONNECT (OK BY VBA/ICD?) (#.09) SDSC SERVICE CONNECTED CHANGES (#409.48) CLAIMS TRACKING ENTRY (#.1) SDSC SERVICE CONNECTED CHANGES (#409.48) PATIENT (#.11) SDSC SERVICE CONNECTED CHANGES (#409.48) DIVISION (#.12) SDSC SERVICE CONNECTED CHANGES (#409.48) SERV. CONNECT (ORIGINAL VALUE) (#.13) SDSC SERVICE CONNECTED CHANGES (#409.48) TRACK EDITS (#1) TRACK EDITS SUB-FILE (#409.481) EDIT NUMBER (#.01) sub-file multiple (#409.481) DATE EDITED (#.02) sub-file multiple (#409.481) EDITED BY (#.03) sub-file multiple (#409.481) TYPE OF ENTRY (#.04) sub-file multiple (#409.481) SERV. CONNECT (OK BY USER?) (#.05) sub-file multiple (#409.481) REVIEW REQUIRED? (#.06) sub-file multiple (#409.481) The following is a list of mail groups included in this patch: -------------------------------------------------------------- Mail Group: ----------- SDSC NIGHTLY TALLY SEND TO SITE The following is a list of options included in this patch: ---------------------------------------------------------- Option Name Type New/Modified ----------- ----------- ------------ SDMGR menu Modified USE AS LINK FOR MENU ITEMS SDSC CHECK COMPILE run routine New SEND TO SITE SDSC COMPILE run routine New SEND TO SITE SDSC EDIT BY DATE run routine New SEND TO SITE SDSC EDIT LISTMAN run routine New SEND TO SITE SDSC ENC REPORT run routine New SEND TO SITE SDSC FIRST PARTY REPORT run routine New SEND TO SITE SDSC MANAGER SUMMARY REPORT run routine New SEND TO SITE SDSC MENU menu New SEND TO SITE SDSC NIGHTLY COMPILE run routine New SEND TO SITE SDSC PROVIDER REPORT run routine New SEND TO SITE SDSC PROVIDER TOTAL REPORT run routine New SEND TO SITE SDSC PURGE NSC ENC run routine New SEND TO SITE SDSC RECOVERED REPORT run routine New SEND TO SITE SDSC REPORTS menu New SEND TO SITE SDSC SERVICE TOTAL REPORT run routine New SEND TO SITE SDSC SINGLE EDIT run routine New SEND TO SITE SDSC SITE PARAMETER run routine New SEND TO SITE SDSC THIRD PARTY REPORT run routine New SEND TO SITE SDSC UNBILL AMT REPORT run routine New SEND TO SITE SDSC USER REPORT run routine New SEND TO SITE SDSC USER TOTAL REPORT run routine New SEND TO SITE The following is a list of templates included in this patch: ------------------------------------------------------------ List Template Name Type New/Modified ------------------ ---- ------------ SDSC DETAIL PROTOCOL New SEND TO SITE SDSC REVIEW PROTOCOL New SEND TO SITE The following is a list of protocols included in this patch: ------------------------------------------------------------ Protocol Name Type New/Modified ------------- ---- ------------ SDSC ACCEPT action New SEND TO SITE SDSC CHANGE action New SEND TO SITE SDSC DETAIL action New SEND TO SITE SDSC MENU menu New SEND TO SITE SDSC RECORD MENU menu New SEND TO SITE SDSC SEND action New SEND TO SITE The following is a list of security keys included in this patch: ---------------------------------------------------------------- Security Key ------------ SDSC CLINICAL SEND TO SITE SDSC SUPER SEND TO SITE The following is a list of parameter definitions included in this patch: ------------------------------------------------------------------------ Parameter Name -------------- SDSC SITE PARAMETER SEND TO SITE Test Sites: Alpha Beta ----------- ----- ---- Bedford, MA X Bronx, NY X Fargo, ND X North Texas, TX X Puget Sound, WA X Tampa, FL X Pre/Post Installation Overview: ------------------------------- *********************** WARNING *********************** Disk space precaution for all sites that are currently running the Class III Service Connection Objective Update Tool (SCOUT) software product... Before installing this patch, please ensure that your production system has enough disk space available to easily contain another file of the same size as the ANU SERVICE CONNECTED CHANGES (#626140) file you are using with the Class III (SCOUT) software. This patch install will copy the existing records in the ANU SERVICE CONNECTED CHANGES (#626140) file and place them in the new SDSC SERVICE CONNECTED CHANGES (#409.48) file. **************************************************************************** Env/Post Installation Overview: ------------------------------- * Environment Check Routine (ENV^SD53P495): Programmer access is required for installing this patch. Prior to installation, the installer must ensure the DUZ(0) node of the DUZ array is set to the "@" symbol. * Post-Install Routine (POST^SD53P495): This routine entry point will determine if your site is running the Class III Service Connection Objective Update Tool (SCOUT) software which is being replaced by this patch. If this is true, a file conversion background job will run to file all valid Outpatient (O/P) Encounter records from the ANU SERVICE CONNECTED CHANGES (#626140) file into the SDSC SERVICE CONNECTED CHANGES (#409.48) file. * Site Parameter Definition value: The Post-Install routine (POST1^SD53P495) will create and set the initial value for the SDSC SITE PARAMETER to 30 DAYS. * File and Global Information: There is one new global, ^SDSC. The ^SDSC global contains the following (1) new file. Journaling File # File Name Global Root Recommended ------ ------------------------------ ------------- ----------- 409.48 SDSC SERVICE CONNECTED CHANGES ^SDSC(409.48, NO The estimated growth of the SDSC SERVICE CONNECTED CHANGES file (#409.48) is approximately two to five percent (2-5%) of the monthly total number of records within the OUTPATIENT ENCOUNTER file (#409.68). ================INSTALLATION INSTRUCTIONS ================= The following options need to be disabled before patch installation: Appointment Management [SDAM APPT MGT] Appointment Check-in/Check-out [SDAM APPT CHECK IN/OUT] Appointment Status Update [SDAM APPT UPDATE] Appointment Status Update Menu [SDAM APPT UPDATE MENU] Scheduling Manager's Menu [SDMGR] Please refer to the "Software Retrieval" and "Installation Instructions" sections of the DVB*4.0*58 patch description for instructions on how to acquire, install, and implement the patch software. ************** POST-INSTALLATION INSTRUCTIONS ************** 1. Background Option (Scheduling): Schedule the new Compile ASCD Encounters on a Nightly Basis [SDSC NIGHTLY COMPILE] option. Using the Schedule/Unschedule Options [XUTM SCHEDULE] option, schedule the option to run daily (i.e. RESCHEDULING FREQUENCY: D@2AM). 2. Security Keys allocation: Using the Allocation of Security Keys [XUKEYALL] option of the Key Management [XUKEYMGMT] menu, allocate the following security keys to the appropriate personnel. a. SDSC CLINICAL This key should be assigned to any clinical reviewer of encounters that are part of the Automated Service Connected Designation (ASCD) system. b. SDSC SUPER This key should be assigned to a supervisor reviewer of encounters that are part of the Automated Service Connected Designation (ASCD) system. 3. Mail Group members: The appropriate personnel should be added to the SDSC NIGHTLY TALLY. 4. If your site is NOT running the Class III (SCOUT) software, the following post-install message will be displayed: ****** The Class III (SCOUT) File Conversion is NOT necessary because the ANU SERVICE CONNECTED CHANGES (#626140) file does not exist on this system. Post-Install process terminated... ****** 5. If your site IS running the Class III (SCOUT) software, the following post-install message will be displayed: ****** Task ####### has been started to run the Class III (SCOUT) File Conversion. You will receive a MailMan message when this task is completed or if it has been manually stopped. ****** MailMan Message Example: ----------------------- Subj: SD*5.3*495 (SCOUT) FILE CONVERSION REPORT [#2012584] 03/02/07@12:21 49 lines From: POSTMASTER In 'IN' basket. Page 1 *New* ------------------------------------------------------------------------- Patch: SD*5.3*495 Automated Service Connected Designation ************ The existing Class III (SCOUT) file, ANU SERVICE CONNECTED CHANGES (#626140), which contains O/P Encounter records that have been compiled for additional Service Connected (SC) review, has been used to create a new Class I file which will provide the same functionality. Only valid O/P Encounter records from the Class III (SCOUT) file, ANU SERVICE CONNECTED CHANGES (#626140), have been filed into the new SDSC SERVICE CONNECTED CHANGES (#409.48) file. The new Automated Service Connected Designation (ASCD) Menu Options enable user access to the O/P Encounter records in the (#409.48) file. ************ SUMMARY OF PROCESSING RESULTS: ============================== <<< The Class III (SCOUT) File Conversion has Completed. >>> DATE/TIME TASK STARTED: Feb 26, 2007 1:19:29 pm DATE/TIME TASK COMPLETED: Feb 26, 2007 1:19:29 pm TOTAL O/P ENCOUNTER RECORDS FOUND: 2998 TOTAL O/P ENCOUNTER RECORDS CONVERTED: 2992 TOTAL O/P ENCOUNTER RECORDS NOT CONVERTED: 6 : REASON NOT CONVERTED: FILING ERROR TO (#409.48) O/P ENCOUNTER IEN: : 22224 : 22225 : REASON NOT CONVERTED: NO O/P ENCOUNTER RECORD (#409.68) O/P ENCOUNTER IEN: : 22174-PATIENT,ONE 10/19/05@14:25 : 22175-PATIENT,FIVE 2/9/07@9:15 : REASON NOT CONVERTED: NO (SCOUT) FILE DATA (#626140) O/P ENCOUNTER IEN: : 22176 : 22177 : : REASON NOT CONVERTED error message explanations: ------------------------------------------------ Three (3) possible error conditions might occur during the file conversion processing. They will be used to report the reason the O/P Encounter record was not converted. The IEN of the encounter will be displayed. They are as follows: # REASON NOT CONVERTED: -- --------------------- 1) FILING ERROR TO (#409.48) 2) NO O/P ENCOUNTER RECORD (#409.68) 3) NO (SCOUT) FILE DATA (#626140) Each error message is specific to the FileMan FILE that the post-install file conversion software could not reference when attempting to file the Class III O/P Encounter record into the new Class I file. - Class I file: SDSC SERVICE CONNECTED CHANGES (#409.48) - Class I file: OUTPATIENT ENCOUNTER (#409.68) - Class III file: ANU SERVICE CONNECTED CHANGES (#626140) * Please refer to the REASON NOT CONVERTED Error List examples in the MailMan message above: ---------------------- Note: When there are records that could not be converted, it will be the responsibility of the site to review each error and determine if that record needs to be manually entered into the new SDSC SERVICE CONNECTED CHANGES (#409.48) file for auditing purposes. Re-Starting or Re-Running the Post-Install process: --------------------------------------------------- The Class III (SCOUT) File Conversion can be run more than one time. Only records that have not previously been looked at for converting will be processed. Please restart the post-install process from the following programmer's prompt: D POST^SD53P495 A new MailMan message will be sent for each new run. This message will contain information from all previously run post-install processing and will be displayed as part of the summary processing results. SUMMARY OF PROCESSING RESULTS: ============================== <<< The Class III (SCOUT) File Conversion has Completed. >>> DATE/TIME TASK STARTED: Feb 26, 2007 1:19:29 pm DATE/TIME TASK COMPLETED: Feb 26, 2007 1:19:29 pm DATE/TIME LAST RUN: Feb 26, 2007 1:19:17 pm TOTAL O/P ENCOUNTER RECORDS FOUND: 2998 TOTAL RECORDS PREVIOUSLY CONVERTED: 2992 TOTAL O/P ENCOUNTER RECORDS CONVERTED: 2992 TOTAL O/P ENCOUNTER RECORDS NOT CONVERTED: 6 : REASON NOT CONVERTED: FILING ERROR TO (#409.48) O/P ENCOUNTER IEN: : 22224 : 22225 : REASON NOT CONVERTED: NO O/P ENCOUNTER RECORD (#409.68) O/P ENCOUNTER IEN: : 22174-PATIENT,ONE 10/19/05@14:25 : 22175-PATIENT,FIVE 2/9/07@9:15 : REASON NOT CONVERTED: NO (SCOUT) FILE DATA (#626140) O/P ENCOUNTER IEN: : 22176 : 22177 : : 6. If your site IS running the Class III (SCOUT) software, following the install you will need to disable the SCOUT menu options. Routine Information: ==================== The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: SD53P495 Before: n/a After: B87466494 **495** Routine Name: SDCOM Before: B5826254 After: B6631731 **15,60,105,132,466,495** Routine Name: SDSCAPI Before: n/a After: B21470995 **495** Routine Name: SDSCCHK Before: n/a After: B39800348 **495** Routine Name: SDSCCLM Before: n/a After: B1275412 **495** Routine Name: SDSCEDT Before: n/a After: B76725826 **495** Routine Name: SDSCINS Before: n/a After: B11936927 **495** Routine Name: SDSCLM Before: n/a After: B8362461 **495** Routine Name: SDSCLM1 Before: n/a After: B677645 **495** Routine Name: SDSCLST Before: n/a After: B5358321 **495** Routine Name: SDSCMSR Before: n/a After: B50399971 **495** Routine Name: SDSCNSCP Before: n/a After: B15365722 **495** Routine Name: SDSCOMP Before: n/a After: B63599781 **495** Routine Name: SDSCPRG Before: n/a After: B10441801 **495** Routine Name: SDSCPRM Before: n/a After: B856844 **495** Routine Name: SDSCPRV Before: n/a After: B25452487 **495** Routine Name: SDSCRP1 Before: n/a After: B37970877 **495** Routine Name: SDSCRP2 Before: n/a After: B51118024 **495** Routine Name: SDSCRPT1 Before: n/a After: B49147516 **495** Routine Name: SDSCRPT2 Before: n/a After: B34356180 **495** Routine Name: SDSCSSD Before: n/a After: B17495006 **495** Routine Name: SDSCUSR Before: n/a After: B25529113 **495** Routine Name: SDSCUTL Before: n/a After: B29887017 **495** Routine list of preceding patches: 466 ============================================================================= User Information: Entered By : MORRISON,JENNIFER Date Entered : OCT 17, 2006 Completed By: WOEHRLE,MARGARET Date Completed: OCT 03, 2007 Released By : BENBOW,PHYLLIS O Date Released : OCT 22, 2007 ============================================================================= Packman Mail Message: ===================== No routines included