To preserve ABA timely filing evidence across claim actions, record the controlling payer, product, contract or program source, service date, action type, start event, deadline, and exception rule. Link every original claim, rejected submission, corrected claim, replacement, reconsideration, and appeal to transmission and receipt evidence. Treat each clock separately and avoid assuming that a later correction or payer conversation resets an earlier deadline.
Define Harper's timely-filing evidence preservation control
Harper's register contains multiple clocks for one claim episode. It distinguishes original claim filing, correction, records response, reconsideration, appeal, refund, and payer-response deadlines. Each date has a source, timezone, calculation rule, evidence, owner, and escalation threshold.
Build the multi-action filing clock register
Record payer and product; contract or program source; effective date; service date; claim and version; action type; start event; calendar or business-day rule; deadline; receipt requirement; submission artifact; clearinghouse and payer receipt; payer control; rejection; correction; appeal; exception and proof; contact reference; extension; owner; warning date; outcome; and retained source. 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 Harper's workflow
Harper verifies the governing source before calculating the clock, records both transmitted and received evidence, and links later actions without replacing earlier dates. Near-deadline items escalate to the appropriate payer, contract, or legal owner. Unknown clocks remain visible and receive urgent source research.
Assign decisions to qualified owners
A clearinghouse timestamp can prove transmission to that receiver and may not prove payer receipt. A payer phone call may clarify a route without extending a deadline. Legal, contract, and program rules decide whether an exception applies.
Work through Harper's fictional example
Harper locks 20 fictional claim episodes. Thirteen have complete sources, start events, calculations, submissions, receipts, payer controls, exception evidence, and owners. Two use the wrong product rule, one counts business days incorrectly, one lacks payer receipt, one assumes a call reset the clock, one has a retro-eligibility exception, and one misses an appeal date. Five repair. Two remain urgent. 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 Harper's measures
Initial clock readiness is 13 of 20 episodes, or 65.0%. Eighteen reach verified clock or documented urgent escalation, or 90.0%. Episodes, claims, actions, dates, receipts, exceptions, and deadlines remain separate units.
Address the main timely-filing evidence preservation risk
Resetting age after a corrected claim can hide the original elapsed time. Treating a vendor acceptance as payer receipt can leave the practice without the evidence needed for an exception or dispute.
Test the multi-action filing clock register against exceptions
Harper tests original claim, front-end rejection, corrected claim, replacement, appeal, records request, retro eligibility, system outage, weekend, product change, and written extension. 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
Escalate immediately when a controlling source, start event, receipt, or deadline is unknown and time remains material. Preserve all transmissions and communications while the route is resolved.
Hand off open work with evidence
Harper's handoff includes every clock, source version, calculation, evidence, warning date, owner, exception, and unresolved assumption. The receiver independently recalculates the nearest deadline.
Maintain Harper's control
Harper refreshes filing rules after payer, product, contract, program, portal, or legal changes. Closed episodes retain the rule version and evidence that governed their action.
Verify Harper's release evidence
Harper's predeadline review checks every open action due within the escalation window, including items waiting on clinical, enrollment, payer, or legal input. A hold preserves the deadline and names the activity still allowed, the evidence needed, and the person accountable for escalation.
Run Harper's independent review
Harper assigns a reviewer who did not build the multi-action filing clock register. The reviewer reconstructs the timely-filing evidence preservation 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. Harper still records the actual payer, product, route, transaction version, receiver, and artifact before applying either source to the multi-action filing clock 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. Harper uses those facts only for the applicable Medicare route; other payers and contracts require their own evidence for timely-filing evidence preservation.
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. Harper 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. Harper stores these meanings in the multi-action filing clock 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. Harper 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. Harper 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. Harper verifies payer order, entity status, purpose, recipient, role-based access, and the narrow data needed for the timely-filing evidence preservation 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. Harper keeps clinical authorship, coding decisions, payer actions, disclosure authority, financial entries, and legal conclusions with their qualified owners throughout the multi-action filing clock register.
Related resources
- Track Payer Claim Control Numbers Across ABA Claim Versions.
- Link Payer Document Requests to the Exact ABA Claim and Deadline.
- Govern an ABA CARC and RARC Action Matrix.
- Prevent Duplicate ABA Claims During Ambiguous Payer Responses.
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.