| DESCRIPTION OF ENHANCEMENTS |
This patch will address the following issues:
INC15788649 - RxRenewal Response - Replace status get assigned wrong
to be marked with the RRX (RXRENEWAL REQUEST EXPIRED) status after 14 days
without a response.
...
Select one of the following:
PT PATIENT(Grouped)
RX PRESCRIPTION RECEIVED DATE
E EXIT
Select By: (PT/RX): PT// RX PRESCRIPTION RECEIVED DATE
status code
...
Technical Resolution:
--------------------
The functionality responsible for the auto expiration of CRN and RRN records
in the PSOERX routine lines BLDITEM+11 thru BLDITEM+14 for the RX view were
copied over to the PSOERXC1 routine which is used by the PT view. This way
no matter which way the user enters the option it will always check and mark
eligible CRN and RRN records as expired.
Test Sites:
-----------
TBD
Documentation Retrieval Instructions:
-------------------------------------
N/A (No documentation changes)
Installation Instructions:
2. INC12814745 - Rx Sig Not Upper-cased when processing inbound eRX
--------------------------
This patch may be installed with users on the system although it is recommended
that it be installed during non-peak hours to minimize potential disruption to
users. Staff should not be processing prescriptions while patch is being
installed. This patch should take less than 5 minutes to install.
1. Choose the PackMan message containing this patch.
2. Choose the INSTALL/CHECK MESSAGE PackMan option.
3. From the Kernel Installation & Distribution System menu, select
the Installation menu. From this menu, select Backup a Transport
Global. This option will create a backup message of any routines
exported with this patch. It will not backup any other changes such
as DD's or templates. When prompted for INSTALL NAME, enter the
patch #, PSO*7.0*631.
4. From the Kernel Installation & Distribution System menu, select
the Installation menu. From this menu, you may select to use the
following options:
3. INC16106925 - Pharmacy messages not assigned appropriate status by
when prompted for INSTALL NAME, enter the patch #, PSO*7.0*631:
a. Compare Transport Global to Current System - This option will
allow you to view all changes that will be made when this patch
is installed. It compares all components of this patch
routines, DDs, templates, etc.
b. Verify Checksums in Transport Global - This option will allow
you to ensure the integrity of the routines that are in the
transport global.
software
5. From the Installation menu, select the Install Package(s) option and
choose the patch to install.
6. When prompted 'Want KIDS to INHIBIT LOGONs during the install?
NO//', respond NO.
7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and
Protocols? NO//', respond NO.
8. If prompted 'Delay Install (Minutes): (0-60): 0//' respond 0.
Back-out/Rollback Strategy:
---------------------------
Back-out will be done only with the concurrence and participation of
development team and appropriate VA site/region personnel. The decision to
back-out or rollback software will be a joint decision between development
team, VA site/region personnel and other appropriate VA personnel.
Prior to installing an updated KIDS package, the site/region should have saved
Defect Tracking System Ticket(s) & Overview:
a backup of the routines in a mail message using the Backup a Transport Global
[XPD BACKUP] menu option (this is done at time of install). The message
containing the backed up routines can be loaded with the "Xtract PackMan"
function at the Message Action prompt. The Packman function "INSTALL/CHECK
MESSAGE" is then used to install the backed up routines onto the VistA System.
The back-out plan is to restore the routines from the backup created.
No data was modified by this patch installation and, therefore, no
rollback strategy is required.
--------------------------------------------
Validation of Roll Back Procedure
---------------------------------
The Roll Back Procedure can be verified by printing the first 2 lines of the
PSO Routines contained in this patch using the option First Line Routine Print
[XU FIRST LINE PRINT]. Once the routines contained in the PSO*7.0*631 patch
have been rolled back, the first two lines of the Routines will no longer
contain the designation of patch PSO*7.0*631 in the patch list section on line
2.
1. INC13163644 - Assist with deleting eRx order on inbound eRx queue
Problem:
--------
The Fresno VA Medical Center reported that 'Denied' incoming eRx response
records were sitting in their eRx Holding Queue (Complete Orders from eRx
[PSO ERX FINISH] option) for months because they do not have any way to
remove them. This issue usually happens when the sites manually renews a
prescription after placing an eRx refill/renewal request for the eRx
prescription. Once the incoming response is received the software is unable
1. INC13163644 - Assist with deleting eRx order on inbound eRx queue
to process the renewal because the eRx is already renewed and files the
record with an RXN (RXRENEWAL RESPONSE - NEW) status instead of assigning it
a more appropriate status such as RXF RXN (RXRENEWAL RESPONSE - FAILED),
which is removed from the eRx Holding Queue once the user acknowledges it.
Resolution:
-----------
The eRx incoming response processing code was changed to automatically assign
a status of RXF to an incoming renewal eRx response if the prescription has
already been manually renewed. This will allow users to successfully remove
Duplicates:
such records from their by using the hidden action ACK (Acknowledge).
Technical Resolution:
---------------------
The line of code below was inserted at REFRESP+24 in the PSOERXA5 routine.
.D UPDSTAT^PSOERXU1(ERXIEN,"RXF","eRx already Renewed.")
It will ensure that when an Denied incoming eRx response is received for an
already renewed prescription the status will be set to RXF instead of RXN.
-----------
Furthermore, another potential code for leaving records in the RXN was
identified in the use of the API $$FIND1^DIC because it did not require an
exact match of the related eRx when the incoming eRx response arrived. The
third parameter was changed to include "O", which will force an exact match
in order to identify the related eRx record.
2. INC12814745 - Rx Sig Not Upper-cased when processing inbound eRX
Problem:
--------
INC15788594 - RxRenewal Response was assigned wrong status flag
The Tucson VA Medical Center reported that when using the eRx Holding Queue
(Complete Orders from eRx [PSO ERX FINISH] option) the user added a patient
instruction (code) with a lower case text to the eRx and the medication
instruction expanded as expected however it did not convert to upper case in
the Inbound ERX Holding queue. The text was appended to the SIG and remained in
lower case through the finishing process in the Patient Prescription Processing
[PSO LM BACKDOOR ORDERS] option.
Resolution:
-----------
INC15794278 - RxRenewal Response - Processing Error (RXE) message is not
It was confirmed that the eRx Holding Queue was not converting the medication
instruction text to upper case when it was retrieved from the MEDICATION
INSTRUCTION file (#51). This patch addresses this problem by always converting
the medication instruction text to upper case.
Technical Resolution:
---------------------
The line tag LSIG in the routines PSOERXU6 and PSOQUTIL was modified to always
convert the medication instruction text to upper case before returning it to
the calling routine.
INC15788861 - RxRenewal Response - Approved failed to generate renewed
3. INC16106925 - Pharmacy messages not assigned appropriate status by software
patch PSO*7*581
Problem:
-------
The VA Health Administration Center Denver reported that the CRN (RXCHANGE
REQUEST - NEW) status of some old (older than 14 days) RxChange request
records without a response were not being assigned the appropriate status CRX
(RXCHANGE REQUEST EXPIRED) as described in the user manual.
order
Resolution:
----------
After some research it was determined that the functionality for automatically
marking the records mentioned above as expired worked when the user selected
RX (PRESCRIPTION RECEIVED DATE) in the prompt below when entering the eRx
Holding queue (Complete Orders from eRx [PSO ERX FINISH] option). However,
if they select PT (PATIENT(Grouped)) the software did NOT check for records
CRN elegible for expiration to mark them as expired. Furthermore, the issue
also seem affect RRN (RENEWAL REQUEST - NEW) records which are also supposed
|
