| DESCRIPTION OF ENHANCEMENTS |
This patch will resolve the following issue:
-------
The Dallas Field Office reported that BCMA MEDICATION LOG file (#53.79) does
not get updated properly when 2 patients are merged. More specifically, the
ORDER REFERENCE NUMBER field (#.11), which contains a pointer to UNIT DOSE
(#55.06) and IV (#55.01) sub-files in the PHARMACY PATIENT file (#55) does
not get updated with the new pointers when the entries in these two sub-files
are moved to a different IEN (Internal Entry Number). In some rare cases, this
will cause the BCMA Medication History Reports to hide one of the orders for
the newly merged patients if both patients had the orders of the same type
(UD/IV) with the same pointer and were administered on the same day.
Resolution:
----------
It was confirmed that the patient merge updates did not update the BCMA
MEDICATION LOG file (#53.79) entries when the IENs for UD/IV orders in the
PHARMACY PATIENT file (#55) were changed. The code was correct to correctly
update the BCMA MEDICATION LOG file (#53.79), ORDER REFERENCE NUMBER (#.11)
when two patients are merged.
Technical Resolution:
INC9104304 - Patient Merge is incorrectly merging BCMA MED LOGS
--------------------
Added a new line tag at the end of the routine PAJPATMR called UPDBML to
updated the ORDER REFERENCE NUMBER field (#.11) on the BCMA MEDICATION LOG
file (#53.79) file for all administrations right after the new IEN is assigned
to UD/IV orders. In addition, the code in UPDBML will kill the old (From) and
set the new (To) cross-references "AADT", "AEDT" and "AOIP" because it was
determined that the Patient Merge routines did not update them either.
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
1) INC9104304 - Patient Merge is incorrectly merging BCMA MED LOGS
Problem:
|
