# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.01 | name(+) | 0;1 | POINTER | 2 | B | The veteran for whom this master record adjustment is created. |
1 | status(+) | 0;2 | SET OF CODES | P:PENDING TRANSMISSION T:TRANSMITTED | AC | This field identifies whether this master record adjustment is pending transmission to Austin or has already been transmitted. |
2 | pointer to authorization node(+) | 0;3 | NUMERIC | This field contains the internal entry number of the authorization record selected for the veteran. This is needed because master record adjustments are related to specific authorizations. The user does NOT enter this field directly. The data is captured automatically when the user selects the authorization. | ||
3 | type(+) | 0;4 | SET OF CODES | A:ADD R:REINSTATE D:DELETE C:CHANGE | Indicates the type (ie add, change) of master record adjustment this is. | |
4 | date transmitted | 0;5 | DATE-TIME | AD | The date that last master record adjustment for this veteran was transmitted to Austin. | |
5 | auth. from date changed | 0;6 | SET OF CODES | 1:YES 2:NO | This field is used as a flag to indicate that the authorization From Date is being changed by this master record adjustment. If this field is set to yes, the authorization To Date is set to spaces when the transaction is created. An Austin requirement is to change the From Date, the To date must be blank. This field only pertains to a 'Change' type transaction. | |
6 | short term mra | 0;7 | BOOLEAN | Y:yes | This field is used as a flag and relates to outpatient medical reimbursements for a veteran with only a short term authorization. For those reimbursements the system automatically creates a master record adjustment sending the most current data. This field is used to identify that this transaction is only temporary and not to establish a long term master record. |
Not Referenced