This file records each transaction as it pertains to inventory.
.01hcpcs(+)0;1FREE TEXTBThis field is the HCPCS code as defined by the .01 field in the PROSTHETIC HCPCS file (661.1).
2date&time stamp(+)0;2DATE-TIMECThis field is the date and time stamp (fileman standard format) of the transaction. This field will be automatically generated by the system and assumes users will record inventory transactions in a timely manner. It is one of the primary key fields and is also recorded on the barcode. It is a requirement that the date@time stamp should have a unique value for any given HCPCS. The reason for this is that HCPCS will also be recorded on an item's barcode and it is important that barcodes will not need changing if a site is integrated at some time in the future. Given the date&time stamp and HCPCS fields it is possible to generate a transactions IEN using the appropriate cross-reference.
3sequence0;3NUMERICThis field is a sequence number starting at 1 and incremented by 1 for each transaction which has the same HCPCS and DATE&TIME STAMP fields. This situation should be very rare and only occurs at all after site integrations. The HCPCS, DATE&TIME STAMP and SEQUENCE fields together make up the primary key for this file. The rationale behind this design is to allow the HCPCS and DATE&TIME STAMP to be printed as a barcode for automated data entry on a stock issue form. Fileman IENs will be derived from appropriate cross-references and, of course, these IENs can all change if a site is integrated. On the rare occasions where there is more than 1 SEQUENCE number associated with a HCPCS and DATE&TIME STAMP the user will have to be prompted to select from a list of transactions. We see no way round this inconvenience but hopefully it will be extremely rare!
4transaction type0;4SET OF CODES1:RECEIPT
This field records the transaction type, which can be one of the following... Receipt - for receiving items into stock. Order - for when a stock item has been ordered from the vendor. Patient Issue - for when a stock item is issued to a veteran. Issue to Lab - this transaction should be used for those items which are used by the labs to fabricate items. An example would be a bag of plaster which could be used for treating several patients. Return to Vendor - if an item has been received into stock but is later returned to the vendor for some reason, then this transaction type should be used. Write Off - use this transaction type when an item is removed from stock and scrapped. Transfer - for transferring stock between locations. The transaction quantity will be -ve for the 'transfer from' location. Return In - for when a veteran returns a stock item previously issued. Reconcile - for when a stock check is done.
5quantity0;5NUMERICThe number of items associated with the transaction.
6value0;6NUMERICThe dollar value of the transaction.
8comment0;8FREE TEXTA short comment can be entered, if required for a particular transaction.
9user0;9POINTER200This field points to the New Person file (200) and identifies the person responsible for creating the transaction on the system.
11hcpcs item(+)0;11NUMERICThis field is the HCPCS ITEM field held on the 661.12 sub field of the PROSTHETIC HCPCS file (661.1). The value held is the sub file's IEN not the ITEM text field.
12vendor0;12POINTER440This field is the FMS VENDOR CODE held on the VENDOR file (440). This field is guaranteed to be unique irrespective of where a database is located. The Vendor IEN should be derived from the 'D' cross-reference of the Vendor file.
13station0;13POINTER4This field is a pointer to the INSTITUTION file (4).
14location0;14POINTER661.5This field is a pointer to the PROSTHETIC STOCK LOCATION file (661.5).

Referenced by 3 types

  1. RECORD OF PROS APPLIANCE/REPAIR (660) -- stock issue
  2. PROSTHETIC TRANSACTION PATIENT ISSUE (661.63) -- inventory transaction
  3. PROSTHETIC INVENTORY GAIN/LOSS (661.69) -- transaction pointer