$TXT Created by at MNTVBB.DOMAIN.EXT (KIDS) on Tuesday, 09/12/23 at 12:22 ============================================================================= Run Date: NOV 08, 2023 Designation: RMPR*3*214 Package : RMPR - PROSTHETICS Priority: Mandatory Version : 3 SEQ #187 Status: Released Compliance Date: DEC 09, 2023 ============================================================================= Associated patches: (v)RMPR*3*213 <<= must be installed BEFORE `RMPR*3*214' Subject: FILE 660 RECORDS MAY CONTAIN ERRONEOUS ICD CODES Category: - Routine Description: ============ This patch will resolve the following issue: INC27716753 - Historic 2319 records showing invalid ICD code error 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 List Templates Associated: Template Name Type 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: INC27716753 - Historic 2319 records showing invalid ICD code error Problem: -------- After installation of patch RMPR*3.0*213, historical 2319 records are still showing an ICD-10 CODE format error. Example: ICD-10 Message: Code not in correct format ICD-10 CODE: Code not in correct format No ICD Code Description ** Inactive ** Date: Further research shows that 2319 records are built from the RECORD OF PROS APPLIANCE/REPAIR (#660) file and require a separate fix from the work performed by RMPR*3.0*213 which repaired records in the PROSTHETIC SUSPENSE (#668) file. Resolution: ----------- The following changes were made to address the issue: The post-install routine RMPR214P has been created to repair records in the RECORD OF PROS APPLIANCE/REPAIR (#660) file that contain the "-1" error code in the SUSPENSE ICD (#8.8) field. Technical Resolution: --------------------- The following changes were made to address the issue: A post-install routine has been created to search through the records in the RECORD OF PROS APPLIANCE/REPAIR (#660) file, looking for the "-1" error code in the SUSPENSE ICD (#8.8) field. When found, the corresponding consult pointer is used to find the correct ICD10 code and insert it into the erroneous record. NOTE - the original data is saved before the SUSPENSE ICD (#8.8) field is updated and that data is available for restoration if needed. Test Sites: ----------- Mann-Grandstaff VA Medical Center (Spokane, WA) Chalmers P. Wylie VA OPC (Columbus, OH) SNOW Change Order Number: ------------------------- Spokane: CHG0418237 Columbus: CHG0418918 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. 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. It is not necessary to disable any options. 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 RMPR*3.0*214. 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*214. 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. a. If prompted 'Enter options you wish to mark as 'Out Of Order':', press the Enter key. b. If prompted 'Enter protocols you wish to mark as 'Out Of Order':', press the Enter key. c. If prompted 'Delay Install (Minutes): (0 - 60): 0//', answer 0 Back-out/Roll Back Plan: ------------------------ NOTE - this is different than the usual plan as there are no routines being modified or added to the system permanently. There is only a post- install routine that is executed during patch installation. There are no routines or other components that need to be backed up prior to installation. Backup of any affected data is done when the post-install routine is running and before the data is corrected. The data modified by this patch installation can be restored by running the backout process from the programmer's prompt via a call to the BACKOUT tag of the RMPR214P routine, i.e. D BACKOUT^RMPR214P. IMPORTANT - this action should only be taken with the concurrence and participation of the development team and appropriate VA site/region personnel. Validation of Back-out Procedure: --------------------------------- Rollback of the affected records can be verified by getting the record ID's (IEN's) from the ^XTMP("RMPR*3.0*214 POST INSTALL",0,660,recordID) global and then examining those specific records using the Fileman Inquire to File Entries option on RECORD OF PROS APPLIANCE/REPAIR (#660) file and confirming that -1 is found in the SUSPENSE ICD (#8.8) field. Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;PROSTHETICS;**[Patch List]**; 30 Oct 98;Build 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: RMPR214P Before: n/a After: B47721387 **214** ============================================================================= User Information: Entered By : Date Entered : JUL 06, 2023 Completed By: Date Completed: NOV 07, 2023 Released By : Date Released : NOV 08, 2023 ============================================================================= Packman Mail Message: ===================== $END TXT