| DESCRIPTION OF ENHANCEMENTS |
1). When an adjustment is made to the balance of a drug in a pharmacy
2). There is a problem with invoices being marked as processed when
in fact they should not have been marked as such because there are
data elements missing.
Solution: When the individual line items are being processed the system
checks the order unit. For a line item to successfully process
as having an order unit, it must match one of the following 3
conditions:
a). The order unit is defined in the initial uploaded item
b). An adjusted order unit has been entered
location or invoice, the adjustment activity is recorded, but the
c). The order unit is defined in the synonym multiple in
the drug file.
3). After installing patch #3, if an invoice is being processed that is
already on file for the same order number, a string too long error
occurs at INVOICE+17 of routine PSAPROC7.
4). Invoices are passing through the processing and verification portions
of Drug Accountability with no problem, however, when the system does
the checking of the data for updating price and drug information, these
stored data is not updated. Some Drug Accountability programs make
problems are found, and nothing is updated.
Solution: This is in part because of problem #2 above, the order unit.
When the line item's data is being placed into the DRUG
ACCOUNTABILITY ORDER file (#58.811), the system assigns the
order unit to be either the value initially entered on the
invoice, or the value in the synonym multiple, otherwise zero.
No mention of the adjusted order unit. The order of assignment
should be, synonym multiple, adjusted, then initial upload.
5). Several facilities do not have their pharmacy locations defined
the adjustments internally before printing out the drug balances,
properly in the DRUG ACCOUNTABILITY STATS file (#58.8), which results in
errors. Usually the error is an undefined variable PSACOMB.
(fixed in routine PSAUTL1)
6). Uploading of incomplete invoiced data is corrected.
7). The dispense unit per order unit is no longer asked for on supply
items.
(PSAVER2 - If the user identifies the drug as supply, then they should
not be prompted for DUOU. Added a Line of code to check for PSASUPP.
while other programs do not make these necessary calculations. Other
8). When the PSA IV ALL LOCATIONS is executed each evening as a background
job, part of the OP dispensing functionality is to check each ward that
is associated with the pharmacy location in the DRUG ACCOUNTABILITY STATS
file (#58.8). Currently the program will discontinue processing if the ward
doesn't match the pharmacy location, BUT it also quits if the ward
does match the location. Therefore no OP dispensing data is recorded.
(fixed in routine PSAPSI3)
9). Balances on Controlled Substances are not updated when the orders
VISTA packages extract data from the Drug Accountability files on
are verified.
10). When an invoice is being processed/edited, the order unit field will
display the order unit associated with the line item based on adjustment,
invoice's order unit or the order unit in the synonym of the drug file.
When this field is to be edited, the only choices displayed are the
original invoiced order unit or the drug file entry. If an adjustment
had been made, the program ignored it. NOIS (HUN-1197-20485)
(Fixed 13 Jan 99 in routine PSAPROC3).
a regular basis, by not setting up the programs internally to make the
11). When patch PSA*3*3 was sent out, the second line syntax for the
routines PSAUDP & PSAUP1 which were released in patch PSA*3*6, was
erased. These two routines are added to this patch with updated second
line syntax.
12). During the set up of a pharmacy location there was a problem with
the call to obtain the outpatient pharmacy location. If there was more
than one location that was spelled similarly the program would take the
first one as default.
calculations for the adjustments, the data they are obtaining is
13). When the user is processing invoices, they can actually enter a
<RETURN> at the select pharmacy location or select master vault prompt.
the system will continue to process normally, but an error will occur
in SITES+1^PSAUTL1. This value must be entered for proper processing.
The user must now up-arrow out of the selection.
incorrect.
|
