$TXT Created by MNTVBB.DOMAIN.EXT (KIDS) on Wednesday, 09/24/25 at 13:26 ============================================================================= Run Date: MAR 05, 2026 Designation: RMPR*3*219 Package : RMPR - PROSTHETICS Priority: Mandatory Version : 3 SEQ #192 Status: Released Compliance Date: APR 05, 2026 ============================================================================= Subject: VEHICLE IDS LONGER THAN 30 CHARACTERS Category: - Data Dictionary - Routine Description: ============ ************************************************************************* * IMPORTANT: Follow steps in "Post-Installation Instructions" section * * after patch installation. * ************************************************************************* This patch addresses the following issue: A Vehicle ID longer than 30 characters can be defined in the VEHICLE OF RECORD (#667) file. The Vehicle ID will then generate an error in some Prosthetics reports. 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: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------------ ------------------- -------------------- VEHICLE OF RECORD (#667) VEHICLE ID# (#.01) Modified 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 New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- INC38221159: Vehicle ID Length Issue Problem: ------- A Vehicle ID longer than 30 characters can be defined in the VEHICLE OF RECORD (#667) file. However, the VistA MUMPS file "B" cross-reference is limited to 30 characters. Vehicle ID's longer than 30 characters will generate an error in some Prosthetics reports. Resolution: ----------- The Prosthetics Business Owners requested a Data Dictionary modification for the VEHICLE ID# (#.01) field in the VEHICLE OF RECORD (#667) file so that entries longer than 30 characters are not filed. The help prompt and description were also modified. Before: ------- 667,.01 VEHICLE ID# 0;1 FREE TEXT (Required) INPUT TRANSFORM: K:$L(X)>40!($L(X)<3) X LAST EDITED: NOV 15, 1991 HELP-PROMPT: Answer must be 3-40 characters in length. DESCRIPTION: This is the Identification Number on the vehicle of record, this is a Unique Key. CROSS-REFERENCE: 667^B 1)= S ^RMPR(667,"B",$E(X,1,30),DA)="" 2)= K ^RMPR(667,"B",$E(X,1,30),DA) After: ------ 667,.01 VEHICLE ID# 0;1 FREE TEXT (Required) INPUT TRANSFORM: K:$L(X)>30!($L(X)<3) X MAXIMUM LENGTH: 30 LAST EDITED: SEP 11, 2025 HELP-PROMPT: This is the Vehicle Identification Number (VIN) on the vehicle of record. The expected VIN length is 17 characters for vehicles produced in 1981 and later. Field accepts 3-30 characters in length. DESCRIPTION: This is the Vehicle Identification Number (VIN). Only one patient may be assigned to each vehicle. CROSS-REFERENCE: 667^B 1)= S ^RMPR(667,"B",$E(X,1,30),DA)="" 2)= K ^RMPR(667,"B",$E(X,1,30),DA) Post-install routine RMPR219P will search for Vehicle IDs longer than 30 characters and send a MailMan message to the installer as well as holders of the RMPRMANAGER security key. See Post-Installation Instructions for more information. Test Sites: ----------- South Texas Veterans Health Care System (STX) Chillicothe VA Medical Center (CLL) Columbus VA Medical Center (COS) SNOW Change Order #: -------------------- South Texas Veterans Health Care System (STX): CO # CHG0690406 Chillicothe VA Medical Center (CLL): CO # CHG0690727 Columbus VA Medical Center (COS): CO # CHG0691293 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Documentation describing the new functionality is not included in this release. Documentation Title File Name --------------------------------------------------------------------- N/A Patch Installation: ------------------- 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. (ex. RMPR*3.0*219) 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 your build RMPR*3.0*219. 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. 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 RMPR219P will search for Vehicle IDs longer than 30 characters. A MailMan message is sent to the installer as well as holders of the RMPRMANAGER security key listing the Vehicle IDs. If none are found, "No Vehicle IDs longer than 30 characters found" will display. Routine RMPR219P is deleted after the install has completed. Subj: RMPR*3.0*219 Post-Install [#563788] 09/19/25@12:07 13 lines From: RMPR*3.0*219 Post-Install In 'IN' basket. Page 1 -------------------------------------------------------------------------- RMPR*3.0*219 post-install routine has completed. Listed below are Vehicle IDs in the VEHICLE OF RECORD (#667) file longer than 30 characters in length. These entries will generate errors in some Prosthetics reports and should be edited to a shorter Vehicle ID. Option "Edit/Delete Vehicle of Record" may be used. To edit an entry, use the tic mark character (`) and the Internal Entry Number (IEN), (ex. '184). File #667 IEN Vehicle ID -------------------- ---------------------------------------- 184 B123456789C123456789D123456789F123456789 185 B123456789C123456789D123456789E12345 193 9999999999912345678901234567890123456789 Enter message action (in IN basket): Ignore// Back-out/Rollback Strategy: --------------------------- In the event of a catastrophic failure, the Facility CIO may make the decision to back-out the patch. Because this patch contains Data Dictionary changes, back-out must be done with the participation of the sustainment team. The back-out plan is to restore the Data Dictionary for the VEHICLE OF RECORD (#667) file to the pre-patch version. This can be provided upon request. Please call the national help desk or enter a help desk ticket, if required. No data was modified by this patch installation and, therefore, no rollback strategy is required. Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;PROSTHETICS;**[Patch List]**;Feb 09, 1996;Build 8 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: RMPR219P Before: n/a After: B9540714 **219** ============================================================================= User Information: Entered By : Date Entered : MAY 14, 2025 Completed By: Date Completed: MAR 05, 2026 Released By : Date Released : MAR 05, 2026 ============================================================================= Packman Mail Message: ===================== $END TXT