Separate ABA First-Pass Transmission, Adjudication, and Payment Yield

Define Caleb's stage-specific first-pass yield control

Caleb's specification names the event that enters and exits every funnel stage. It prevents a 999 transaction-set result from becoming a claim-level acceptance rate and keeps paid claims from standing in for the original worklist. Corrections and appeals form linked later cohorts.

Build the claim funnel measurement specification

Record reporting period; original worklist rule; claim and version; local validation; transmission; clearinghouse claim result; 999 due and received; 277CA due and received; payer receipt; adjudication; resubmission; denial; zero-payment state; payment; maturity date; exclusion and reason; numerator; denominator; owner; source; and reconciliation. 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 Caleb's workflow

Caleb locks the worklist, follows each claim through the defined stages, and waits for the stage-specific maturity window. He reconciles prior-stage counts to next-stage outcomes and keeps every claim visible. Ratios are calculated only from units supported by the named artifact.

Assign decisions to qualified owners

A higher early-stage yield can coexist with poor adjudication or payment performance. Payment yield mixes coverage, contract, coding, payer, and timing factors unless segmented carefully. These process measures do not establish clinical quality or cause.

Work through Caleb's fictional example

Caleb locks 40 fictional original claims. Thirty-six pass local release, 34 are forwarded, 32 receive payer claim acknowledgment, 27 reach adjudication without resubmission, and 23 receive payment by the defined maturity date. Four local holds, two clearinghouse rejects, two payer rejects, and five later corrections explain the stage reductions. Four first-pass denials explain the remaining gap between 27 adjudicated claims and 23 payments. Every outcome stays visible. 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 Caleb's measures

Local release is 36 of 40, or 90.0%. Forwarding is 34 of 36, or 94.4%. Payer acknowledgment is 32 of 34, or 94.1%. First-pass adjudication is 27 of 32, or 84.4%. Mature payment yield is 23 of 27 adjudicated claims, or 85.2%. Each ratio retains its own denominator.

Address the main stage-specific first-pass yield risk

Dividing paid claims by only adjudicated claims can hide local holds and front-end rejects. Combining transaction, claim, and payment artifacts in one percentage creates a number that cannot guide a specific repair.

Test the claim funnel measurement specification against exceptions

Caleb tests local hold, batch 999 reject, proprietary clearinghouse report, 277CA reject, corrected claim, denial, zero payment, partial payment, maturity cutoff, and missing artifact. 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

Do not publish a yield when the entry rule, unit, artifact, clock, or denominator cannot be reproduced. Label immature claims separately and preserve them for the next measurement window.

Hand off open work with evidence

Caleb's handoff includes cohort rules, stage definitions, source artifacts, counts, arithmetic, maturity windows, exclusions, and unmatched claims. The receiver recalculates every rate from the locked inventory.

Maintain Caleb's control

Caleb reviews funnel definitions after clearinghouse, payer, contract, software, or workflow changes. Trend comparisons retain the same stage and rule version or clearly mark the break in series.

Verify Caleb's release evidence

Caleb reconciles every stage as opening units minus explicit outcomes and unresolved units. This control catches claims that disappear between reports and confirms that corrections, appeals, and payments stay linked to the original cohort without changing its denominator.

Run Caleb's independent review

Caleb assigns a reviewer who did not build the claim funnel measurement specification. The reviewer reconstructs the stage-specific first-pass yield 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. Caleb still records the actual payer, product, route, transaction version, receiver, and artifact before applying either source to the claim funnel measurement specification.

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. Caleb uses those facts only for the applicable Medicare route; other payers and contracts require their own evidence for stage-specific first-pass yield.

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. Caleb 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. Caleb stores these meanings in the claim funnel measurement specification.

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. Caleb 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. Caleb 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. Caleb verifies payer order, entity status, purpose, recipient, role-based access, and the narrow data needed for the stage-specific first-pass yield 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. Caleb keeps clinical authorship, coding decisions, payer actions, disclosure authority, financial entries, and legal conclusions with their qualified owners throughout the claim funnel measurement specification.

Related resources

• Investigate a Missing ABA Remittance After Adjudication.
• Validate Payer-Specific Clean-Claim Status for ABA Reporting.
• Reconcile Corrected ABA Claim Versions to Payer Status.
• Reconcile ABA Allowed Amount, Contract Adjustment, and Payment.

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.