$TXT Created by G at CHY0077.FO-BAYPINES.DOMAIN.EXT (KIDS) on Friday, 09/11/26 at 12:30 ============================================================================= Run Date: SEP 30, 2026 Designation: SD*5.3*954 Package : SD - SCHEDULING Priority: Mandatory Version : 5.3 SEQ #801 Status: Released Compliance Date: OCT 15, 2026 ============================================================================= Associated patches: (v)SD*5.3*944 <<= must be installed BEFORE `SD*5.3*954' (v)SD*5.3*951 <<= must be installed BEFORE `SD*5.3*954' (v)SD*5.3*953 <<= must be installed BEFORE `SD*5.3*954' Subject: SCHEDULING UPDATES TO SUPPORT FRONT END APPS Category: - Routine - Other - Enhancement (Mandatory) 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*954 includes several defect corrections and enhancements including: The new SDES2 GET PATIENT REG 2 Remote Procedure Call (RPC) will include the BAD ADDRESS INDICATOR (#.121) field in its returned JavaScript Object Notation (JSON) object for Integrated Scheduling Solution. The SDES2 DEL CLINIC REACT DATE RPC description was updated to remove a typo. The SDES2 CREATE APPOINTMENT2 RPC was updated to include a check for errors after the initial Request Lock check. If errors are detected, the appropriate error information is included in the return JSON object. The logic supporting the SDES2 DEL CLINIC REACT DATE RPC was updated to only have objects for Clinic and Error. The logic that validates the user in the SDCONTEXT array was updated to not error when the user is a visitor who doesn't have existing access/verify codes. 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 ----------- ---- -------------------- 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 DEL CLINIC REACT DATE Modified SDES2 GET PATIENT REG 2 New Parameter Definitions Associated: --------------------------------- N/A Additional Information: ----------------------- N/A New Service Requests (NSRs): N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1) VSE-12381: VistA: Create new version of SDES2 GET PATIENT REGISTRATION RPC to standardize output object for ISS needs. Problem: Modify SDES2 GET PATIENT REGISTRATION RPC to add bad address indicators to the different addresses (where applicable). Resolution: The new SDES2 GET PATIENT REG 2 Remote Procedure Call (RPC) will include the BAD ADDRESS INDICATOR (#.121) field in its returned JavaScript Object Notation (JSON) object for Integrated Scheduling Solution. 2) VSE-12427: VistA: Modify RPC description for SDES2 DEL CLINIC REACT DATE. Problem: Need to update the SDES2 DEL CLINIC REACT DATE RPC description to remove typo. Resolution: The SDES2 DEL CLINIC REACT DATE RPC description was updated to remove a typo. 3) VSE-12493: VistA: Modify SDES2 CREATE APPOINTMENT2 to add check for ERRORS array after initial Request Lock check. Problem: It was discovered in Charleston that there is an issue with the SDES2 CREATE APPOINTMENT2 RPC where it does not check the ERRORS array after calling the API that checks to see if the reference Request record is locked. Therefore, if a Request is locked and the ERRORS array is set, an appointment will still be created, but since there's a ERRORS array, the RPC ultimately passes back the error without including the Appointment object. The original RPC, SDES2 CREATE APPOINTMENT, is already correctly checking this array. Resolution: The SDES2 CREATE APPOINTMENT2 RPC was updated to include a check for errors after the initial Request Lock check. If errors are detected, the appropriate error information is included in the return JSON object. 4) VSE-12518: VistA: Modify SDES2 DEL CLINIC REACT DATE to only send one object in return. Problem: Need to update the logic supporting the SDES2 DEL CLINIC REACT DATE RPC to remove RETN("Clinic","ID") from the returned JSON object. Resolution: The logic supporting the SDES2 DEL CLINIC REACT DATE RPC was updated to only have objects for Clinic and Error. 5) VSE-12552: VistA: Modify the logic being called to verify a user being sent in the SDCONTEXT array to allow for universal scheduling. Problem: It was identified that when the ESSO RPC is using to create a new user in the VistA Instance to support universal scheduling, that the current logic is erroring out due because the visitor DUZ does not have an access/verify code. In order to support universal scheduling a change is requested to recognize that the user is a visitor and not error out. Resolution: The logic that validates the user in the SDCONTEXT array was updated to not error when the user is a visitor who doesn't have existing access/verify codes. Test Sites: ----------- Dallas, TX (NTX) Iron Mountain, MI (IRO) Test Sites - SNOW Change Order #: --------------------------------- Dallas, TX (NTX): CHG0786337 Iron Mountain, MI (IRO): CHG0786340 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. After the post install has finished running, sites can delete the SDES954P routine using the Delete Routines [XTRDEL] option if they wish. 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*954. 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*954 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*954b. 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*954b 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 4 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: SDES2APPTUTIL Before:B111107103 After:B111300726 **866,871,875,877,878,880,881, 890,893,905,907,922,909,944, 954** Routine Name: SDES2CANCELAPPT Before:B182558925 After:B185630280 **869,871,873,875,877,878,880, 886,897,918,920,909,929,944, 954** Routine Name: SDES2CANCELAPPT2 Before:B174879273 After:B175542424 **943,944,954** Routine Name: SDES2CREATEAPPT2 Before:B200648861 After:B203201286 **940,941,944,954** Routine Name: SDES2DELCLNREADT Before: B33012235 After: B32211026 **953,954** Routine Name: SDES2GETREGS2 Before: n/a After:B169987381 **954** Routine Name: SDES2VAL200 Before: B4580812 After: B6708793 **853,875,954** Routine Name: SDES2VALCONTEXT Before: B5084950 After: B5115813 **853,860,895,951,954** Routine Name: SDES954P Before: n/a After: B11473094 **954** Routine list of preceding patches: 944, 951, 953 ============================================================================= User Information: Entered By : Date Entered : APR 29, 2026 Completed By: Date Completed: SEP 30, 2026 Released By : Date Released : SEP 30, 2026 ============================================================================= Packman Mail Message: ===================== $END TXT