$TXT Created by at CLN1G1.AAC.DOMAIN.EXT (KIDS) on Thursday, 10/06/22 at 13:21 ============================================================================= Run Date: FEB 15, 2023 Designation: PSO*7*682 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #584 Status: Released Compliance Date: MAR 18, 2023 ============================================================================= Associated patches: (v)PSO*7*441 <<= must be installed BEFORE `PSO*7*682' Subject: INBOUND ERX PENDING ORDER SELECTING WRONG PROVIDER Category: - Routine Description: ============ This patch addresses the following issue: INBOUND ERX PENDING ORDER SELECTING WRONG PROVIDER Associated ticket(s): ===================== 1. INC21921117 - INBOUND ERX PENDING ORDER SELECTING WRONG PROVIDER Associated NSR(s): ================== N/A Defect Tracking System Ticket(s) & Overview: =========================================== 1. INC21921117 - INBOUND ERX PENDING ORDER SELECTING WRONG PROVIDER Problem: ------- Once an eRX order is validated and moved to the PENDING OUTPATIENT ORDERS FILE (#52.41), in the finishing process, if a validated provider has an inactive account in a local VistA system, VistA is picking the last provider used on a previously finished prescription. This problem is not isolated to eRX processing. The same issue occurs if any pending outpatient order has a provider that is inactive or no longer authorized to write orders when it is finished in Patient Prescription Processing [PSO LM BACKDOOR ORDERS]. If a new order is entered in Patient Prescription Processing [PSO LM BACKDOOR ORDERS] prior to processing the pending order that is for an inactive or invalid provider during the finishing process a message displays indicating the provider is inactive or invalid and prompts for a new provider and populates the provider prompt with the provider from the new order. The prompt should default to the provider associated with the PENDING OUTPATIENT ORDERS FILE (#52.41). Resolution: ---------- Routine PSODIR is modified to use the provider from the PENDING OUTPATIENT ORDERS FILE (#52.41) as the default for the provider prompt and not allow it to be overwritten. Technical Resolution: -------------------- There is already code to set the default to the provider from the PENDING OUTPATIENT ORDERS FILE (#52.41) but when PSORX("PROVIDER NAME") exists it overwrites the default. PSORX("PROVIDER NAME") is set to the provider selected during entering a new order for defaulting when entering multiple orders for the same patient. The default is set from the PENDING OUTPATIENT ORDERS FILE (#52.41) PROVIDER field (#5) at line PROVEN+1^PSODIR: DIC("B")=$P(^VA(200,$P($G(OR0),"^",5),0),"^") and is not changed with this patch. At line PROVEN+9^PSODIR, the default, DIC("B"), is overwritten by PSORX("PROVIDER NAME") if it exists: S:$G(PSORX("PROVIDER NAME"))]"" DIC("B")=PSORX("PROVIDER NAME"), this line is changed to: S DIC("B")=$S($G(DIC("B"))]"":DIC("B"),1:$G(PSORX("PROVIDER NAME"))) This change allows the default from the PENDING OUTPATIENT ORDERS FILE (#52.41) to be used while not affecting other processing that also uses PROVEN^PSODIR for prompting for the provider. Participating Test Sites: ========================= Erie VAMC, Erie PA TN Valley HCS, Nashville TN Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Patch Installation: ------------------- Pre/Post Installation Overview: 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. 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 PSO*7.0*682 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 PSO*7.0*682 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 Post-Installation Instructions: Back-out/Rollback 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 build 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 build 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 build from the backup created. No data was modified by this patch installation and, therefore, no rollback strategy is required. 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: PSODIR Before:B139275213 After:B140806117 **37,46,111,117,146,164,211, 264,275,391,372,416,422,504, 457,572,587,441,682** Routine list of preceding patches: 441 ============================================================================= User Information: Entered By : Date Entered : APR 18, 2022 Completed By: Date Completed: FEB 14, 2023 Released By : Date Released : FEB 15, 2023 ============================================================================= Packman Mail Message: ===================== $END TXT