PSJ*5.0*397 (11664)    BUILD (9.6)

Name Value
NAME PSJ*5.0*397
DATE DISTRIBUTED 2020-04-17 00:00:00
PACKAGE FILE LINK INPATIENT MEDICATIONS
REQUIRED BUILD
  • PSJ*5.0*370
    ACTION:   Don't install, leave global
  • PSJ*5.0*146
    ACTION:   Don't install, leave global
TYPE SINGLE PACKAGE
ALPHA/BETA TESTING NO
DESCRIPTION OF ENHANCEMENTS
This patch will resolve the following issues:
1) INC6081255 - BCMA scanning IV medication as invalid lookup
 
Problem: 
-------
The VA Sierra Nevada Health Care System reported that BCMA IV piggyback label
scanned as invalid look up when they should be valid. This happened when, for
example, an edit on the Volume of the solution on the order should have caused
the previously printed label(s) to be invalidated and new label(s) generated 
according to the BCMA Parameters. New label(s) were generated for the edited
order, however all labels (old and new) were being erroneously invalidated.
  
    
Resolution:
----------
This problem happened because the software performs a date/time comparison
between the Volume edit and the label creation to determine whether a label
is valid or not. If the label was printed before the Volume edit the label is
considered invalid. The problem is that it was using the format YYYMMDD.HHMMSS
for the Volume edit date/time and the format YYYMMDD.HHMM for the Label
creation date/time. So, if the new label(s) where printed within the same
minute of the Volume edit the software mistakenly assumed the new labels were
INC6081255 - BCMA scanning IV medication as invalid lookup
printed before the Volume edit.
  
Technical Resolution:
--------------------
Changed the code at EN+61 in the routine PSIVBCID to truncate the order edit
date/time to YYYMMDD.HHMM format when doing the comparison with the label
print date/time. This way labels printed after the order edit should never be
considered invalid.
  
   
INC6231181 - Over the last several months, there has been at least 5 times
INC6231181 - Over the last several months, there has been at least 5 times
             that I am aware of where CPRS and BCMA aren't communicating on
             verification of order.
 
Problem: 
-------
The Madison VA Hospital reported that the BCMA nurse verification information
was not being properly reset (removed) after the field SPECIAL INSTRUCTIONS
was edited by Inpatient Pharmacy users through the Inpatient Order Entry [PSJ
OE] option. In CPRS the nurse verification is correctly being reset (removed)
HITPS-6742   that I am aware of where CPRS and BCMA aren't communicating on
after this field is edited in Inpatient Pharmacy. According to the site this
poses the risk of medication being administered through BCMA without the
proper re-review and re-verification. This issue is also being considered a
Patient Safety Issue (PSI) and the number assigned by the Patient Safety team
is HITPS-6742.
     
Resolution:
----------
Every time the SPECIAL INSTRUCTIONS field is edited for an inpatient unit dose
order the nurse verification information (if any) will be invalidated/removed,
             verification of order.
which will be reflected in the BCMA application. Depending on how the site 
BCMA parameters is set it will require a re-verification of the order in CPRS
before it can be administered through the BCMA application.
  
Technical Resolution:
--------------------
Created a new line tag in the routine PSJBCMA2 called RESETNV responsible for
removing the nurse verification information in the PHARMACY PATIENT file (#55),
UNIT DOSE sub-file (#55.06), fields VERIFYING NURSE (#16) DATE VERIFIED BY
NURSE (#17) and setting the NV FLAG field (#51) to 0 (NO). These fields are
    
used by BCMA to determine whether an order have been verified or not by a
nurse.
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
TRACK PACKAGE NATIONALLY YES
XPI1 NO
XPO1 NO
XPZ1 NO
SEQ# 342
BUILD COMPONENTS
  • ENTRIES:
    • PSJBCMA2
      ACTION:   SEND TO SITE
      CHECKSUM:   B62768742
    • PSIVBCID
      ACTION:   SEND TO SITE
      CHECKSUM:   B6703839