| DESCRIPTION OF ENHANCEMENTS |
This patch will address the following issues:
--------------------------------------------
1. INC11549905 - when you enter a new prescription the QTY rounds up unless
you change the days supply.
Problem:
--------
The Oscar G. Johnson VA Medical Center reported that when editing the Days
Supply fields for a Clozapine prescription that the QTY field value is not
rounding up, instead it remains a factional value, forcing the user to fix
it mannually.
Resolution:
-----------
The issue was confimed and the calculation of the QTY value was fixed to
round any fractional value up. So, if the automatic calculation results in
a value such 4.2, for example, it will be rounded up to 5.
Technical Resolution:
---------------------
Changed the routine PSOCLUTL at line tag QTYCHK+9 to always round the value of
1. INC11549905 - when you enter a new prescription the QTY rounds up unless
the variable QTY up.
S:QTY PSORXARY("QTY")=(QTY+.99)\1,$P(PSORXARY("RX0"),U,7)=(QTY+.99)\1
2. INC11595547 - CLOZAPINE ORDER - Day Supply- Quantity - # of Refill -
Expiration date calculation
Problem:
--------
After the installation of patch PSO*7*574 the expiration date calculation for
you change the days supply.
clozapine prescriptions is wrong for some scenarios after editing the # of
Refills or Days Supply fields. For example, when you edited a prescription
with 28-day supply and 0 refills, with an expiration date of 28 past the issue
date, to 14-day supply and 1 refill it was setting the expiration to 14 days
past the issue date, instead of keeping the 28 days.
Resolution:
-----------
The calculation of the expiration date for clozapine prescriptions was resolved
to correctly calculate the total number of days supply of the entire
2. INC11595547 - CLOZAPINE ORDER - Day Supply- Quantity - # of Refill -
prescription, including the refills.
Technical Resolution:
---------------------
Removed a line of code in the PSOEXDT routine (shown below) introduced by
PSO*7*574 that was preventing the expiration date from being calculated
correctly for clozapine prescriptions.
; Added Clozapine check to not modify Expires date ; PSO*574
A Q:+$G(PSORXED("CLOZ EDIT"))
Expiration date calculation
3. INC11627662 - PSOL EDIT - Edit Data for a Patient in the Clozapine Program
Problem:
--------
After the installation of patch PSO*7*574 the option Edit Data for A Patient in
the Clozapine Program [PSOL EDIT] started resetting the REGISTRATION DATE field
(#58) in the PHARMACY PATIENT file (#55) even after the user simply returns
through the 3 fields in the option without modifying any of them. The
REGISTRATION DATE field should only be reset when the user changes the value of
3. INC11627662 - PSOL EDIT - Edit Data for a Patient in the Clozapine Program
the CLOZAPINE REGISTRATION NUMBER.
Edit Data for a Patient in the Clozapine Program [PSOL EDIT]
Edit Data for a Patient in the Clozapine Program
Select clozapine patient : CLOZPAT,TEST
CLOZAPINE REGISTRATION NUMBER: MR12345// MR12345
CLOZAPINE STATUS: ACTIVE TREATMENT
RESPONSIBLE PROVIDER: TEST,PROVIDER// TEST,PROVIDER
Resolution:
-----------
The Clozapine REGISTRATION DATE will only be reset when the value of the
CLOZAPINE REGISTRATION NUMBER is modified.The issue was confimed and the calculation of the QTY value was fixed to
round any fractional value up. So, if the automatic calculation results in
a value such 4.2, for example, it will be rounded up to 5.
Technical Resolution:
---------------------
Changed the routine PSOCLUTL at line tag QTYCHK+9 to always round the value of
Defect Tracking System Ticket(s) & Overview:
the variable QTY up.
S:QTY PSORXARY("QTY")=(QTY+.99)\1,$P(PSORXARY("RX0"),U,7)=(QTY+.99)\1
|
