| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | event identifier(+) | 0;1 | FREE TEXT | B | This is a unique identifier of an event logged into the AR Event file. Usually the first 3 numbers will be the station number followed by a dash. | |
| .02 | type of event(+) | 0;2 | POINTER | 341.1 | The event type describes the type of event that occurred for a debtor by storing all events that occur for this debtor. This allows better reporting capabilities, financial integrity, and history recreation. In version 4.0 of AR, the only types of events that are tracked under this new system are notification type events (letters, UBs, and patient statements) and comments. Eventually, payments, refunds, etc. will be tracked in this new file but are currently being tracked in the Accounts Receivable transaction file. | |
| .05 | debtor(+) | 0;5 | POINTER | 340 | This debtor field is used to store what debtor this event belongs to. By storing events by debtor, this will allow a more efficient system when trying to re-create the activity for a debtor account. | |
| .06 | date/time of event(+) | 0;6 | DATE-TIME | The Date/Time of event represents the date the event occurred. For example, if a user is logging a comment against a debtor account for the previous day, then this field would be dated for that day and not the day it is being entered. This allows the user to back-date events that occurred in the past. | ||
| .07 | date/time closed(+) | 0;7 | DATE-TIME | The date/time an event is closed is the time the AR package 'recognizes' the event as being closed and complete. An event has two status, OPEN and CLOSED. While a transaction is in a status of 'OPEN' the AR package does not recognize the transaction. | ||
| .08 | created by | 0;8 | POINTER | 200 | This is the person that caused the event to be created. | |
| .09 | site(+) | 0;9 | POINTER | 4 | The site field represents the site that the event belongs to. This field would be used when multiple divisional sites are supported and will allow events to be 'traced' to a particular site. | |
| .11 | status(+) | 0;11 | SET OF CODES | 0:OPEN 1:CLOSED | The status of an event is either OPEN or CLOSED. When an event for a debtor is in an 'OPEN' status, this means that activity is occurring and has not completed. After the activity is completed, the event would be changed to a status of CLOSED. | |
| 1.01 | principal amount | 1;1 | NUMERIC | This field contains the principal amount of the event if applicable. Some events, such as comment type events, do not have a dollar amount associated with the event. | ||
| 1.02 | interest amount | 1;2 | NUMERIC | This field contains the interest amount of the event if applicable. Some events, such as comment type events, do not have a dollar amount associated with the event. | ||
| 1.03 | administrative | 1;3 | NUMERIC | This field contains the administrative amount of the event if applicable. Some events, such as comment type events, do not have a dollar amount associated with the event. | ||
| 1.04 | court amount | 1;4 | NUMERIC | This field contains the court cost amount of the event if applicable. Some events, such as comment type events, do not have a dollar amount associated with the event. | ||
| 1.05 | marshal amount | 1;5 | NUMERIC | This field contains the marshal cost amount of the event if applicable. Some events, such as comment type events, do not have a dollar amount associated with the event. | ||
| 2.01 | comment | 2;0 | WORD-PROCESSING | This field gives the user the ability to give expanded comments for an event or the reason the event occurred or to better describe the event. For example, if a patient called on the phone, an event could be logged to describe the call and what was discussed with the patient. | ||
| 4.01 | brief comment(+) | 4;1 | FREE TEXT | A brief comment may exist for certain types of events that can be entered by the user. A brief comment would consist of a short summary to better describe the reason for the event. | ||
| 4.02 | follow-up date | 4;2 | DATE-TIME | AE | Comment type transactions that are entered by the user can have an optional follow-up date. The follow-up date will allow the AR package to remind the user, via a nightly report, to take some action based on the event. For example, if a patient calls and needs information that is not readily available, a user can enter as a comment with a follow-up date as a 'reminder' to return the information to the patient. | |
| 5.01 | bill number | 5;1 | POINTER | 430 | If the event type is related to a bill in the Accounts Receivable file, then the bill number will be stored in this field. For now, the only events that will contain a bill are notification type events. | |
| 5.02 | notification number | 5;2 | SET OF CODES | 1:FIRST 2:SECOND 3:THIRD 4:LAST | This field is used when a notification is sent to a debtor. A notification is either a patient statement, UB bill to insurance company, or follow-up letter to Vendors, Institutions, and persons. This field will represent the number of times a notification was sent. If the notification being sent is over three, then this field will be set to four. | |
| 6.01 | ccpc statement date | 6;1 | DATE-TIME | This is the date of the STATEMENT on the sttement from CCPC in Austin. |
Not Referenced