MyTherapyWizard Book demo
Insurance, Private-Pay & Contract Billing TEAMS

Dual coverage, billed automatically.

Coordination of benefits and secondary insurance billing for therapy practices. Coordination of benefits logic for dual-coverage clients. Automatic secondary claim generation after primary adjudication.

Watch video Book a demo →
Feature walkthrough

COB & Secondary Insurance, product walkthrough

VIDEO EMBED · REPLACE WITH <iframe>

Overview

Coordination of benefits is where most therapy billing systems quietly lose money. MyTherapyWizard detects secondary coverage at eligibility time, classifies it as COB-IN or COB-OON based on the org's in-network list, and supports crossover claim submission from the same workflow as the primary.

When eligibility returns a secondary payer for a patient, MyTherapyWizard cross-references the secondary payer against the org_payers table, the org's configured in-network payer list. If the secondary is in-network, the flag is COB-IN. If not, COB-OON. Both flag types require admin review before billing; neither triggers automatic action. Admin can apply service stop or hold directly from a COB flag row. Default COB handling (e.g., 'always flag COB-OON for manual review before billing') is configurable per org.

For COB-IN patients, after the primary ERA is posted, MyTherapyWizard generates and submits a secondary claim to ClaimMD with crossover_id populated from the primary claim. No manual rebuild of the 1500 form, no separate portal login. COB flags surface in the Needs Action tab alongside auth alerts and unsigned notes, same flag architecture, same review workflow.

See it in action

Product screens, workflow diagrams, and example outputs. Replace each slot with a real screenshot or illustration.

IMG 01 · HEROPrimary product shot
IMG 02Workflow detail
IMG 03Output example
IMG 04Data / chart view
IMG 05Mobile / tablet view
How it works

Under the hood.

The technical architecture, API integration points, and data model that make this feature work the way it does.

01

org_payers table drives in-network classification.

org_id, payer_id, in_network boolean. Populated during org setup. After every eligibility response, MyTherapyWizard checks the returned secondary payer against this table. Flag type COB_IN or COB_OON is written to the flag record.

02

Secondary claim submission with crossover_id from primary.

After the primary ERA is posted, admin confirms patient responsibility and initiates the secondary. MyTherapyWizard submits to ClaimMD /services/upload/ with crossover_id populated from the primary claim, standard X12 837P crossover semantics.

03

Same flag architecture as ELIG_CHANGE and service stop.

COB_IN and COB_OON flags use the same immutable, timestamped architecture as eligibility-change and service-stop flags. Admin creates a new action to override, originals are never edited.

04

Default COB handling configurable per org.

Org settings include COB behavior preferences (e.g., 'always flag COB-OON for manual review before billing'). Respected by the Needs Action queue and the billing workflow.

Why it matters

01

Stop leaving secondary coverage on the table.

COB-IN flagged automatically at eligibility. Crossover claim submitted to ClaimMD after primary posts. Secondary reimbursement collected on claims that would otherwise be adjusted to patient responsibility.

02

COB-OON review gates billing.

Out-of-network secondary payers flag for manual review before the primary even submits, so admin can price the service correctly or initiate a conversation with the family.

03

Service stops directly from the COB flag row.

If secondary coverage changes mid-episode, admin can Stop, Hold, or mark Insurance Change from the flag. Propagates to the therapist worklist immediately.

See cob & secondary insurance inside MyTherapyWizard.

Book a 30-minute walkthrough with our clinical team. We will show the exact workflow for your discipline and caseload.