Therabill Support Specialist
- Total activity 1763
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 1
- Subscriptions 883
Activity overview
Latest activity by Therabill Support Specialist-
Therabill Support Specialist created an article,
Submitter Number does not meet format restrictions for this payer. It must start with State Code WA followed by 5 or 6 numbers.
This rejection occurs when a claim is submitted to Medicare Washington but did not provide WebPT Therabill with the correct Submitter ID when you received your approval. To Resolve You will need t...
-
Therabill Support Specialist created an article,
CLAIM FREQUENCY CODE: INVALID; MUST BE A VALID FREQUENCY CODE [6]
This error occurs when using the Claim Frequency Code 6 for the payer. The payer claim frequency code is a code on the electronic (EDI) claim that indicates if the claim is an initial submission, ...
-
Therabill Support Specialist created an article,
Category: Acknowledgement/Returned as unprocessable claim The Claim/Encounter has been rejected and has not been entered into the adjudication system Status: Returned to Entity Entity: Payer^^^\\\\R^^R SUBMIT WITH SSN, EDI PI(10) OR MVI ICN (17)^^^
This rejection from the Insurance payer indicates the patient information in the chart does not match the patient/client information the payer has on record or the claim may have been sent to the w...
-
Therabill Support Specialist created an article,
Therabill Onboarding Agenda
Therabill 60 Day Onboarding Period for Integrated Members (8-Week Agenda) The below timeline is for reference only to give you an idea of expected onboarding timelines and topics. Members may gradu...
-
Therabill Support Specialist created an article,
SERVICE LINE ADJUDICATION OR PAYMENT DATE: INVALID; MUST BE GREATER THAN OR EQUAL TO ADJUSTMENT REASON CODE EFFECTIVE DATE AND MUST BE LESS THAN OR EQUAL TO ADJUSTMENT REASON CODE TERM DATE [YYYYMMDD]
This rejection of a secondary insurance claim occurs during the payment posting process when the clinic applies an invalid Remark code. To Resolve Follow the steps below to delete the adjustment th...
-
Therabill Support Specialist created an article,
PAYER RESPONSIBILITY SEQUENCE NUMBER: INVALID; WITHIN A GIVEN CLAIM, VALUES CANNOT OCCUR MORE THAN ONCE
This error occurs when more than one payment is submitted on a claim session to a secondary payer. Secondary payer claims should only have one payment and one adjustment from the primary payer. ...
-
Therabill Support Specialist created an article,
Element NM104 (Name First) is present. This Element is marked as \'Excluded\' and therefore must not be present in the data. Segment NM1 is defined in the guideline at position 2500. Invalid data: xxxx
This error occurs on Medicare claims for one of the following reasons: The Insured demographic information does not list SELF as the Relationship to Patient. When Medicare is the payer, the insur...
-
Therabill Support Specialist created an article,
Element NM102 (Entity Type Qualifier) does not contain a valid identification code: \'1\' is not allowed. Segment NM1 is defined in the guideline at position 2500. Invalid data: 1
This error occurs on Medicare claims for one of the following reasons: The Insured demographic information does not list SELF as the Relationship to Patient. When Medicare is the payer, the insur...
-
Therabill Support Specialist created an article,
Element NM103 (Name Last or Organization Name) is missing. This Element\'s user option is \'Must Use\'. Segment NM1 is defined in the guideline at position 0150
This error occurs on Medicare claims for one of the following reasons: The Insured demographic information does not list SELF as the Relationship to Patient. When Medicare is the payer, the insu...
-
Therabill Support Specialist created an article,
Value of element SBR01 has been already used in loops 2000B/2300. Elements SBR01 are expected to be different from SBR01 specified in loop 2000B and to have unique values within loop 2300 excluding \'U\' value. Segment SBR is defined in the guideline at p
Value of element SBR01 has been already used in loops 2000B/2300. Elements SBR01 are expected to be different from SBR01 specified in loop 2000B and to have unique values within loop 2300 excluding...