$TXT Created by F at CLN1G1.AAC.DOMAIN.EXT (KIDS) on Saturday, 10/22/22 at 09:44 ============================================================================= Run Date: DEC 12, 2022 Designation: PSO*7*706 Package : PSO - OUTPATIENT PHARMACY Priority: EMERGENCY Version : 7 SEQ #572 Status: Released Compliance Date: DEC 14, 2022 ============================================================================= Associated patches: (v)PSO*7*692 <<= must be installed BEFORE `PSO*7*706' Subject: MOVE OF ERX AUTO-MATCH FOR DRUG AND PROVIDER TO VISTA (VERSION 2) Category: - Routine Description: ============ This patch will address the following issue: 1. INC23078077 - Delayed delivery of electronic doctor orders through VHA Inbound eRx hub Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC23078077 - Delayed delivery of electronic doctor orders through VHA Inbound eRx hub Problem: ------- Patch PSO*7*692 was released on September 21st, 2022 to address this issue. However, an issue was discovered with the logic to auto-match Prescriber and Drug in VistA once the eRx XML message is received from the eRx Hub. Resolution: ------------- This patch corrects the auto-match VistA algorithm to addresses this issue. Technical Resolution: -------------------- Patch PSO*7*692 assumed that the XML parameter in the PSOERXI1 INCERX RPC Broker call (responsible for processing incoming eRx from the eRx Hub) contained the entire eRx XML record. However, during tests with the updated eRx Hub it turned out that the incoming XML message is fragmented in 3 parameters: XML, XML2 and XML3. Information about Prescriber and Drug seems to be sent on XML2 and that's why the logic in PSO*7*692 failed. This patch now checks the parsed information stored in the ^TMP($J,"PSOERXO1") global, which is supposed to contain the complete incoming XML information from XML, XML2 and XML3. 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*706) 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*706) 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*706 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 1 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOERXI1 Before:B214011411 After:B214099544 **581,617,692,706** Routine list of preceding patches: 692 ============================================================================= User Information: Entered By : Date Entered : OCT 20, 2022 Completed By: Date Completed: DEC 12, 2022 Released By : Date Released : DEC 12, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT