$TXT Created by at CLN1G1.AAC.DOMAIN.EXT (KIDS) on Wednesday, 10/28/20 at 12:32 ============================================================================= Run Date: DEC 17, 2020 Designation: PSO*7*609 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #515 Status: Released Compliance Date: JAN 16, 2021 ============================================================================= Associated patches: (v)PSO*7*434 <<= must be installed BEFORE `PSO*7*609' Subject: OPAI CERTIFIED MAIL ISSUES Category: - Routine Description: ============ This patch will resolve the following issue: 1) When using Patient Prescription Processing [PSO LM BACKDOOR ORDERS] Menu Option and the user selects PU (Patient Update), if the user selects option #4 LOCAL CERTIFIED MAIL for at the MAIL: prompt, the selection will not be reflected in the RXD segment of the Prescription Dispense HL7 records for the OPAI (Out Patient Automated Interface). Defect Tracking System Ticket(s) & Overview: 1) INC9883331 - OPAI Not Sending "CERTIFIED MAIL" for patients with Pharmacy Patient Mail preference of "4 - LOCAL CERTIFIED MAIL" Problem 1: ---------- When Selecting #4 - LOCAL CERTIFIED MAIL during Patient Update in PSO LM BACKDOOR ORDERS at the MAIL:Prompt, the HL7 prescription record RXD segment (pc 13) will not be populated with CERTIFIED MAIL but will be populated with REGULAR MAIL. Resolution 1: ------------- A modification will be made in routine PSOHLDS1 to evaluate the LOCAL CERTIFIED MAIL selection and update the HL7 record correctly. Test Sites: ----------- VA Central California Health Care System (Fresno, CA) Wilkes-Barre VA Medical Center (Wilkes Barre, PA) 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: PSO*7.0*609 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. Post-Installation Instructions: ------------------------------- NONE Back-Out/Roll Back Plan: ------------------------ In the event of a catastrophic failure, the Facility CIO may make the decision to back-out the patch. It is imperative that you have performed a backup of the routine included in this patch prior to installation. The back-out plan is to restore the routine from the backup created. No data was modified by this patch installation and, therefore, no rollback strategy is required. To verify the back-out completed successfully, ensure the checksum matches the pre-patch checksum from the patch descriptions. Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 6 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOHLDS1 Before: B48730314 After: B50888998 **156,232,255,200,305,336,351, 434,609** Routine list of preceding patches: 434 ============================================================================= User Information: Entered By : Date Entered : APR 01, 2020 Completed By: Date Completed: DEC 17, 2020 Released By : Date Released : DEC 17, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT