$TXT Created by G at CHY0077.FO-BAYPINES.DOMAIN.EXT (KIDS) on Tuesday, 07/08/25 at 23:08 ============================================================================= Run Date: JUL 22, 2025 Designation: SD*5.3*915 Package : SD - SCHEDULING Priority: Mandatory Version : 5.3 SEQ #761 Status: Released Compliance Date: AUG 05, 2025 ============================================================================= Associated patches: (v)SD*5.3*889 <<= must be installed BEFORE `SD*5.3*915' (v)SD*5.3*895 <<= must be installed BEFORE `SD*5.3*915' (v)SD*5.3*914 <<= must be installed BEFORE `SD*5.3*915' Subject: SCHEDULING UPDATES TO SUPPORT FRONT END APPS - SPRINT 13.2 Category: - Routine - Enhancement (Mandatory) - Other Description: ============ VistA Scheduling (VS) patch SD*5.3*915 includes several defect corrections and enhancements including: The logic supporting the SDES2 NO-SHOW Remote Procedure Call (RPC) was update to no longer call $$GETAPT^SDESCHECKOUT as this was preventing appointments marked as no-show from showing back up in the request grid in ISS and from closing out the encounter side of the visit the in Computerized Patient Record System (CPRS). A post install routine will use stop code combinations identified by the Scheduling Business Owners to set the DIRECT PATIENT SCHEDULING? field to yes. The new SDES2 CREATE APPT REQ2 RPC Creates a new appointment request in the SDEC APPT REQUEST (#409.85) file and will return all the details of the appointment request. The logic supporting the SDEC APPDEL RPC was updated to prevent the child request from being deleted from parent request when the child appointment is cancelled. A post install routine will identify duplicate entries in the SDEC RESOURCE (#409.831) file. The logic supporting the SDES2 GET CLINIC BY STOP CODE RPC was updated to: 1. Return an empty JSON Object when no data matches the search criteria. 2. To update the naming convention to match Scheduling standards. 3. To fix an issue where data from one clinic would not be cleared out before processing the next matching clinic's data. EHRM Impact Statement: ---------------------- This patch should have no EHRM impact, and can be installed at all sites, including EHRM converted sites. Patch Components: ----------------- 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 ----------- ---- -------------------- SDESRPC Broker Modified 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 CREATE APPT REQ2 New SDES2 GET CLINIC BY STOP CODE Modified Parameter Definitions Associated: --------------------------------- N/A Additional Information: ----------------------- N/A New Service Requests (NSRs): N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1) VSE-9998: VistA: Modify SDES2NOSHOW to no longer call $$GETAPT^SDESCHECKOUT. Problem: When marking an appt as a no show, it is not returning the appt request back to the request grid. In addition, when appts are entered in the Integrated Scheduling Solution (ISS) as a no-show it is not closing out the encounter side of the visit in the Computerized Patient Record System (CPRS) and the appts are showing still as action required. Resolution: The logic supporting the SDES2 NO-SHOW Remote Procedure Call (RPC) was update to no longer call $$GETAPT^SDESCHECKOUT as this was preventing appointments marked as no-show from showing back up in the request grid in ISS and from closing out the encounter side of the visit the in Computerized Patient Record System (CPRS). 2) VSE-10065: VistA: Create a post install to update the "DIRECT PATIENT SCHEDULING?" field for clinics with specific stop code. Problem: Create a post install routine that will use stop code combinations attached to the ticket to determine and assign the DIRECT PATIENT SCHEDULING? field to yes. * If a clinic is active (or has a future reactivation date), the DISPLAY CLIN APPT TO PATIENTS? is YES and has a Primary AMIS Code of 322 and no secondary, or secondary of 185, 186, 187, 117, 125, 160, or 123, after the post install is run, the DIRECT PATIENT SCHEDULING? field is marked with Y (yes). * If a clinic is active (or has a future reactivation date), the DISPLAY CLIN APPT TO PATIENTS? is YES and has a Primary AMIS Code of 323 and No secondary, or secondary of 185, 186, 187, 117, 125, 160, or 123, after the post install is run, the DIRECT PATIENT SCHEDULING? field is marked with Y (yes). * If a clinic is active (or has a future reactivation date), the DISPLAY CLIN APPT TO PATIENTS? is YES and has a Primary AMIS Code of 350 and no secondary, or secondary of 185, 186, 187, 117, 125, 160, or 123, after the post install is run, the DIRECT PATIENT SCHEDULING? field is marked with Y (yes). * If clinic is inactive, do not change the field. * If a clinic is active, but the DISPLAY CLIN APPT TO PATIENTS? field is NO, then do not change the field. If a clinic is active, but the DISPLAY CLIN APPT TO PATIENTS? field is NO and the DIRECT PATIENT SCHEDULING? (#61) is YES this is reported. Resolution: A post install routine will use stop code combinations identified by the Scheduling Business Owners to set the DIRECT PATIENT SCHEDULING? field to yes. 3) VSE-10134: VistA: Create a new version of SDES2 CREATE APPT REQUEST to return the request object. Problem: To optimize the current process, when creating a new appointment request, the response should return the appointment request object back. Resolution: The new SDES2 CREATE APPT REQ2 RPC Creates a new appointment request in the SDEC APPT REQUEST (#409.85) file and will return all the details of the appointment request. 4) VSE-10257: VistA: Modify SDEC APPDEL logic to keep link between child and parent MRTCs. Problem: An issue was reported with VetText cancelled appointments when the appointments request is a child MRTC. After research it was discovered that SDEC APPDEL RPC removes the child request from the list of children for the parent. Resolution: The logic supporting the SDEC APPDEL RPC was updated to prevent the child request being deleted from the list of child requests for the parent request when the child appointment is cancelled. 5) VSE-10278: VistA: Create a post install to identify duplicate clinic resources. Problem: Multiple sites have reported that there are missing appointments showing on the calendar grid. Research shows that the appointments that are missing are assigned to a different resource and both resources are pointing to the same clinic. Resolution: A post install routine will identify duplicate entries in the SDEC RESOURCE (#409.831) file. 6) VSE-10342: VistA: Update SDES2 GET CLINIC BY STOP CODE to return empty JSON object when no matching data is found. Problem: The SDES2 GET CLINIC BY STOP CODE RPC needs the following updates: 1. When no clinics match the specified Primary and Credit Stop criteria, the RPC should return an empty JSON object. Currently, no empty JSON object is returned when no clinics match the Primary and Credit Stop Code search criteria. 2. The naming convention for the returned JSON object should match. This applies to both returned data, and returned errors. OUT("clinic",1 <- Current name when data is returned OUT("Error",1)="Invalid AMIS Primary Stop Code: Code 343." OUT("clinicByStopCodes",1)="" <- Current name when error is returned 3. Data from the first clinic is leaking into the second clinic selected. (see attached email) Resolution: The logic supporting the SDES2 GET CLINIC BY STOP CODE RPC was updated to: 1. Return an empty JSON Object when no data matches the search criteria. 2. To update the naming convention to match Scheduling standards. 3. To fix an issue where data from one clinic would not be cleared out before processing the next matching clinic's data. Test Sites: ----------- Altoona, PA (ALT) North Texas (Dallas), TX (NTX) Test Sites - SNOW Change Order #: Altoona, PA (ALT) - CHG0628381 North Texas (Dallas), TX (NTX) - CHG0628640 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. Post-install routine SDES914P will perform the following actions: 1. A post install routine will use stop code combinations identified by the Scheduling Business Owners to set the DIRECT PATIENT SCHEDULING? field to yes. 2. A post install routine will identify and remove duplicate entries from the SDEC RESOURCE (#409.831) file. 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*915. 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*915 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: ------------------------------- Post install routine SDES915P will automatically run at the end of the installation process. After the post install has finished running, sites can delete the SDES915P routine using the Delete Routines [XTRDEL] if they wish. 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*915b. 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*915b 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 2 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: SDECAR2 Before:B211273527 After:B208299605 **627,642,658,671,686,694,745, 799,805,820,823,893,895,915** Routine Name: SDES2CRTAPREQ2 Before: n/a After: B4955384 **915** Routine Name: SDES2GETCLINST Before: B10423749 After: B10744932 **914,915** Routine Name: SDES2NOSHOW Before: B25699867 After: B25548771 **871,875,889,915** Routine Name: SDES915P Before: n/a After: B48345714 **915** Routine list of preceding patches: 889, 895, 914 ============================================================================= User Information: Entered By : Date Entered : MAY 16, 2025 Completed By: Date Completed: JUL 22, 2025 Released By : Date Released : JUL 22, 2025 ============================================================================= Packman Mail Message: ===================== $END TXT