Coordination of Benefits (COB) Detective

The Problem

Members with coverage under multiple plans (e.g., employee plan + spouse's plan, Medicare + Medicaid, Medicaid + commercial) create overpayment risk: if both payers pay without knowing about the other, total payment can exceed the member's actual expense, creating duplicate payments the payer must recover. COB (Coordination of Benefits) rules dictate payment order (primary/secondary) and require coordination. Payers must identify members with other coverage, verify COB status, apply COB rules at claims adjudication, and recover overpayments. Manual COB identification relies on member disclosure or chance discovery; proactive identification requires data matching across multiple sources.

Data Requirements

Data Sources:

• Claims data (837/835 with member ID, service dates, amounts) , for pattern analysis and overpayment identification
• Member enrollment data , demographics, effective dates, employer group affiliation
• Employer group records (large self-funded employers) , member coverage under multiple employer plans
• Medicare/Medicaid crossover files , members with dual Medicare/Medicaid enrollment
• Other carrier inquiry system (via X12 270/271) , COB verification responses
• COB rule matrix , primary/secondary determination rules by coverage type
• Internal COB policy , payer's specific COB handling procedures

Data Classification:

• Public: None typically
• Internal Structured: Claims data, member enrollment, employer records, COB rule matrix
• Internal Unstructured: COB correspondence, prior recovery attempts
• External Third-Party: Other carrier COB verification responses (via EDI)
• Sensitive/Regulated: All claims and enrollment data is PHI; COB discovery and recovery are sensitive and subject to HIPAA regulations

Data Quality Requirements:

• Timeliness: Claims should be analyzed for COB opportunity within 30 to 60 days of submission; COB inquiries should receive responses within 20 days (X12 standard).
• Completeness: Claims must have accurate member ID, service dates, and amounts; employer records should cover 90%+ of employed members; Medicare/Medicaid crossover files updated monthly.
• Accuracy: Member ID must be consistent across carriers; coverage dates must be accurate; amounts must be precise for recovery calculation.

Integration Complexity: Medium , Requires claims data analysis (standard payer capability), access to employer records (internal), Medicare/Medicaid crossover files (CMS bulk download), and COB inquiry system (X12 270/271 or carrier-specific APIs). EDI integration is standard for payers. Main complexity is rule engine (COB rules vary by coverage type and state).

Regulatory Alignment

• HIPAA COB Rules (45 CFR § 162.411): Health plans must comply with COB standards; coordination must not delay payment beyond CMS timely filing rules.
• CMS Prompt Payment Rules: COB inquiry and coordination must not delay primary plan payment.
• State COB Laws: Some states have specific COB requirements; payer must comply with state rules.

Comparable Implementations

• Optum COB Management Solutions , Industry standard for COB operations
• X12 270/271 EDI Standard , Authoritative reference for COB inquiry/verification standard
• CMS COB Guidance , CMS guidance on coordination of benefits