$TXT Created by HOMAS at MNTVBB.DOMAIN.EXT (KIDS) on Wednesday, 08/02/23 at 20:20 ============================================================================= Run Date: MAR 10, 2025 Designation: PRC*5.1*231 Package : PRC - IFCAP Priority: Mandatory Version : 5.1 SEQ #207 Status: Released Compliance Date: APR 09, 2025 ============================================================================= Subject: IFCAP TRANSMISSION DESCRIPTION AND COMMENT SIZE LIMIT Category: - Routine Description: ============ The purpose of this patch is to count the character size of the DESCRIPTION (#442.05) and COMMENTS (#442.04) fields accumulated for transmission in the PROCUREMENT & ACCOUNTING TRANSACTIONS FILE (#442) and limit the output for transmission from each of those fields to 210 characters. This patch is approved for both VA VistA and EHRM sites. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) 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 --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A Additional Information: ----------------------- N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: 1. INC27604165 IFCAP-AMA- receiving reports not transmitting. Problem: -------- When a VistA/IFCAP receiving report transmission message exceeds a transaction size limitation of 32,750 characters, the transmission data will not be received into the VA Accounting System/FMS Management System (FMS) due to the oversize transaction. Resolution: ----------- Modify Routine PRCFARR2 where the ^UTILITY file is created from the Description field in preparation for transmission. Ensure no matter how many characters are entered in the Description field, only the first 210 characters from the Description field are received for transmission. Modify Routine PRCFARR3 where the ^UTILITY file is created from the Comments field in preparation for transmission. Ensure no matter how many characters are entered in the Comments field, only the first 210 characters from the Comments field are received for transmission. Test Sites: ----------- Amarillo VA Health Care System (504), Amarillo, TX C.W. Bill Young VA Medical Center (FL) (516), Bay Pines, FL SNOW Change Order #: -------------------- Amarillo - # CHG0408001 C.W. Bill Young - # CHG0555480 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. File Title File Name Format --------------------------------------------------------------------- N/A Documentation describing the new functionality is not included in this release. Documentation Title File Name --------------------------------------------------------------------- N/A Patch Installation: ------------------- Pre/Post Installation Overview: ------------------------------- N/A 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 PRC*5.1*231. 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 PRC*5.1*231. 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: N/A Back-Out/Roll Back Plan: ------------------------ Prior to installing an updated KIDS package, the installer should have saved a backup of the routine in a mail message using the Backup a Transport Global [XPD BACKUP] menu option from the Kernel Installation and Distribution System Menu and selecting the Installation Menu. The back-out plan is to restore the routine from the backup created. The message containing the backed-up routine can be loaded with the "Xtract PackMan" function at the Message Action prompt. The Packman function "INSTALL/CHECK MESSAGE" is then used to install the backed-up routine onto the VistA System. If the patch was backed up for the build, from the Kernel Installation and Distribution System Menu, select the Installation Menu. Select the Install Package(s) option and choose the patch (PRC*5.1*231b) to install. Routine Information: ==================== The second line of each of these routines now looks like: V ;;5.1;IFCAP;**[Patch List]**;4/21/95;Build 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PRCFARR2 Before: B12288555 After: B13717941 **231** Routine Name: PRCFARR3 Before: B14517748 After: B16338754 **231** ============================================================================= User Information: Entered By : Date Entered : JUL 25, 2023 Completed By: Date Completed: MAR 10, 2025 Released By : Date Released : MAR 10, 2025 ============================================================================= Packman Mail Message: ===================== $END TXT