$TXT Created by F at CLN1G1.AAC.DOMAIN.EXT (KIDS) on Tuesday, 02/25/20 at 10:03 ============================================================================= Run Date: JUN 15, 2020 Designation: PSS*1*243 Package : PSS - PHARMACY DATA MANAGEMENT Priority: Mandatory Version : 1 SEQ #210 Status: Released Compliance Date: JUL 15, 2020 ============================================================================= Associated patches: (v)PSS*1*170 <<= must be installed BEFORE `PSS*1*243' (v)PSS*1*220 <<= must be installed BEFORE `PSS*1*243' (v)PSN*4*569 <<= must be installed BEFORE `PSS*1*243' Subject: MATCH/UN-MATCHING DRUGS CROSS-REFERENCE PROBLEMS Category: - Routine Description: ============ This patch, along with patch PSN*4.0*569, will address the following ePrescribing (eRx) issue: 1. INC9317643 - We have noticed a number of drugs that do not auto match for inbound eRx orders DUPLICATE - INC9105989 - eRx software auto-matched wrong drug product Defect Tracking System Ticket(s) & Overview: 1. INC9317643 - We have noticed a number of drugs that do not auto match for inbound eRx orders DUPLICATE - INC9105989 - eRx software auto-matched wrong drug product Problem: -------- There is a reported issue with incoming eRx orders not automatically matching the ordered drug with a VistA corresponding Dispense Drug, even when the National Drug Code (NDC) received matches 1 to 1 with a specific Veteran's Administration (VA) Product entry. It was also noticed the issue to be more prevalent with dispense drugs that have been recently re-matched to a different VA Product entry due to changes from Milligrams (MG) to MCG (Micrograms) in the strength. After researching this issue it was determined that the root cause of the problem was a 'corruption' of the "APR" cross-reference in the DRUG (#50) file which was not properly set or killed after Dispense Drugs were matched, un-matched or re-matched to VA Product entries. Such cross-reference is used by the eRx drug auto-matching processing and that's the reason it failed for some drugs. It turned out that two other cross-references, "AND" and "APN", also had the same issue. No user functionality side-effects have been reported related to these other two cross-references though. Resolution: ----------- The setting and killing of the "APR", "AND" and "APN" cross-reference have been completely reviewed at every point where a Dispense Drug is matched, un-matched or re-matched to a VA Product and after this patch is installed they should be properly maintained. Furthermore, a post-install routine will completely kill off the 3 cross-references and re-build them entirely. The NDF (National Drug File) patch PSN*4.0*569 is also being released along with this patch because the matching functionality is available in both applications, NDF and PDM (Pharmacy Data Management). Technical Resolution: --------------------- Changed the routines PSSDEE1 and PSSUTIL to kill and set the cross-references "AND", "APN" and "APR" properly. Test Sites: ----------- Fayetteville VA Medical Center (MC) (Fayetteville, AR) Puget Sound Health Care System (HCS) (Tacoma, WA) Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. 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. Staff should not be processing prescriptions while patch is being installed. This patch should take less than 5 minutes to install. NOTE: The associated patch PSN*4.0*569 should be installed before PSS*1.0*243. Installation Instructions: 1. Choose the PackMan message containing this patch. Then select the INSTALL/CHECK MESSAGE PackMan option to load the patch. 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. (ex. PSS*1.0*243) 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 of any routines exported with this patch. It will not backup any other changes such as DDs or templates. 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. iv. When prompted 'Delay Install (Minutes): (0 - 60): 0//', answer 0. Post-Installation Instructions: After the patch is installed the post-install routine PSS243PI will be executed to completely kill off the entire "AND", "APN" and "APR" cross- references and re-build them correctly. Back-out/Rollback Strategy: --------------------------- 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 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. The back-out plan is to restore the routines from the backup created. No data was modified by this patch installation and, therefore, no rollback strategy is required. Validation of Roll Back Procedure: ---------------------------------- The Roll Back Procedure can be verified by printing the first 2 lines of the PSS Routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routines contained in the PSS*1.0*243 patch have been rolled back, the first two lines of the Routines will no longer contain the designation of patch PSS*1.0*243 in the patch list section on line 2. Routine Information: ==================== The second line of each of these routines now looks like: ;;1.0;PHARMACY DATA MANAGEMENT;**[Patch List]**;9/30/97;Build 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSS243PI Before: n/a After: B2383569 **243** Routine Name: PSSDEE1 Before: B22862330 After: B20696513 **15,20,34,38,68,90,208,220,243** Routine Name: PSSUTIL Before: B99593608 After:B110921565 **34,38,147,155,170,243** Routine list of preceding patches: 170, 220 ============================================================================= User Information: Entered By : Date Entered : FEB 11, 2020 Completed By: Date Completed: JUN 12, 2020 Released By : Date Released : JUN 15, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT