DRUG ACCOUNTABILITY (84)    PACKAGE (9.4)

Fix undefined error reported in NOIS#.

PSA*2.0*9

 The following changes were made to address Y2K compliance issues.
 Line Tag  : PROCESS+11
 Exception : Flagged to be changed 
             $E(PSADT-100-(+$E(PSADT,4,5)=1*8800),1,5)*100
 Resolution: No change necessary, the code is calculating the previous
             month, and all Y@K checks appear to function correctly.
 
 Routine   : PSAUP1
 Line Tag  : XTMP+21
 Exception : Use of checking to see if number is >90 does not comply with
             a 70-30 split.
  
 Resolution: Changed to check for date within the recommended 70-30 split.
 
 Routine   : PSUDP
 Line Tag  : PICKLST+10
 Exception : Setting the node in global ^XTMP("PSAPV",0) to DT+1 would not
             be appropriate for dates such as FEB 28th.
 Resolution: Changed to a "C^%DTC" call which uses FileManager to calculate
             the correct date.
  

When the Inpatient dispensing data is gathered, the program checked only
one entry for each ward to find a match for a pharmacy location. A loop
has been installed to check for the proper pharmacy location.

 When the Outstanding Credits [PSA OUTSTANDING CREDITS] option is
 executed, and undefined error occurs in routine PSACREDO at line PRINT+17.
 The error occurs when all items on a invoice are adjusted to zero.

When the vendor sends the synonym node entry for the invoice's entry in the
DRUG file (#50). A variable was used in the assumption that the vendor
was supplying the facility with the correct information.
An error occurs when the program tries to find the matching information
on nodes that do not exist.

 When trying to match items to the National Drug file, the software was
 using old NDF globals. 

 When the user tries to print a report of invoices that were uploaded, 
 an undefined error could occur at HAVDEDRG+1 of the PSAUP4 routine if
 the 2 node was missing from the DRUG file (#50).

  When an invoice is uploaded, the program checks for the UPC and NDC. If
 these fields are not populated, the program exits. A check for the VSN
 was added to enable the program to continue.
 
  This will also cause problems in the verify portion. A check has been
 added to one of the verification routines.

 This build contains the correct version of routine PSATI which was
 released in patch PSA*3*18. That patch had test version number five as
 the final version. 

The set-up for device selection will not allow 80 column reports to be
sent to the screen. This causes massive amounts of wasted paper
to obtain information that should be readily available to the user.
This patch will allow 80 column reports to be sent to the screen.

 When invoices are added during processing, the DIC call used should be
 a FILE^DICN. Plus the lookup variable is set to look for an exact match.
 Order numbers such as "(B)123244556" cannot be added to the DRUG 
 ACCOUNTABILITY ORDER file (#58.811). This patch corrects the call.

When invoices are added during processing, the DIC call used should be 
a FILE^DICN. Plus the lookup variable is set to look for an exact match.  
Order numbers such as "(B)123244556" cannot be added to the DRUG 
ACCOUNTABILITY ORDER file (#58.811). This patch corrects the call.  
 
The solution to this, as stated in the first line, is to change the DIC
call to a FILE^DICN call.  

 If an items quantity is adjusted to zero, the system would pick up the
 invoiced quantity instead.

 There is a problem with the routine that is called when a picklist
 is filed away in Unit Dose. The routine improperly processed the incoming
 data. The processing method created incomplete data records of drug
 transactions.
 
 To correct this, the program does not rely on a temporary global being
 created. The data is extracted directly from the UNIT DOSE PICK LIST 
 STATS (#57.6) file.

1. This patch modifies the Input Transform of the following fields to
   RECEIVED field (#20) and BALANCE field (#22) in the ORDERS sub-file
   (#58.800118) of the DRUG sub-file (#58.8001) in the DRUG
   ACCOUNTABILITY STATS file(#58.8).
 
 - MONTHLY ACTIVITY field (#.01), BEGINNING BALANCE field (#1), ENDING
   BALANCE field (#3), TOTAL RECEIVED field (#5), TOTAL ADJUSTED field
   (#7), TOTAL DISPENSED field (#9), TOTAL RETURN TO STOCK field (#11)
   and TOTAL TURN IN FOR DESTRUCTION field (#12) in the MONTHLY
   ACTIVITY sub-file (#58.801) of the DRUG sub-file (#58.8001) in the
   DRUG ACCOUNTABILITY STATS file (#58.8).
   allow three decimal digits:
 
 - This patch updates the data dictionary of the QUANTITY field (#5),
   BALANCE FORWARD field (#9), QUANTITY RECEIVED field (#27), QUANTITY RET
   TO STOCK field (#35), QUANTITY TURN IN FOR DESTROY field (#38), BALANCE
   FWD RET/STK field (#41), NEW QUANTITY field (#50), ADJUSTED BY QUANTITY
   field (#51), BAL FWD EDIT VERIFIED ORDER field (#54), ADJUSTMENT
   QUANTITY field (#57), BAL FWD CANCEL VERIFIED ORD field (#59),
   QUANTITY TRANSFERRED field (#70), ORIGINAL COUNT field (#75), WASTED
   QUANTITY field (#76), LIQUID AMOUNT field (#77) and CORRECT COUNT field
   (#79) in the DRUG ACCOUNTABILITY TRANSACTION file (#58.81).
 
 
2. This patch modifies the data dictionary of the BALANCE FORWARD field
   (#9) in the DRUG ACCOUNTABILITY TRANSACTION file (#58.81), to prevent
   editing through VA FileMan options.
 
3. This patch modifies the data dictionary of the the TRANSACTION NUMBER
   field (#.01) in the DRUG ACCOUNTABILITY TRANSACTION file (#58.81), to
   disallow deletion though VA FileMan options.
 - STOCK LEVEL field (#2), BALANCE field (#3), REORDER LEVEL field (#4),
   QUANTITY TO REORDER field (#5) and MAXIMUM QUANTITY PER ORDER field
   (#8.5) in the DRUG sub-file (#58.8001) in the DRUG ACCOUNTABILITY
   STATS file(#58.8).
 
 - QUANTITY ORDERED field (#5), QUANTITY DISPENSED field (#19), QUANTITY

 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.

This enhancement provides a DELPHI based redesign of the Upload Invoices 
process currently in the Drug Accountability/Inventory Interface Version 
3.0 software. This option is used to upload invoice data from the Prime 
Vendor and update VISTA Drug Accountability files.  The redesigned 
function, using DELPHI instead of ProComm script files will make 
uploading invoices simpler and faster.  
 

 1. When sites do not process all uploaded invoices, problems arise when 
 2. Another problem this patch corrects is with the filing of monthly data
 on drug items. Monthly data was incorrectly stored for some items in 
 the DRUG ACCOUNTABILITY STATS file (#58.8). This patch corrects already 
 affected entries, and restricts the erroneous filing of incorrect data 
 in the future.
 the next batch of invoices is uploaded. Drug Accountability attempts to 
 match each item with items in the DRUG file (#50). The process will
 continue to add matching data to the item. If the invoices remain on the 
 system long enough an error will occur.
 
 The solution to this is to bypass the matching process on invoice data 
 that has already been uploaded.  
 

This patch will fix two undefined errors in menu option Edit Verified
Drug File (#50), an undefined error occurs when trying to subtract the
invoiced quantity.
Invoices.
An undefined error occurs when editing a verified invoice if the user 
changes the name of a drug and the order units are different.  This error
occurs when prompting for the Dispense Units per Order Unit.
 
When the user edits a line item and changes the drug name, the invoiced
quantity is updated in the Drug File (#50); subtracted from the invoiced 
item and added to the new item.  If the invoiced line item is not in the

 This enhancement contains the updated GUI based changes for the Upload
 Invoices process used by Drug Accountability V. 3.0 to process invoice
 data received from the new Prime Vendor, McKesson. 

This patch will modify the Report Potential NDC Matches option to use the 
same criteria as the Controlled Connection by NDC Match.

This patch addresses the problem in Drug Accountability where the menu 
"Setup/Edit a Pharmacy Location" [PSA LOCATION EDIT] generates the 
following error: $ZERROR=DAVEB+5^PSAENTO:3, %DSM-E-UNDEF, undefined  
variable Y(0,0).

Compliance with MailMan patch XM*7.1*50 and NDF patch PSN*3.18*5

This patch will modify PSA PROCESS PRIME VENDOR DATA  Process Uploaded 
Prime Vendor Invoice Data to always prompt the user when there is a change
in the Vendor Stock Number's NDC.  This is currently happening only if the
current NDC is numeric.

THIS PATCH CORRECTS AN UNDEFINED LOCATION ERROR.

 1. When sites do not process all uploaded invoices, problems arise when 
 2. Another problem this patch corrects is with the filing of monthly data
 on drug items. Monthly data was incorrectly stored for some items in 
 the DRUG ACCOUNTABILITY STATS file (#58.8). This patch corrects already 
 affected entries, and restricts the erroneous filing of incorrect data 
 in the future.
 the next batch of invoices is uploaded. Drug Accountability attempts to 
 match each item with items in the DRUG file (#50). The process will
 continue to add matching data to the item. If the invoices remain on the 
 system long enough an error will occur.
 
 The solution to this is to bypass the matching process on invoice data 
 that has already been uploaded.  
 

This patch addresses two problems:
 
1.      Uploading on invoices from the new prime vendor has lost the 
capability to automatically match invoice items to the drug file entries 
and manual editing is necessary on nearly every item on every invoice.
 
2.      The wrong VSN is shown for the selected item to be edited when 
editing verified invoices. The VSN displayed belongs to the last item 
presented in the choices for selection display.

INCORRECT QUANTITY ADDED TO DRUG IN DRUG FILE

This patch will correct a syntax error in routine PSAVERA2.
 
Multiple options with erroneous outpatient division on 
pharmacy locations.

This patch address the following problems:
2.      85690   Drugs that are added to pharmacy locations are initially 
setup with a minimum of information and need to be completed manually by 
the pharmacy staff. A method of notification is needed to let the 
pharmacy staff know which drugs are needing completion.
 
3.      68611   Invoice items that have a zero quantity are updating 
inventory costing for dispensing. This results in a miss-representation 
of costs being presented for statistics and being billed to third party 
insurances.
 
1.      68526           Price updates into the Drug file #50 are failing 
due to current logic that both order units and dispense units between the 
matched drug and the invoice must be equal before updating. Also, the
reporting and/or representation of which drugs are about to have order
units, costs, dispense units, and/or NDCs is hard to read, not concise,
and unwanted changes are being overlooked.
 

This patch addresses the following problems:
DRUG ACCOUNTABILITY STATS file (#58.8) has several of it's indexes 
scrambled and the users are not able to select the drug within that 
pharmacy location for any further processing purposes. A post init 
routine will scan and clean up bad indexes it finds.
 
3.      100058 Drug Balances by Location [PSA DISPLAY LOCATION]
The report menu "Drug Balances by Location" show entries for inactive 
drugs that have a zero quantity. Those items are now not to be shown.
 
4.      108683 Verify Invoices [PSA VERIFY INVOICES]
  
Drugs that are new to a pharmacy location in the DRUG ACCOUNTABILITY 
STATS file (#58.8) are needing more data entered to complete their being 
setup for processing. Such items as current balance, stock level, and 
reorder levels are needed. A separate, individual mail message is 
currently sent regarding each drug that is newly added. The volume of 
messages is overwhelming.
 
A single consolidated mail message by invoice regarding drugs that are 
newly added is needed to replace the individual mail messages.
1.      68490   Editing Verified Invoices [PSA EDIT VERIFIED INVOICE]
Saying 'NO" to processing the edit changes made for DISPENSE UNITS field 
(#14.5) and/or DISPENSE UNITS PER ORDER UNIT field (#15) of the Drug file 
(#50), does not restore those fields to their previous values.
 
2.      68779   Editing Verified Invoices [PSA EDIT VERIFIED INVOICE]
A drug that is newly picked and added newly to a pharmacy location in the 

HD68504 Invoices not being able to be up loaded. This patch corrects 
problems with the algorithm used to convert invoice files received from 
McKesson. The process incorrectly inserts zeros to the transaction set 
control number, which caused the length of the number to exceed the 
required specification length. An example of the error message is shown 
below:
 
Control# 0000000000000000000000000033
The ST control# (piece 3) should be 4 to 9 characters in length.

This patch addresses the following problem:
2. HD128777: Pharmacy locations, in the DRUG ACCOUNTABILITY STATS file 
#58.8, may have their associated entries in the drug file updated by zero 
quantity invoice items if the location is not marked for tracking 
inventory or re-order levels.
 
NOTE: A post init will review the Drug file (#50) and remove all but the 
first of identical synonym duplicates from under a drug. A "PSA*3*56 
Delete Duplicate Drug Synonyms report" mailman message will be sent to 
the person who performs the installation identifying what drug-synonyms 
had identical synonyms deleted. It will also indicate if there were none 
 
found to be removed.
 
EXAMPLE 1)      Duplicate synonyms found and were deleted.
Subj: PSA*3*56 Delete Duplicate Drug Synonyms report  [#2019687] 
03/17/06@17:11
11 lines
From: PSA*3*56 POST INIT  In 'IN' basket.   Page 1
--------------------------------------------------------------------------
PSA*3*56 DELETE DUPLICATE SYNONYMS REPORT
The following Drug-Synonyms have had identical synonyms removed from the 
1. HD68257: Drug SYNONYM field (#9) duplicates are being created in the 
drug.
Drug Name                       DRG#,SYN#   NDC            VSN
ACETAMINOPHEN, CODEINE 60MG TAB 3994,7      00406-0484-10  2792513
OU: CS        PPOU: $9.60                   DUOU: 1000     PPDU: $.01
ACETAMINOPHEN, CODEINE 60MG TAB 3994,11     00406-0484-10  2792513
OU: BT        PPOU: $9.60                   DUOU: 1000     PPDU: $.01
ACETAMINOPHEN, CODEINE 60MG TAB 3998,7      00406-0484-10  2792513
OU: CS        PPOU: $9.60                   DUOU: 1000     PPDU: $.01
ACETAMINOPHEN, CODEINE 60MG TAB 3998,11     00406-0484-10  2792513
OU: BT        PPOU: $9.60                   DUOU: 1000     PPDU: $.01
DRUG file (#50). The process of verifying an invoice that is adding a new 
 
EXAMPLE 2) No duplicate synonyms found and none were deleted.
Subj: PSA*3*56 Delete Duplicate Drug Synonyms report  [#2019688] 
03/17/06@17:15
3 lines
From: PSA*3*56 POST INIT  In 'IN' basket.   Page 1
--------------------------------------------------------------------------
PSA*3*56 DELETE DUPLICATE SYNONYMS REPORT
 
There were no duplicate drug-synonyms found. No synonyms were removed.
drug synonym to the DRUG file (#50) was found to be adding duplicates in 
 
Enter message action (in IN basket): Ignore//
the same invoice and between invoices that were processed at the same 
time. The verification process now insures duplicates are not being 
created.
 

A variable was mistakenly left out in the programming of patch PSA*3*8.

This option gives the user the ability to select and store drugs that are
to be returned to the manufacturer.
 
The OUTDATED MEDICATIONS option is located within the PHARMACY LOCATION
MAINTENANCE menu and locked with the PSAMGR key.

This patch addresses the following problems:
Processed status!' is presented.
Processing invoices through a particular path and question sequence will 
generate the above message which is wrong as the invoice has just 
completed processing necessary to be able to proceed to the verification 
stage.
 
3. HD 91604 An undefined error occurs when the selection list of invoices 
to send on to verification has a missed node in the display numbering 
sequence of the invoices. The user is able to put in a range from the 
beginning of the list to the last number in the list and the processing 
   
tries to work on all numbers in between. It hits the number of the 
missing node and it breaks.
1. HD 68113 Invoice select prompt (1-0)
The software is not properly detecting when all invoices being worked 
with have been processed. It is asking the user to make a selection when 
there are no invoices left to select from. The software errors out with 
an undefined if the user continues.
 
2. HD 93607 A faulty message 'The invoice has not been placed in a 

This patch will correct the problem of the Post Verify e-mail
not sent when changes are made to the invoice.

This patch addresses the following problems:
giving the user the chance to verify the selection. The drug name is 
unique and the few characters input by the user is enough to select the 
drug. Once the drug is selected it is not easy to navigate the software 
to a place where the drug can be reselected if the selection completed by 
the software is not what the user wanted.
 
1. HD 67762 PSANDF 12 digit NDC
The emerging standard is becoming 11 digits for the National Drug Code 
(NDC). The code had previously been set to create/require 12 digits by 
adding leading zeros. It is now set to create/require 11 digit NDCs. 
 
2. HD 68340 Forced selection of unique drug names.
The software is completing the selection of a unique drug name without 

This patch is addressing the following problems:
2. HD 118113. The sites have requested that the verification screens also 
display the vendor DUOU and drug description.
Both processing and verification screens will have the following 
information line displayed. The information displayed depends on the 
availability of vendor information uploaded.
 
========================= 
SAMPLE OF THE ADDED LINE: 
========================= 
There are two versions of the display line added.
 
1)      The line if the drug information is available
 PV-Drug-Descrip:    ACETAM? TB #4    ROX RN4X25        PV-DUOU: 100
 
2)      The line if the drug information is not available.
PV-Drug-Descrip:    Not available. Item is OTC or new after February 2006.
 
===========================
SAMPLE of modified screen:
===========================
The same line of information is presented in both processing and 
1. HD 112456 Reinstate the display of vendor item Dispense Units per 
verifying screens.
 
Order#: C563685000  Invoice#: 7246433050  Invoice Date: Sep 07, 2005
-----------------------------------------------------------------------
 
1  ACETAMINOPHEN, CODEINE 60MG TAB (Controlled Substance)
Qty Invoiced: 10                      UPC: 300054802324
Order Unit  : TU                      NDC: 00054-8023-24
Unit Price  : $9.60                   VSN: 1334150
 
Order Unit (DUOU) during processing. PSA*3*48 initiated a temporary plan 
PV-Drug-Descrip:    ACETAM? TB #4    ROX RN4X25        PV-DUOU: 100
 
Dispense Units: TAB
Dispense Units Per Order Unit: 2000
to aid sites in starting Drug Accountability by shipping in a side file 
from the vendor and display DUOU for matching drugs when possible during 
processing. It has been requested that the vendor drug description also 
be included to aid in matching items to drugs.
 

Problem HD129689 - Undefined error while processing invoice
--------------------------------------------------------------
The program PSAPROC7 will be modified to cleanup the variables prior
to the call to DICN0.
 
Problem HD92886 - Leading zero's in supply item description 
--------------------------------------------------------------
If a line item on an invoice is edited to be a supply item and
the supply item description starts with a numeric (Example: 16
vial dram, or 10x10 sponge) the system interprets the leading
numeric's as an internal entry number to the Drug File.  This
--------------------------------------------------------------
will cause the software to erroneously select the wrong drug.
 
Resolution HD92886 - Leading zero's in supply item description
--------------------------------------------------------------
The code has been modified to ignore the fact that the supply
item description starts with a leading numeric.
 
Problem HD68635 - Undefined error while editing invoices
--------------------------------------------------------------
In rare cases, the UPC and/or the NDC code in an invoice has
During the processing of an invoice, it is possible to receive
no value.  If this is the case, the software will error out
with an undefined error while editing an invoice to be verified.
 
Resolution HD68635 - Undefined error while editing invoices
--------------------------------------------------------------
The code in question will be strengthened to not error out when
this scenario occurs.
The following message:
Undefined N1+3 DICNO Unable to Process Invoice
This error is caused by the system not properly cleaning up variables
used by the program DICN0.
 
Resolution HD129689 - Undefined error while processing invoice

This patch addresses the following problems:
terms of the McKesson contract, is the date they deposit the invoice into 
their output directories for sites to access. The default date in VistA 
DA terms had been and is, the received at site date. Management has
determined it is best to require the users to manually enter the receive 
date than to present a default date which is never correct and should not 
be accepted.
 
3.  68532  PSADRUGP   <UNDEFINED>DISP~PSADRUGP
The "Enter/Edit a Drug" [PSA PV DRUG ENTER/EDIT] errors when the drugs
inactivation date is less then the day of the data entry.
 
 
4. 131384  PSAVER2   Error using Verify Invoice [PSA VERIFY INVOICES] 
When verifying invoices, the application errors if the data in the
processed invoice contains a semicolon. 
 
5. 134108  PSAVER, PSAVER1, PSAVER4      Invoice approved twice
During Invoice Verification, multiple users are aloud to select the same
invoice and verify it.  The quantities in the DRUG file (#50) are updated 
each time the invoice is verified.
 
1.  67941  PSAPROC1   undefined in PSAPROC1
6.   154985     PSAVER1    Invoice not verified, but message appears
Invoices are being marked as verified at the line item level when using 
the Verify Invoices [PSA VERIFY INVOICES] option and selecting an
invoice from the <<< EDIT INVOICES TO BE VERIFIED SCREEN >>>
If a Controlled Substance (CS) drug has not been assigned to a master 
vault, the  subsequent code path  is killing variables it will be needing 
later when it returns from the call to perform vault selection.
 
2.  68039  PSAPROC3   default date
The data element in invoices that represents the receive date, under 

With the deployment of Cache version 5, it was discovered that the short
modifies all routines that currently use a lock timeout value of less than
3 seconds to check for the node ^DD("DILOCKTM") and to use the value
defined there, otherwise the lock timeout value is set to a default value
of 3 seconds.
lock timeout values could generate a lock failure. Patch DI*22*147, which
has already been released, provided a solution to resolve this issue and
future lock issues.
 
This patch instituted a new default lock timeout of three seconds based on
a global node setting of ^DD("DILOCKTM")=3.
 
In order to avoid the lock issue in Drug Accountability, this patch

This patch addresses the following problems:
     report shows the status as UNKNOWN.
 
2.  187185   Can only verify one invoice at a time after PSA*3*60
 When using the EDIT INVOICES TO BE VERIFIED SCREEN and the user selects
 multiple invoices to edit, the application quits after editing the first
 invoice.
 
1.  186350   DA INVOICES UNKNOW STATUS
.There are two separate issues 
  a. The invoice status remains LOCKED VERIFYING when there are errors
     in the invoice.  This LOCKED VERIFYING status does not allow any
     further action until the invoice status has been reset to PROCESSED
     or VERIFIED.
  b. When an invoice is in a LOCKED VERIFYING status, the Print Orders

This patch addresses the following problems:
When using the "Edit Verified Invoices" [PSA EDIT VERIFIED INVOICE] 
option, the application does not remove the correct quantity which
results in inaccurate quantities being recorded. 
 
3. 119930  PSAPROC4   Multiple NDC match selection needs DUOU displayed
When using the "Process Uploaded Prime Vendor Invoice Data" [PSA PROCESS 
PRIME VENDOR DATA] option, the user is presented a list of drugs and 
related information if there is multiple synonyms exist. Currently the 
Dose Unit Order Unit (DUOU) is not displayed in that information.  The 
lack of this informationcan result in the wrong drug being selected 
 
during invoice processing.
 
4. 191994  PSAVERA   Duplicate receipt issue
When using the Edit Verified Invoices [PSA EDIT VERIFIED INVOICE] option 
to edit an invoice that has not been verified, the DRUG ACCOUNTABILITY
TRANSACTION file (#58.81) is updated.  Then when the user verifies the 
invoice the DRUG ACCOUNTABILITY TRANSACTION file (#58.81) is updated 
again causing duplicate transactions for the invoice item(s) that the 
edit was done on.
1.  68175  PSAENTO    Time Out Issue
User reported that the "Set Up/Edit a Pharmacy Location" [PSALOCATION 
EDIT] option does not quit properly when the application times out at
the INPATIENT SITE NAME prompt.
 
2.  98252  PSAVERA    Daily Activity Log does not record change on CS 
invoice 

This patch is a combination of patches 3,4,5,7,8,9,10,11,12,13.

This patch modifies the screens within the processing and verification
 
Currently, the Item Description and the inner pack fields are stored in
a temporary global which was setup in patch PSA*3*54. This global is no
longer used. The addition of the four fields is intended to assist the
user with the matching of incoming invoice items to the Drug (#50) file.
Below is an example of what the screens look like prior to installation
of this patch.
 
                       <<< PROCESS LINE ITEM SCREEN >>>
Order#: 3TC01  Invoice#: 7289249573  Invoice Date: Oct 05, 2007
processes within Drug Accountability. Additional drug information is
6  HYDROCORTISONE
Qty Invoiced: 1                       UPC: 30472034356
Order Unit  : EA                      NDC: 00472-0343-56
Unit Price  : $0.67                   VSN: 1279124
 
PV-Drug-Descrip: HYDROCORT AC CRM 1%  ALP 30GM@  PV-DUOU: 28.4
 
After patch installation:
 
                       <<< PROCESS LINE ITEM SCREEN >>>
now being included in the invoice files received from the prime vendor.
Order#: 3TC01  Invoice#: 7289249573  Invoice Date: Oct 05, 2007
6  HYDROCORTISONE
Qty Invoiced: 1                       UPC: 30472034356
Order Unit  : EA                      NDC: 00472-0343-56
Unit Price  : $0.67                   VSN: 1279124
 
PV-Drug-Description  : HYDROCORT AC CRM 1%  ALP 30GM@  PV-DUOU : 28.4
PV-Drug-Generic Name : HYDROCORTISONE                  PV-Units: 1
 
The additional fields are:
 Generic Description
 Item Description
 Prime Vendor Units (i.e. # bottles in sell unit)
 Inner Pack   (i.e. # pills in bottle)

This patch addresses the following problems:
 
1. 167457  Non CS drugs appear on narcotic dispensing/receiving report
The PSA IV ALL LOCATIONS [PSA IV ALL LOCATIONS] background job colliding
with CS dispensing.
 
2. 205861  ^PSDRUG LOCKS
PSA Verify Invoice processing is not unlocking the drug when finished.

This patch addresses the following problems:
The drug accountability list does not differentiate between the 
integrated sites.
 
3. 184524 - NDC changed from numbers to letters
Drug accountability invoice processing is changing the NDC from numeric 
to letters.
 
4. 222558 - Supply item match to drug file
The PRE Verify and POST Verify Variance Reports inaccurately report
changes for supply items that have leading numerics.
 
 
5. 229658 - Outdated Medications
The Outdated Medications [PSA OUTDATED MEDICATIONS] option does not 
display
all possible matches for a drug if the DRUG file (#50) index "C" is a
match to the information entered at the "Scan Drug barcode or enter a drug
name" prompt.
1.  180658 - Outdated Medications Option Not Working
The Outdated Medication [PSA OUTDATED MEDICATIONS] option, which allows
for documentation of the return of non-controlled substances, used the CS
Destruction file (#58.86).  This file will not allow the user's name to be
recorded.
 
2.  172859 - Outdated drug list for integrated sites

This patch addresses the following problems:
 
3. HD266899 - Error when running PSA IV ALL LOCATIONS
When running the "Outdated Medications" report and it quits unexpectedly,
the ^TMP("PSA",$J global is left behind causing the "PSA IV ALL LOCATIONS"
option to error.
 
4. HD265183 - Blank Order Unit on zero qty received causes supplies
              to appear on error report
When an invoice contains a blank Order Unit and a zero quantity, all 
supply items that follow, are included in the error report.
 
 
5. HD273421 - Cost Calculated Incorrectly on Outdated Meds
The cost on the Items To Be Returned report should be calculating based
on number of Dispense Units returned multiplied by Price Per Dispense
Unit from file 50. Instead, it is multiplying the number of containers
by the Price Per Dispense Unit:
1.  HD257764 - UNDEF ERROR
When editing the ORDER UNIT for a Supply Item of a verified order, the
application errors with an undefined error.
 
2.  HD255967 - UNDEF ERROR <UNDEFINED>EDIT1+36^PSAUTL1
During Order Processing if 2 users select same orders to process and 1
user is editing an order, the application will error.

The FY08 Q4 Enhancement Release includes the following enhancement in the
    1      Batch Work List            [PSA RET DRG BATCH WORKLIST]
    2      Batch Complete List        [PSA RET DRG BAT COMPLETE LIST]
    3      View/Update Batch          [PSA RET DRG VIEW/UPDATE BATCH]
    4      Return Drug Credit Report  [PSA RET DRG REPORT]
 
The Batch Work List [PSA RET DRG BATCH WORKLIST] option will be used to
process open return batches, which are assigned a statuses of 'AWAITING
PICKUP' and 'PICKED UP'.
 
The Batch Complete List [PSA RET DRG BAT COMPLETE LIST] option allows 
Drug Accountability V. 3.0 application.
users to access and update batches with any status.
 
The View/Update Batch [PSA RET DRG VIEW/UPDATE BATCH] option is used for
single batch processing, independent of its status.
 
The Return Drug Credit Report [PSA RET DRG REPORT] option provides
the users with summary and detailed reports of all return batches.
 
Security Keys:
-------------
 
In order to have access to the new options, a user must have the PSORPH
or PSARET security key. The PSORPH key is an existing key in the
Outpatient Pharmacy V. 7.0 application. The PSARET is a new security key
in the Drug Accountability application, will be transported in this patch
and should be assigned to users who will be responsible for returning
drugs to the contractor.
 
New Files:
---------
The following two new files are being added to the Drug Accountability
A new module is being added to the Drug Accountability application to 
V. 3.0 application to support the functionality delivered by this patch.
 
 
                                UP    SEND  DATA                USER
                                DATE  SEC.  COMES   SITE  RSLV  OVER
FILE #  FILE NAME               DD    CODE  W/FILE  DATA  PTRS  RIDE
--------------------------------------------------------------------
58.35   RETURN DRUG             YES   YES   NO
58.36   RETURN DRUG CONTRACTOR  YES   YES   NO
 
address one of the findings in the GAO Report GAO-04-755 dated July 2004
 
The RETURN DRUG file (#58.35) is used to store all the information
about drugs being returned to the manufacturer while the RETURN DRUG
CONTRACTOR file (#58.36) is used to store the list of contractors
that the VA Medical Center (VAMC) uses for returning drugs for credit.
Most likely there will be only one contract active at a time for most,
if not all, VAMCs.
related to implementing a better control over Return Drug Credits. The new
module is called Return Drug Credit Menu and contains the following 4
options.
 

This patch addresses the following problems:
  The Drug Accountability Transaction History report in not correctly
  calculating the drug balance for dispensed drugs.  Currently the report
  is adding the dispensed quantity instead of deducting it.
 
1.  HD335328 - Routine patch list needs editing
  When PSA*3*69 was release there was five new routines introduced.
  The format of the second line of five Routines sent out with patch
  PSA*3*69 need to be corrected. Instead of *69* they need to be *69*.
 
2.  HD342000 - Dispensed units not automatically subtracting from
               inventory

This patch addresses the following problems:
 sent back.  This was a mistake. It should be received in and then out.
 Then the verifier did the verification and changed the qty received to
 reflect the original qty received - correcting the mistake.
 After verifying the invoice, the user checked the Controlled Substance
 package and found the drug did not show as being received.
  
3.  HD322644 - Run away PSA IV ALL LOCATIONS - All Location Dispense/Purge
 The PSA IV ALL LOCATIONS - All Location Dispense/Purge nightly job does
 not complete.
 
 
4. HD279969 - verifying invoices with blank order unit no longer on
              discrepancy report
 When processing a invoice with a blank ORDER UNIT the system returns a
 zero and does not generate a discrepancy report.
1.  HD211457 - Locked Invoice
 Sites are reporting that the invoices are being left in a LOCK
 VERIFYING status.
 
2.  HD285500 - Can't received drug (CS) into vault
 When a invoice was downloaded and processed by a tech, the quantity
 received was changed to 0 on one item because it was going to be

This patch addresses the following problems:
 
1.  SUBSCRIPT>LINE+45^PSAPROC7
 
2.  Only Outpatient Figures on Reports
 
3.  DRUG TRANsaction History does not cleanup variables if up caret at 
    the device prompt.

This patch addresses the following problems:
Run no updates are being made to the Drug Accountability Transaction file
(#58.81) or the Drug Accountability Stats file (#58.8).
 
3. INC000000842761 - Drug Accountability - Drug File Updates
When the invoiced Price Per Order Unit is .01 and Dispense Units Per
Order Unit is 100, the Price Per Dispense Unit is calculating it at 0
when it should be .0001 during invoice processing/verifying.
 
1. INC000000443727 - Verify invoices and no action is taken
When a Controlled Substance follows a drug that has a quantity of 0,
the Invoice Verify routine does not create the Controlled Substance 
transaction in the Drug Accountability Transaction file (#58.81).
 
2. INC000000212726 - Outpatient Dispensing (All Drugs) Option not working
When the Outpatient Dispensing (All Drugs) [PSA OP ALL DRUGS] option is

This patch addresses one (1) issue:
 
Problem:
--------
Verified Drug Accountability (McKesson) invoices will not be set 
to a status of Complete if the user edits the invoice, verifies, 
and closes (or is disconnected from) their Reflections session at  
the "Type <Enter> to continue or '^' to exit:" prompt.  This causes 
an out-of-balance situation with regards to the controlled substance 
vault.
 
 
Resolution:
-----------
If a user edits an invoice prior to verifying, VistA routine ^PSAVER1 
sets the invoice status to VERIFIED and prompts for the user to 
continue or exit, via subroutine END^PSAPROC. The prompt at that point
waits for a response.  If the user's Reflections session ends without 
completing the final prompt, important processing is missed with 
regards to setting up invoice data for the background job that changes 
the status from VERIFIED to COMPLETE.
 
1. McKesson invoice verified, but controlled substance balance did
To resolve this issue, the call to execute the prompt via END^PSAPROC 
has been moved to a more appropriate spot in EXIT^PSAVER.
   not update
 
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
 
1.  I5849148FY15

This patch creates the PHARMACY PRIME VENDOR mail group. The Prime Vendor
Line Item Report will be sent to this mail group from the Austin
Automation Center twice per week.

This patch will resolve the following issue.
        
Problem: 
--------
VA Southern Nevada reported that they were unable to correct vault medication
with negative balance which is also inactive in the drug file. The negative
balance is actually caused by a problem in the Edit Verified Invoices [PSA
EDIT VERIFIED INVOICE] option which incorrectly records transactions when
an invoice is edited and a controlled substance drug is replaced with a
non-controlled substance drug and vice-versa.
       
 
Resolution:
-----------
Modified the Edit Verified Invoices [PSA EDIT VERIFIED INVOICE] option to
correctly record inventory transactions accordingly whether the drug is
marked as controlled substance or not.
  
Technical Resolution:
---------------------
Changed the routines PSAVERA and PSAVERA1 which are responsible for updating
the inventory transactions after a verified invoice is edited.
INC0933704 - Unable to  correct vault medication with negative balance which
             is also  inactive in the drug file
     
Defect Tracking System Ticket(s) & Overview:
--------------------------------------------
INC0933704 - Unable to  correct vault medication with negative balance which
             is also inactive in the drug file

An incident was reported that when a pharmacist changes the drug name for 
a line item on an invoice using the option VERIFY INVOICES and then the 
invoice is subsequently verified by a different pharmacist, the new change
is not saved properly in the invoice file. In turn, this causes some of
the various drug accountability reports to be inaccurate.

This patch will resolve the following issues:
 
Several sites have reported that when editing a verified invoice by 
changing a non-controlled substance drug to a controlled substance drug a 
negative balance for the non-controlled drug is appearing on the 
Controlled Substance Inventory Sheet. Another defect experienced with 
this same type of edit is the inability to select the non-controlled 
substance drug by name when trying to adjust the negative balance in the 
controlled substance vault.

When the Receiving Directly into Drug Accountability [PSA RECEIVING]
option is used, the following error occurs:
$ZE= HEADER+3^PSAREPV:3, %DSM-E-UNDEF, undefined variable PSA(2)
 
Also, the problem of not being able to enter decimal digits for the
dispense units per order unit has been corrected.

 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.

When an invoice is selected to be printed, and the invoice is still in
the temporary global used to hold data prior to processing/verification,
the last invoice in the file will be printed, instead of the selected
invoice.