RXNT Billing Export Guide

Getting Started

If your organization is interested in an ongoing export of your RXNT billing data, notify your RXNT account representative of your interest and provide them with the email address you will use to access your data. 

Note: The email address must be a Gmail or Gmail-based email address (Google Account) as the ongoing export will be provided through a secure web link hosted by Google. The email address does not need to be your primary email address. 

Access Your Data

Once we receive your email address, a web link will be provided to you so you can access the exports. To access the data associated with the URL, you will need to log into the Gmail account for the email address provided to RXNT. Alternatively, you will be prompted to sign in to the Gmail account associated with the email address provided to RXNT if you are logged out of all Gmail accounts prior to clicking on the URL.

Your export file will be updated daily at 12:00a ET, 8:00a ET, and 3:00p ET. The exports will be provided in .csv format and will contain all records (not simply net new records). 

Note: If you prefer to access the data via code, please notify your RXNT account representative. They will schedule a technical consultation to assess the feasibility of this option for your organization. 

Data Elements

The following data elements will be available in the export: 

  • adjustment_codes
  • adjustment_codes_ins
  • admission_date
  • admission_hour
  • admission_source
  • admission_type
  • allowed_amount
  • anesthesia_end_hour
  • anesthesia_procedure
  • anesthesia_start_hour
  • attending_NPI
  • attending_provider
  • attending_provider_first_name
  • attending_provider_last_name
  • attending_provider_middle_initial
  • batch_date
  • billing_event_type
  • billing_provider
  • billing_provider_entity_name
  • billing_provider_first_name
  • billing_provider_last_name
  • billing_provider_npi
  • case_description
  • case_id
  • case_name
  • case_prior_authorization_code
  • case_type
  • charge_amount
  • charge_created_by
  • charge_created_date
  • charge_is_self_pay
  • charge_type
  • claim_adjustment_reason
  • claim_external_id
  • claim_form_type
  • claim_form_type_code
  • claim_id
  • claim_priority
  • claim_sent_date
  • claim_status
  • claim_status_date
  • claim_status_id
  • claim_validation_status
  • co_insurance_amount
  • co_payment_amount
  • corporate_company_id
  • CPT_code_description
  • created_by
  • created_by_login_id
  • deductible_amount
  • disallowed_amount
  • discharge_hour
  • discharge_status
  • display_encounter_id
  • doctor_company_id
  • doctor_company_name
  • dx_A
  • dx_B
  • dx_C
  • dx_D
  • encounter_charge_id
  • encounter_created_date
  • encounter_detail_charge_id
  • encounter_detail_id
  • encounter_detail_status_code
  • encounter_fee_schedule_name
  • encounter_icd_type
  • encounter_id
  • encounter_status
  • EPSDT
  • EPSDT_condition_indicator
  • era_payment_claim_status_code_id
  • expected_rate
  • external_encounter_id
  • external_payment_id
  • external_reference_encounter_id
  • financial_class_active
  • financial_class_active_responsible_party
  • financial_class_name
  • financial_class_name_responsible_party
  • financial_class_payer
  • financial_class_responsible_party_name
  • health_insurance_type_name
  • inactivated_by
  • inactivated_date
  • initial_billed_date
  • insurance_encounter_detail_payment_id
  • insurance_misc_payment_id
  • is_assignment_accepted
  • is_denial
  • is_posted
  • is_unsettled_encounter
  • last_claim_status
  • leave_open
  • line_item_EMG
  • line_item_EPSDT
  • line_item_noncovered_charge
  • line_item_payer_electronic_id
  • line_item_payer_group_number
  • line_item_payer_id
  • line_item_payer_phone
  • line_item_payment_responsible_party
  • line_item_place_of_service
  • line_item_purchase_service_provider
  • line_item_referring_provider
  • line_item_rendering_provider
  • line_item_res_party_type
  • line_item_responsible_payer_policy_number
  • line_item_service_date
  • line_item_service_to_date
  • line_item_status
  • line_of_business
  • lis_patientid
  • M1
  • M2
  • M3
  • M4
  • master_case_prior_authorization_todate
  • master_cpt_code
  • modified_by
  • modified_date
  • noof_visits
  • operating_physician
  • operating_physician_npi
  • other_operating_physician
  • other_operating_physician_npi
  • paid_by
  • patient
  • patient_cell_phone
  • patient_chart_number
  • patient_city
  • patient_dob
  • patient_encounter_detail_payment_id
  • patient_encounter_misc_payment_id
  • patient_first_name
  • patient_fund_detail_id
  • patient_gender
  • patient_gender
  • patient_guarantor_pat_report
  • patient_home_phone
  • patient_id
  • patient_last_name
  • patient_middle_initial
  • patient_other_phone
  • patient_responsibility_amount
  • patient_state
  • patient_street_address_1
  • patient_street_address_2
  • patient_type
  • patient_work_phone
  • patient_zipcode
  • payer_electronic_id
  • payer_group_number
  • payer_id
  • payer_name
  • payer_phone
  • payer_policy_number
  • payment_amount
  • payment_created_by
  • payment_created_by_login_id
  • payment_created_date
  • payment_date
  • payment_id
  • payment_method
  • payment_patient_id
  • payment_reference
  • payment_responsible_party
  • payment_responsible_party_id
  • payment_transaction_code
  • penalty
  • person_relationship
  • place_of_service
  • posted_date
  • primary_insurance_group_number
  • primary_insurance_name
  • primary_insurance_phone
  • primary_insurance_policy_number
  • primary_responsible_payer
  • prior_authorization_number
  • procedure_code
  • procedure_code_id
  • procedure_name
  • ready_to_bill_date
  • reason_code
  • referring_NPI
  • referring_provider
  • referring_provider_first_name
  • referring_provider_last_name
  • referring_provider_middle_initial
  • remaining_visits
  • rendering_provider
  • rendering_provider_ein
  • rendering_provider_entity_name
  • rendering_provider_first_name
  • rendering_provider_last_name
  • rendering_provider_npi
  • responsible_party_code
  • responsible_party_type_id
  • responsible_payer
  • resubmission_code_type_id
  • revenue_code
  • scheduling_npi
  • scheduling_provider
  • scheduling_provider_first_name
  • scheduling_provider_last_name
  • scheduling_provider_middle_initial
  • secondary_insurance_name
  • service_date_from
  • service_date_to
  • service_facility_location_id
  • service_facility_location_id_external
  • supervising_NPI
  • supervising_physician
  • supervising_provider_first_name
  • supervising_provider_last_name
  • supervising_provider_middle_initial
  • tertiary_insurance_name
  • total_adjustment_amount
  • TotalCharges
  • transaction_type_code
  • UB04_location_type
  • unit_charge_amount
  • units
  • writeoff_amount

If you are interested in RXNT exposing further details in the export, submit an idea to RXNT via email at ideas-PM-rxnt@mailer.aha.io with the subject “RXNT Daily Export” and the field name(s) you’d like to see in the export. These ideas will be considered as they are received and prioritized based on the overall demand for the additional fields. 

Leverage Your Data

Billing Event Type

The column for Billing Event Type describes the type of data found in each row of the data export. There are 7 possible values that fall into two types of rows, payment rows and charge rows. 

Payment Rows:

When building reports or calculations for payments, use payment rows. You can combine these different payment row types into a single report or calculation as needed (or choose only one payment row type if required). For the charge data related to each payment row, you will find the relevant charge data in the columns of the payment row - this can be helpful for identifying payment/charge relationships but isn’t recommended for charge-related calculations. 

  • Insurance Payment
  • Misc Insurance Payment
  • Unapplied Insurance Payment
  • Patient Payment
  • Misc Patient Payment
  • Unapplied Patient Payment
  • Patient Fund Payment

Charge Rows:

When building reports or calculations for charge-related inquiries, use only charge rows. Payment rows will not provide accurate overall charge reporting, because charges without an associated payment will not appear in the payment rows. Also, attempting to combine Charge and Payment row types in the same reporting will provide incorrect charge calculations - charges that have received a corresponding payment will appear twice.

  • Billed Charge
  • Unbilled Charge
Was this article helpful?
0 out of 1 found this helpful