$TXT Created by               F at CLN1G1.AAC.DOMAIN.EXT  (KIDS) on Tuesday, 10/04/22 at 09:41
=============================================================================
Run Date: JAN 25, 2023                     Designation: PSJ*5*426
Package : PSJ - INPATIENT MEDICATIONS         Priority: Mandatory
Version : 5       SEQ #375                      Status: Released
                  Compliance Date: FEB 25, 2023
=============================================================================

Associated patches: (v)PSJ*5*51    <<= must be installed BEFORE `PSJ*5*426'
                    (v)PSJ*5*353   <<= must be installed BEFORE `PSJ*5*426'
                    (v)PSJ*5*364   <<= must be installed BEFORE `PSJ*5*426'
                    (v)PSJ*5*373   <<= must be installed BEFORE `PSJ*5*426'
                    (v)PSJ*5*399   <<= must be installed BEFORE `PSJ*5*426'

Subject: NURSE-VERIFICATION OUT OF SYNC BETWEEN CPRS AND BCMA

Category: 
  - Routine

Description:
============

 This patch will resolve the following issues:
   
 1) INC20355923-HITP-8866 - Medication order activated by pharmacy and
    verified by nursing, but not able to give in BCMA as it is acting like
    it isn't after Renewal Complex Order
  
    INC22900561(d)-HITPS-8861
  
 2) INC20555433 - Pharmacy Hold not setting Nurse Verify when ON/OFF action in
                  pharmacy.
   
 3) INC23152064 - MOCHA alert scrolled off the screen when a med with no
                  GCNSEQNO
  
 Defect Tracking System Ticket(s) & Overview:
 --------------------------------------------
 1) INC20355923-HITP-8866 - Medication order activated by pharmacy and
    verified by nursing, but not able to give in BCMA as it is acting like
    it isn't after Renewal Complex Order
    
    INC22900561(d)-HITPS-8861
  
 Problem:
 --------
 The Togus VA Medical Center reported that nurse verification was reset in BCMA
 after the order expired. It was confirmed that once an inpatient order expired
 the software was removing the BCMA verification information while in CPRS the
 order remained verified.
  
 Resolution:
 ----------
 The software was changed to not remove the nurse verification in BCMA when the
 order is expired.
  
 Technical Resolution:
 --------------------
 The line of code at ORC+8^PSJHL4 was modified to avoid resetting the Nurse
 Verification information when a expiration messages (PSOC="SS") is received
 from CPRS. In addition, a new API was created in PSJUTL3 called DELNV to 
 remove the BCMA Nurse verification because it was used to address the issue
 below.
    
 2) INC20555433 - Pharmacy Hold not setting Nurse Verify when ON/OFF action in
                  pharmacy.
  
 Problem:
 --------
 It was reported that nurse verification was reset in CPRS when an order is
 placed or removed from hold through the Inpatient Pharmacy application
 while in BCMA the order remains nurse verified.
  
 Resolution:
 ----------
 The software was changed to remove the nurse verification in BCMA when the
 order is placed or removed from Hold.
  
 Technical Resolution:
 --------------------
 Included code at HOK+7^PSGOEH1 and HOK+11^PSGOEH0 (for Unit Dose orders), and
 HOLD+4^PSIVOE (for IV orders) to remove the BCMA Nurse verification (call to
 DELNV^PSJUTL3) when an order is placed or removed from hold.
   
 3) INC23152064 - MOCHA alert scrolled off the screen when a med with no
                  GCNSEQNO
  
 Problem:
 --------
 Rocky Mountain Regional VA Medical Center reported that sometimes the Order
 Checks alerts (example below) displayed on the screen does not present a
 prompt for the user to hit <RET> continue, for example, after reading the
 alert. Instead, it hangs for 2 seconds and disappears from the screen, which
 requires the user to scroll up on the terminal emulator in order to view
 the error message. It was observed by the reporting user that this happened
 when the dispense drug was matched to an NDF VA Product without a value in
 GCNSEQNO field.
  
   Order Check Message Example:
   ---------------------------
   Order Checks could not be done for Drug: FERROUS BISGLYCINATE 90MG CAP,ORAL,
   please complete a manual check for Drug Interactions, Duplicate Therapy and
   appropriate Dosing.  
  
 Resolution:
 ----------
 The software was written to only pause when the display of the alert message
 above would display at the bottom of the screen. A change was made to always
 pause (as shown below) after the message above is displayed independently
 where in the screen the message is displayed.
  
   Order Check Message Example:
   ---------------------------
   Order Checks could not be done for Drug: FERROUS BISGLYCINATE 90MG CAP,ORAL,
   please complete a manual check for Drug Interactions, Duplicate Therapy and
   appropriate Dosing.  
  
   Press Return to continue...
  
 Technical Resolution:
 --------------------
 The lines DRUGERR+8^PSJOC and DRUGERR+18^PSJOC were modified to remove the
 condition that the position had to be at the bottom of the screen for the
 [Press Return to continue...] prompt to be displayed. The command to wipe off
 the screen was also removed at both lines. Furthermore, the line tag
 PAUSE^PSJLMUT1 was modified to remove the setting of the DIR("?") because it
 was causing the "Press Return to continue..." to display 3 times after the
 user typed anything different than <RET> or "^".
    
  
 Patient Safety Issues (PSIs):
 -----------------------------
 HITPS-8861
 HITPS-8866
          
 Test Sites:
 -----------
 Fresno VA medical center (Fresno, CA)
 Ralph H. Johnson VAMC (Charleston, SC)   
  
  
 Patch Installation:
  
 Pre/Post Installation Overview:
 -------------------------------
 It is not necessary to disable any options.  
  
 Pre-Installation Instructions:
 ------------------------------ 
 This patch should 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.|TAB|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*426)
  
         NOTE: Using <spacebar><enter> 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*426
          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 <enter> and take the default response 
               of "NO".
          v.   When prompted with, "Send mail to: Last name, First 
               Name", press <enter> to take default recipient. Add 
               any additional recipients.
          vi.  When prompted with "Select basket to send to: IN//", 
               press <enter> 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.
  
   
 Back-out Procedures:
 --------------------
 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.
  
 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.
  
 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 PSJ*5.0*426
 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.

Routine Information:
====================
The second line of each of these routines now looks like:
 ;;5.0;INPATIENT MEDICATIONS;**[Patch List]**;16 DEC 97;Build 4

The checksums below are new checksums, and
 can be checked with CHECK1^XTSUMBLD.

Routine Name: PSGOEH0
    Before: B11742800   After: B12211312  **,51,426**
Routine Name: PSGOEH1
    Before:  B9067432   After:  B9508146  **426**
Routine Name: PSIVOE
    Before:  B6508638   After:  B6611174  **51,426**
Routine Name: PSJHL4
    Before: B83393640   After: B80704606  **1,12,27,34,40,42,55,47,50,
                                           56,58,98,85,105,107,110,111,
                                           154,134,197,226,279,419,399,
                                           426**
Routine Name: PSJLMUT1
    Before: B76113417   After: B75306325  **4,27,29,49,58,107,110,146,
                                           175,201,181,281,329,373,426**
Routine Name: PSJOC
    Before:B113286726   After:B112308741  **181,260,252,257,281,256,364,426**
Routine Name: PSJUTL3
    Before: B43541107   After: B46663569  **58,353,426*
 
Routine list of preceding patches: 51, 353, 364, 373, 399

=============================================================================
User Information:
Entered By  :                               Date Entered  : DEC 06, 2021
Completed By:                               Date Completed: JAN 24, 2023
Released By :                               Date Released : JAN 25, 2023
=============================================================================


Packman Mail Message:
=====================

$END TXT