To build an ABA claim source-to-field map, list every required claim value, its authoritative source, accountable owner, effective date, transformation rule, validation, and correction path. Separate clinical facts, provider identity, payer configuration, authorization, coding decisions, and transmission fields. A copied value is not evidence. Hold the claim when sources conflict, and preserve the final value plus the evidence used to select it.
Define Asha's source-to-field mapping control
Asha treats each claim field as a sourced assertion. The map shows where the value originated, whether a person interpreted it, which software transformed it, and what later artifact confirmed or rejected it. This makes a blank, stale, or conflicting value visible before a claim leaves the practice.
Build the claim data-lineage register
Record claim and service-line field; paper-form item or electronic loop, segment, and element when licensed instructions permit; business meaning; source system and record; source owner; clinical author where applicable; date of service; effective period; transformation; required format; validation; payer or route variant; exception owner; hold reason; approved value; correction history; transmission artifact; and final disposition. Use structured fields for comparison, clocks, source versions, holds, routing, and measurement. Keep narrative for clinical reasoning, uncertainty, disagreement, correction context, accessibility, family communication, and the qualified reviewer's explanation.
Run Asha's workflow
Asha begins with the actual professional-claim output, traces every populated field backward, and flags any value sourced from memory, a copied prior claim, or an unlabeled default. Clinical facts return to the completed clinical record. Provider roles return to enrollment, contract, roster, license, and service evidence. Payer-specific fields return to the current companion guide or written instruction. She tests the map with one ordinary claim and several exceptions before release.
Keep authority with the right role
The map records evidence and decision ownership. It does not grant clinical, coding, payer, or legal authority. A clinician controls permitted clinical corrections. A qualified coding reviewer interprets the current coding sources. Operations may verify identity and routing evidence without rewriting either clinical facts or code meaning.
Work through Asha's fictional example
Asha locks 18 fictional claim configurations. Thirteen trace every required field to a current source and validation rule. Two contain a copied authorization number, one uses a prior service location, one lacks a rendering-provider effective date, and one cannot explain a modifier default. Three repair. Two remain held. This synthetic cohort tests workflow and arithmetic only. It supplies no coding, coverage, authorization, licensure, claim, payment, or legal conclusion for a real person, provider, plan, or service.
Calculate Asha's measures
Initial lineage completeness is 13 of 18, or 72.2%. Sixteen configurations reach release or a documented final hold, or 88.9%. A configuration is one payer, product, provider role, service, location, and date span. Claims, service lines, fields, source records, and corrections retain different denominators.
Address the main source-to-field mapping risk
A technically valid value can still be wrong for the person, provider, service, or date. Silent defaults are especially risky because repeated acceptance may look like proof even when the receiving payer has not evaluated the underlying fact.
Test the claim data-lineage register against exceptions
Asha tests copied prior claim, source changed mid-day, two active coverage records, stale roster, multiple service locations, missing diagnosis source, modifier default, authorization split, corrected note, and clearinghouse reformatting. Each test records the starting evidence, expected rule, actual event, affected unit, immediate hold, qualified owner, correction, retest, and disposition. Records stay in the predeclared cohort when they fail.
Run an independent acceptance test
An independent reviewer selects five populated fields from two claims and walks each one back to authoritative evidence without asking the preparer. The reviewer also reproduces the transformation and identifies who could approve a correction. An untraceable default, circular source, or overwritten value fails.
Document the stop condition
Stop release when a required field lacks an authoritative source, two current sources conflict, a transformation cannot be reproduced, or the identified owner lacks authority to resolve the difference. Record the hold at field and claim level so a later batch process cannot bypass it.
Maintain Asha's control
Asha versions the artifact, sources, transformations, rules, permissions, training, and acceptance tests. Changes trigger focused revalidation of affected configurations rather than silent global replacement. Open exceptions retain an owner, age, due date, safeguard, and escalation path.
Use the adopted professional-claim standard
Current 45 CFR 162.1102 identifies the adopted professional health-care claim standard. Asha uses the licensed implementation material and the actual trading-partner instructions for the source-to-field mapping. A later publication, vendor screen, or paper-form label does not replace the federally adopted version or the receiver's valid route rules.
Separate electronic and paper instructions
CMS's professional paper claim page explains the CMS-1500 and electronic filing in Medicare scope, while its essential-fields lesson illustrates key Medicare claim data. The NUCC Version 13.0 manual supplies current national paper-form instructions and directs users to payer, clearinghouse, or vendor guidance. Asha does not treat a paper item, Medicare example, or screen label as a universal 837P instruction.
Verify setting and provider identity
The CMS place-of-service code set says POS reports where professional services were rendered and directs users to individual payers for reimbursement policy. The CMS NPI fact sheet distinguishes individual and organizational identifiers and states that an NPI does not establish licensure, credentialing, enrollment, or payment. The claim data-lineage register preserves those boundaries before release.
Scope edit evidence to the actual program
CMS limits its Medicaid NCCI methodologies to specified Medicaid fee-for-service claims reimbursed using HCPCS or CPT codes. The public edit-files page says an edit or MUE value does not establish state coverage and posts quarterly changes. Asha records program, quarter, payer-specific additions, source version, and review outcome rather than applying one edit table to every source-to-field mapping case.
Read acknowledgments by their business meaning
The March 2026 CMS Medicare claim-status fact sheet distinguishes initial 999 and claim-level 277CA stages in that Medicare route. X12 RFI 2099 explains that a 999 acceptance does not necessarily establish the carrier receipt date and points to business-level evidence such as a payer-sent 277CA. Asha maps every response to its sender, unit, and stated meaning.
Use ABA coding commentary within scope
The ABA Coding Coalition FAQ offers stakeholder explanations about current adaptive-behavior coding. It is not the AMA, a licensed code set, a payer policy, or legal authority. Asha uses it to identify questions for the claim data-lineage register, then verifies the current licensed material and applicable payer source before a coding decision.
Preserve clinical authorship and compliance roles
The CASP public summary supplies scoped autism-treatment context. The BACB Ethics Code governs covered behavior analysts and addresses documentation and billing duties, while BACB states that it has no separate organizational jurisdiction. The OIG General Compliance Program Guidance is voluntary and nonbinding. Asha uses qualified role assignment, issue reporting, investigation, correction, auditing, and follow-up without claiming that the workflow guarantees compliance.
Related resources
- Reconcile Scheduled, Documented, and Billable ABA Time.
- Trace ABA Claims Through Clearinghouse and Payer Acknowledgments.
- Validate ABA Provider Roles Before Claim Release.
- Reconcile ABA Batch, Claim, and Service-Line Counts Before Transmission.
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, Professional Paper Claim Form CMS-1500.
- Centers for Medicare and Medicaid Services, Medicare Billing CMS-1500 and 837P essential claim fields.
- National Uniform Claim Committee, 1500 Claim Form Reference Instruction Manual Version 13.0.
- Centers for Medicare and Medicaid Services, Place of Service Code Set.
- Centers for Medicare and Medicaid Services, National Provider Identifier fact sheet.
- Centers for Medicare and Medicaid Services, Medicaid NCCI Methodologies.
- Centers for Medicare and Medicaid Services, Medicaid NCCI Edit Files.
- Centers for Medicare and Medicaid Services, Checking Medicare Claim Status, March 2026.
- X12, RFI 2099, 999 Confirming Claim Receipt.
- ABA Coding Coalition, Frequently Asked Questions.
- U.S. Department of Health and Human Services Office of Inspector General, General Compliance Program Guidance.
