$TXT Created by F at CLN1G1.AAC.DOMAIN.EXT (KIDS) on Wednesday, 07/06/22 at 10:39 ============================================================================= Run Date: SEP 21, 2022 Designation: PSO*7*692 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #566 Status: Released Compliance Date: OCT 11, 2022 ============================================================================= Associated patches: (v)PSO*7*617 <<= must be installed BEFORE `PSO*7*692' (v)PSO*7*639 <<= must be installed BEFORE `PSO*7*692' Subject: MOVE OF ERX AUTO-MATCH FOR DRUG AND PROVIDER TO VISTA Category: - Routine Description: ============ This patch will address the following issue: Meds-By-Mail (MbM) reported that electronic prescriptions (eRx) are received several hours after the outside prescriber transmitted them. Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC23078077 - Delayed delivery of electronic doctor orders through VHA Inbound eRx hub Problem: ------- Meds-By-Mail (MbM) reported that electronic prescriptions (eRx) are received several hours after the outside prescriber transmitted them. The problem seems to be caused by a increasing traffic handled by the eRx Hub which centralizes all nationwide incoming eRx prescriptions into the VA. One part of the processing by the eRx Hub is the auto-matching of patient, provider and drug. In other words, the eRx Hub tries to pre-emptively find a VistA corresponding for these three fields before forwarding the incoming prescription to the VistA site. The auto-matching for the provider and drug is accomplished by the eRx Hub through two VistALink calls (one for the provider and one for the drug) to the VistA site and if a match is found at the VistA site it returns the IENs (Internal Entry Number) back to the eRx Hub which in turn records the success/failure for an auto-match statistics reporting purpose and then sends the matched IENs back to the VistA site along with the complete eRx prescription. Although not 100% confirmed, the suspicion is that such calls to VistA have become quite costly as the volume of incoming eRx increased drastically in the past few months and are likely to be partially responsible for the processing delays. Resolution: ---------- The solution to this problem is two-fold: 1) A change is being made in VistA through this patch to the processing of the incoming eRx to check if the eRx Hub provider and drug auto-matches were successful or not ("fail"). If not, using the incoming data from the outside prescriber VistA will utilize the exact same VistA code currently used by the eRx Hub to try to auto-match these locally and if it succeeds it will auto populate VistA Provider and/or VistA Drug fields. 2) Once this patch has been released and installed nationally at every VistA site, an update will then be made at the eRx Hub to shut off the auto-match processing for provider and drug. This will consist of stopping the two VistALink calls made to the VistA site and always sending to VistA a "fail" result with an "Auto-match not performed" reason. Technical Resolution: -------------------- A new routine (PSOERUT) was created to parse an XML message into a local array and code was added to INCERX+29^PSOERXI1 and INCERX+48^PSOERXI1 to call the new API XML2GBL in the new routine to parse the incoming XML message, retrieve the provider and drug information and call the same code the eRx Hub was calling (via RPC calls) to perform the auto-match for provider and drug (PRVMTCH^PSOERXA0 and DRGMTCH^PSOERXA0). Furthermore, it was determined that the array variable (PSODRUG("IEN")) used at CSID+9^PSOUTL, used to check if a drug is a controlled substance or not, was wrong and was replaced with DRGIEN. Test Sites: ---------- West Palm Beach VAMC, (West Palm Beach, FL) Meds by Mail 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/Post Installation Overview: ------------------------------ There are no pre/post installation routines included with this patch. 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. (ex. PSO*7.0*692) 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 (ex. PSO*7.0*692) 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//', respond NO. ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', respond NO. iii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', respond NO. iv. When prompted 'Delay Install (Minutes): (0 - 60): 0//', respond 0. Post-Installation Instructions: ------------------------------ None. 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 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 Back-out Procedure: -------------------------------- The Back-out Procedure can be verified by printing the first 2 lines of the routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routines contained in patch PSO*7.0*692 have been backed out, the first two lines of the routines will no longer contain the designation of this patch 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 4 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOERUT Before: n/a After: B2212347 **692** Routine Name: PSOERXI1 Before:B182379733 After:B214011411 **581,617,692** Routine Name: PSOUTL Before:B184065130 After:B183877997 **1,21,126,174,218,259,324,390, 313,411,466,477,626,639,692** Routine list of preceding patches: 617, 639 ============================================================================= User Information: Entered By : Date Entered : JUN 27, 2022 Completed By: Date Completed: SEP 21, 2022 Released By : Date Released : SEP 21, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT