$TXT Created by MNTVBB.DOMAIN.EXT (KIDS) on Tuesday, 11/09/21 at 08:07 ============================================================================= Run Date: MAR 30, 2022 Designation: PSO*7*658 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #552 Status: Released Compliance Date: APR 30, 2022 ============================================================================= Associated patches: (v)PSO*7*442 <<= must be installed BEFORE `PSO*7*658' Subject: HL7 FIELD ORC-13 IS SOMETIMES BLANK TRANSMITTING TO OUTPATIENT DISPENSE ROBOT Category: - Routine Description: ============ This patch addresses the following issue: 1. HL7 FIELD ORC-13 (Enterer's Location) IS SOMETIMES BLANK TRANSMITTING TO SCRIPTPRO Associated ticket(s): ===================== 1. INC19108358- HL7 FIELD ORC-13 (Enterer's Location) IS SOMETIMES BLANK TRANSMITTING TO OUTPATIENT DISPENSE ROBOT Associated NSR(s): ================== N/A Participating Test Sites: ========================= New Jersey HCS, West Orange NJ Erie VAMC, Erie PA Defect Tracking System Ticket(s) & Overview: =========================================== 1. INC19108358- HL7 FIELD ORC-13 (Enterer's Location) IS SOMETIMES BLANK TRANSMITTING TO OUTPATIENT DISPENSE ROBOT Problem: ------- The ORC-13 field (Enterer's Location) in the HL7 is sometimes blank, causing the system to default to the wrong inventory center. It was found that this occurs when the option PULL EARLY FROM SUSPENSE is used. When running PP (Pull Rx (OP)) from the Outpatient Medications screen in Patient Prescription Processing the issue does not occur and ORC-13 (Enterer's Location) is populated with the selected LABEL PRINTER. Resolution: ---------- Routine PSORXL is modified to pass variable PSOLAP to the background processing job unconditionally. Prior to this patch the variable PSOLAP was only passed when variable SUSPT was false, when SUSPT was true it attempted to pass PFION which doesn't exist anywhere in Vista. Technical Resolution: -------------------- Prior to this patch QLBL+7^PSORXL used the following condition to send either variable PFION or PSOLAP depending on the existence of variable SUSPT: $S($G(SUSPT):"PFION",1:"PSOLAP") This patch modifies QLBL^PSORXL to remove the condition and reference to "PFION" and unconditionally send "PSOLAP" the same as occurs when PP is used in Patient Prescription Processing. I did search all routines, the PROTOCOL file (#101), and the OPTION file (#19) and unsuccessfully located any reference to PFION except in QLBL^PSORXL Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Pre-Installation Instructions: ============================= This patch may be loaded with users on the system. You may wish to install it during non-peak hours. Installation will take less than 1 minute. 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*658 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*658 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*658 patch has 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 2 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSORXL Before:B124632613 After:B125322084 **8,21,24,32,47,135,148,287, 334,251,354,367,370,442,658** Routine list of preceding patches: 442 ============================================================================= User Information: Entered By : Date Entered : SEP 30, 2021 Completed By: Date Completed: MAR 30, 2022 Released By : Date Released : MAR 30, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT