$TXT Created by at NHM0001D.FO-BAYPINES.DOMAIN.EXT (KIDS) on Wednesday, 08/06/25 at 09:41 ============================================================================= Run Date: DEC 08, 2025 Designation: SD*5.3*911 Package : SD - SCHEDULING Priority: Mandatory Version : 5.3 SEQ #773 Status: Released Compliance Date: JAN 08, 2026 ============================================================================= Associated patches: (v)SD*5.3*863 <<= must be installed BEFORE `SD*5.3*911' (v)SD*5.3*879 <<= must be installed BEFORE `SD*5.3*911' Subject: ADVANCED CLINIC SEARCH/CONSULTS AND RTC USING ICN Category: - Routine - Other - Enhancement (Mandatory) 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-2084 Allow a user to search for Clinics to include in the Advanced Clinic Search report. 2) TMP-3560 Provide the Advanced Clinic Search report in the Telehealth Management Toolbox 3) TMP-3613 Updates to Advanced Clinic Search 4) TMP-3668 Add total number of results in the Advanced Clinic Search report 5) TMP-3669 Add a legend in the Advanced Clinic Search report 6) TMP-3670 Display indicator in the Advanced Clinic Search report if clinics are available in patient facing apps 7) TMP-3672 Stop Code search updates in the Advanced Clinic Search 8) TMP-3676 Correctly derive institution and Station 9) TMP-3027 Search for Appointment Requests using Integrated Control Number (ICN) instead of Data File Number (DFN) Electronic Health Record Modernization (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 ------------ ----------- ----------- SD ADV CLINIC SEARCH run routine New SD TELE TOOLS Menu 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-2084: Allow a user to search for Clinics to include in the Advanced Clinic Search report Problem: -------- Scheduling Managers need to be able to search for clinics in the Telehealth Management Toolbox using several criteria so that the clinics are included in the Advanced Clinic Search report. Resolution: ----------- Routine SDTMPUT4 was created to provide this capability. This ticket focused on developing the search criteria. 2. TMP-3560: Provide the Advanced Clinic Search report in the Telehealth Management Toolbox Problem: -------- Scheduling Managers need to be able to use the Advanced Clinic Search report in the Telehealth Management Toolbox so that they can identify clinics that already meet a criterion and do not create new ones. This ticket focused on the report output. Resolution: ----------- Further development was done on routine SDTMPUT4 to create the custom header and report output. 3. TMP-3613: Updates to Advanced Clinic Search Problem: -------- Add the Advanced Clinic Search to the Telehealth Management Toolbox. The user can see that the exclamation mark in the Provider columns identifies the default provider. Patch documentation is updated. Resolution: ----------- Options were created for the Advanced Clinic Search Report and the Telehealth Management Toolbox. An explanation for '!' character next to the default providers name was added to the provider column header. Added the CHAR4 field to the report. The TMP user manual was updated to include the Advanced Clinic Search Report. 4. TMP-3668: Add total number of results in the Advanced Clinic Search Report Problem: -------- As a VistA Scheduling Manager, I need to be able to see the total number of clinics as well as the total number of active and inactive clinics in the Advanced Clinic Search report so that I know how many clinics were returned from my search. Resolution: ----------- The following information was added to the bottom of the report: xxxx CLINICS TOTAL (xxxx INACTIVE, xxxx ACTIVE) 5. TMP-3669: Add a legend in the Advanced Clinic Search report Problem: -------- As a VistA Scheduling Manager, I need to have a legend added to the Advanced Clinic Search report so that I understand the meaning of the symbols used in the report. Resolution: ----------- The following legend was added to the report header: FLAGS: *=INACTIVE CLINIC, +=DISPLAY APPT TO PATIENTS, S=INACTIVE STOP CODE, C=INACTIVE CREDIT STOP CODE 6. TMP-3670: Display indicator in the Advanced Clinic Search report if clinics are available in patient facing apps Problem: -------- As a VistA Scheduling Manager, I need to know if the clinics returned in the Advanced Clinic Search report is viewable by patients in patient-facing applications Resolution: ----------- The '+' indicator was added to the Flags field of the ADVANCED CLINIC SEARCH report to indicate clinics that display appointments to patients in patient-facing applications. 7. TMP-3672: Stop Code search updates in the Advanced Clinic Search Problem: -------- The user can run the Advanced Clinic Search using a combination of a Stop Code and Credit Stop Code, or the user can run the Advanced Clinic Search with one code and the report displays all clinics that have a matching Stop Code or Credit Stop Code. Resolution: ----------- The report was modified to allow stop code search by pairs or individual stop codes in the stop code or credit stop codes fields, or both. 8. TMP-3676: Correctly derive institution and Station Problem: -------- As a Scheduler, I need to derive the station assigned to institution field correctly through the DIVISION field (#3.5) of the HOSPITAL LOCATION file (#44) and MEDICAL CENTER DIVISION file (#40.8). Resolution: ----------- The fix was made to derive the institution, and it's assigned station by deriving it through the DIVISION field (#3.5) of the HOSPITAL LOCATION file (#44) and MEDICAL CENTER DIVISION file (#40.8). This fix was implemented in the Clinic Inquiry of the Telehealth Inquiries [SD TELE INQ] option. Also, the change was made to the process generating (SIU~S12) HL7 message that is sent from VistA to TMP when scheduling of VistA appointment. 9. TMP-3027: Search for Appointment Requests using ICN instead of DFN Problem: -------- As a TMP Scheduler, I need to view Appointment Requests (Consult, Return To Clinic) using the patient's ICN instead of DFN so that VistA will return all Appointment Requests regardless of the DFN being used at the VistA site. Resolution: ----------- VistA will be modified to accept the DFN^ICN string and use ICN to process Consults & RTCs by doing an internal lookup for the correct DFN from the ICN value. VistA will use the derived DFN value and not use the one sent by TMP, which sometimes is incorrect. Test Sites: ----------- Atlanta, GA (ATL) Boise, ID (BOI) Philadelphia, PA (PHI) Test Sites - SNOW Change Order #: Production ---------- ATL - CHG0652826 BOI - CHG0652812 PHI - CHG0652830 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 SD*5.3*911 User Manual SD_5_3_P911_MAN_UM 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*911 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*911 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*911b. 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*911b 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*911 patch no longer contain 911** 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 15 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: SDHL7CON Before:B110026015 After:B120631772 **704,773,812,858,879,911** Routine Name: SDTMPHLA Before:B113349418 After:B110304237 **704,733,773,780,798,812,821,911** Routine Name: SDTMPUT0 Before:B128069194 After:B125989227 **773,779,812,817,821,832,859, 863,911** Routine Name: SDTMPUT4 Before: n/a After:B121773161 **911** Routine list of preceding patches: 863, 879 ============================================================================= User Information: Entered By : Date Entered : FEB 21, 2025 Completed By: Date Completed: SEP 26, 2025 Released By : Date Released : DEC 08, 2025 ============================================================================= Packman Mail Message: ===================== $END TXT