| REQUIRED BUILD |
-
- PSA*3.0*3
- ACTION: Don't install, leave global
-
- PSA*3.0*27
- ACTION: Don't install, leave global
-
- PSA*3.0*15
- ACTION: Don't install, leave global
-
- PSA*3.0*12
- ACTION: Don't install, leave global
-
- PSA*3.0*19
- ACTION: Don't install, leave global
-
- PSA*3.0*17
- ACTION: Don't install, leave global
-
- PSA*3.0*20
- ACTION: Don't install, leave global
-
- PSA*3.0*23
- ACTION: Don't install, leave global
|
| DESCRIPTION OF ENHANCEMENTS |
1. This patch modifies the method used to update a drug's NDC and other
If the invoiced item's Order Unit and Dispense Units per Order Unit match
the same fields in the DRUG file, but the price of the dispense unit has
changed then the following process occurs:
a. The new price per dispense unit is compared with the PRICE PER
DISPENSE UNIT field (#16) in the DRUG file (#50), to see if it is
within 5%. If it is not within the 5% difference, the PRICE PER
DISPENSE UNIT field (#16) in DRUG file (#50) is set to the invoiced
price per dispense unit, and the PRICE PER ORDER UNIT field (#13)
pricing information.
in the DRUG file (#50) is set to the invoiced price per order unit.
b. A MailMan message is sent to members of a new mail group called:
'PSA NDC UPDATES' to inform them of the price change. The subject of
this message is: "DRUG file Price/NDC Update".
c. Because of the problems with price calculations in the past, a post
patch install routine has been added to correct current incorrect
prices.
2. When processing invoices, the system checks for the pharmacy locations
that will be used during processing. If no locations are found the
program proceeds to exit the option. However, in the exit logic the
system checks to see if the user has up arrowed or if something has
failed. If the exit variable has not been set, the program continues on
to automatically enter the invoice into VISTA.
3. Another problem this created was when the user would proceed with manual
processing of these invoices, the pharmacy location field would be empty.
This creates an undefined global node when the program tried to find the
The revised method of updating the NDC and price information is as
location name. If pharmacy locations are not set up, the exit variable
is not set, therefore the invoices are processed.
4. When the Connect Unlinked DRUG/ITEM MASTER file Entries [PSA UNLINKED
LOOP] option is executed an undefined error occurs. The problem stems
from the user not selecting a drug to link to. The solution to this
problem is to change where the routine is called.
5. When printing the Verification Error Report if the report is printed to
the screen or a slave printer it's fine. If the report is queued to a
follows:
printer, none of the data prints out.
The problem with this was that the variable saved for the print job was
a simple variable, not a variable array as it should be.
6. Due to site integration, invoices can sometimes be processed more
than once. The invoice file is checked during uploading to see if the
invoice currently exists, but the check is not performed when the user
processes the information. The solution to this is a check being added
that will compare the invoice's Order Number, Invoice Number and the
line items against what is stored in VistA. If a close enough match is
found, a comparison array of data will be displayed for the user. After
displaying the data, the user has the option of eliminating the incoming
invoice.
7. The option Delete Un-processed Invoices [PSA DELETE INVOICES] has been
created to delete invoices that are on file past a user specified date.
8. When processing invoices, if an item has the same vendor stock number
but different NDCs, a new synonym entry is created. When the item is
If the NDC on an invoiced item does not match the NDC field (#31) in
being processed again, the system will display the same drug as two
different choices. The problem is, that there is not enough detailed
information provided for proper selection. The solution to this was to
add the NDC to the display.
9. When invoices are processed for multiple divisions, or by multiple
personnel, all invoices show the same person as the processor. This
was caused by the last function of processing. When the user finishes
processing, the program would look at each invoice. If the invoice
was marked as processed, the data would be moved into the proper files.
the DRUG file (#50), then the NDC entry in the DRUG file (#50) will be
the program did not distinguish between users. The solution to this is
to file the data immediately for each invoice as it is marked as
processed.
changed to the invoiced NDC.
|
