$TXT Created by at CLN1G1.AAC.DOMAIN.EXT (KIDS) on Wednesday, 05/19/21 at 15:09 ============================================================================= Run Date: JUL 06, 2021 Designation: PSO*7*639 Package : PSO - OUTPATIENT PHARMACY Priority: EMERGENCY Version : 7 SEQ #527 Status: Released Compliance Date: JUL 08, 2021 ============================================================================= Associated patches: (v)PSO*7*457 <<= must be installed BEFORE `PSO*7*639' (v)PSO*7*626 <<= must be installed BEFORE `PSO*7*639' Subject: VISTA OUTPATIENT GENERATES AN ERROR WHEN SPEED RENEW IS USED Category: - Routine Description: ============ This patch will address the following issues: 1. INC17106168 - Cincinnati VISTA application is not allowing me to renew prescription orders. Duplicates: ----------- INC17248638 - Speed renewal function in HAC back door VistA is kicking all our users out of VistA. INC18019604 - Unable to use renew function when entering RX's -- 'CID+#^PSOUTL' Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC17106168 - Cincinnati VISTA application is not allowing me to renew prescription orders. Duplicates: ----------- INC17248638 - Speed renewal function in HAC back door VistA is kicking all our users out of VistA. INC18019604 - Unable to use renew function when entering RX's -- 'CID+#^PSOUTL' Problem: ------- The Dayton VA Medical Center reported an error with the Speed Renew action in the Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option. It was confirmed that this issue was introduced by patch PSO*7.0*626. Resolution: ------------- The patch address the error and also allows the user to enter an ISSUE DATE up to 1 year in the past for speed renewals. Before the users were limited to a date no greater than 6 months. Then, it will screen out any CS prescriptions if the ISSUE DATE entered is greater than 6 months with the following message: Rx# 2299064 - Rx is for a CS Drug and the Issue Date entered (Jul 17, 2020) is greater than 6 months. Type to continue or '^' to exit: Technical Resolution: -------------------- Changed the code under line tags CID and CIDH to allow and ISSUE DATE value of up to 360 days in the past if the variable DA is defined and the Rx is non-CS or if the variable DA is not defined. And restrict a date up to 180 days in the past if the variable DA is defined and the Rx is CS. Introduced code at PROCESS+22 in the routine PSORENW4 to screen out CS prescriptions if the ISSUE DATE value is greater than 180 days. Test Sites: ----------- South Texas Veterans Health Care System, (San Antonio, TX) VA Maryland Health Care System - Perry Point Division (Perry Point, MD) 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*639) 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*639) 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*639 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: PSORENW4 Before: B91746035 After: B95512266 **11,23,27,32,37,64,46,75,71, 100,130,117,152,148,264,225, 301,390,313,411,444,504,508, 550,457,639** Routine Name: PSOUTL Before:B182315264 After:B184065130 **1,21,126,174,218,259,324,390, 313,411,466,477,626,639** Routine list of preceding patches: 457, 626 ============================================================================= User Information: Entered By : Date Entered : MAR 17, 2021 Completed By: Date Completed: JUL 06, 2021 Released By : Date Released : JUL 06, 2021 ============================================================================= Packman Mail Message: ===================== $END TXT