CARC 22the denial code for care that may be covered by another payer per COB
Primary vs secondaryclaims must go to the correct payer first or they reject
MSP rulesMedicare Secondary Payer rules decide order when Medicare is involved

Coordination of benefits decides which plan pays first when a patient has more than one, and getting it wrong is a common, avoidable denial. When a payer believes another plan is primary, it rejects the claim, often with CARC 22. The fix is determining the correct order of liability and getting the COB record updated. Flexbone does both.

What COB is and why claims deny on it

Coordination of benefits is the set of rules that determines the order in which multiple plans pay: which is primary, which is secondary. Patients with a spouse's plan, with both commercial and Medicare or Medicaid, or with retained coverage after a job change commonly have more than one plan. When a claim goes to a payer that believes it is not primary, it denies, frequently with CARC 22, care may be covered by another payer per coordination of benefits, or a related COB code. These denials are avoidable when the order is known and the COB record is current.

Complimentary Flexbone audit

Get an outside read on your coordination of benefits workflow

In 30 minutes we map your current volume, the payers and systems involved, where staff time goes, and the highest-ROI calls and follow-ups Flexbone can take off your team first, scoped to the work you actually run.

Book an audit →

Updating COB with payers and Medicare

The resolution is usually a phone call. The patient's COB record at the payer is stale or missing, and someone has to call to confirm the other coverage, establish the correct primary, and update the record. When Medicare is involved, Medicare Secondary Payer rules govern the order, and the COB update may run through the Benefits Coordination and Recovery Center. Flexbone places these calls, confirms the order of liability, gets the COB record updated, and captures the reference number so the corrected claim pays.

How Flexbone runs coordination of benefits

Flexbone works COB on the front end and the back end. During eligibility, it detects multiple coverages and establishes the likely order so the claim goes to the right payer first. On denials, it works the CARC 22 and related COB rejections: calling the payer, correcting the record, and resubmitting. Results write back to the practice management system, and cases needing patient input, such as confirming other coverage, are routed to staff. The work is scoped to your payers and patient mix.

How Does a Flexbone Deployment Work?

Every deployment starts from the work as your team does it today, not from a product demo. The steps below are the same whether the first agent answers phones, checks eligibility, or files incoming documents.

  1. Audit first, then automate. We listen to a sample of your calls and read the work queues, then agree with your team on which work to automate first. The audit is complimentary.
  2. Forward-deployed engineers map your SOPs. An engineer sits with the staff who do the work and turns your written and unwritten rules into agent logic.
  3. Agents act on your rules, and exceptions go to a person. Each step follows logic built from your SOPs. A case outside those rules, or one the agent is not confident about, goes to your team with the context attached.
  4. Every action leaves a record. A check in a web application saves a screenshot, a call saves a transcript, and results are written back where your team already looks.
  5. Start with one or two agents on the systems you already run. The agents work in your EHR, practice management system, phone system, and the web applications your staff use, as they are configured today, so nothing is migrated or rebuilt.
  6. The same team stays after go-live. We monitor results, tune the agents as payers and workflows change, and add agents as new work is found.

The engagement model is described in more detail in forward-deployed engineering for healthcare contact centers.