$TXT Created by MNTVBB.DOMAIN.EXT (KIDS) on Monday, 02/13/23 at 09:29 ============================================================================= Run Date: MAR 02, 2023 Designation: PSO*7*689 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #585 Status: Released Compliance Date: MAR 31, 2023 ============================================================================= Associated patches: (v)PSO*7*646 <<= must be installed BEFORE `PSO*7*689' (v)PSO*7*651 <<= must be installed BEFORE `PSO*7*689' Subject: ERX - REQUEST THE FORMULARY STATUS DISPLAYS WHEN MATCHING DRUG Category: - Routine Description: ============ This patch addresses the following issue: Sites have requested to have the non-Formulary identifier (***N/F***) show after auto drug match and a previous manual validation. Associated ticket(s): ===================== 1. INC22708310 eRx - Requesting the formulary status of VistA drugs display when matching them Defect Tracking System Ticket(s) & Overview: =========================================== 1. INC22708310 eRx - Requesting the formulary status of VistA drugs display when matching them Problem: ------- Fayetteville VA Medical Center (AR) is requesting non-Formulary identifier to show after auto drug match and a previous manual validation. This could be a patient safety issue and is a cost issue. Non-formulary drugs are slipping through that probably should not. This would help efficiency while processing prescriptions from the inbound eRX queue. Resolution: ---------- In option Complete Orders from eRx [PSO ERX FINISH], on the second screen of the eRx Holding Queue Display and the second screen of PSO ERX DRUG VALIDATION, the non-Formulary identifier (***N/F***) is added to the right of the Vista Drug. In addition, when validating the drug/sig, the non-Formulary identifier (***N/F***) will be added in two places; to the right of the drug on the prompts 'Current Vista Drug:' and 'You have selected:'. Technical Resolution: -------------------- Routine PSOERX1G is modified to display the non-Formulary identifier (***N/F***) on line DISPRX+4^PSOERX1G Before patch .S LINE=LINE+1 D SET^VALM10(LINE,"Vista Drug"_$S(DRMANVAL:"[v]",1:"")_": "_VADRG_" "_$P($$VADRSCH^PSOERXUT(VADRGIEN),"^",3)) After patch .S PSONF="" I $G(VADRGIEN) S PSONF=$S($P(^PSDRUG(VADRGIEN,0),"^",9):"***(N/F)***",1:"") ;p689 .S LINE=LINE+1 D SET^VALM10(LINE,"Vista Drug"_$S(DRMANVAL:"[v]",1:"")_": "_VADRG_" "_$P($$VADRSCH^PSOERXUT(VADRGIEN),"^",3)_PSONF) Routine PSOERXD1 is modified to display the non-Formulary identifier (***N/F***) on line INIT+109^PSOERXD1 Before patch S LINE=LINE+1 D SET^VALM10(LINE," (1) Vista Drug: "_VADRG_" "_$P($$VADRSCH^PSOERXUT(VADRGIEN),"^",3)) After patch S PSONF="" I $G(VADRGIEN) S PSONF=$S($P(^PSDRUG(VADRGIEN,0),"^",9):"***(N/F)***",1:"") ;p689 S LINE=LINE+1 D SET^VALM10(LINE," (1) Vista Drug: "_VADRG_" "_$P($$VADRSCH^PSOERXUT(VADRGIEN),"^",3)_PSONF) Routine PSOERXD2 is modified to display the non-Formulary identifier (***N/F***) on lines VDRG1+9^PSOERXD2 & VDRG1+23^PSOERXD2. VDRG1+9^PSOERXD2 Before patch: I VAODRG W !,"Current Vista Drug: "_$$GET1^DIQ(50,VAODRG,.01,"E")_" "_$P($$VADRSCH^PSOERXUT(VAODRG),"^",3) After patch I VAODRG W !,"Current Vista Drug: "_$$GET1^DIQ(50,VAODRG,.01,"E")_" "_$P($$VADRSCH^PSOERXUT(VAODRG),"^",3)_$S($P(^PSDRUG(VAODRG,0),"^",9):" ***(N/F)***",1:"") VDRG1+23^PSOERXD2 Before patch: W !!,"You have selected: "_$P(Y,U,2),!,"Would you like to use this drug/supply?" S DIR(0)="YO" D ^DIR K DIR After patch: W !!,"You have selected: "_$P(Y,U,2)_ )_$S($P(^PSDRUG(+Y,0),"^",9):" ***(N/F)***",1:""),!,"Would you like to use this drug/supply?" S DIR(0)="YO" D ^DIR K DIR Test Sites: ========== Fayetteville VAMC, Fayetteville AR Manchester VAMC, Manchester NH Associated NSR(s): ================== N/A 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*689 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*689 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 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 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. 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 build contained in the PSO*7.0*689 patch has been backed out, the first two lines of the routine 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 13 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOERX1G Before:B181029040 After:B182938181 **617,646,689** Routine Name: PSOERXD1 Before:B165859081 After:B167376443 **467,520,551,582,581,635,617, 651,689** Routine Name: PSOERXD2 Before:B181925759 After:B183005048 **467,506,520,508,551,581,617, 651,689** Routine list of preceding patches: 646, 651 ============================================================================= User Information: Entered By : Date Entered : JUN 02, 2022 Completed By: Date Completed: MAR 02, 2023 Released By : Date Released : MAR 02, 2023 ============================================================================= Packman Mail Message: ===================== $END TXT