Creating secondary claims

Menu location: Claims menu, Secondary Bill Claims

Toolbar button: Secondary Bill

Creating secondary claims is usually automated. When needed, you can manually create a secondary/tertiary claim while viewing a paid claim in the system, or you can secondary bill a group of released claims through the Claims menu, Secondary Bill Claims option.

When secondary claims are created, they are saved as new, unreleased claims. The payer on the secondary claim is the payer associated with the payer indicator at the top of the claim in the status bar.

A local status code is added to the secondary claim that shows its source and a status code is added to the parent claim to show that a secondary claim has been created from it. You can use these codes to find secondary and tertiary claims in the system through the Claim filter.

Caution

Unless you set them differently, new secondary claims are unreleased claims. If they contain errors, they will not be sent to the payer until you have opened, validated, and fixed any payer errors that validation reports.

 

Tips

 

To locate claims by local status codes, in filter select Status: Local Code from one of the user-selectable field lists and enter one or more of these codes:

Code Description
150 Claim secondary billed manually
151 Claim secondary billed from R/A (835)
152 Claim secondary billed from AiiClosed Advanced Inquiry Interface (Aii) is the program that queries Medicare for early adjudication results. Largely replaced by Medicare Direct Entry (MDE). (or Direct Entry)
153 Secondary bill - created manually
851 Secondary bill - created from R/A (835)
855 Forwarded to Additional Payer(s)
998 Secondary bill - created from Aii (or Direct Entry)

If you use the toolbar button or menu option to create secondary claims, they may have either the 153 local status code or the 851 local status code. If the system is able to apply secondary billing rules for your site to the new claims, then you will see the 851 code in the History tab. If the system can only use the basic process to force the creation of a secondary claim in order to bypass an issue, then you will see the 153 code in the History tab.

Auto lists and creating secondary claims

Three trigger events in auto list allow you to set up post-creation tasks that are tailored to the type of remit data that generated the secondary claims:

  • Secondary Claims Generated from 835: The auto-list runs immediately after secondary claims are created from payment data in an 835 file.
  • Secondary Claims Generated from Aii: The auto-list runs immediately after secondary claims are created from payment data in an Aii file.
  • Secondary Claims Generated: An auto list triggered by this event runs immediately after secondary claims are created from any remit source. If you currently use an auto list triggered by Secondary Claim Generated and create new auto lists that are triggered by the new remit-source triggers, you should remove the old auto list. Failure to do so will result in two auto lists (the new and the old) running after secondary claims have been created.
Note

The automation of creating secondary claims is set up in Remit Import Options and Secondary Billing.