How can I verify what was electronically sent on a claim to the payer? (CollaborateMD)

  • Updated

Issue

According to the billing option settings, the billing provider does not show as it’s following the override on which billing provider needs to go out. How can we verify what was electronically sent on each Loop and Segment?

Environment

CollaborateMD

Resolution

You can verify what information was electronically sent on a claim to the payer from CMD from the claim or the claim tracker.

Note: You will need to confirm with the payer which loop and segment the information should be on. The clearinghouse is unable to verify this information. 

From the Claim

  1. Go to the Claim tab on the left-hand side of your screen.
  2. Select the Claim tab again. 
  3. Select More at the top. 
  4. Select Preview Electronic Claim to display the ANSI file for that specific claim. 

From Claim Tracker

  1. Go to the Claim tab, and then select Claim Tracker.
  2. At the top of the screen, select the Download Reports drop-down and then select Claim Files (837).

  3. Use the filters to help locate the claim by search. 
    • TCN: This field is the related number you can find when opening a specific claim on Claim Tracker. See example: 
    • Claim #: The claim number for the actual claim you would like to search for. 
    • Patient: If you would like to search for a specific patient to pull up all of their ANSI files. 
    • Payer ID: If you're searching for a specific ANSI file based on payer ID.
    • Payers: If you want to search based on your payers list.
    • Payer Type: If you want to search based on your payer types.
    • Billing Providers: If you want to search for a specific Billing Provider from your list.
    • Rendering Providers: If you want to search for a specific Rendering Provider from your list.
    • Facilities: If you want to search for specific Facilities from your list.
  4. Select the checkbox for the file you want to download and click Download Claim Files (837).

Was this article helpful?

0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.