PSB*3.0*125 (11645)    BUILD (9.6)

Name Value
NAME PSB*3.0*125
DATE DISTRIBUTED 2020-01-28 00:00:00
PACKAGE FILE LINK BAR CODE MED ADMIN
REQUIRED BUILD
  • PSB*3.0*122
    ACTION:   Don't install, leave global
  • PSB*3.0*87
    ACTION:   Don't install, leave global
TYPE SINGLE PACKAGE
ALPHA/BETA TESTING NO
DESCRIPTION OF ENHANCEMENTS
This patch will resolve the following issues:
--------------------------------------------
1) INC8817299 -BCBU MAR Shows Expired Meds as Requiring Administration
          
Problem: 
--------
BCBU MAR reports were showing medications on the grid as needing
administration on their Stop date/time, when the time value ends in a zero,
e.g. 0900 & 0930.  
 
Solution:
 
--------
Correct BCBU routine ALPBFRM1 to put asterisks in that time cell on the MAR
Grid.
 
Technical Resolution:
---------------------
In routine ALPBFRM1, "+" the variable, when it is created after it
concatenates the time to the end of the date.  This will trim off 
insignificant trailing zeros, prior to later compare operations checking if
the grid cell date.time is = to the stop date.time of this order.
1) INC8817299 - BCBU MAR Shows Expired Meds as Requiring Administration
 
2) INC9226190 - BCMA Contingency program requires verify code be changed
                each time you log into the program
      
Problem: 
--------
VA Western New York Healthcare System at Buffalo reported that after patch
PSB*3*122 was installed the Initialize a Backup Workstation with BCMA Users 
[PSB BCBU USER INIT] option which is used to send BCMA users over from VistA
to the BCBU workstation was forcing the users to change their VERIFY CODE at
2) INC9226190 - BCMA Contingency program requires verify code be changed
the BCBU workstations when they tried to logon. It was confirmed that the
issue was introduced by PSB*3*122. In order to fix the problem that required
the option above to be run twice in order for the new users ACCESS/VERIFY 
CODEs to work the re-indexing of the new records on the NEW PERSON file (#200) 
was moved past the "hard setting" of ACCESS/VERIFY CODEs, which resolved the
original but the re-indexing also treats the ACCESS CODE as new and therefore
forces a new VERIFY CODE to be entered by the user at the BCBU workstation.
 
Solution:
--------
                each time you log into the program
Kept the "hard setting" of the ACCESS CODE prior to re-indexing the new record
in the NEW PERSON file (#200) but moved the "hard setting" of the VERIFY CODE
information after the re-indexing which addresses the issue.
 
Technical Resolution:
---------------------
Moved the call "D IX1^DIK" up to FILE+20, before setting the VERIFY CODE 
information.
   INC9209704(d) - Modify MIW BCMA BU devices to prevent users from needing
                   to create a secondary Verify Code
 
Defect Tracking System Ticket(s) & Overview:
TRACK PACKAGE NATIONALLY YES
XPI1 NO
XPO1 NO
XPZ1 NO
BUILD COMPONENTS
  • ENTRIES:
    • ALPBFRM1
      ACTION:   SEND TO SITE
      CHECKSUM:   B95230274
    • ALPBGEN1
      ACTION:   SEND TO SITE
      CHECKSUM:   B25368227