| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | site(+) | 0;1 | POINTER | 4 | B | This is the site that the AR activity will be tracked for. A station can only have one site defined and multiple divisional sites are not currently supported. This identifies charges or events to a particular site in the event that information is shared or sent to a centralized system. |
| .02 | suppress rights & obligations | 0;2 | BOOLEAN | 0:NO 1:YES | Suppression of Rights and Obligations for RX copayment and Means Test bills can be accomplished by setting this parameter to 'YES'. All patients should be given their notice of Rights and Obligations, but some sites may wish to have these notices pre-printed or duplicated, rather than having the AR software print them individually. | |
| .03 | last bill number | 0;3 | FREE TEXT | This field contains the last number used on bills and FMS transactions. | ||
| .04 | ub printer(+) | 0;4 | FREE TEXT | This parameter defines the device to which Universal Billing forms (UBs) for Reimbursable Health Insurance bills are to print. A 'nightly process' is run every night by the AR system and one of the tasks that this process runs is the printing of the UB forms. This parameter needs to be set to the device which contains the UB forms for printing. | ||
| .05 | pharmacy copay statement info | 0;5 | SET OF CODES | 1:BRIEF 2:EXPANDED | This parameter defines the type of information to be displayed on the patient statement for RX copays. Some patients may want to have very detailed information about any RX copay charges on their statement, while others may require brief information. This parameter will be the default for ALL patients and will define the amount of information displayed on the patient statement. A second related parameter can be defined for each patient that will over-ride this site parameter. For example, if a site decides to have all their patients receive 'brief' information for RX copay charges, then this parameter should be set to 'BRIEF'. However, a particular patient may request more detailed information, in which case, this parameter should remain as BRIEF and the parameter for the patient should be set to DETAILED. | |
| .06 | last event number | 0;6 | FREE TEXT | Last number used by event number driver. | ||
| .07 | alc (deposits) | 0;7 | FREE TEXT | ALC code as assigned by Financial Management. | ||
| .08 | report printer(+) | 0;8 | FREE TEXT | This parameter defines the report printer for the AR system. A 'nightly process' is run every night by the AR system and one of the tasks that this process runs is the printing of the Patient Statements and Follow-up reports. This parameter needs to be set to the device that these reports should be printed. | ||
| .09 | suppress zero balance | 0;9 | BOOLEAN | 0:NO 1:YES | This parameter allows the site to suppress printing patient statements that have a zero balance. A patient may have had activity during a particular month that has left the account balance at zero (ex., patient got a $2.00 charge and paid it immediately). The system will print this activity to inform the patient on a patient statement. This information, even though the account balance is zero, is printed to confirm the payment was applied correctly and also for reimbursement and 'proof' of payment to insurance companies. However, some sites may wish not to print these statements and provide the information on a 'as-needed' basis. | |
| .1 | date/time system last updated | 0;10 | DATE-TIME | This field is set by the system and should not be directly edited. The AR nightly process is suppose to run every night to update interest and administrative charges, print patient statements, print UB bills, create refund bills, etc. This parameter is set when this process has completed every night. If the process does not complete, the AR clerk will be warned and IRM should take action to resolve the problem. If the process does not run to completion, certain events that must occur may have not be run to completion. | ||
| .11 | site statement day | 0;11 | NUMERIC | This is the day of the month that the site will send statements to CCPC. | ||
| .12 | local ccpc statements | 0;12 | SET OF CODES | 0:NO STATEMENTS TO LOCAL MAIL GROUP 1:SEND STATEMENTS TO LOCAL MAIL GROUP | This answer will determine whether the RCCPC STATEMENTS mail group receives the CCPC Patient Statement transmission messages that go to the CCPC. | |
| .13 | ccpc start-up date | 0;13 | DATE-TIME | This date will reflect the first statement date that the waiver rights statements are printed. | ||
| 2.01 | statement comment 1 | 2;1 | FREE TEXT | When printing Patient Statements, the site can have pre-defined text print on the first page of every statement. This parameter defines the first line of free-text comment to be displayed on every patient statement. | ||
| 2.02 | statement comment 2 | 2;2 | FREE TEXT | When printing Patient Statements, the site can have pre-defined text print on the first page of every statement. This parameter defines the second line of free-text comment to be displayed on every patient statement. | ||
| 3.01 | date of master irs offset(+) | 3;1 | DATE-TIME | The date entered into this parameter will be the date the system automatically attempts to create IRS MASTER code sheets to be sent to IRS. IRS Master code sheets can only be run certain times of the year. If a site does not wish to have these code sheets automatically generated, this field should remain empty and the option should be used to create the IRS master code sheets. | ||
| 3.02 | date of irs offset letter(+) | 3;2 | DATE-TIME | The date entered into this parameter will be the date the system automatically attempts to print IRS OFFSET letters to be sent to patients. IRS offset letters can only be printed certain times of the year. If a site does not wish to have these letters print automatically, this field should remain empty and the option should be used to print the IRS offset letters. | ||
| 3.03 | irs offset amount(+) | 3;3 | NUMERIC | The IRS charges the VA a fee for each account sent to IRS for offset against IRS refunds. The fee is set each year by IRS and should be entered into this field. The amount entered into this field will be added to the total amount forwarded to IRS for each account. This fee is only charges to VA if the IRS collects money. The fee is also not added to the AR system since the patient does not owe this money unless the IRS actually offsets a refund. | ||
| 3.04 | responsible for irs codesheets | 3;4 | POINTER | 200 | If a site wishes to have the Master Code sheets or update code sheets generated, a person with a valid electronic signature MUST be entered into this field. If IFCAP package requires that a person be identified as the 'responsible official' for code sheets. The person entered into this field will be entered as the responsible official with each IRS OFFSET code sheet only. | |
| 3.05 | top station code | 3;5 | FREE TEXT | This code is a two character alpha-numeric code that is tr ansmitted to Treasury on Treasury Offset documents. It is used to identify the site to Treasury. Without this code, sites will not be able to access their data. | ||
| 4 | rate effective date | 4;0 | MULTIPLE | 342.04 | This multiple stores information relating to the interest rate, penalty rate, and administration charges to apply to accounts and bills that are past due. Each year these rates can change and the rate at the time a bill is created remains in effect for that bill until it is closed. | |
| 5 | burster machine code | 5;E1,245 | FREE TEXT | This is the MUMPS code that will be executed to WRITE out a burster machine mark. The burster machine mark indicates the beginning of a new letter so the machine will 'stuff' the envelope. The write command could be, for example, a solid black line so that when the printed document is inserted into the burster machine it recognizes the beginning of a new letter. Different burster machines work differently so the manual must be referred to for instructions. The mark will appear in the middle of the top-header of patient statements and also at the top of follow-up letters. | ||
| 6 | integrated site | 6;1 | BOOLEAN | 1:YES 0:NO | This field will used to determine if the sat station prompt should be asked during the creation of a receivable. | |
| 7.02 | number of days eft unmatched | 7;2 | NUMERIC | This field allows the user to select how many days an EFT (electronic funds transfer) shall age before it is reported as unmatched. | ||
| 7.03 | number of days era unmatched | 7;3 | NUMERIC | This field allows the user to select how many days an ERA (electronic remittance advice) shall age before it is reported as unmatched. | ||
| 8.01 | # of days for rd elig chg rpt | 8;1 | NUMERIC | This field allows the user to select how many days in the past Rated Disability Changes will be checked for the Rated Disability Eligibility Change Report which is scheduled by IRM to be run on a recurring basis. If no value is added in this field the report will default to 31 days. | ||
| 8.02 | number of days for dmc reports | 8;2 | NUMERIC | This field allows the user to select how many days in the past bills for episodes of care will be included for the following reports when scheduled by IRM to be run on a recurring basis: DMC Debt Validity Report DMC Debt Validity Management Report Rated Disability Eligibility Change Report The minimum value for this field is 365 days (1 year) and the maximum value is 3650 days (10 years). If no value is added in this field the report will default to 365 days. | ||
| 9.4 | patch post init history | 9.4;0 | MULTIPLE | 342.01 | This field is used internally by AR to track when post inits are run at sites. | |
| 20.01 | vitria standard directory(+) | 20;1 | FREE TEXT | This field will contain the name of the specific directory into the nightly task will place the data files. This will be the standard directory which Vitria will scan for files to retrieve. | ||
| 20.02 | mail group(+) | 20;2 | POINTER | 3.8 | This field will point to the mail group that will receive any specific error messages to be received at the user level. | |
| 20.03 | date of last transmission(+) | 20;3 | DATE-TIME | This field will contain the last date that the transmission of a batch occurred. The field will be used to check the validity of a date field in the event someone re-indexes one of the main files used in the CBO AR Data Extract. | ||
| 20.04 | cbo status | 20;4 | SET OF CODES | 1:ON 0:OFF | This field will be set to '1' if this system is 'ON' or '0' if this system is 'OFF'. Only test systems will be allowed to 'turn off' the CBO AR Data Extract. | |
| 20.05 | maximum number records(+) | 20;5 | NUMERIC | This field will be used to split up large data extracts into multiple batches. | ||
| 20.06 | system type | 20;6 | SET OF CODES | T:TEST P:PRODUCTION | Designates whether the system is a Test or Production system. | |
| 20.07 | legacy site? | 20;7 | BOOLEAN | 1:YES 0:NO | This field should be answered 'Yes' if the install site is a legacy site. This field should be answered 'No' if the install site is NOT a legacy site. | |
| 20.08 | primary domain | 20;8 | FREE TEXT | This field should be the domain name of the primary VA site for the legacy site. It is important to have this value in order for acknowledgement messages to be forwarded to the legacy site. | ||
| 20.09 | extract running? | 20;9 | DATE-TIME | This field will be set when the running of CBO AR Data Extract starts. This is to prevent multiple jobs from running at the same time and impacting normal system function. | ||
| 30 | emergency response begin date | 30;1 | DATE-TIME | This field stores the date/time the emergency began. When this field is populated, an emergency situation is in effect, which will cause the suspension of TOP and DMC referrals, CCPC statements and interest and admin charges from being calculated. If the date falls within this beginning date and the Emergency Response End date, the suspension will take place. | ||
| 31 | emergency response end date | 30;2 | DATE-TIME | This field stores the date/time the emergency ends. When this field is populated, an emergency situation is in effect, which will cause the suspension of TOP and DMC referrals, CCPC statements and interest and admin charges from being calculated. If the date falls within this end date and the Emergency Response Begin date, the suspension will take place. |
Not Referenced