$TXT Created by              NNE at MNTVBB.DOMAIN.EXT  (KIDS) on Tuesday, 02/27/24 at 14:48
=============================================================================
Run Date: MAY 09, 2024                     Designation: PSJ*5*451
Package : PSJ - INPATIENT MEDICATIONS         Priority: Mandatory
Version : 5       SEQ #388                      Status: Released
                  Compliance Date: JUN 09, 2024
=============================================================================

Associated patches: (v)PSJ*5*441   <<= must be installed BEFORE `PSJ*5*451'

Subject: UNDEFINED ERRORS FOR UD ORDERS

Category: 
  - Routine

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

 This patch addresses the following two incident tickets:
  
 1. INC30646734 - VISTA PSJ UNDEFINED ERROR AFTER COPYING UD ORDER WITH 
 REMOVAL REQUIRED.
  
 2. INC31233823 - VISTA PSJ UNDEFINED ERROR AFTER EDITING START TIME 
 BEFORE ACCEPTING UD ORDER REQUIRING REMOVAL.
  
  
 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
  
 Templates Associated:
  
 Template Name         Type    File Name (Number)  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 (PSIs):
 N/A
  
  
 Defect Tracking System Ticket(s) & Overview:
 --------------------------------------------
 1. INC30646734 - VISTA PSJ UNDEFINED ERROR AFTER COPYING UD ORDER WITH 
 REMOVAL REQUIRED.
  
 2. INC31233823 - VISTA PSJ UNDEFINED ERROR AFTER EDITING START TIME 
 BEFORE ACCEPTING UD ORDER REQUIRING REMOVAL.
  
  
 Problem
 -------
 1. INC30646734 - Albany VA Medical Center (NY) reported an undefined 
 error that occurs in VistA backdoor pharmacy INPATIENT ORDER ENTRY 
 [PSJU MGR] when you copy an active unit dose order, that has a transdermal
 patch orderable item field "Prompt for removal in BCMA",  set to "Removal
 Period Required Prior to Next Administration", edit the start date/time, 
 and then choose to edit the admin time,  say NO to the prompt "Is this 
 correct", then enter in a new ADMIN time. The system hard errors and 
 kicks you out of Vista. Hard error is <UNDEFINED>DONE+3^PSGOE91 
 *PSGOEEF(41).
  
  
 Resolution:
 -----------
 1. INC30646734 - Adding a check for data in the PSGOE91 routine DONE tag 
 for the PSGOEEF(PSGF2) variable.  In some cases, there is no data and the 
 variable is not defined therefore causing a hard error and kicking the 
 user out.  Adding the check will allow the logic to continue to process 
 the UD order without a hard error.  Also adding a change to the PSGOE91 
 routine A10 tag, so the date/time will display appropriately. Currently 
 it shows the correct date and then an up caret with the internal date.
  
 Technical Resolution:
 ---------------------
 1. INC30646734 - Routine PSGOE91 is modified at line to check for data in 
 the variable causing the undefined error, and correcting the format of 
 the date.
  
 Line DONE+3
    I PSGOEE G:'PSGOEEF(PSGF2) @BACK S PSGOEE=PSGOEEF(PSGF2)
 To
    I PSGOEE G:'$G(PSGOEEF(PSGF2)) @BACK S PSGOEE=PSGOEEF(PSGF2)
  
 Line A10+6
    I X="",PSGSD W "  "_PSGSDN G DONE
 To
    I X="",PSGSD W "  "_$P(PSGSDN,"^") G DONE
  
  
 Problem
 -------
 2. INC31233823 - Albany VA Medical Center (NY) reported an undefined 
 error that occurs in VistA backdoor pharmacy INPATIENT ORDER ENTRY 
 [PSJU MGR] when editing the start date before accepting an active unit
 dose order (without a copy). Hard error is <UNDEFINED>DONE+3^PSGOE81
 *PSGOEEF(39).
  
  
 Resolution:
 -----------
 2. INC31233823 - Adding a check for data in the PSGOE81 routine DONE 
 tag for the PSGOEEF(PSGF2) variable.  In some cases, there is no data and
 the variable is not defined therefore causing a hard error and kicking the
 user out.  Adding the check will allow the logic to continue to process 
 the UD order without a hard error.
  
 Technical Resolution:
 ---------------------
 2. INC31233823 - Routine PSGOE81 is modified to check for data in the 
 variable causing the undefined error.
  
 Line DONE+3
    I PSGOEE G:'PSGOEEF(PSGF2) @BACK S PSGOEE=PSGOEEF(PSGF2)
 To
    I PSGOEE G:'$G(PSGOEEF(PSGF2)) @BACK S PSGOEE=PSGOEEF(PSGF2)
  
  
  
 Test Sites:
 -----------
 Upstate NY HCS, Albany NY 
 Milwaukee VAMC, Milwaukee WI 
  
 SNOW Change Order #:
 --------------------
 Upstate NY HCS, CO# - CHG0472606 
 Milwaukee VAMC, CO# - CHG0472231
  
  
  
 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*451) 
  
         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*451.
          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
            
  
 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 BUILD 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 build 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 build 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 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 PSJ 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 PSJ*5.0*451.

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

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

Routine Name: PSGOE81
    Before:B156404668   After:B156550640  **26,50,64,58,82,110,111,136,
                                           113,267,315,334,373,366,327,
                                           441,451**
Routine Name: PSGOE91
    Before:B154461173   After:B154688310  **50,64,58,110,111,136,113,179,
                                           265,267,285,315,334,373,366,
                                           327,441,451**
 
Routine list of preceding patches: 441

=============================================================================
User Information:
Entered By  :                               Date Entered  : FEB 02, 2024
Completed By:                               Date Completed: MAY 08, 2024
Released By :                               Date Released : MAY 09, 2024
=============================================================================


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

$END TXT