Clarification on claim cancellation linkage and deduplication in BCDA v3
Arjun subramaniyan
Hi Team,
As we evaluate BCDA APIs for future use in population health analytics, we’d appreciate guidance on how BCDA v3 handles ambiguous claim cancellation relationships, particularly for fully adjudicated MSSP claims.
Section 5.3.2 of the CCLF Information Packet describes an example where cancellation claim #6 could cancel either claim #2 or #5. The net expenditure remains correct because both candidate claims have zero payment. However, if their diagnoses, procedures, units, or other clinical attributes differ, selecting the wrong surviving claim could affect clinical and utilization analytics even though financial totals reconcile.
The BFD v3 deduplication guidance describes using CLM-CNTL-NUM and prior control numbers in ExplanationOfBenefit.related, while acknowledging limitations when intermediate versions are missing.
Could you share a worked example, ideally sample EOB JSON with the expected surviving records, illustrating:
Resolution: Does BFD have authoritative upstream linkage that resolves this CCLF ambiguity, or can it remain in BCDA v3?
Representation: Which identifiers, relationships, and status fields distinguish canceled, superseded, and surviving claims?
Incomplete linkage: What should consumers do when intermediate versions are unavailable or multiple candidates remain?
Clinical attributes: How should consumers determine which diagnoses, procedures, and service details to retain or remove in those cases?
We understand that deduplication across partially and fully adjudicated sources is a separate concern. Here, we’re specifically trying to understand cancellation and replacement handling within fully adjudicated claims so we can consume BCDA data correctly.
Thank you!