$TXT Created by MNTVBB.DOMAIN.EXT (KIDS) on Tuesday, 12/27/22 at 08:13 ============================================================================= Run Date: FEB 14, 2023 Designation: PSJ*5*437 Package : PSJ - INPATIENT MEDICATIONS Priority: Mandatory Version : 5 SEQ #376 Status: Released Compliance Date: MAR 17, 2023 ============================================================================= Associated patches: (v)PSJ*5*416 <<= must be installed BEFORE `PSJ*5*437' Subject: COMPLEX CLINIC MEDS IV ORDERS NOT DISPLAYING UNDER CLINIC LOCATION Category: - Routine Description: ============ This patch addresses the following issue: Complex Clinic Medications orders finished as IV orders incorrectly display under the Inpatient section of the Inpatient Medication profile instead of under the Clinic Location. Defect Tracking System Ticket(s) & Overview: 1. INC22909170 - Order placed in an outpatient clinic location sent erroneously to IV medications package Duplicate - INC23448603 - Clinic complex IV order is coming over as IV infusion after processing Problem: -------- A complex Clinic Medications order for an IV medication is entered in the Computerized Patient Record System (CPRS) and then finished as an IV and accepted in VistA's Inpatient Order Entry option [PSJ OE]. The resulting orders, either Non-Verified or Active, incorrectly display under the Inpatient section of the Inpatient Medication profile. The orders should display under the Clinic Location on the profile. When selecting and viewing these orders, the Visit Date (Field 16) is not populated. This issue is caused by the APPOINTMENT DATE/TIME field (#139) of the IV multiple (#100) in the PHARMACY PATIENT file (#55) not getting populated when the orders are finished. Resolution: ----------- Routine PSJCOMV has been modified to populate the APPOINTMENT DATE/TIME field (#139) of the IV multiple (#100) in the PHARMACY PATIENT file (#55). Technical Resolution: --------------------- The following code has been added at line IV+8^PSJCOMV: S:+$G(P("APPT")) $P(^TMP("PSJCOM",$J,+ON,"DSS"),U,2)=P("APPT") This will populate the DSS node piece 2 of the ^TMP "PSJCOM" global that will end up in the APPOINTMENT DATE/TIME field (#139) and in variable ORAPPT where it is used in routine IV^ORMPS1 to determine the DIALOG for the order. Test Sites: ----------- Coatesville VAMC (Coatesville, PA) VA Central California HCS (Fresno, CA) 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. It is not necessary to disable any options. 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 PSJ*5.0*437. 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 PSJ*5.0*437. 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: ------------------------------- None Installation Verification: -------------------------- Successful installation can be verified by reviewing the first 2 lines of the routine contained in the patch. The second line will contain the patch number (437) in the [PATCH LIST] section. The Calculate and Show Checksum Values [XTSUMBLD-CHECK] option can be run to compare the routine checksums to what is documented in the patch description. 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 the 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. Then select the Install Package(s) option [XPD INSTALL BUILD] and choose the patch (PSJ*5.0*437b) 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 printing the first 2 lines of the routine contained in this patch using the First Line Routine Print option [XU FIRST LINE PRINT]. Once the routine contained in the PSJ*5.0*437 patch has been backed out, the first two lines of the routine 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: ;;5.0;INPATIENT MEDICATIONS;**[Patch List]**;16 DEC 97;Build 2 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSJCOMV Before: B41451152 After: B42072783 **110,127,267,257,281,416,437** Routine list of preceding patches: 416 ============================================================================= User Information: Entered By : Date Entered : JUL 20, 2022 Completed By: Date Completed: FEB 14, 2023 Released By : Date Released : FEB 14, 2023 ============================================================================= Packman Mail Message: ===================== $END TXT