$TXT Created by MNTVBB.DOMAIN.EXT (KIDS) on Thursday, 03/10/22 at 09:40 ============================================================================= Run Date: MAY 13, 2022 Designation: PSO*7*669 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #556 Status: Released Compliance Date: JUN 13, 2022 ============================================================================= Associated patches: (v)PSO*7*617 <<= must be installed BEFORE `PSO*7*669' Subject: ERX ALLOW SELECT PROVIDER BEFORE IT COMPLETE VIA PSO PROVIDER ADD OPTION Category: - Routine Description: ============ This patch will resolve the following issues: 1. INC19990362 - eRx allows selecting providers before complete creation via Option PSO PROVIDER ADD Patient Safety Issues (PSIs): ----------------------------- N/A Additional Information: ----------------------- Defect Tracking System Ticket(s) & Overview: Duplicate ticket: INC20553546,INC20131975 Problem: -------- Option Add New Providers [PSO PROVIDER ADD] creates new provider records in NEW PERSON file 200. If the option is "^" out of before reaching a certain prompt, then the entry gets deleted out of NEW PERSON file. While the provider record is actively being created by Add New Providers [PSO PROVIDER ADD], the provider becomes selectable as a provider in the Outpatient Pharmacy eRx option "Complete Orders from eRx" [PSO ERX FINISH]. If after the eRx is finished and creates a pending order in PENDING OUTPATIENT ORDERS file 52.41, and then the user "^" out of option Add New Providers, then the entire NEW PERSON file provider record is deleted. But the files PENDING OUTPATIENT ORDERS and ORDER file 100 records are not updated and remains pointing to that NEW PERSON entry. In "Patient Prescription Processing" [PSO LM BACKDOOR ORDERS], if the Provider field is edited in the pending prescription, then a hard error occurs. Resolution: ----------- The following changes were made to address the issues listed above: 1) Update the logic for the Option PSO ERX FINISH (Complete Orders from eRx) using Edit in action VM (VALIDATE PROVIDER) to check if the provider is being added. The user will receive a warning message "Provider is being edited by XXX " and will be reprompted to select provider Technical Resolution: --------------------- The following changes were made to address the issues listed above: 1) Routine PSOERX1A in tag PROV was modified to check if the selected provider is locked. The lock is created via option PSO PROVIDER ADD. The user will receive a warning message "Provider is being edited by XXX " and will be reprompted for a new provider if the provider is locked in option Complete Orders from eRx [PSO ERX FINISH] Test Sites: ----------- Birmingham VAMC Birmingham, AL Iron Mountain VAMC Iron Mountain, MI 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-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*669) 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*669. 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/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. If the patch was backed up for the build, from the Kernel Installation and Distribution System Menu, select the Installation Menu. Then select the Install Package(s) option and choose the patch (PSO*7.0*669b) to install. 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 two lines of the routines contained in this patch using the First Line Routine Print [XU FIRST LINE PRINT] option. After the routines contained in this patch have been backed out, the second line of the routines will no longer contain the designation of this patch in the patch list section. 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: PSOERX1A Before:B210939178 After:B226817121 **467,527,508,551,581,617,669** Routine list of preceding patches: 617 ============================================================================= User Information: Entered By : Date Entered : JAN 13, 2022 Completed By: Date Completed: MAY 12, 2022 Released By : Date Released : MAY 13, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT