Billing Pay Adjustment History Table - PM
The billing_pay_adj_history table is populated for each and every time a payment is entered for a service of a client manually or via 835 processing.
Records can also be added to the table if guarantor liability is transferred from one guarantor to another.
| Field | Data Type | Composite Index field | Foreign Key | Foreign Table | Comments |
|---|---|---|---|---|---|
| adjust_code_code | String | ||||
| adjust_code_value | String | ||||
| automatic_receipt_number | String | ||||
| check_number | String | ||||
| CLAIM_NUMBER | String | Populated if the service has been claimed | |||
| contractual_write_off | String | No | Yes | billing_posting_codes | Will indicate if the payment type code is a contractual write off code |
| credit_card_token | String | ||||
| data_entry_by | String | The 'User Description' of the user that last updated the row | |||
| data_entry_by_option | String | The 'User Description' of the user that last updated the row when the User ID is defined with Prompt for Username at Form Entry=Yes | |||
| data_entry_date | Date | ||||
| data_entry_source | String | ||||
| data_entry_time | String | ||||
| data_entry_user_id | String | Yes | RADplus_users | ||
| data_entry_user_name | String | ||||
| date_of_payment | Date | ||||
| date_of_receipt | Date | ||||
| date_of_service | Date | No | Yes | billing_tx_history | |
| device_name | String | No | The name of the credit card device used to process the credit card payment. | ||
| EPISODE_NUMBER | Integer | ||||
| FACILITY | Integer | Yes | |||
| group_code_code | String | ||||
| group_code_value | String | ||||
| GUARANTOR_ID | String | No | Yes | billing_guar_table | |
| GUARANTOR_ID_transfer_to | String | billing_guar_table | Guarantor ID of the destination guarantor when payment type is transfer. Note, if transfer code was configured as liability distribution open, it most likeley will be the primary guarantor | ||
| ID | String | ||||
| JOIN_TO_BILLING_TX_CHARGE | String | No | Yes | billing_tx_charge_detail | An additional unique ID for the service which serves as a pointer to the unique record ID in billing_tx_charge_detail |
| JOIN_TO_PAYMENT_HISTORY | String | Yes | No | unique identifier transaction field of record within billing_pay_adj_history | |
| JOIN_TO_TX_HISTORY | String | No | Yes | billing_tx_history | The unique ID assigned to the specific Client's service. Will be the date of service in Julian date format followed by a counter starting with ".001". |
| JOIN_TO_TX_HISTORY_tra_to | String | No | Yes | billing_tx_history | unique identifier transaction field of record within billing_tx_history where liability was transferred to from a payment record where the payment type is transfer |
| merchant_id | String | No | The merchant ID (MID) associated with the credit card payment. | ||
| option_desc | String | The name of the remittance or payment form that last updated the row | |||
| option_id | String | No | Yes | RADplus_option_info | The unique ID of the remittance or payment form that last updated the row |
| ORIG_JOIN_TO_TX_HISTORY | String | No | Yes | billing_tx_history | Unique transaction identifier consisting of julian date, decimal point, and three digit counter, i.e. 58074.001. This field will only be populated if the record was transferred |
| PATID | String | Yes | Yes | patient_current_demographics | Unqiue client identifier |
| payment_amount | Numeric | ||||
| payment_location_code | String | ||||
| payment_location_value | String | ||||
| payment_type_code | String | Yes | billing_posting_codes | ||
| payment_type_value | String | ||||
| posting_comments | String | ||||
| receipt_reversed | String | Will indicate if the receipt was reversed | |||
| reciept_number | String | ||||
| return_ref_number | String | The returned reference number for a credit card or ACH transaction. | |||
| system_code | String | System Code (user defined or sub system code) the user was logged in as when filing a payment/adjustment | |||
| type_of_payment | String | ||||
| unique_row_id2 | String | The unique ID assigned to the posting for each service. Will be "CR" followed by the posting date (date of payment) | |||
| user_row_access_code | String | Flag to indicate whether or not user who is accessing report has access to a row of data within the billing_tx_history table based on whether or not the row of data is associated with a program that is associated with a root or subsystem code the user is currently logged into when accessing the report. Valid values are 0 (user does not have access to row of data), 1 (user has access to row of data and is currently logged into the root/subsystem code associated with the program), 2 (user has access to row of data and is currently NOT logged into the root/subsystem code associated with the program). This functionality does not take affect unless a record selection within the report invokes this field such as user_row_access_code=1 | |||
| v_client_name | String | ||||
| v_program_of_service_code | String | ||||
| v_program_of_service_value | String | ||||
| v_program_X_RRG_code | String | ||||
| v_program_X_RRG_value | String | ||||
| v_PROVIDER_ID | String | Yes | staff_current_demographics | Unique identifer of the staff person or practitioner who performed the service | |
| v_service_code | String | Yes | billing_tx_master_table | Service code of the service | |
| write_off_by_liab_dist | String | ||||