| DESCRIPTION OF ENHANCEMENTS |
This patch will address the following issue:
Problem:
-------
Meds-By-Mail (MbM) reported that electronic prescriptions (eRx) are received
several hours after the outside prescriber transmitted them. The problem seems
to be caused by a increasing traffic handled by the eRx Hub which centralizes
all nationwide incoming eRx prescriptions into the VA. One part of the
processing by the eRx Hub is the auto-matching of patient, provider and drug.
In other words, the eRx Hub tries to pre-emptively find a VistA corresponding
for these three fields before forwarding the incoming prescription to the
VistA site. The auto-matching for the provider and drug is accomplished by the
eRx Hub through two VistALink calls (one for the provider and one for the
drug) to the VistA site and if a match is found at the VistA site it returns
the IENs (Internal Entry Number) back to the eRx Hub which in turn records the
success/failure for an auto-match statistics reporting purpose and then sends
the matched IENs back to the VistA site along with the complete eRx
prescription. Although not 100% confirmed, the suspicion is that such calls to
VistA have become quite costly as the volume of incoming eRx increased
drastically in the past few months and are likely to be partially responsible
for the processing delays.
1. INC23078077 - Delayed delivery of electronic doctor orders through VHA
Resolution:
-------------
The solution to this problem is two-fold:
1) A change is being made in VistA through this patch to the processing of
the incoming eRx to check if the eRx Hub provider and drug auto-matches
were successful or not ("fail"). If not, using the incoming data from the
outside prescriber VistA will utilize the exact same VistA code currently
used by the eRx Hub to try to auto-match these locally and if it succeeds
Inbound eRx hub
it will auto populate VistA Provider and/or VistA Drug fields.
2) Once the this patch has been released and installed nationally at every
VistA site an update will then be made at the eRx Hub to shut off the
auto-match processing for provider and drug. This will consist of
stopping the two VistALink calls made to the VistA site and always
sending to VistA a "fail" result with a "Auto-match not performed"
reason.
Technical Resolution:
--------------------
A new routine (PSOERUT) was created to parse an XML message into a local array
and code was added to INCERX+29^PSOERXI1 and INCERX+48^PSOERXI1 to call the
new API XML2GBL in the new routine to parse the incoming XML message, retrieve
the provider and drug information and call the same code the eRx Hub was
calling (via RPC calls) to perform the auto-match for provider and drug
(PRVMTCH^PSOERXA0 and DRGMTCH^PSOERXA0). Furthermore, it was determined that
the array variable (PSODRUG("IEN")) used at CSID+9^PSOUTL, used to check if
a drug is a controlled substance or not was wrong and was replaced with
DRGIEN.
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
1. INC23078077 - Delayed delivery of electronic doctor orders through VHA
Inbound eRx hub
|
