PSJ*5.0*451 (13682)    BUILD (9.6)

Name Value
NAME PSJ*5.0*451
DATE DISTRIBUTED 2024-02-27 00:00:00
PACKAGE FILE LINK INPATIENT MEDICATIONS
REQUIRED BUILD
  • PSJ*5.0*441
    ACTION:   Don't install, remove global
TYPE SINGLE PACKAGE
DESCRIPTION OF ENHANCEMENTS
 
 
Problem(s):
-----------
1. INC30646734 - Albany VA Medical Center (NY) reported an undefined 
error that occurs in VistA backdoor pharmacy (inpatient order entry), 
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 
This patch addresses the following two incident tickets:
kicks you out of Vista. Hard error is <UNDEFINED>DONE+3^PSGOE91 
*PSGOEEF(41).
 
2. INC31233823 - Albany VA Medical Center (NY) reported an undefined 
error that occurs in VistA backdoor pharmacy (inpatient order entry) 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:
 
-----------
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.
 
2. INC31233823 - Adding a check for data in the PSGOE81 routine for the 
1. INC30646734 - VISTA PSJ UNDEFINED ERROR AFTER COPYING UD ORDER WITH 
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:
---------------------
1. INC30646734 - Routine PSGOE91 is modified at line to check for data in 
the variable causing the undefined error, and correcting the format of 
REMOVAL REQUIRED.
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
 
 
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)
2. INC31233823 - VISTA PSJ UNDEFINED ERROR AFTER EDITING START TIME 
BEFORE ACCEPTING UD ORDER REQUIRING REMOVAL.
 
TRACK PACKAGE NATIONALLY YES
XPI1 NO
XPO1 NO
XPZ1 NO
SEQ# 388
BUILD COMPONENTS
  • ENTRIES:
    • PSGOE91
      ACTION:   SEND TO SITE
      CHECKSUM:   B154688310
    • PSGOE81
      ACTION:   SEND TO SITE
      CHECKSUM:   B156550640