$TXT Created by                  at CLN1G1.AAC.DOMAIN.EXT  (KIDS) on Monday, 01/06/20 at 11:12
=============================================================================
Run Date: AUG 05, 2020                     Designation: PSJ*5*398
Package : PSJ - INPATIENT MEDICATIONS         Priority: Mandatory
Version : 5       SEQ #345                      Status: Released
                  Compliance Date: SEP 05, 2020
=============================================================================

Associated patches: (v)PSJ*5*327   <<= must be installed BEFORE `PSJ*5*398'
                    (v)PSJ*5*338   <<= must be installed BEFORE `PSJ*5*398'

Subject: VARIOUS UD ISSUES/CLOZ COMPLEX ORDER ISSUE / BCMA MED REPORT ISSUE

Category: 
  - Routine
  - Other

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

 This patch will address the following issues:
  
 1.  When editing a pending prescription, if the Dosage Ordered is more 
     than 1/2 of the Dispense Units no warning message is displayed.
  
 2.  When a complex Clozapine order is entered in CPRS that goes over 
     the Limit of 7, 14 or 28 days, the stop date is not displaying
     correctly in Vista after the order is Active when there is an edit to
     the stop date.
  
 3.  The START DATE/TIME field # [10] set to null in the UNIT DOSE 
     multiple File (#55.06) within the PHARMACY PATIENT file (#55) was
     causing a Critical error when trying to run a Clinic Missed Medication
     report in the Bar Code Medication Administration (BCMA) GUI
     application.  
  
 4.  When finishing a pending Unit Dose order, prior to the order being 
     Accepted, the user selects the hidden option "OCI", a hard error of 
     "<UNDEFINED>LOOP+6^XQOR1 *ON" occurs.
  
  
 Defect Tracking System Ticket(s) & Overview:
 --------------------------------------------
  
 1. INC8083635 - Dosage changed on warfarin from 5mg to 3mg didn't fire a
                  warning to the pharmacist finishing the order.
  
 Problem:
 -------
 A pharmacist edited a pending prescription, after consult with the doctor, for
 warfarin from 5mg to 3mg.  There was no warning message displayed to the
 pharmacist that the Dosage Ordered and Dispense Units do not match.
  
 If the Dosage Ordered is less than 1/2 of the Dispense Units on the edit, 
 the warning message will display.  If the Dosage Ordered is more than 1/2 
 of the Dispense Units no warning message is displayed.
  
 Resolution:
 ----------
 A modification was made in routine PSJDOSE to display the warning message 
 for any order where the Dosage Ordered is different from the Dispense Units.
  
  
 2. INC8534791 - Stop date in CPRS does not match stop date in Patient 
                  Profile.
  
 Problem:
 -------
 When a complex Clozapine order is entered in CPRS that goes over the limit
 of 7, 14 or 28 days, the stop date is not displaying correctly in Vista after
 the order is Active when there is an edit to the stop date.
  
 CPRS shows the orders correctly.  The code is pulling the stop date 
 from the NON-VERIFIED ORDERS file (#53.1) after the order is active when
 the profile screen is refreshed.
  
 Resolution:
 ----------
 A modification was made to routine PSJLMPRU to check to see if order
 is active.  If so, do not pull the stop date from the NON-VERIFIED
 ORDERS file (#53.1).
  
  
 3. INC8188788 - BCMA Missed Med Report by CLINIC Gives Error Message 
                 "Unable to Reach VistA"
    INC8919618(d) BCMA "not a valid floating point value"
  
 Problem:
 -------
 The START DATE/TIME field [#10] set to null in the UNIT DOSE multiple 
 file # (55.06) within the PHARMACY PATIENT file (#55) was causing a 
 critical error when trying to run a Clinic Missed Medication report in 
 the Bar Code Medication Administration (BCMA) GUI application.  This only 
 occurs, while finishing a pending unit dose order at 09:59 or 19:59 and 
 editing the Schedule field changing it to NOW, via Inpatient Order Entry. 
 The system time would be calculated to either 10:00 or 20:00 for the new 
 order's Start date/time.
  
  
 Resolution:
 ----------
 A modification was made to routine PGOETO to stop comparing the variable 
 that contained the START DATE/TIME field information to the + version of 
 that same variable and when compared unequal when the then it would set 
 the Start date of the order to null.  The code now simply checks if the 
 variable is true (> 0), then stores the + version of the variable to the 
 PHARMACY PATIENT file (#55).
  
  
 4. INC8666181 - Vista hard error with Unit Dose hidden Option "OCI"
  
 Problem:
 -------
 A Pharmacist finished a pending order that prompted to be finished as IV 
 or Unit Dose and Unit Dose is selected. Then, prior to the order being 
 Accepted, the user selected the hidden option Overrides/Interventions 
 [OCI] and a hard error of "<UNDEFINED>LOOP+6^XQOR1 *ON", occurs.
  
  
 Resolution:
 ----------
 Correct the ENTRY ACTION field [#20] in the PROTOCOL file (#101) entry 
 PSJ LM OVERRIDES.  If the ON variable is not defined or null, the 
 corrected mumps code will now initialize the ON variable with the order 
 number found in the PSGORD variable.
  
  
 Patient Safety Issues (HITPS):
 -----------------------------
 HITPS-6797  (INC8083635)
  
 Protocol
 --------
 PSJ LM OVERRIDES
  
 Test Sites:
 ----------
 Phoenix VAMC, Phoenix AZ
 Heartland West HCS 
  
  
 Software and Documentation Retrieval Instructions:
 --------------------------------------------------
 The software for this patch is being released in a PackMan message.
  
 Patch Installation:
  
 Pre-Installation Instructions:
 --------------------------    
 If installed during the normal workday, it is recommended that the 
 Outpatient Pharmacy users be off the system. Other VISTA users
 will not be affected.   Install Time - less than 2 minutes (unless 
 otherwise indicated)
  
  
 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*7*398):
  
         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 of any routines exported with this patch. 
        It will not backup any other changes such as DDs or 
        templates. 
  
     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//', NO.
            
            a. When prompted 'Enter options you wish to mark as 
               'Out Of Order':', press the Enter key.
  
  
            b. When prompted 'Enter protocols you wish to mark as 
               'Out Of Order':', press the Enter key.
  
            c. When prompted 'Delay Install (Minutes):  (0 - 60): 0//',
               answer 0.
  
  
      
 Back-out/Rollback Strategy:
 ====================
 Post Installation Instructions:
 -------------------------------
 None.
  
 Installation Verification:
 --------------------------
 Successful installation can be verified by reviewing the first 2 lines 
 of the routines contained in the patch. The second line will contain the 
 patch number (398) in the [PATCH LIST] section.
   
  ;;5.0;INPATIENT MEDICATIONS;**[PATCH LIST]**;16 DEC 97;[BUILD #]
    
 The option Calculate and Show Checksum Values [XTSUMBLD-CHECK] can be run 
 to compare the routine checksums to what is documented in the patch
 description.
  
 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. 
 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 PSJ 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*398 patch have been rolled back, the first
 two lines of the Routines will no longer contain the designation
 of patch PSJ*5.0*398 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 3

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

Routine Name: PSGOETO
    Before: B46539798   After: B46488938  **3,13,25,31,33,50,68,58,85,
                                           105,90,117,110,111,112,161,254,
                                           267,268,315,327,398**
Routine Name: PSJDOSE
    Before: B64879386   After: B67306879  **50,65,106,111,216,264,328,338,398**
Routine Name: PSJLMPRU
    Before: B26845194   After: B27774491  **16,58,85,110,185,181,267,323,
                                           317,373,327,398**
 
Routine list of preceding patches: 327, 338

=============================================================================
User Information:
Entered By  :                               Date Entered  : DEC 10, 2019
Completed By:                               Date Completed: AUG 03, 2020
Released By :                               Date Released : AUG 05, 2020
=============================================================================


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

$END TXT