$TXT Created by at MNTVBB.DOMAIN.EXT (KIDS) on Tuesday, 11/03/20 at 08:15 ============================================================================= Run Date: DEC 16, 2020 Designation: PSO*7*628 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #514 Status: Released Compliance Date: JAN 16, 2021 ============================================================================= Associated patches: (v)PSO*7*557 <<= must be installed BEFORE `PSO*7*628' Subject: DC'D/CANCELLED ORDER FINSHED BY PHARMACY Category: - Routine Description: ============ This patch will resolve the following issue: INC11452401 - A cancelled/Discontinued outpatient pharmacy order can be processed by the Patient Prescription Processing option which causes CPRS order to become active. Defect Tracking System Ticket(s) & Overview: INC11452401 - A cancelled/Discontinue outpatient pharmacy order can be processed by the Patient Prescription Processing option which causes CPRS order to become active. Problem: ------- A cancelled outpatient pharmacy order can be processed by the Patient Prescription Processing option. This happens when simultaneously a a provider is dc'ing a pending order while a pharmacist is processing it on the Outpatient Pharmacy package side. On the CPRS site, the order is successfully cancelled. But after the pharmacist finishes the order, the cancelled CPRS order changes to an "active" status but the order text still shows "discontinued". The CPRS provider will not notice this change unless they refresh the patient's screen or revisits the patient's chart at a later time. In the incident reported by the site, the prescription was filled multiple times before it was identified that the provider had originally dc'd it. Resolution: ----------- Modify the logic to add a condition for a status check. When the user selects an entry order, it checks for the status "Discontinued" and display a warning message on the screen. Below is an example that display on the bottom screen: This order had been discontinued Press Return to continue: Test Sites: ----------- Louis Stokes Medical Center (Cleveland) Miami VAMC Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. 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. 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. 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 a. When prompted 'Enter options you wish to mark as 'Out Of Order':', press the Enter key. b. When prompted 'Enter protocols you wish to mark as 'Out Of Order':', press the Enter key. c. When prompted 'Delay Install (Minutes): (0 - 60): 0//', answer 0. Back-Out/Roll Back Plan: ------------------------ Post Installation Instructions: ------------------------------- None. Installation Verification: -------------------------- Successful installation can be verified by reviewing the first 2 lines of the routines contained in the patch. The second line will contain the patch number (628) in the [PATCH LIST] section. ;;7.0;OUTPATIENT MEDICATIONS;**[PATCH LIST]**;16 DEC 97;[BUILD #] The option Calculate and Show Checksum Values [XTSUMBLD-CHECK] can be run to compare the routine checksums to what is documented in the patch description. 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. 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 PSJ 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*628 patch have been rolled back, the first two lines of the Routines will no longer contain the designation of patch PSO*7.0*628 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 5 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOORFIN Before: B73391798 After: B76560802 **7,15,27,32,44,46,84,106,111, 117,131,146,139,195,225,315, 266,338,391,372,416,446,505, 508,557,628** Routine list of preceding patches: 557 ============================================================================= User Information: Entered By : Date Entered : OCT 14, 2020 Completed By: Date Completed: DEC 16, 2020 Released By : Date Released : DEC 16, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT