$TXT Created by MNTVBB.DOMAIN.EXT (KIDS) on Monday, 12/13/21 at 14:53 ============================================================================= Run Date: JAN 04, 2022 Designation: PSJ*5*422 Package : PSJ - INPATIENT MEDICATIONS Priority: Mandatory Version : 5 SEQ #367 Status: Released Compliance Date: FEB 04, 2022 ============================================================================= Associated patches: (v)PSJ*5*325 <<= must be installed BEFORE `PSJ*5*422' Subject: NON-VERIFIED/PENDING ORDERS PROCESSING Category: - Routine - Data Dictionary Description: ============ This patch addresses the following issues: 1. INC15531625 - Pharmacy Package Delay in pulling up the pending inpatient medication order queue (Non-Verified/Pending Orders) INC17772912 (Duplicate) - delays with Pending Inpatient Orders 2. INC17835358 - Non-verified/pending orders summary not accurate 3. INC17835358 - Clinic Meds are not being counted under Clinic location Note: INC17835358 is a single ticket but actually 2 separate issues which is why it is listed twice. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- PHARMACY PATIENT (#55) UNIT DOSE (#55.06) NV FLAG (#51) Modified ANV index description PHARMACY PATIENT (#55) IV (#55.01) PV FLAG (#142) Modified APIV index description PHARMACY PATIENT (#55) IV (#55.01) NV FLAG (#143) Modified ANIV index description Defect Tracking System Ticket(s) & Overview: 1. INC15531625 - Pharmacy Package Delay in pulling up the pending inpatient medication order queue (Non-Verified/Pending Orders) Duplicate - INC17772912 - delays with Pending Inpatient Orders Problem: -------- When a user goes to the Non-Verified/Pending Orders [PSJU VBW] option to view a summary, the screen displays Searching for Pending and Non-Verified orders followed by many dots which seem to delay the display of the summary report. Resolution: ----------- This delay is due to the report parsing through APV & APIV indexes of PHARMACY PATIENT (#55) file when a pharmacist runs the report or the ANV & ANIV indexes of PHARMACY PATIENT (#55) file when a non-pharmacist runs the report. The APV index is used to identify orders that have been verified by a nurse but not a pharmacist. The APIV index is used to identify IV orders that have been verified by a nurse but not a pharmacist. The ANV index is used to identify orders that have been verified by a pharmacist but not a nurse. The ANIV index is used to identify IV orders that have been verified by a pharmacist but not a nurse. Parsing through these indexes causes invalid counts on the report as well as a delay in processing and displaying the results. Routine PSGVBWU is modified to remove this code from the report. This will leave only the summary counts obtained from the NON-VERIFIED ORDERS (#53.1) file. Prior to this patch a dot displayed for each patient encountered in the NON-VERIFIED ORDERS (#53.1) file as well as a dot for each patient encountered in the PHARMACY PATIENT (#55) file. After this patch a dot will only be displayed for every 25 patients encountered in the NON-VERIFIED ORDERS (#53.1) file. Technical Resolution: --------------------- Prior to this patch CNTORDRS+6^PSGVBWU contained a W "." Which displayed a dot for each patient reviewed. After the patch the W command is changed to W:PSJPCNT#25=0 "." and is now in line CNTORDRS+8^PSGVBWU: .S PSJPCNT=PSJPCNT+1 W:PSJPCNT#25=0 "." The code that was removed were lines CNTORDRS+17^PSGVBWU through CNTORDRS+61^PSGVBWU. This comment was added in place of these lines: ;PSJ*5.0*422: Deleted logic searching file 55 since the subscripts ; searched do not apply to pending/non-verified orders. ; The additional unneeded searches caused sessions to ; hang at sites until the searches completed. During investigation of this issue, it was also discovered that the description for several indexes were incorrect. Index ANV in PHARMACY PATIENT (#55) file incorrectly stated: - This is used to identify orders that have been verified by a nurse but not a pharmacist. It should read: - This is used to identify orders that have been verified by a pharmacist but not a nurse. Index APIV in PHARMACY PATIENT (#55) file incorrectly stated: - This is used to identify orders that have not been verified by a pharmacist. It should read - This is used to identify orders that have been verified by a nurse but not a pharmacist. Index ANIV in PHARMACY PATIENT (#55) file incorrectly stated: - This is used to identify orders that have not been verified by a nurse. It should read - This is used to identify orders that have been verified by a pharmacist but not a nurse. The index descriptions above are updated and corrected with this patch. 2. INC17835358 - Non-verified/pending orders summary not accurate Problem: -------- If you have patients with the following orders on their profile, when using Non-Verified/Pending Orders [PSJU VBW] option, processing for Non-Verified orders has the following issues. - Patient 1 and 2 both have Non-Verified IV and Non-Verified Unit Dose orders on the profile. If the Non-Verified IV order was entered first, i.e. before the Non-Verified Unit Dose order, when selecting to process Non-Verified IV Orders for the Ward no orders will be found for those patients. - Patient 1 and 2 both have Non-Verified Unit Dose and Non-Verified IV orders on the profile. If the Non-Verified Unit Dose order was entered first, i.e. before the Non-Verified IV order, when selecting to process Non-Verified Unit Dose Orders for the Ward no orders will be found for those patients. Resolution: ----------- Routine PSGVBW is modified so that orders are displayed correctly. Technical Resolution: --------------------- Lines IF+11 through IF+16 of routine PSGVBW were modified. 3. INC17835358 - Clinic Meds are not being counted under Clinic location Problem: -------- When running the Non-Verified/Pending Orders report and requesting the Order Summary, any clinic orders encountered for a patient that is admitted will appear in the ward groups/ward summary instead of in the clinic group/clinic summary. Resolution: ----------- Routine PSGVBWU is modified to check if the order is in a clinic location before determining if the patient is assigned to a ward. Technical Resolution: --------------------- Routine PSGVBWU was modified from line CNTORDRS+5^PSGVBWU through line CNTORDRS+20^PSGVBWU Test Sites: ----------- Central Arkansas Healthcare System (Little Rock, AR) San Diego Healthcare System (San Diego, 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 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 the patch or build name. (ex. PSJ*5.0*422) 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*422. 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 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. 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 (PSJ*5.0*422b) to install. The back-out plan is to restore the routines from the backup created. No data was modified by this patch installation and, therefore, no rollback strategy is required. While no data was modified by this patch installation there was a change to the FileMan Data Dictionary for the PHARMACY PATIENT (#55) file. Indexes ANV, APIV and ANIV had minor changes to their descriptions. When the backup of the build is restored the Data Dictionary will be reset and the changes rolled back. 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 routines contained in the PSJ*5.0*422 patch have 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. The Data Dictionary should be checked for PHARMACY PATIENT (#55) file for the ANV, APIV and ANIV indexes to confirm the text changes were rolled back. If only routines were backed up then these will need to be manually edited to be restored. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.0;INPATIENT MEDICATIONS;**[Patch List]**;DEC 16, 1997;Build 9 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSGVBW Before: B98265649 After: B98719044 **5,16,39,59,62,67,58,81,80, 110,111,133,139,155,241,243, 265,275,304,325,422** Routine Name: PSGVBWU Before: B77076603 After: B47091956 **3,44,47,67,58,110,111,196,241,422** Routine list of preceding patches: 325 ============================================================================= User Information: Entered By : Date Entered : JUL 28, 2021 Completed By: Date Completed: JAN 03, 2022 Released By : Date Released : JAN 04, 2022 ============================================================================= Packman Mail Message: ===================== $END TXT