To track payer claim control numbers across ABA claim versions, record which payer or intermediary assigned each identifier, when it was assigned, which claim version it identifies, and where it appears in status, remittance, correction, void, or appeal artifacts. Keep internal claim IDs, clearinghouse controls, payer controls, authorization numbers, and payment traces in separate fields with explicit links.
Define Imani's payer claim-control-number lineage control
Imani's crosswalk maps identifiers by issuer, purpose, scope, and lifecycle event. A single claim episode can have internal IDs, batch controls, clearinghouse IDs, payer control numbers, corrected-version identifiers, remittance controls, and payment traces. Each remains stable evidence rather than a generic claim number field.
Build the claim identifier crosswalk
Record episode; person; service date; claim version; internal claim and line; batch; interchange and transaction controls; clearinghouse claim ID; payer and product; payer claim control; assigned event and time; original-reference relationship; corrected, replacement, or void version; 276 or 277 status; 277CA; ERA control and payer claim ID; appeal reference; authorization number; TRN; source system; owner; conflict; and closure. Structured fields preserve identity, source, level, version, clock, comparison, access, action, hold, calculation, correction, retest, and closure. Narrative captures clinical meaning, uncertainty, disagreement, family communication, privacy, legal deferral, and the responsible owner's rationale.
Run Imani's workflow
Imani captures identifiers from original artifacts, validates the issuer, and records the edge between versions. She uses payer controls for status and correction only when the route requires them. Conflicting or reused numbers enter review, and no identifier is copied into another role merely to satisfy a field.
Assign decisions to qualified owners
A clearinghouse tracking number is not automatically the payer's claim control. An authorization number does not identify adjudication, and a payment trace does not identify the submitted claim version. Similar-looking values must retain their source and purpose.
Work through Imani's fictional example
Imani reviews 24 fictional episodes. Sixteen have complete internal, clearinghouse, payer, status, remittance, and version links. Two substitute authorization IDs, one reuses a batch number, one attaches a remittance to the wrong payer control, one loses the original reference, one has a payer-assigned corrected ID, one lacks issuer evidence, and one uses a payment trace. Six repair. Two stay held. This synthetic cohort tests control logic and arithmetic only. It creates no coding, coverage, clean-claim, authorization, payment, patient-balance, disclosure, appeal, privacy, or legal conclusion for a real person, provider, plan, claim, or remittance.
Calculate Imani's measures
Initial crosswalk readiness is 16 of 24 episodes, or 66.7%. Twenty-two reach verified lineage or documented conflict, or 91.7%. Episodes, versions, issuers, identifiers, artifacts, and payments remain distinct denominators.
Address the main payer claim-control-number lineage risk
A generic claim-number field can overwrite the identifier needed for a correction, status inquiry, or appeal. Reused numbers can also attach another claim's remittance to the wrong account.
Test the claim identifier crosswalk against exceptions
Imani tests clearinghouse ID, payer control, Medicare-style ICN example, corrected payer ID, original reference, authorization number, batch control, remittance control, payment trace, reused number, and wrong issuer. Each fixture retains source version, expected state, actual state, affected unit, safeguard, owner, repair, retest, and disposition. Failed, unknown, and held items remain inside the predeclared cohort.
Document the stop condition
Hold the affected status, correction, void, appeal, or posting action when issuer, scope, version, or relationship of the identifier is unclear. Preserve every source artifact and ask the payer or trading partner for clarification.
Hand off open work with evidence
Imani's handoff includes the identifier dictionary, issuer, version, lifecycle event, crosswalk edges, conflicts, deadlines, and owner. The receiver traces one original and corrected version through status and remittance.
Maintain Imani's control
Imani validates the crosswalk after payer, clearinghouse, billing, remittance, or appeal-system changes. Reused and orphan identifiers become regression fixtures and remain visible until resolved.
Run Imani's independent review
Imani assigns a reviewer who did not build the claim identifier crosswalk. The reviewer reconstructs the payer claim-control-number lineage source, state, calculation, action, and close from retained evidence. Earlier versions, failed tests, unknowns, and holds remain available. Hidden exceptions, unexplained values, overwritten history, missing population, or unauthorized decisions fail review.
Start with the adopted claim and status standards
Current 45 CFR 162.1102 identifies the adopted professional-claim standard. The CMS claims-status page identifies the 276 request and 277 response. Imani still records the actual payer, product, route, transaction version, receiver, and artifact before applying either source to the claim identifier crosswalk.
Keep the Medicare stage example inside Medicare
The March 2026 CMS Medicare claim-status guide distinguishes 999 front-end processing, 277CA claim-level acknowledgment, payer control assignment, clean-claim payment-status timing, and duplicate risk during editing. Imani uses those facts only for the applicable Medicare route; other payers and contracts require their own evidence for payer claim-control-number lineage.
Read remittance codes with their level and context
CMS's Medicare remittance page separates claim, service-line, and provider-level adjustments and explains group codes, CARCs, RARCs, and PLB in Medicare scope. Imani links the code combination to the raw remittance, original claim, payer source, and qualified decision rather than treating one code as a complete outcome.
Use current X12 code-list status
The X12 external-code-list index defines the scopes of CARCs, RARCs, claim status, and related lists. The current CARC list explains why a claim or line was paid differently than billed. The current RARC list separates supplemental remarks from informational alerts. Imani stores these meanings in the claim identifier crosswalk.
Version updates instead of overwriting history
The X12 code-update listing shows a July 1, 2026 update and notes a corrected RARC N922 effective date on August 3, 2026. Imani retains start, modification, and stop dates, source-check time, and historical mappings so an older remittance is evaluated against the relevant code-set state.
Distinguish receipt and correction identifiers
X12 RFI 2099 says 999 acceptance does not necessarily establish carrier receipt date. X12 RFI 2060 explains the payer-control-number requirement for the standard replacement or void path after adjudication and notes that pending routes can differ. Imani preserves transaction, claim, payer, and version identities separately.
Protect payer order and payment data
The CMS coordination-of-benefits page describes the covered-entity COB transaction. HHS payment guidance and minimum-necessary guidance apply only when their HIPAA conditions are met. Imani verifies payer order, entity status, purpose, recipient, role-based access, and the narrow data needed for the payer claim-control-number lineage work.
Keep clinical and compliance authority scoped
The CASP public summary and BACB Ethics Code supply limited clinical and professional context. The OIG GCPG is voluntary and nonbinding. Imani keeps clinical authorship, coding decisions, payer actions, disclosure authority, financial entries, and legal conclusions with their qualified owners throughout the claim identifier crosswalk.
Related resources
- Govern an ABA CARC and RARC Action Matrix.
- Preserve ABA Timely-Filing Evidence Across Claim Actions.
- Reconcile ABA Allowed Amount, Contract Adjustment, and Payment.
- Link Payer Document Requests to the Exact ABA Claim and Deadline.
Sources
- Council of Autism Service Providers, ABA Practice Guidelines Version 3.0 public summary.
- Behavior Analyst Certification Board, Ethics Code for Behavior Analysts.
- Electronic Code of Federal Regulations, 45 CFR 162.1102, standard for health care claims.
- Centers for Medicare and Medicaid Services, Health Care Claims Status.
- Centers for Medicare and Medicaid Services, Checking Medicare Claim Status, March 2026.
- Centers for Medicare and Medicaid Services, Health Care Payment and Remittance Advice.
- X12, External Code Lists.
- X12, Claim Adjustment Reason Codes.
- X12, Remittance Advice Remark Codes.
- X12, Code Updates Listing.
- X12, RFI 2099, 999 Confirming Claim Receipt.
- X12, RFI 2060, Withdrawal or Void Claim and Response.
- Centers for Medicare and Medicaid Services, Coordination of Benefits transaction.
- U.S. Department of Health and Human Services, Uses and Disclosures for Treatment, Payment, and Health Care Operations.
- U.S. Department of Health and Human Services, Minimum Necessary Requirement.
- U.S. Department of Health and Human Services Office of Inspector General, General Compliance Program Guidance.
