Skip to main content

Compile Inbound HL7 Charge Batch File

  1. Last updated
  2. Save as PDF

Compile the charges/credits received via an HL7 inbound interface into a batch of charges.

  • The compile process will create a batch of charges that will include all those transactions in temporary storage whose dates of service falls within the date range specified, inclusive. A transaction can only be included within a single batch. Once included, a transaction will NOT be available for pickup during any subsequent compile process. However, a batch that has only been compiled and not yet posted can be deleted. Once a batch is deleted, all included transactions are returned to temporary storage and so made available for pickup during any subsequent compile process.
  • A credit that is included in the compile process but has a date of service that is past the compile through date will be returned to the charge queue for pickup during a subsequent compile. (This only applies to pharmacy credits that have a date of service that is past the compile through date.)
  • Once a batch has been compiled or posted a report will be launched to display the batch details. There is a separate section in the report for charge/credit errors. It is necessary that an ODBC connection be defined so that the included report can be run through the standard report viewer.
  • In the case of more than one matching charge, a credit will first be applied to a charge with the same service unit amount and date. If there is no such charge, it will then be applied to one with the same service unit amount (any date), and if there is still no such charge, to the one with the closest matching service unit amount (any date).

When working with credits, see the Crediting Process Overview before a final compile is completed.

  1. Go to Avatar PM > HL7 Interface > Charge Processing > Compile Inbound HL7 Charge Batch File.
  2. In the Compile For Which Charge Type field, select the charge type. All charge/credit transactions received via an HL7 inbound interface are categorized by charge type. The specific type is determined by the connection through which the charge/credit is received. 
    Note: A single connection cannot receive charges/credits of more than one type (e.g. it can receive either lab or pharmacy charges/credits but not both).
  3. Use the From and Through Date Of Service fields to limit the compile to those transactions that have an associated date of service that falls within these dates.
  4. In the Add Surcharge To Each Line Item field, select whether or not a surcharge amount should be added to every charge.
    NCPDP claims can add the surcharge amount within the Compile/Edit/Post/Unpost Roll-Up Services Worklist form.
    • If Yes, enter the amount in the Surcharge Amount field.
  5. In the Update Fee From Service Fee Table field, select whether or not the fee associated with a charge will be calculated based on the myAvatar service fee table definition. If No, the fee associated with the charge will be the amount specified by the ancillary system.
  6. In the File Charges Using Default Service Code field, select whether or not all charges should be filed under a single generic service code.
    • If No, all charges will be filed using the service code specified by the ancillary system.
    • If Yes, select a code in the Default Service Code field. This is the single generic service code under which all charges will be filed.
  7. Click Process.
► SQL Tables
  • HL7.hl7_i_charges
  • HL7.hl7_i_chg_errors
  • HL7.hl7_i_credits
  • HL7.hl7_i_pharm_supp_data
► See Also