$TXT Created by R at MNTVBB.DOMAIN.EXT (KIDS) on Monday, 04/27/20 at 17:01 ============================================================================= Run Date: JUL 07, 2020 Designation: PSO*7*584 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #496 Status: Released Compliance Date: AUG 08, 2020 ============================================================================= Associated patches: (v)PSO*7*246 <<= must be installed BEFORE `PSO*7*584' (v)PSO*7*385 <<= must be installed BEFORE `PSO*7*584' (v)PSO*7*574 <<= must be installed BEFORE `PSO*7*584' Subject: CLINICAL OUTPATIENT PHARMACY FIXES Category: - Routine Description: ============ This patch will resolve the following issues: INC7454020 - Pro Re Nata (PRN) schedules calculating erroneous default quantity INC7698142 - Duplicate Health Level Seven (HL7) messages sent to Outpatient Pharmacy Automation Interfaces (OPAI) device INC7444486 - Drug Costs report is incorrect Additional Information: ----------------------- Patient Safety Issues (PSIs): HITPS-6870 Defect Tracking System Ticket(s) & Overview: INC7454020 - Some PRN schedules are calculating an erroneously high default quantity when entering orders. PRN orders should not calculate default quantities. Problem: -------- When entering a prescription through Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option, some PRN schedules are creating large default quantities. PRN orders should not calculate default quantities. The quantity should be entered by the provider. Resolution: ----------- A modification has been made in routine PSOSIG to prevent the calculation of a default quantity for a PRN schedule. INC7698142 - Duplicate HL7 messages generated by VistA and sent to OPAI device (PSI: HITPS-6870) Problem: -------- The issue is not related to HL7 messages nor the OPAI device. The issue is actually when a user modifies the number of refills after a prescription has been released. When that happens, the system sends additional records to OPAI device that causes the prescription to be cancelled in the OPAI device. Resolution: ------------ A modification has been made in routine PSOORED7 to prevent modification of the number of refills once the prescription has been released. INC7444486 - Drug Costs report is incorrect Problem: -------- The DRUG COSTS [PSO DRUG COSTS] report option is incorrectly reporting costs for refills by using the amount contained in the unit price (UNIT PRICE OF DRUG (#17) field in the PRESCRIPTION (#52) file) of the original fill instead of using the amount contained in the refill's current unit price of drug (CURRENT UNIT PRICE OF DRUG (#1.2) field in the REFILL (#52.1) sub-file in the PRESCRIPTION (#52) file). Resolution: ----------- The process, Monthly Rx Cost Compilation, that is executed to compile the monthly drug costs was modified (routine PSOCSTM) to use the values contained in the CURRENT UNIT PRICE OF DRUG (#1.2) field in the REFILL (#52.1) sub-file in the PRESCRIPTION (#52) file when totaling the drug costs of refills and partial fills. Test Sites: ----------- Miami HCS (Miami, FL) Oklahoma City HCS (Oklahoma City, OK) Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Patch Installation: ------------------- Pre-Installation Instructions: If installed during the normal workday, it is recommended that the Outpatient Pharmacy users be off the system. Other VistA users will not be affected. Install Time - less than 2 minutes. Installation Instructions: 1. Choose the PackMan message containing this patch. Then select the INSTALL/CHECK MESSAGE PackMan option to load the patch. 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. (ex. PSO*7.0*584) 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 of any routines exported with this patch. It will not backup any other changes such as DDs or templates. 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. iv. When prompted 'Delay Install (Minutes): (0 - 60): 0//', answer 0. 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 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 the PSO*7.0*584 patch 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 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOCSTM Before: B46011931 After: B48241145 **4,17,19,28,89,212,246,584** Routine Name: PSOORED7 Before: B24029981 After: B25174680 **148,247,281,289,358,385,584** Routine Name: PSOSIG Before:B104287072 After:B105661023 **46,99,114,391,313,282,455, 446,402,500,515,514,574,584** Routine list of preceding patches: 246, 385, 574 ============================================================================= User Information: Entered By : Date Entered : OCT 25, 2019 Completed By: Date Completed: JUL 07, 2020 Released By : Date Released : JUL 07, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT