$TXT Created by at NHM0001D.FO-BAYPINES.DOMAIN.EXT (KIDS) on Wednesday, 05/07/25 at 09:34 ============================================================================= Run Date: MAY 23, 2025 Designation: SD*5.3*894 Package : SD - SCHEDULING Priority: Mandatory Version : 5.3 SEQ #756 Status: Released Compliance Date: MAY 30, 2025 ============================================================================= Associated patches: (v)SD*5.3*780 <<= must be installed BEFORE `SD*5.3*894' (v)SD*5.3*888 <<= must be installed BEFORE `SD*5.3*894' Subject: SEND INACTIVATE/REACTIVATE DATES TO TMP, CLINIC REMAP ISSUES Category: - Routine Description: ============ TeleHealth Management Platform (TMP) is implementing processes that will keep Veterans Health Information Systems and Technology Architecture (VistA) clinic and appointment data for telehealth clinics and appointments in sync with the TMP application. This patch includes the following: 1) TMP-3064 Send INACTIVATE and REACTIVATE dates to TMP in Clinic Updates When an INACTIVATE date or REACTIVATE DATE is set in VistA, TMP will be updated with these dates for the VistA clinic via an existing HL7 record. 2) TMP-3431 Do not send transactions when a clinic remap does not change the grid When a clinic remap is executed, but there are no new holidays, do not send block transactions for the existing holidays. 3) VSE-9570: VistA: Fix defects found in REMAP CLINIC [SDD] The Remap Clinic [SDD] option was updated to not remove the 'CAN' node when the timeslots have been cancelled. After the remap, the date will be correctly stored in the 9 node of the ST subscript. After remap, cancellations for clinics with special patterns will be preserved. EHRM Impact Statement: ---------------------- This patch should have no EHRM impact, and can be installed at all sites, including EHRM converted sites. Patch Components: ----------------- File Data Included: File Name (Number) Entry Name New/Modified/Deleted ------------------ ------------------ -------------------- N/A Files & Fields Associated: File Name (Number) Field Name (Number) New/Mod/Del ------------------ ------------------- ------------ 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/Del/Mod ------------ ----------- ----------- Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A HL7 Logical Links New/Modified/Deleted ----------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A HL7 Application Parameter Associated: Application Parameter Name New/Modified/Deleted -------------------------- ------------------------ 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 New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- None Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. TMP-3064: Send INACTIVATE and REACTIVATE dates to TMP in Clinic Updates Problem: -------- When the INACTIVATE DATE (#2505) or the REACTIVATE DATE (#2506) fields in the HOSPITAL LOCATION FILE (#44) are updated, TMP is not aware of these dates and the correct status of the clinic. Resolution: ----------- Routine SDTMPHLB was modified to send these two fields in the LDP segment of the clinic update message (MFN~M05). These were existing fields in the HL7 record that were previously not populated. 2. TMP-3431: Do not sent transactions when a clinic remap does not change the grid Problem: -------- When VistA users remap a clinic, Federal Holidays are being sent over and over again to TMP and each time a new Reserve Resource is being created. This is clogging up the Views and Service Calendar on those dates. Resolution: ----------- Modified routine SDD0 to not send a holiday block transaction if the date was already marked as a holiday. 3. VSE-9570: VistA: Fix defects found in REMAP CLINIC (SDD) Problem: -------- Fix defects found in REMAP CLINIC [SDD] option. Three issues: o When re-mapping a clinic with cancelled timeslots, the 'CAN' subscript is removed. o When initially creating the availability on the ST subscript, the 9 subscript is set to the date. After remap, the clinic IEN is stored in the 9 subscript. o Remapping clinic re-opens a blocked slot (block and move)- where the blocked slot is being re-opened has to do with the fact that there is a special pattern "OST" defined for this clinic on this day. The logic is picking up the OST subscript rather than the ST value. In the case where the appointment no longer exists on this day, and there are no appointments found by APPT^SDD0, the logic jumps to OVR, which will set the ST subscript without taking into account cancellations. Resolution: ----------- The Remap Clinic [SDD] option was updated to not remove the 'CAN' node when the timeslots have been cancelled. After the remap, the date will be correctly stored in the 9 node of the ST subscript. After remap, cancellations for clinics with special patterns will be preserved. Test Sites: ----------- Boise VAMC (BOISE) Iowa City VAMC (IOWA) Philadelphia VMAC (PHY) Test Sites - SNOW Change Order #: Production ---------- BOISE - CHG0609222 IOWA - CHG0609248 PHY - CHG0609565 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software is released as a PackMan message and is distributed from FORUM. 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. File Description File Name FTP Mode ------------------------------------------------------------------------ PIMS Technical Manual PIMS_TM Binary Patch Installation: ------------------- Pre/Post Installation Overview: It is not necessary to disable any options. 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 the patch or build name SD*5.3*894 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 your build SD*5.3*894 iii. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build R Routines Enter response: Build 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. Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO// respond NO. ii. When Prompted "Want KIDS to INHIBIT LOGONs during the install? NO//" respond NO. iii. When Prompted "Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//" respond NO. iv. If prompted 'Delay Install (Minutes): (0-60): 0//' respond 0. Post-Installation Instructions: ------------------------------- None. Back-Out/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*894b. 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*894b backup installs without any issues. Validation of Back-out Procedure -------------------------------- The Back-out Procedure can be verified by printing the first 2 lines of the routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routines contained in the SD*5.3*894 patch no longer contain 894** in the second line, the patch has been backed out. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.3;Scheduling;**[Patch List]**;Aug 13, 1993;Build 8 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: SDD0 Before: B30454698 After: B32906666 **167,401,529,674,726,753,775, 780,894** Routine Name: SDTMPHLB Before: B49669966 After: B51558086 **704,733,714,773,888,894** Routine list of preceding patches: 780, 888 ============================================================================= User Information: Entered By : Date Entered : SEP 24, 2024 Completed By: Date Completed: MAY 21, 2025 Released By : Date Released : MAY 23, 2025 ============================================================================= Packman Mail Message: ===================== $END TXT