$TXT Created by at MNTVBB.DOMAIN.EXT (KIDS) on Monday, 04/08/24 at 08:39 ============================================================================= Run Date: MAY 01, 2024 Designation: RMPR*3*211 Package : RMPR - PROSTHETICS Priority: Mandatory Version : 3 SEQ #188 Status: Released Compliance Date: JUN 01, 2024 ============================================================================= Associated patches: (v)RMPR*3*163 <<= must be installed BEFORE `RMPR*3*211' (v)RMPR*3*198 <<= must be installed BEFORE `RMPR*3*211' Subject: LOOKUP BY PURCHASE CARD ERROR; NO RMPR PURGE SUS USER WARNING Category: - Routine - Data Dictionary Description: ============ The patch addresses the following issues: 1. There are two (2) issues with the Reconcile/Close Out Purchase Card Transaction option [RMPR4 CLOSE OUT]. The application allows the user to delete the last remaining billing item (original billing item) on a purchase card transaction. If after the delete, the end user times-out or enters an up caret ("^") at the Select ITEM prompt, the system leaves an incomplete record that cannot be canceled or edited through the menu. A second issue occurs with the option when a user deletes an item and then adds additional items. When this occurs, the programming does not properly update the BILLING ITEM multiple (#664.02) counters in the PROSTHETICS 1358 FILE (#664). 2. The option "Purge Suspense Records" [RMPR PURGE SUS] does not give the user a chance to verify whether they want to proceed with the purge. They do not have an option to cancel out of the purge once the report is displayed, nor are they given an estimate of the date range that will be purged before they commit. As a result, sites are inadvertently running the purge or running it without understanding how much data they will lose. This is causing sites to unintentionally lose important patient data. Patch Components: ================= Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- PROSTHETICS 1358 (#664) BILLING ITEM (sub-file (#664.02) BILLING ITEM (#.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 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: ============================================ 1. INC20520033 - Patient Lookup By Purchase Card Error Problem: -------- When an end user attempts to reconcile the credit card purchasing transaction using Reconcile/Close Out Purchase Card Transaction [RMPR4 CLOSE OUT], the application allows the user to delete the single remaining billing item (original billing item) on the transaction. If after the delete, the end user times out or enters an up caret ("^") at the Select ITEM prompt, it leaves an erroneous record that cannot be cancelled or edited through the Reconcile/Close Out Purchase Card Transaction [RMPR4 Close Out] option. The system displays the following message: "INCOMPLETE RECORD..file 664..entry.. ##### ...PLEASE CONTACT YOUR IRM or CANCEL THIS ENTRY!!!". The second issue occurs with the Reconcile/Close Out Purchase Card Transaction [RMPR4 Close Out] option when a user deletes an item and then adds additional items. When this occurs, the programming does not properly update the BILLING ITEM multiple (#664.02) counters in the PROSTHETICS 1358 FILE (#664). Resolution: ----------- This patch modifies the data dictionary for the Prosthetics 1358 file (#664), Billing item multiple (#664.02), Billing Item field (#.01) to prevent a delete of the item when there is only one (1) item remaining. The Delete Test for the field is added to call an extrinsic function $$IC^RMPR4E21 to check the number of items. If the number is equal to 1, the extrinsic returns a true value to disallow a delete. *****NOTE***** The patch does not correct existing purchase card transactions that have no BILLING ITEMS associated. For the second issue, the patch modifies the item file code in ^RMPR4E21 to update the item counters properly. Routines: RMPR4E21 2. INC24634237 - RMPR PURGE SUS Not Warning Users INC24634256 - DUPLICATE ************NOTE************ NOTE: An update to the Prosthetics VistA software (Patch RMPR*3.0*207) in October 2021 changed the maximum allowable days from 730 to 4000 for Suspense Purge. The increase of maximum allowable days from 730 to 4000 (10 years) is in line with PSAS updated business practice guidelines when fulfilling Veteran requests for supplies/accessories to previously prescribed equipment. The Business Practice Guidelines for VistA Prosthetics Purge Obsolete Data purge settings is as follows: SUSPENSE PURGE: 4000 CLOSE-OUT PURCHASING PURGE: 730 CANCELLATION PURCHASING PURGE: 730 IMPORTANT ========= It is recommended that these parameters be reviewed and changed to the recommended values. Problem: -------- The option "Purge Suspense Records" [RMPR PURGE SUS] does not give the user a chance to verify whether they want to proceed with the purge. They do not have an option to cancel out of the purge once the report is displayed, nor are they given an estimate of the date range that will be purged before they commit. As a result, sites are inadvertently running the purge or running it without understanding how much data they will lose. This is causing sites to unintentionally lose important patient data. Resolution: ----------- This patch modifies routine ^RMPR8PG to check whether there is any suspense to purge, and if so, it displays an estimate of records to be purged and the date range of the records. With the default answer set to "NO", it also asks the user to confirm whether they want to proceed. Routines: RMPR8PG Participating Test Sites: ======================== Fargo VAMC, Fargo ND Cheyenne VAMC, Cheyenne WY SNOW Change Order # =================== Cheyenne VAMC - CO# CHG471085 Fargo VAMC - CO# CHG0470846 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 the patch or build name. (RMPR*3.0*211) 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*211. 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. Installation Verification: -------------------------- Successful installation can be verified by reviewing the first 2 lines of the routines contained in the patch. The second line will contain the patch number (211) in the [PATCH LIST] section. ;;3.0;Prosthetics**[Patch List]**; 24 Jun 93 The Calculate and Show Checksum Values option [XTSUMBLD-CHECK] can be run to compare the routine checksums to what is documented in this patch description. Successful installation for the field can be verified by reviewing the BILLING ITEM field (#.01) in the BILLING ITEM multiple (#664.02) in the PROSTHETICS 1358 (#664) with FileMan. There should be a DELETE TEST line for the field that looks like: DELETE TEST: 1,0)= I $$IC^RMPR4E21=1 Back-Out/Roll Back Plan: ------------------------ Back-out will be done only with the concurrence and participation of development team and appropriate VA site/region personnel. The decision to back-out or rollback software will be a joint decision between the development team, VA site/region personnel and other appropriate VA personnel. Prior to installing an updated KIDS package, the site/region should have saved a backup of the routines in a mail message using the Backup a Transport Global [XPD BACKUP] menu option (this is done at time of install). The message containing the backed-up routines 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 routines 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. Then select the Install Package(s) option and choose the patch (RMPR*3.0*211) to install. The back-out plan is to restore the routines from the backup created. The installation of the Transport Global Backup (RMPR*3.0*211b) will not restore the BILLING ITEM multiple (#664.02) DELETE TEST attribute. This must be done manually. In the event a back-out is required, log a ServiceNow incident requesting assistance. Validation of Back-out Procedure -------------------------------- The Back-out Procedure can be verified by confirming the checksums have been returned to the pre-patch value using CHECK1^XTSUMBLD. It can also be verified by printing the first 2 lines of the RMPR routine(s) contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routine(s) contained in this patch have been backed out, the Second line of each routine will no longer contain the designation of patch RMPR*3*211. Back-out of the data dictionary changes can be verified by using the LIST FILE ATTRIBUTES in FILEMAN for the BILLING ITEM multiple (#664.02) and examining the DESCRIPTION and DELETE TEST attributes for the BILLING ITEM field (#.01). Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;PROSTHETICS;**[Patch List]**;Feb 09, 1996;Build 10 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: RMPR4E21 Before: B67777687 After: B75299662 **3,12,26,28,30,34,41,45,62, 111,78,114,118,133,137,182,198, 211** Routine Name: RMPR8PG Before: B7739853 After: B21497561 **5,75,140,163,211** Routine list of preceding patches: 163, 198 ============================================================================= User Information: Entered By : Date Entered : SEP 07, 2022 Completed By: Date Completed: MAY 01, 2024 Released By : Date Released : MAY 01, 2024 ============================================================================= Packman Mail Message: ===================== $END TXT