Files > FEE BASIS BATCH

name

FEE BASIS BATCH

number

161.7

location

^FBAA(161.7,

description

Contain all batches established by Fee Basis users. Payments are assigned to a batch and payment data is transmitted for payment in batches. Per VHA Directive 10-93-142, this file definition should not be modified.

Fields

#	Name	Location	Type	Details	Index	Description
.01	number(+)	0;1	FREE TEXT		B	The number identifying this batch. The batch number is automatically assigned to the batch when a clerk opens a batch.
1	obligation number(+)	0;2	FREE TEXT			The obligation number (which must exist in the obligation file) associated with this batch number. When this batch is processed by the Austin Central Fee system, and passed to the CALM payment system, the funds for these payments will be from the obligation number identified here.
2	type(+)	0;3	SET OF CODES	B3:MEDICAL PAYMENTS B5:HOMETOWN PHARMACY PAYMENTS C1:VENDOR FILE ACTIVITIES C2:VETERAN MRA ACTIVITIES C4:PHARMACY FILE ACTIVITIES B2:TRAVEL PAYMENTS B9:CH/CNH		The type field identifies what type of records will be contained in this batch. For example, this could be a 'Pharmacy Payment' type batch or could be a 'Medical Payment' type batch.
3	date opened	0;4	DATE-TIME			The date this batch was opened by the clerk or the date it was last reopened by the clerk or supervisor.
4	clerk who opened	0;5	POINTER	200	C	The clerk who opened the batch or the clerk or supervisor who last reopened this batch.
4.5	date clerk closed	0;13	DATE-TIME			The date that the clerk closed the batch. Payments cannot be entered after the batch is closed.
5	date supervisor closed(+)	0;6	DATE-TIME		ADS	The date and time that the supervisor reviewed and released for payment or the date released to the NVH Pricer.
6	supervisor who certified(+)	0;7	POINTER	200		The supervisor who reviewed the batch to release/certify that the batch was approved for transmission to Austin for payment.
8	total dollars(+)	0;9	NUMERIC			The total dollars that will be paid for items in this batch. This field is calculated when the batch is closed. This field will NOT be accurate if the batch has NOT been closed.
9	invoice count	0;10	NUMERIC			The number of individual invoices associated/included in this batch.
10	payment line count(+)	0;11	NUMERIC			The total number of payment line items included in this batch.
11	status(+)	ST;1	SET OF CODES	C:CLERK CLOSED S:SUPERVISOR CLOSED O:OPEN T:TRANSMITTED F:CENTRAL FEE ACCEPTED V:VOUCHERED P:FORWARDED TO PRICER A:ASSIGNED PRICE R:REVIEWED AFTER PRICER	AC	The current status of the batch (ie Open, Clerk Closed, Transmitted).
12	date transmitted	0;14	DATE-TIME			The date/time the supervisor used the 'Queue Data for Transmission' option. This is NOT the actual date/time the transmission occurred.
13	date finalized	0;12	DATE-TIME		AF	This is the date that the batch is finalized. This occurs after the batch has been sent to Austin and the Austin processing has occurred. This is the final step where any items rejected by the Austin system have been rejected and the batch is finalized.
14	person who completed	0;16	POINTER	200		The supervisor who completed/finalized the batch.
15	rejects pending	0;17	BOOLEAN	Y:YES		A flag which indicates whether this batch has any line items which were rejected and have yet to be reassigned to a new batch.
16	station number	0;8	FREE TEXT			The station number (as defined centrally) for the station that is processing this batch.
17	contract hospital batch	0;15	BOOLEAN	Y:yes		A flag set to 'Yes' if the batch is a Contract Hospital batch.
18	batch exempt	0;18	BOOLEAN	Y:YES N:NO		Population of this field indicates the batch is exempt from processing by the Austin Pricer.
19	statistical batch	0;19	BOOLEAN	1:YES 0:NO		This flag is set by the software. Batches with this flag set to '1' (YES) will NOT make payment through FMS. It is used to update payment records both in DHCP and Central Fee.
20	finalized with vista	1;1	BOOLEAN	1:YES		This field indicates if batch was finalized (completed) using the VistA Finalize a Batch option as opposed to some other method such as the Fee Basis Claims System (FBCS). This field is automatically populated by the software. It was added by patch FB*3.5*132 and will not be populated for batches finalized prior to installation of that patch.
21	voucher msg date	1;2	DATE-TIME			This field is automatically populated with the current date when a Voucher Batch message is generated for the batch. This field will be used to determine if the application acknowledgement from Central Fee is overdue.
22	voucher msg ack status	1;3	SET OF CODES	P:PENDING E:ERROR A:ACKNOWLEDGED		This field holds the status of the acknowledgement for the most recent voucher batch message. This field will be automatically set to Pending when a voucher batch message is generated. The FBAA VOUCHER SERVER server option will update this field to Error or Acknowledged based on the voucher batch acknowledgement message from Central Fee.
23	status set to retransmit by	1;4	POINTER	200		This field is automatically populated with the current user when the Reprocess Overdue Batch option is used to reset the status of a payment batch so the batch will be retransmitted to Central Fee. This field is used to track exceptions to the normal batch process.
24	status set to retransmit date	1;5	DATE-TIME			This field is automatically populated with the current date when the Reprocess Overdue Batch option is used to reset the status of a payment batch so the batch will be retransmitted to Central Fee. This field is used to track exceptions to the normal batch process.
25	transmitted batch was rejected	1;6	BOOLEAN	1:YES		This field is automatically populated with YES when the Reprocess Overdue Batch option is used to flag an entire batch as rejected. This field is used to identify when an exception to the normal batch process occurred.