$TXT Created by L at MNTVBB.DOMAIN.EXT (KIDS) on Wednesday, 01/24/24 at 08:22 ============================================================================= Run Date: APR 23, 2024 Designation: PSO*7*742 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #618 Status: Released Compliance Date: MAY 24, 2024 ============================================================================= Associated patches: (v)PSO*7*728 <<= must be installed BEFORE `PSO*7*742' Subject: ONEVA FILLS NOT MATCHING IN SCRIPTPRO Category: - Routine Description: ============ This patch addresses one issue: A site reported that when they fill some OneVA prescriptions from other VA host sites into their ScriptPro via the OPAI interface, the dispense drug comes across as UNKNOWN in ScriptPro. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File Number New/Modified/Deleted --------- ----------- -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ------------ ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A List Templates Associated: Template Name Type New/Modified/Deleted ------------- ---- ------------ N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSI's) ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: =========================================== INC29058009- OneVA fills not recognized in ScriptPro through OPAI Problem: -------- A site reported that when they fill some OneVA prescriptions from other VA host sites into their ScriptPro via OPAI interface, the dispense drug comes across as UNKNOWN in ScriptPro. Resolution: ----------- A modification to routine PSOHLDS5 was made to assign the dispense drug name in the RXE segment of the HL7 record equal to the VA PRINT NAME (#5) from the VA PRODUCT file (#50.68). Previously, the value of the dispense drug name was assigned the value of the NAME field (#.01) in the VA PRODUCT file. Test Sites: ----------- Manchester VAMC, Manchester NH Orlando VAMC, Orlando FL SNOW Change Order #: -------------------- Manchester CO# - CHG0468879 Orlando CO# - CHG0467914 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 2 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 name. (ex. PSO*7.0*742). 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*742. 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. Post-Installation Instructions: ------------------------------- N/A 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 routine in a mail message using the Backup a Transport Global [XPD BACKUP] menu option from the Kernel Installation and Distribution System Menu and selecting the Installation Menu. The back-out plan is to restore the routine from the backup created. The message containing the backed-up routine 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 routine onto the VistA System. If the patch was backed up for the build, from the Kernel Installation and Distribution System Menu, select the Installation Menu. Select the Install Package(s) option and choose the patch (PSO*7.0*742b) to install. 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 confirming the checksums have been returned to the pre-patch value using CHECK1^XTSUMBLD. It can also be verified by printing the first 2 lines of the PSO routine(s) contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routine(s) contained in this patch have been backed out, the Second line of each routine will no longer contain the designation of patch PSO*7.0*742 Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 1 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOHLDS5 Before:B211463334 After:B211463834 **643,728,742** Routine list of preceding patches: 728 ============================================================================= User Information: Entered By : Date Entered : OCT 11, 2023 Completed By: Date Completed: APR 23, 2024 Released By : Date Released : APR 23, 2024 ============================================================================= Packman Mail Message: ===================== $END TXT