| DESCRIPTION OF ENHANCEMENTS |
This patch will resolve the following issue:
--------
If a patient has an active titration RX and a pending controlled
substance RX from CPRS, and then a new order is placed for the patient
via COMPLETE ORDERS FROM OERR [PSO LMOE FINISH] option, a hard error can
occur. After placing the new order and accepting, a hard error occurs:
<UNDEFINED>ACLOG+5^PSON52 *PSOCSP("NAME"). In addition, the remarks field
for new order incorrectly refers to the CPRS controlled substance RX as
being edited.
Resolution:
-----------
It was discovered that when the user selects the "CS" controlled
substances as the primary filter when finishing a patient's
orders via COMPLETE ORDERS FROM OERR [PSO LMOE FINISH] option,
the logic pulls the data for any pending controlled substances for the
patient selected. This causes the data to be set to the pending
controlled substance, even if the pharmacist chooses to place a new
order. Most of the variables are newed in the logic except for the OR0
variable which is not cleared out when the a new order is placed. This is
the reason for the <UNDEFINED>ACLOG+5^PSON52 *PSOCSP("NAME") error and why
1) INC24967678 - This patch will address the issue described in
the remarks contain the controlled substance data.
Technical Resolution:
---------------------
The fix for this issue is to new the OR0 variable in the AGAIN tag of
PSONEW.
ServiceNow Incident INC22865486, regarding the <UNDEFINED>ACLOG+5^PSON52
error when creating a new order in the COMPLETE ORDERS FROM OERR
[PSO LMOE FINISH] option. In addition, this patch will resolve the
incorrect RX reference in the remarks field.
Problem:
|
