| DESCRIPTION OF ENHANCEMENTS |
Problems resolved with this patch:
HIN-1198-41911
9. Some Mail message headers showing a 'null' user identity. The variable
XMDUZ was not being reset for subsequent messages.
Resolution:
The variable XMDUZ is set for each message generated.
10. IV statistics are wrong. A mix of calculation variables being used
were wrong.
NTH-0199-72479
Resolution:
The proper variables were identified and calculations re-coded.
11. The Controlled Substance Statistical Data report columns need to be
better aligned and the footnotes "* Non-Formulary" and "# Not on National
Formulary"" are missing.
Resolution:
The Controlled Substance Statistical Data report has been modified.
TAM-0299-30835
12. The Controlled Substance extract errors out when a type 2 transaction
has a quantity = 0.
NOIS:
MUR-0199-31080
Resolution:
The logic has been modified to quit the transmission of a record when the
quantity = 0.
13. The procurement extract was building lines in the MailMan messages
that were exceeding MailMan acceptable parameters.
NOIS:
LON-1198-60747
LEB-0299-20160
Resolution:
The length of the description of items contained in the extract have been
limited to 50 characters.
Resolution:
14. Undefined variable error in the procurement extract was generated due
to data arrays not being initialized properly.
NOIS:
EKH-0199-42100
NAS-0299-30308
WPB-0299-31308
Resolution:
The XMY array is now properly reset providing the address for the
The data arrays are properly initialized.
15. Controlled Substance reports are improperly flagging formulary drugs
as non-formulary.
NOIS:
MAR-0299-21304
Resolution:
The logic for flagging the formulary status has been corrected.
subsequent messages.
16. The AR extracts would send out multiple detailed messages whose
contents were duplicates. This was caused by the array holding the data
not being initialized properly.
NOIS:
HIN-0199-41269
Resolution:
The code has been modified to properly initialize the data array.
17. The costing formula in the procurement extract includes a $J function
which failed when the parameters of the formula were modified. The formula
was proper but the calculation was then too complex for the $J function.
NOIS:
CAH-1298-30287
Resolution:
The code was changed to perform the calculation first outside of the $J
2. Unit Dose generates an allocation error. The PSUTA array used in the
function and then hand the result to the $J function.
unit dose extract grows too large for the local partition.
NOIS:
ALX-1298-71646
DEN-0199-51099
BED-0299-11199
Resolution:
The PSUTA array has been moved to the ^TMP global.
3. Procurement generates an allocation error. The PSUMIT array grows too
1. The XM mailer hung in the background looking for user input. Modules
large for the local partition.
NOIS:
IOW-1198-40646
Resolution:
The PSUMIT array has been moved to the ^TMP global.
4. The procurement module has cost calculation and dividing by zero
errors.
needing to send more than one detailed message to Hines for a division
The procurement costing equation was wrong and there were cases when one
of the cost-per-unit factors used in the calculations were not available
and zero was being used for division.
NOIS:
NYN-1298-10759
Resolution:
The formulas for costing factors have been amended. In cases
where the cost factors are not available the reports have been amended
were getting hung in the background. The XMY array needed to be recreated
to reflect null or NA in the reports.
5. The outpatient extracts shows the wrong division in the message
headers. The software was pulling division names from File #40.8 instead
of File #59.
NOIS:
IOW-0199-41095
Resolution:
for each subsequent message.
Routines PSUOP4, PSUOP6 have been modified to pull division names from
File #59.
6. Division names for AR/WS, Procurement, and CS in the headers are not
matching the facility numbers. The coded lookup from File #40.8 is pulling
up entries associated with IENs instead of facility numbers.
NOIS:
CTX-1198-71660
MON-1298-52507
POR-0199-52307
Resolution:
The existence of a .001 field allows the pulling up of names by IEN
numbers. The lookups for names by facility number is now coded to limit
the search to the 'C' cross-reference only.
7. The AR/WS extract is generating subscript errors at DIV+6^PSUAR1. There
are inpatient locations that may not be linked to the PHARMACY AOU STOCK
file (#58.1).
NOIS:
NOIS:
MON-1198-50086
CLA-1298-20491
CHA-0199-30249
Resolution:
The coding in PSUAR1 has been modified to accommodate cases where
inpatient locations are not linked within the PHARMACY AOU Stock File
(#58.1).
RIC-1198-20912
8. The PSUARNM array is growing too large for the local partition in the
AR/WS extract and generates allocation errors.
NOIS:
OKL-1198-70175
Resolution:
The PSUARNM array has been moved to ^TMP for storage and processing in
routine PSUAR4.
|
