| DESCRIPTION OF ENHANCEMENTS |
1. This patch will update the activity log for orders that are
**************************************************************************
2. When queuing an Extra Units Dispensed Report to a printer the last
line was not being printed. This patch will correct this problem.
3. The Cost at Discharge [PSJU DCR] option was mistakenly left out of the
Inpatient Medications version 5.0 distribution. This option is no longer
used. This patch will distribute the option as Delete at Site.
4. A problem was identified with the auto-reinstate feature. A patient
discontinued by Computerized Patient Record Systems (CPRS) due to a change
had an active order that was auto-discontinued upon ward transfer. He was
then issued a new order for the same drug. The transfer was later deleted
and his previous meds were reinstated. As a result, the patient ended up
with 2 duplicate orders.
Checks have now been included to prevent the reinstatement of an order if
a new duplicate order has been added. For IVs, if the order to be
reinstated has any additive the same as the new order it will not be
reinstated.
in Treating Specialty. It adds a new entry to the ACTIVITY LOG REASON
The notification e-mail, advising of medication orders automatically
reinstated, has also been amended to include any orders that could not be
re-instated due to duplicates existing on the system. The recipient list
for the e-mail also now includes the verifying nurse, verifying
pharmacist, the physician, the provider and who entered the record (where
applicable).
5. When using the "edit intervention" after a critical interaction comes
up on UD order entry, the prompt "Intervention" came up with the default
of ALLERGY instead of CRITICAL INTERACTION. This has now been amended so
file (#53.3). The new entry is 1040 AUTO DISCONTINUED (TREATING SPECIALTY
that if a Critical or a Significant drug interaction is detected, the
appropriate default is used.
TRANSFER).
***************************PLEASE NOTE************************************
While this patch doesn't require OR*3*45, the functionality will not work
as intended without patch OR*3*45.
|
