Billing Tx Charge Detail Table - PM
The billing_tx_charge_detail table is populated when a service is entered in any myAvatar service entry screen or method. There can be multiple records per client, per service if liability is distributed to multiple guarantors.
If no financial eligibility is on file for a client, one record per service will be created in this table with the guarantor value of "NTST Default Guarantor", GUARANTOR_ID "99999".
| Field | Data Type | Composite Index Field | Foreign Key | Foreign Table | Comments |
|---|---|---|---|---|---|
| auth_number_calc | No | No | This is the authorization number from the Managed Care Authorization form that is used to determine used dollars, no auth was valid at the time the service was closed, this field will be blank. | ||
| authorization_number | No | No | Authorization number. | ||
| bep_stuff | No | No | This will return "BEP" followed by the episode number for the client. | ||
| billing_units | No | No | |||
| CLAIM_NUMBER | No | No | Populated if service has been claimed. | ||
| claimed_auth_number | No | No | Claimed Authorization Number | ||
| claimed_CER_uniqueid | No | No | This is the unique ID associated with the claimed authorization. | ||
| date_of_service | Date | No | No | User entered date value for date service was rendered. | |
| date_of_svc_close | Date | No | No | ||
| EPISODE_NUMBER | Integer | No | No | Sequential numeric field generated by myAvatar for each admission. | |
| FACILITY | Integer | No | No | Root system code value (numeric) | |
| GUARANTOR_ID | String | No | Yes | billing_guar_table | Unique identifier for guarantor where liability has been distributed. |
| guarantor_liability | No | Amount guarantor is responsible for. A record will not be created in this table if a guarantor within the client's financial eligibility does not have any liability distributed to it | |||
| guarantor_total_payments | Integer | No | No | Calculated value of all payments, adjustments, and transfers for the guarantor for detail record | |
| ID | String | Yes | Composite index consisting of FACILTY || PATID || JOIN_TO_ fields | ||
| JOIN_TO_CER_uniqueid | String | No | Yes | history_managed_care_auths | This is the unique ID associated with the authorization |
| JOIN_TO_CER_unq_calc | String | No | Yes | This is the link to the authorization that is used to determine used dollars, units, and visits and will become locked once the service is closed. If no auth was valid at the time the service was closed, this field will be blank. | |
| JOIN_TO_PAYMENT_HISTORY_ | String | No | Yes | billing_pay_adj_history | Unique payment record identifier consisting of the letter "B", julian date, decimal point, and three digit counter, i.e. B58074.001 |
| JOIN_TO_TX_HISTORY | String | Unique transaction identifier consisting of julian date, decimal point, and three digit counter, i.e. 58074.001. This field should always be linked when linking billing_tx_history to billing_tx_charge_detail tables | |||
| 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 |
| re_bill_claim_number | String | No | Yes | billing_rebill_tx_assign | This will show the last claim under which this service was re-billed to this guarantor |
| re_bill_status | String | No | This will show the Claim Submission Reason Code (such as "6", "7" or "8") associated with the re_bill_claim_number | ||
| re_bill_status_value | String | No | This will show the Claim Submission Reason Code (such as "Corrected", "Replacement" or "Void") associated with the re_bill_claim_number | ||
| remaining_balance | Numeric | No | |||
| service_status_code | String | No | No | Flag to indicate whether a charge has been closed, choices are O or C. The default is O indicating changes to a client's financial eligibility could affect this record's liability distribution | |
| service_status_value | String | No | No | ||
| slide_fee_plan_level | String | No | No | ||
| slide_fee_scale_val_code | String | No | No | ||
| slide_fee_scale_val_value | String | No | No | ||
| sliding_fee_coverage | String | No | No | ||
| split_units | |||||
| transfer_to_guarantor_code | String | No | No | The 'Guarantor_ID' the user selected in the remittance or payment form to transfer liability to | |
| transfer_to_guarantor_value | String | No | No | Name of guarantor for which the charge was transferred to. This field will only be populated if the charge was transferred to another guarantor. | |
| transferred_service | String | No | No | Indicator to identify whether the record was created via transfer of liability or not. Valid values are "TRA" for the record to which the liability was transferred to and null for a record where liability has not been transferred which is default | |
| user_row_access_code | String | No | No | 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_accounting_period | String | No | No | Populated with MM/YYYY where MM is the last day of the month for the accounting period that the payment record is associated | |
| v_claim_date | No | No | date of claim if service has been closed and claimed | ||
| v_client_name | String | No | No | Name of client | |
| v_duration | No | No | duration (minutes) of service if the service code was defined as a user defined time duration | ||
| v_location_code | String | No | No | place of service code | |
| v_modifiers | String | No | No | ||
| v_program_of_visit_code | String | No | Yes | table_program_definition | Populated with program code of the episode for which the service was filed |
| v_program_of_visit_value | String | No | No | ||
| v_program_X_rrg_code | String | No | No | ||
| v_program_X_rrg_value | String | No | No | ||
| v_PROVIDER_ID | String | No | Yes | staff_current_demographics | ID number of staff member who provided the service |
| v_PROVIDER_NAME | String | No | No | Name of staff member who provided the service | |
| v_SERVICE_CODE | String | No | Yes | billing_tx_master_table | Service code |
| v_service_value | String | No | No | Description of service |