| DESCRIPTION OF ENHANCEMENTS |
This patch will address the following eRx issues:
list of status screened out for "Refill Response" type records, which will
drop the erroneously RRP records from the Work Queue as soon as the patch
is installed.
2) Changed the routine PSOERX1B at line tag ADD+64 and the routine at line tag
AUTODC+38 to only update the record status to RRP if the record type is a
"Refill Request". This will prevent "Refill Response" records from being
wrongly updated to RRP.
Patient Safety Issues (PSIs):
-----------------------------
N/A
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
1. INC7957997 - Grammar error in eRx processing screen
Problem:
--------
Alaska VA Healthcare System reported a grammar issue while accepting an eRx
prescription into VistA via the Complete Orders from eRx [PSO ERX FINISH]
option. After validating a patient via this option the software checks whether
the same patient has other eRx prescriptions waiting to be validated and if
any additional are found it will issue the following message/prompt (example):
This patient has other prescriptions for: Dec 04, 2019
Patient: XXXXXX,XXXXXXX
1. INC7957997 - Grammar error in eRx processing screen
DRUG PROVIDER REC DATE
--------------------------------------------------------------------------
1.) GABAPENTIN 300 MG ORAL CAPSUSMITH,KATELON JAN 04, 2020
2.) METOPROLOL SUCCINATE ER 100 SMITH,KATELON JAN 04, 2020
Would you like apply the above validation to these prescriptions?
Enter Yes or No: N//
The issue is with "...like apply..." which should read "...like to apply..."
Resolution:
-----------
Inserted "to" between "like" and "apply".
Technical Resolution:
---------------------
Changed the routine PSOERX1B at line tag BPROC+41 to include "to" between
"like" and "apply".
2. INC6442610 - inbound eRx issue - order stuck in queue
2. INC6442610 - inbound eRx issue - order stuck in queue
INC6659074(d) - Wrong erx status code generated in VistA inbound erx
software version 3.0
INC6245922(d) - eRX issue with acknowledging messages in RRD status that
change to RRP status for 1 patient
Problem:
--------
VA Puget Sound Health Care System reported that Refill Response eRx records
with a status of RRP (REFILL REQUEST PROCESSED) are accumulating on their eRx
INC6659074(d) - Wrong erx status code generated in VistA inbound erx
Work Queue and the users do not have a mechanism to remove them. This problem
interferes with their work because these types of records fills up pages and
of their Work Queue and there is no further processing needed to be performed
on them. Upon extensive research it was determined that RXA (REFILL RESPONSE
ACKNOWLEDGED) Refill Request records were erroneously being updated to RRP
once a new prescription was accepted via eRx for the same medication that was
previously designed. To illustrate a little further the sequence of events
happened the following way:
1) Patient had eRx 'A' that had already been previously filled and did not
software version 3.0
have any more refills left.
2) The VA Pharmacist uses the RR (eRx Refill Request) through the Patient
Prescription Processing [PSO LM BACKDOOR ORDERS] option and a message is
sent out to the Dr's Office.
3) The Dr's Office denies the Refill/Renewal by sending a new eRx record to
VistA which create a Refill Request records with a status of RXD (REFILL
RESPONSE DENIED/DNTF).
4) The VA Pharmacist then acknowledges the RXD record through the Complete
Orders from eRx [PSO ERX FINISH] option, which changes the status of the
Refill Response from RXD to RXA successfully removing it from the eRx
INC6245922(d) - eRX issue with acknowledging messages in RRD status that
Work Queue.
5) Later, the Dr's Office sends to VistA a new prescription for the patient
with the same medication
6) The VA Pharmacist processes the new eRx prescription and Accepts it.
This action creates the problem because it mistakenly changes the status
of the previously updated Refill Response from RXA to RRP, bringing it
back to the eRx Work Queue which does not offer any means for the users
to remove such records from the Work Queue.
Resolution:
change to RRP status for 1 patient
-----------
This patch will stop the status update from RXA to RRP described in the step
#6 above. Furthermore, it will remove all RRP records from the eRx Work Queue.
The RRP records will still be visible if users intentionally are looking for
them through the SR (Search Queue) action, which is how the Work Queue was
designed to work originally.
Technical Resolution:
---------------------
1) Changed the routine PSOERX at line tag BLDITEM+22 to include "RRP" in the
|
