$TXT Created by G at CHY0077.FO-BAYPINES.DOMAIN.EXT (KIDS) on Thursday, 08/27/26 at 09:31 ============================================================================= Run Date: SEP 08, 2026 Designation: SD*5.3*950 Package : SD - SCHEDULING Priority: Mandatory Version : 5.3 SEQ #799 Status: Released Compliance Date: SEP 22, 2026 ============================================================================= Associated patches: (v)SD*5.3*940 <<= must be installed BEFORE `SD*5.3*950' (v)SD*5.3*949 <<= must be installed BEFORE `SD*5.3*950' Subject: SCHEDULING UPDATES TO SUPPORT FRONT END APPS Category: - Routine - Other Description: ============ ************************************************************************** * This patch should be queued to be installed during off hours to * * minimize errors being logged as users actively call the Remote * * Procedure Calls (RPC) being updated by the patch. * * * * This patch should NOT be installed or queued to be installed * * during the installation of any other Scheduling patch. * ************************************************************************** VistA Scheduling (VS) patch SD*5.3*950 includes several defect corrections and enhancements including: The logic supporting the following Remote Procedure Calls (RPC) were updated to return the patient-friendly clinic name when it is defined and the clinic name if it isn't: SDES PRINT APPT LETTER SDES PRINT APPT LETTERS SDES2 PRINT APPT LETTER SDES2 PRINT APPT LETTERS The logic supporting the SDES2 DISPOSITION APPT REQ RPC was updated to store the name of the RPC that is making the update in the EAS RPC (#100) field and the value in from the SDCONTEXT("AppID") input parameter, when defined, into the EAS APPID (#101) field. The RPC's definition was also updated to note the new SDCONTEXT("AppID") input parameter. The logic supporting the SDES2 DISPOSITION RECALL REQ RPC was updated to store the name of the RPC that is making the update in the EAS RPC (#100) field and the value in from the SDCONTEXT("AppID") input parameter, when defined, into the EAS APPID (#101) field. The RPC's definition was also updated to note the new SDCONTEXT("AppID") input parameter. The SDES2 ADD CONTACT ATTEMPT RPC definition was updated to include details for the new SDCONTEXT("AppID") input parameter. The three post installs that were originally planned for deployment in SD*5.3*949 patch were moved into SD*5.3*950 and associated documentation was updated. EHRM Impact Statement: ---------------------- This patch should have no EHRM impact, and can be installed at all sites, including EHRM converted sites. Patch Components: New/Modified/Deleted ----------------- -------------------- Files & Fields Associated: New/Modified/Deleted -------------------------- -------------------- File Name (Number) Field Name 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 --------------------- -------------------- SDES2 ADD CONTACT ATTEMPT Modified SDES2 DISPOSITION APPT REQ Modified SDES2 DISPOSITION RECALL REQ Modified Parameter Definitions Associated: --------------------------------- N/A Additional Information: ----------------------- N/A New Service Requests (NSRs): N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1) VSE-11691: VistA: Use Patient friendly name for the clinic letters. Problem: As a patient, I would like my appointment-related letters and list of appointments to use a patient-friendly clinic name, so that I know where my appointment is located. Resolution: The logic supporting the following Remote Procedure Calls (RPC) were updated to return the patient-friendly clinic name when it is defined and the clinic name if it isn't: SDES PRINT APPT LETTER SDES PRINT APPT LETTERS SDES2 PRINT APPT LETTER SDES2 PRINT APPT LETTERS 2) VSE-11843: VistA: Update SDES2 DISPOSITION APPT REQ to store RPC on creation. Problem: When files are being updated within the VistA system the Acheron audit ID should be stored when updates are done via Acheron. Current logic within SDES2 DISPOSITION APPT REQ updates the audit ID; however, the system does not update which RPC was invoked to make the update. Resolution: The logic supporting the SDES2 DISPOSITION APPT REQ RPC was updated to store the name of the RPC that is making the update in the EAS RPC (#100) field and the value in from the SDCONTEXT("AppID") input parameter, when defined, into the EAS APPID (#101) field. The RPC's definition was also updated to note the new SDCONTEXT("AppID") input parameter. 3) VSE-11844: VistA: Update SDES2 DISPOSITION RECALL REQ to store RPC on creation. Problem: When files are being updated within the VistA system the Acheron audit ID should be stored when updates are done via Acheron. Current logic within SDES2 DISPOSITION RECALL REQ RPC updates the audit ID; however, the system does not update which RPC was invoked to make the update. Resolution: The logic supporting the SDES2 DISPOSITION RECALL REQ RPC was updated to store the name of the RPC that is making the update in the EAS RPC (#100) field and the value in from the SDCONTEXT("AppID") input parameter, when defined, into the EAS APPID (#101) field. The RPC's definition was also updated to note the new SDCONTEXT("AppID") input parameter. 4) VSE-12216: VistA: Modify RPC description for SDES2 ADD CONTACT ATTEMPT. Problem: Need to update the RPC description to include the SDCONTEXT("AppID") input parameter to the SDCONTEXT input parameter for SDES2 ADD CONTACT ATTEMPT. Resolution: The SDES2 ADD CONTACT ATTEMPT RPC definition was updated to include details for the new SDCONTEXT("AppID") input parameter. 5) VSE-12227: VistA: Include all Patch 949 post installs into Patch 950. Problem: Need to move all the post installs that were originally planned for deployment in SD*5.3*949 patch into SD*5.3*950 and updated associated documentation. Resolution: The three post installs that were originally planned for deployment in SD*5.3*949 patch were moved into SD*5.3*950 and associated documentation was updated. Test Sites: ----------- Salt Lake City, UT (SLC) San Diego, CA (SDC) Test Sites - SNOW Change Order #: --------------------------------- Salt Lake City, UT (SLC): CHG0770822 San Diego, CA (SDC): CHG0771772 Software and Documentation Retrieval Instructions: ---------------------------------------------------- Software is distributed by PackMan message. Other Software Files: This release also includes documentation and other software files. They can be obtained at: https://download.vista.domain.ext/index.html/SOFTWARE/ File Title File Name Format -------------------------------------------------------------------------- PIMS Technical Manual SD_PIMS_TM Binary Documentation describing the new functionality is included in this release. Documentation can be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/. Documentation can also be obtained at https://download.vista.domain.ext/index.html/SOFTWARE. Documentation Title File Name --------------------------------------------------------------------- PIMS Technical Manual SD_PIMS_TM Patch Installation: ------------------- Pre/Post Installation Overview: ------------------------------- Sites will read the National Patch Module (NPM) MailMan message and extract the Kernel Installation & Distribution System (KIDS) build. Then sites will use the Kernel Installation & Distribution System [XPD MAIN] menu to perform checks and install the patch. 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 5 minutes to install. Installation Instructions: 1. Choose the PackMan message containing this build. Then select the INSTALL/CHECK MESSAGE PackMan option to load the build. 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 SD*5.3*950. NOTE: Using will not bring up a Multi-Package build even if it was loaded immediately before this step. It will only bring up the last patch in the build. B. Select the Backup a Transport Global option to create a backup message. You must use this option and specify what to backup; the entire Build or just Routines. The backup message can be used to restore the routines and components of the build to the pre-patch condition. i. At the Installation option menu, select Backup a Transport Global ii. At the Select INSTALL NAME prompt, enter SD*5.3*950 iii. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build (including Routines) R Routines Only Backup Type: B// iv. When prompted "Do you wish to secure your build? NO//", press and take the default response of "NO". v. When prompted with, "Send mail to: Last name, First Name", press to take default recipient. Add any additional recipients. vi. When prompted with "Select basket to send to: IN//", press and take the default IN mailbox or select a different mailbox. 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 NO. ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer NO. iii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer NO. Post-Installation Instructions: ------------------------------- Back-Out Plan/Roll Back Plan: ----------------------------- 1. Load the Backup MailMan Message a. Go into MailMan and find the backup message created in step 3a of the installation process and read that message. b. At the "Type to continue or '^' to exit:" prompt enter ^ to get to the command prompt. c. At the command prompt enter X for eXtract and press enter. d. At the "Select PackMan function:" prompt enter 6 for INSTALL/CHECK MESSAGE and press enter. e. At the "OK to Continue with Load? NO//" prompt, type YES and press enter. f. At the "Want to Continue with Load? YES//" prompt, press enter. g. Exit MailMan. 2. Go Into the Kernel Installation & Distribution System (KIDS) and load and install the backup like you would a regular patch. a. Enter D ^XUP at the command prompt. b. At the "Select OPTION NAME:" prompt, enter Kernel Installation & Distribution System" and press enter. c. From the main KIDS menu, select the Installation ... option. d. From the Installation ... option, select 6 Install Package(s). e. At the "Select INSTALL NAME:" prompt enter SD*5.3*950b. f. If prompted for "Want KIDS to INHIBIT LOGONs during the install? NO//" take the default by pressing enter. g. If prompted for "Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//" take the default by pressing enter. h. At the DEVICE: prompt, enter the output device of your choice. i. Verify that the SD*5.3*950b backup installs without any issues Routine Information: ==================== The second line of each of these routines now looks like: ;;5.3;Scheduling;**[Patch List]**;Aug 13, 1993;Build 6 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: SDES2APTLETTER Before:B135335854 After:B136512973 **895,898,899,901,903,922,909,950** Routine Name: SDES2ARCLOSE Before: B16649988 After: B17333303 **866,873,875,909,929,940,950** Routine Name: SDES2DISPRECALL Before: B13553271 After: B14739070 **866,895,922,909,950** Routine Name: SDES950P Before: n/a After:B155281909 **950** Routine Name: SDESAPPTLETTERS Before:B128867061 After:B130058772 **824,895,903,922,950** Routine Name: SDLT Before: B31508296 After: B33591885 **185,213,281,330,398,523,441, 555,622,641,680,705,917,922, 950** Routine Name: SDRRISRU Before: B23449413 After: B25173716 **536,627,648,799,818,866,895, 909,950** Routine list of preceding patches: 940 ============================================================================= User Information: Entered By : Date Entered : APR 29, 2026 Completed By: Date Completed: SEP 08, 2026 Released By : Date Released : SEP 08, 2026 ============================================================================= Packman Mail Message: ===================== $END TXT