To validate payer specific clean claim status for ABA reporting, identify the controlling payer, program, contract, claim type, route, and service or receipt date. Record the source's definition, qualifying event, known defects, required documentation, clock, and exclusions. A transmitted file, 999, clearinghouse acceptance, or 277CA can establish a processing stage while still falling short of universal clean-claim proof.
Define Bella's payer-specific clean-claim status control
Bella uses one evidence row for each claim included in a clean-claim metric. The row states which source creates the classification and the date on which the claim met it. Medicare examples remain Medicare-specific; Medicaid, commercial, Marketplace, and contract definitions receive their own rows.
Build the clean-claim evidence register
Record payer and product; program; contract; claim type and version; service date; submission; receiver; 999; 277CA; payer control; documentation due; defect or development; source definition and effective date; qualifying event; clean date; nonclean reason; reclassification; payment clock; exclusion; owner; evidence link; and final adjudication. 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 Bella's workflow
Bella builds the definition before selecting a reporting cohort. She matches each claim to the source and records whether additional information or external development was required. Claims with unknown status remain visible as unknown instead of being omitted or assumed clean.
Assign decisions to qualified owners
Clean-claim status can affect processing or payment measures under a specific source. It does not establish coverage, medical necessity, accurate coding, prior authorization, adjudication, or payment. Stage acknowledgments retain their own narrower meanings.
Work through Bella's fictional example
Bella reviews 25 fictional claims received during one period. Fifteen meet a documented payer-specific clean definition, five are nonclean because development is required, three are rejected before payer intake, and two lack sufficient evidence. Twenty-three classifications are supported. Two remain unknown. 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 Bella's measures
Among the 20 payer-received claims with supported clean or nonclean classifications, 15 are clean, or 75.0%. The three pre-intake rejects remain visible but stay outside that payer-received denominator. Classification completeness is 23 of all 25 claims, or 92.0%. Claims, stages, classifications, days, defects, and payments remain separate units.
Address the main payer-specific clean-claim status risk
Removing rejects and unknowns can inflate clean-claim performance. Treating every clearinghouse-forwarded claim as clean can also hide payer documentation requirements and delayed development.
Test the clean-claim evidence register against exceptions
Bella tests 999 acceptance, 277CA acceptance, payer control, missing attachment, records request, corrected claim, paper route, Medicaid definition, commercial contract, and unknown status. 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
Withhold the clean-claim label when the controlling source, qualifying event, required evidence, or claim version is unknown. Keep the claim in the reporting population with a visible unknown or excluded status and reason.
Hand off open work with evidence
Bella's handoff includes the source definition, effective date, claim cohort, qualifying event, known defect, classification, clock, and reviewer. The receiver reproduces the rate from the locked rows and documented exclusions.
Maintain Bella's control
Bella refreshes definitions after payer, contract, program, documentation, route, or legal changes. She reclassifies only affected claims and keeps prior metrics tied to the rule version that governed their period.
Verify Bella's release evidence
Bella's release review samples a claim labeled clean, one labeled nonclean, and every unknown. The reviewer confirms the controlling definition, qualifying event, development history, and claim version. Reporting shows the unknown cohort separately so missing evidence cannot improve the clean rate.
Run Bella's independent review
Bella assigns a reviewer who did not build the clean-claim evidence register. The reviewer reconstructs the payer-specific clean-claim status 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. Bella still records the actual payer, product, route, transaction version, receiver, and artifact before applying either source to the clean-claim evidence register.
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. Bella uses those facts only for the applicable Medicare route; other payers and contracts require their own evidence for payer-specific clean-claim status.
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. Bella 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. Bella stores these meanings in the clean-claim evidence register.
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. Bella 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. Bella 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. Bella verifies payer order, entity status, purpose, recipient, role-based access, and the narrow data needed for the payer-specific clean-claim status 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. Bella keeps clinical authorship, coding decisions, payer actions, disclosure authority, financial entries, and legal conclusions with their qualified owners throughout the clean-claim evidence register.
Related resources
- Separate ABA First-Pass Transmission, Adjudication, and Payment Yield.
- Reconcile ABA Allowed Amount, Contract Adjustment, and Payment.
- Investigate a Missing ABA Remittance After Adjudication.
- Govern an ABA CARC and RARC Action Matrix.
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.
