$TXT Created by NABER,DAVID at DEVVCC.FO-ALBANY.MED.VA.GOV (KIDS) on Wednesday, 12/08/10 at 11:35 ============================================================================= Run Date: DEC 14, 2010 Designation: SD*5.3*568 Package : SD - SCHEDULING Priority: Mandatory Version : 5.3 SEQ #468 Status: Released Compliance Date: JAN 14, 2011 ============================================================================= Associated patches: (v)SD*5.3*380 <<= must be installed BEFORE `SD*5.3*568' (v)SD*5.3*485 <<= must be installed BEFORE `SD*5.3*568' (v)SD*5.3*549 <<= must be installed BEFORE `SD*5.3*568' (v)SD*5.3*570 <<= must be installed BEFORE `SD*5.3*568' Subject: CLINIC STOP FILE (#40.7) AUDIT & LOCKDOWN Category: - Routine - Data Dictionary - Enhancement (Mandatory) Description: ============ **NOTE** Before installing this patch, check your P-MESSAGE-HFS device entry in the DEVICE file (#3.5) to make sure it exists and works. As part of the Fiscal Year (FY) 11 Decision Support System (DSS) updates, the CLINIC STOP file (#40.7) will be locked down. After installation of this patch, only entries related to "local" AMIS REPORTING STOP CODES (field #1, file 40.7), will be editable. The following AMIS REPORTING STOP CODES are considered "local": 451-456, 458-473, 475-479, and 482-485. For these local entries, only the NAME (field #.01, file 40.7) field will be editable. All other fields will be uneditable. A new option Edit Clinic Stop Code Name - Local Entries Only option [SD EDIT LOCAL STOP CODE NAME] will be added to the Supervisor Menu [SDSUP] and will allow you to edit entries in the CLINIC STOP file that are considered local based on the AMIS REPORTING STOP CODE assigned to it, as described above. As part of the CLINIC STOP (#40.7) file lock down, a check for entries with duplicate AMIS REPORTING STOP CODES (field #1, file #40.7) will be conducted. If there are any duplicates that require user intervention, an email message will be sent to the holders of the ECXMGR and SD SUPERVISOR keys as well as the CSPIMS mail group on FORUM for resolution. If there are no entries to be updated, the users will receive an "all clear" email. In addition, a comparison will be made between the entries in the local CLINIC STOP (#40.7) file and a "gold" listing of CLINIC STOP entries. Any entries missing from the local file will be added. Any local entries that are not in the gold file will be inactivated. Any differences between the local entries and the gold listing will cause the local entries to be updated to match what's in the gold listing. An email message detailing the updates completed during the review will also be sent to the holders of the ECXMGR and SD SUPERVISOR keys. The DSS Identifier Non-Conforming Clinics Report [ECX CLN STOP REP] option will be queued to run in the background and any output will be sent to the holders of the ECXMGR and SD SUPERVISOR keys. The Non-Conforming Clinics Stop Code Report [SD CLN STOP CODE REP] option will be queued to run in the background and any output will be sent to the holders of the SD SUPERVISOR and ECXMGR keys. For both of the non-conforming reports, any entries identified as having invalid/inactive stop codes should be updated to use active stop codes. If you receive a "duplicates could not be resolved" message, please contact ITM (formerly IRM) for assistance. Both of the non-conforming reports utilize the P-MESSAGE-HFS device to send the output to the appropriate recipients. The reports will print even if there are no clinics to be updated. **NOTE** If you do not receive the email messages as a result of the patch installation, it's possible there is a problem with your P-MESSAGE-HFS set up. In that case, you'll need to run the reports manually (the option names are listed above). This patch will also introduce a new option, Clinic Edit Log Report [SD CLINIC EDIT LOG], which will be placed on the Setup for DSS Clinic Information [ECX SETUP CLINIC] menu. This option will allow you to identify changes made to entries in the HOSPITAL LOCATION file (#44). This report will be sortable by USER NAME or by DATE CHANGED and will identify the field changed (each change is reported individually) and will include the old and new values as well as who made the change and which entry was changed. This option may also be assigned as a standalone option for Scheduling users, as needed. As a result of adding auditing to fields in the HOSPITAL LOCATION file (#44), the recompiling of the SDB input template is required. This will be done automatically as part of the post-install tasks. This patch addresses the following New Service Request (NSR): ------------------------------------------------------------- There is no NSR associated with this patch. This patch addresses the following Remedy Ticket(s): ---------------------------------------------------- There are no Remedy tickets associated with this patch. Components Sent With Patch -------------------------- The following is a list of files included in this patch: UP SEND DATA DATE SEC. COMES SITE RSLV FILE # NAME DD CODE W/FILE DATA PTS -------------------------------------------------------------------- 40.7 CLINIC STOP YES YES NO 44 HOSPITAL LOCATION YES NO NO The following is a list of fields included in this patch: FIELD FILE ------------------------------------------------------------------------ NAME (#.01) HOSPITAL LOCATION (#44) NON-COUNT CLINIC? (Y OR N) (#2502) HOSPITAL LOCATION (#44) CREDIT STOP CODE (#2503) HOSPITAL LOCATION (#44) INACTIVATE DATE (#2505) HOSPITAL LOCATION (#44) REACTIVATE DATE (#2506) HOSPITAL LOCATION (#44) AMIS REPORTING STOP CODE (#1) CLINIC STOP (#40.7) INACTIVE DATE (#2) CLINIC STOP (#40.7) CONVERT TO STOP CODE (#3) CLINIC STOP (#40.7) COST DISTRIBUTION CENTER (#4) CLINIC STOP (#40.7) RESTRICTION TYPE (#5) CLINIC STOP (#40.7) RESTRICTION DATE (#6) CLINIC STOP (#40.7) The following is a list of options included in this patch: Option Name Type New/Modified ------------------ ---- ------------ SD CLINIC EDIT LOG SEND TO SITE New SD EDIT LOCAL STOP CODE NAME SEND TO SITE New Documentation Retrieval: ------------------------ Updated documentation describing the new functionality introduced by this patch is available. The preferred method is to FTP the files from download.vista.med.va.gov. This transmits the files from the first available FTP server. Sites may also elect to retrieve documentation directly from a specific server as follows: Albany ftp.fo-albany.med.va.gov Hines ftp.fo-hines.med.va.gov Salt Lake City ftp.fo-slc.med.va.gov The documentation, including User and Technical manuals will be in the form of Adobe Acrobat files. Documentation can also be found on the VA Software Document Library at: http://www4.va.gov/vdl/application.asp?appid=100 Below is a list of the files related to this patch that will be needed and available via the FTP sites listed above. File Description File Name FTP Mode ----------------------------------------------------------------------- Scheduling Module User Manual SD_5_3_568_PIMS_SUPV.pdf Binary Supervisor Menu (SUPV) Scheduling Module User Manual (SDBE) SD_5_3_568_PIMS_SDBE.pdf Binary TEST SITES ---------- Big Spring Boston Cheyenne Heartland West Little Rock North Texas INSTALLATION ============ This patch may be installed with users on the system although it is recommended that it be installed during non-peak hours to minimize potential disruption to users. This patch should take less than 5 minutes to install. **NOTE** Before installing this patch, check your P-MESSAGE-HFS device entry in the DEVICE file (#3.5) to make sure it exists and works. If you do not have a P-MESSAGE-HFS device, the non-conforming reports will not be automatically delivered to the recipients. You may add P-MESSAGE-HFS as a mnemonic to any existing P-MESSAGE type device entry to allow the reports to be delivered. The non-conforming reports may also be run manually, should you not have the P-MESSAGE-HFS device set-up before installation. 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu. 2. From the Kernel Installation and Distribution System Menu, select the Installation menu. 3. From this menu, you may elect to use the following options (when prompted for INSTALL NAME, enter SD*5.3*568): a. Backup a Transport Global b. Compare Transport Global to Current System c. Verify Checksums in Transport Global 4. Use the Install Package(s) option and select the package SD*5.3*568. 5. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//', you may respond NO. 6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', you may respond NO. 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', respond NO. 8. If prompted 'Delay Install (Minutes): (0-60): 0//; respond '0'. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.3;Scheduling;**[Patch List]**;Aug 13, 1993;Build 14 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: SD44AUDI Before: n/a After: B10879260 **568** Routine Name: SD53P568 Before: n/a After:B103417051 **568** Routine Name: SDB Before: B17221185 After: B17476813 **20,63,167,455,568** Routine Name: SDNACT Before: B19685388 After: B20033650 **63,380,549,568** Routine Name: SDREACT Before: B19399143 After: B20261844 **63,167,380,568** Routine Name: SDUTL3 Before: B6616869 After: B12703154 **30,39,41,148,177,568** Routine list of preceding patches: 177, 455, 549 ============================================================================= User Information: Entered By : ELLIS,DONNA Date Entered : FEB 11, 2010 Completed By: SBERRO,SANDRA Date Completed: DEC 13, 2010 Released By : BENBOW,PHYLLIS O Date Released : DEC 14, 2010 ============================================================================= Packman Mail Message: ===================== $END TXT