PSO*7.0*705 (13317)    BUILD (9.6)

Name Value
NAME PSO*7.0*705
DATE DISTRIBUTED 2022-11-15 00:00:00
PACKAGE FILE LINK OUTPATIENT PHARMACY
REQUIRED BUILD
  • PSO*7.0*659
    ACTION:   Don't install, remove global
TYPE SINGLE PACKAGE
DESCRIPTION OF ENHANCEMENTS
 
use this field. In particular, this affects SPMP functionality. When file 
101.52 field 10 is null, this may cause the Vista SPMP transmissions to 
submit an incorrect DEA Number for the provider.
 
 
Patient Safety Issues (PSIs):
-----------------------------
N/A
 
 
This patch will resolve the following issue:
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
Problem:
--------
1) INC23385693 - It was discovered that when a provider's DEA number 
expires on the same date as the issue/written date, field #10 DEA NUMBER
can be null in the Order DEA Archive file (#101.52).  When this happens,
the SPMP transmission should still send the provider's DEA number, but
instead it will send either null or the Facility DEA# which is incorrect.
 
 
 
Resolution 1:
-------------
To fix the issue for the SPMP transmission, the routine PSOASAP0 tag 
PRE02 will be modified to pass the issue/written date to the $$DEA^XUSER
call, so the provider's DEA number will be sent even though it expires on
the same day as the RX issue/written date.
1) INC23385693 - Controlled substance eRx prescriptions can be finished 
in VistA on a day after the authorizing provider's DEA Number expires as 
long as the Issue/Written Date of the eRX is before or equal to the 
provider's DEA expiration date. This is by design. However, when this 
happens, it causes field #10 DEA NUMBER to be null in the Order DEA 
Archive file (#101.52). This will have side effects in functionality that 
TRACK PACKAGE NATIONALLY YES
XPI1 NO
XPO1 NO
XPZ1 NO
SEQ# 586
BUILD COMPONENTS
  • ENTRIES:
    • PSOASAP0
      ACTION:   SEND TO SITE
      CHECKSUM:   B178203552