============================================================================= Run Date: SEP 14, 2021 Designation: SD*5.3*787 Package : SD - SCHEDULING Priority: Mandatory Version : 5.3 SEQ #645 Status: Released Compliance Date: OCT 01, 2021 ============================================================================= Associated patches: (v)SD*5.3*770 <<= must be installed BEFORE `SD*5.3*787' Subject: FY22 STOP CODE CHANGES Category: - Routine Description: ============ Scheduling patch, SD*5.3*787, provides fiscal year 2022 annual updates to the CLINIC STOP (#40.7) file as requested by the Office of Finance, Managerial Cost Accounting Office (MCAO). When inactivating stop codes in the CLINIC STOP (#40.7) file, the DSS UNITS (#724) file also needs to be updated. Therefore, this patch is being released along with Event Capture patch EC*2.0*155, that inactivates The DSS Units. Both patches will be bundled together with this Scheduling Patch being the primary. Note: Patch SD*5.3*787 (FY22 STOP CODE CHANGES) is being released along with patch EC*2.0*155 (FY22 INACTIVE STOP CODE DSS UNIT REVIEW) in a host file SD53_787_EC20_155.KID. *** IMPORTANT NOTE *** ************************************************************************** * This patch is being released with a compliance date of October 1, * * 2021 and should be installed as close to Close of Business (COB) on * * September 30, 2021 as possible, but not after October 1, 2021. Early * * installation of this patch could result in transmission of incorrect * * Stop Codes that will result in errors from Austin. * * * * Coordination with the MAS (Medical Administration Service) PAS * * (Program Application Specialist)/ADPAC (Automated Data Processing * * Application Coordinator) is imperative as patch SD*5.3*787 will * * cause changes to the CLINIC STOP (#40.7) file. * * * * Testing can be done in a site's mirror account before installation * * in production to verify changes. * * * * Patch SD*5.3*787 modifies and creates Stop Codes effective October 1, * * 2021; therefore, installing early may modify certain Stop Codes that * * may currently be in use at your site. * * * * It is advised that clinics with Stop Codes with restriction date/type * * changes should be corrected as soon as possible after installation. * * * * Please keep in mind that new Stop Codes should not be assigned in * * MAS/Scheduling until October 1, 2021 as the PCE encounters bearing * * FY22 Stop Codes will not be accepted in in Austin until that date. * * * * All other MAS Stop Code changes should be made as early as possible * * on October 1, 2021. * ************************************************************************** Instructions for the FY22 Stop Code Patch: Patch SD*5.3*787 makes additions and changes to the CLINIC STOP (#40.7) File as of October 1, 2021. No clinic can be created using any new Stop Codes contained in the patch until after this patch is implemented. Scheduling & patch installer should coordinate to perform the following sequence: 1. Patch installer installs the patch late on September 30 or early on October 1, 2021. 2. Scheduling staff: Run the Non-Conforming Clinics Stop Code Report [SD CLN STOP CODE REP]menu option to list those clinics that need changes in the HOSPITAL LOCATION (#44) file for FY22. 3. Scheduling staff: Make changes in the HOSPITAL LOCATION (#44) file so that the clinics will have the correct Stop Codes in place for October 1st clinic appointments. MCA Staff: 1. Before October 1 (prior to installation of the patch) run Option 2: Create DSS Clinic Stop Code File [ECXSCLOAD] menu option from the Setup for DSS Clinic Information [ECX SETUP CLINIC]menu option. 2. Follow normal procedures to run the DSS CLI Extract for September 2021. It is the create and edit, not the 'approve', that changes the values included in the CLI extract. Perform normal AUDITS for the CLI Extract. 3. DO NOT make changes for October clinics at this time. 4. Between October 19 and 31, after auditing and receiving confirmation of successful deblocking of the transmitted September CLI Extract, proceed with FY22 Stop Code changes to the DSS Clinics and Stop Codes Worksheet: a. After the September extract has been run, transmitted and is considered final (in your mind, no re-run/re-transmit needed), you may run Option 2 CREATE DSS Clinic Stop Code File [ECXSCLOAD]. This option creates local entries in the CLINICS AND STOP CODES (#728.44) file and compares this file to the HOSPITAL LOCATION (#44) file to see if there are any differences since the last time the file was reviewed. b. After Option 2 has completed, use the Option 3: Clinics and DSS Stop Codes Print [ECXSCLIST]. This option produces a worksheet of (A) All Clinics, (C) Active, (I) Inactive, or only the (U) Unreviewed Clinics that are awaiting approval. c. Run Option 7: Clinic & Stop Codes Validity Report [ECX STOP CODE VALIDITY]. This step will check that all Stop Codes conform. Note: a 'blank' output indicates there are no problems with Stop Code and credit stop validity. d. Update for FY22 as needed using Option 4: Enter/Edit Clinic Parameters [ECXSCEDIT] menu option. e. Approve changes using Option 5: Approve Reviewed DSS Clinic Worksheet [ECXSCAPPROV] menu option. Finalize all Stop Code changes on the worksheet to be ready to run the October DSS CLI Extract. f. MCA teams with questions, please log a ticket with MCAO Help Desk, https://mcaapp.vha.domain.ext/MCAOHelpDesk/Default.aspx. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File Number New/Modified/Deleted --------- ----------- -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A Additional Information: ----------------------- New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: 1. INC18133748 FY22 Stop Code changes Problem: -------- The Office of Finance, Managerial Cost Accounting Office (MCAO), has requested Fiscal Year 2022 Stop Code updates to the CLINIC STOP (#40.7) file. Resolution: ----------- Post-install routine, SD53FY22, has been created to update the CLINIC STOP (#40.7) file by inactivating one (1) Stop Code and change the name and restriction date of two (2) existing Stop Codes; effective 10/01/2021. Listed below are the applicable Stop Code updates: Stop Code being inactivated (will take effect on 10/1/2021): Code Name Inactivation Date 320 DEMENTIA CLINIC 10/1/2021 Stop Code with name and restriction date changes (will take effect when the patch is installed): Stop Code: 189 Old Name: STORE & FORWARD HOME PROV SITE New Name: S&F HOME NON VA PROV SITE Old Restriction Date: APR 01, 2013 New Restriction Date: OCT 01, 2021 Stop Code: 698 Old Name: SF TELECARE FROM NONVAMC PROV New Name: REMOTE PT MONITOR PROV SITE Old Restriction Date: OCT 01, 2011 New Restriction Date: OCT 01, 2021 Test Sites: ----------- San Diego VAMC Baltimore VAMC Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released using a host file. The host file is available at the following location: /srv/vista/patches/SOFTWARE/SD53_787_EC20_155.KID Use SFTP ASCII protocol. Patch Installation: ------------------- Pre/Post Installation Overview: This patch should be installed as close to 09/30/2021 as possible, but not after 10/01/2021. EC*2.0*155 will queue the inactivation of any DSS Units, that are set to send no records and have an inactive/invalid stop code, for 10/01/2021 at 1:00 AM. If this patch is installed after that time, the post-install will queue immediately. Pre-Installation Instructions: 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 3 minutes to install. Installation Instructions: 1. Use the Load a Distribution option contained on the Kernel Installation and Distribution System Menu to load the Host file. When prompted to "Enter a Host File:" enter /srv/vista/patches/SOFTWARE/SD53_787_EC20_155.KID 2. From the Kernel Installation and Distribution System Menu, select the Installation Menu. From this menu, a. Select the Verify Checksums in Transport Global option to confirm the integrity of the routines that are in the transport global. When prompted for the INSTALL NAME enter the patch name. (ex. SD*5.3*787) b. The Backup a Transport Global option should be skipped as this patch implements a new routine. c. You may also elect to use the following options: i. Print Transport Global - This option will allow you to view the components of the KIDS build. ii. 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 of the components of this patch, such as routines, DDs, templates, etc. d. Select the Install Package(s) option and choose the patch to install. i. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//', answer . ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer . iii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer . Post-Installation Instructions: 1. Details of the changes applied by this patch are provided during the installation and may also be reviewed with the Install File Print option on the Utilities menu on the Kernel Installation and Distribution System menu. 2. It is important to check the CLINIC STOP (#40.7) file post installation to make sure that all of the updates are correctly reflected in the CLINIC STOP (#40.7) file. If any discrepancies are found, you should enter a ServiceNow (SNOW) ticket. 3. You may delete the routine, SD53MY21, from your production system after the patch has been successfully verified. Back-Out/Roll Back Plan: ------------------------ Due to the complexity of this patch, it is not recommended for back-out, and a restore from a backup of the Transport Global should not be attempted. In the event that a patch installer decides to back out this patch, the patch installer should contact the Enterprise Service Desk (ESD) to submit a ServiceNow (SNOW) helpdesk ticket. The development team will need to issue a follow-on patch in order to comprehensively back-out this patch and restore the system to a functioning state. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.3;Scheduling;**[Patch List]**;Aug 13, 1993;Build 2 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: SD53FY22 Before: n/a After: B67487926 **787** ============================================================================= User Information: Entered By : Date Entered : MAY 04, 2021 Completed By: Date Completed: SEP 14, 2021 Released By : Date Released : SEP 14, 2021 ============================================================================= Packman Mail Message: ===================== No routines included