$TXT Created by at CLN1G1.AAC.DOMAIN.EXT (KIDS) on Monday, 05/04/20 at 06:23 ============================================================================= Run Date: AUG 06, 2020 Designation: PSO*7*598 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #500 Status: Released Compliance Date: SEP 06, 2020 ============================================================================= Associated patches: (v)PSO*7*508 <<= must be installed BEFORE `PSO*7*598' (v)PSO*7*574 <<= must be installed BEFORE `PSO*7*598' Subject: Code fix due to PSO*7*457/ Inbound eRx Ext Person file dupe Category: - Routine Description: ============ This patch will resolve the following issue(s): 1) When entering outpatient prescriptions and attempt to edit the issue date, the system will allow you to change the issue date to more than 6 months in the past. 2) When inbound eRx prescriptions are processed duplicate entries in the ERX EXTERNAL PERSON file [#52.48] can occur. Patient Safety Issues (PSIs): ----------------------------- HITPS-7055- INC9219761 Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1) INC9219761 - When entering outpatient prescriptions and attempt to edit the issue date, the system will allow you to change the issue date to more than 6 months in the past. Problem: -------- When utilizing PSO LM BACKDOOR ORDERS to enter new prescriptions, if a user needs to edit the Issue Date, the system allows them to enter a date more than 6 months in the past. This issue was corrected in patch PSO*7*538 but patch PSO*7*457 inadvertently overlaid some of the code meant to fix the issue. Resolution: ------------ Modify routine PSOBKDED to restore the modifications that were first introduced in patch PSO*7*538 that will not allow a prescription issue date to be more than 6 months in the past. 2) INC7789329 - When inbound eRx prescriptions are processed duplicate entries in the ERX EXTERNAL PERSON file [#52.48] can occur. Problem: ----------- When inbound eRx prescriptions are processed duplicate entries the ERX EXTERNAL PERSON file [#52.48] can occur. If the external Provider has an existing entry in the ERX EXTERNAL PERSON file [#52.48] without a DEA number and another eRx from the same external Provider is processed (which does include a DEA number) this will cause a duplicate Provider entry to occur in the ERX EXTERNAL PERSON file [#52.48]. Once there is a duplicate Provider entry in the ERX EXTERNAL PERSON file [#52.48] this will cause additional duplicates to be created every time for the same Provider if the inbound eRx does not include a DEA#. Resolution: ------------ Add code to routine PSOERXU2 which will search the ERX EXTERNAL PERSON file [#52.48] in reverse order to find the most recent entry that matches the NPI and DEA#. If that match is not found an additional reverse order search is made attempting to find a match for the NPI and Provider name. If either search finds a match that provider will be used, if either search does not find a match the original code will be executed to completion. Test Sites: ---------- Heartland West HCS Erie VAMC, Erie PA Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Patch Installation: Pre-Installation Instructions: -------------------------- If installed during the normal workday, it is recommended that the Outpatient Pharmacy users be off the system. Other VISTA users will not be affected. Install Time - less than 2 minutes (unless otherwise indicated) 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. 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//', NO. a. When prompted 'Enter options you wish to mark as 'Out Of Order':', press the Enter key. b. When prompted 'Enter protocols you wish to mark as 'Out Of Order':', press the Enter key. c. When prompted 'Delay Install (Minutes): (0 - 60): 0//', answer 0. Back-out/Rollback Strategy: ==================== Post Installation Instructions: ------------------------------- None. 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 (598) in the [PATCH LIST] section. ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997 The option Calculate and Show Checksum Values [XTSUMBLD-CHECK] can be run to compare the routine checksums to what is documented in the patch description. 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. No data was modified by this patch installation and, therefore, no rollback strategy is required. Validation of Back-out Procedure --------------------------------- The Back-out Procedure can be verified by printing the first 2 lines of the PSO Routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routines contained in the PSO*7.0*598 patch have been rolled back, the first two lines of the Routines will no longer contain the designation of patch PSO*7.0*598 in the patch list section on line 2 Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOBKDED Before:B101355784 After:B101481664 **11,46,91,78,99,117,133,143, 268,378,416,282,450,402,518, 525,538,457,557,574,598** Routine Name: PSOERXU2 Before: B50733365 After: B56457252 **508,598** Routine list of preceding patches: 508, 574 ============================================================================= User Information: Entered By : Date Entered : FEB 11, 2020 Completed By: Date Completed: AUG 05, 2020 Released By : Date Released : AUG 06, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT