$TXT Created by at DEVVCC.DOMAIN.EXT (KIDS) on Monday, 12/18/23 at 15:15 ============================================================================= Run Date: DEC 03, 2024 Designation: VIAB*1*24 Package : VIAB - VISTA INTEGRATION ADAPTOR Priority: Mandatory Version : 1 SEQ #23 Status: Released Compliance Date: JAN 03, 2025 ============================================================================= Associated patches: (v)VIAB*1*20 <<= must be installed BEFORE `VIAB*1*24' (v)VIAB*1*23 <<= must be installed BEFORE `VIAB*1*24' Subject: BMS LISTORDERACTIONS - ORDER TEXT CHARS LIMIT Category: - Routine Description: ============ This patch addresses a Bed Management System (BMS) issue using the LISTORDERACTIONS call. When part of the return string, the order text field value is too large, the LIST^DIC call returns a soft error "The data requested for the record is too long to pack together." and no patient result data is passed to BMS. This patch will forward a portion of the large returning value enabling results to pass over to BMS. Patch Components: ----------------- Entities Associated: N/A Files & Fields Associated: N/A Forms Associated: N/A Mail Groups Associated: N/A Options Associated: N/A Protocols Associated: N/A Remote Procedure Calls Associated: N/A Security Keys Associated: N/A Templates Associated: N/A Additional Information: ----------------------- Blood Bank Team Coordination: N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: 1. INC29062131 2. INC30434414 Problem: -------- Problem: LISTORDERACTIONS uses the LIST^DIC call within its code. If the size of the Order's Order Text field is too large and exceeds a number of characters, LIST^DIC returns an 'overflow' error "The data requested for the record is too long to pack together." and the result doesn't pass over to BMS. Resolution: ----------- Resolution: In an effort to pass the result to BMS, the text will get truncated after a text exceeds the 3675 characters limit with the trailing tag: "<*NOTE: order text reached max length, please check appropriate system for full order text*>" Test Sites: ----------- Finger Lakes at Upstate New York Orlando VAMC SNOW Change Order #: -------------------------------- UPSTATE NEW YORK HCS - CHG0537003 Orlando VAMC - CHG0535602 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released via a PackMan message. Patch Installation: ------------------- Pre-Installation Instructions: This patch should be installed during non-peak hours to minimize potential disruption to users. This patch should take less than 1 minute 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 VIAB*1.0*24. 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 VIAB*1.0*24. 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 this message? 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. If prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer . iv. When prompted 'Delay Install (Minutes): (0 - 60): 0//', answer 0. Post-Installation Instructions: N/A Backout Procedures: ------------------- If rollback/backout is required, the KIDS build that was created in step 2B may be installed to restore all modified components back to their pre-patch released state. The message containing the backed-up components can be loaded with the "Xtract PackMan" function at the Message Action prompt. The Packman function "INSTALL/CHECK MESSAGE" is then used. Routine Information: ==================== The second line of each of these routines now looks like: ;;1.0;VISTA INTEGRATION ADAPTER;**[Patch List]**;06-FEB-2014;Build 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: VIABMS4 Before: B33250417 After: B35577850 **15,20,24** Routine list of preceding patches: 20 ============================================================================= User Information: Entered By : Date Entered : DEC 18, 2023 Completed By: Date Completed: DEC 02, 2024 Released By : Date Released : DEC 03, 2024 ============================================================================= Packman Mail Message: ===================== $END TXT