To preserve ABA claim evidence across EHR billing and payer systems, assign stable record and version identifiers and link each claim to its clinical, scheduling, authorization, provider, coding, transmission, acknowledgment, remittance, payment, and correction artifacts. Retain authorship, timestamps, source meaning, access, and custody. Use record-specific retention and legal rules. An export or screenshot should supplement, not silently replace, the authoritative record and audit trail.
Define Rhea's cross-system claim evidence custody control
Rhea builds an index rather than one giant copied file. The index points to authoritative artifacts, records their versions and access restrictions, and maintains a verified export path for systems that may become unavailable. It distinguishes evidence captured at the time from a later reconstruction.
Build the linked claim evidence index
Record evidence-index ID; person and claim; source system; artifact type; authoritative or derivative status; record ID; version or hash; author; service time; entry time; correction time; access class; legal or contract hold; retention rule owner; export format; custody transfer; linked authorization, payload, acknowledgment, remittance, EFT, and correspondence; missing artifact; recovery owner; and validation. Structured fields support versioning, comparison, clocks, holds, routing, measurement, and retesting. Narrative preserves clinical meaning, uncertainty, disagreement, family communication, access needs, legal deferral, and why the qualified owner selected the final path.
Run Rhea's workflow
Rhea maps every system that creates, receives, transforms, or stores claim evidence. She tests authorized retrieval for an ordinary claim, correction, appeal, audit, outage, and vendor exit. Derivative copies retain source links and timestamps. Deletion and retention settings are reviewed by qualified privacy, legal, records, payer, and clinical owners.
Keep authority with the responsible role
HHS explains that the HIPAA Privacy Rule does not set medical-record retention periods, although its protections apply while protected health information is maintained. Other federal, state, payer, contract, clinical, and litigation-hold rules may govern particular artifacts. HHS business-associate contract guidance describes contract and safeguard duties within covered-entity and business-associate relationships. The index does not make every copied record authoritative or create one retention period, and a BAA or vendor export does not by itself resolve each party's duties.
Work through Rhea's fictional example
Rhea locks 18 fictional claim evidence packages. Twelve link every required artifact with versions, authorship, access, retention owner, and tested retrieval. Two lack outbound payloads, one has a screenshot without source metadata, one lost a corrected note version, one cannot link ERA to EFT, and one depends on a departing vendor login. Four repair. Two remain on hold. This synthetic cohort tests control and arithmetic only. It creates no coding, coverage, authorization, claim, payment, employment, privacy, or legal conclusion for a real person, provider, payer, or service.
Calculate Rhea's measures
Initial package completeness is 12 of 18, or 66.7%. Sixteen packages reach verified retrieval or a documented preservation escalation, or 88.9%. Packages, artifacts, versions, users, claims, remittances, and deposits are counted separately.
Address the main cross-system claim evidence custody risk
Evidence scattered across systems can look complete until an appeal, audit, or vendor exit requires the original version. Bulk copying can also expand access and create conflicting records.
Test the linked claim evidence index against exceptions
Rhea tests late entry, corrected note, payer portal expiry, clearinghouse exit, remittance reissue, employee termination, legal hold, restricted record, outage export, and restored backup. Each test retains the starting evidence, source version, expected result, actual event, affected unit, immediate safeguard, owner, correction, retest, and final disposition. Failures stay in the predeclared cohort.
Document the stop condition
Stop release or destructive lifecycle action when a required artifact, version, author, custody link, access rule, or retention owner is unresolved. Use a restricted preservation hold while qualified owners decide the lawful and contractually supported path.
Hand the work off without losing evidence
A custody handoff identifies every transferred artifact, authoritative source, version or hash, access class, sender, receiver, transfer time, validation result, retention owner, and unresolved gap. The receiver confirms readable retrieval rather than accepting a file count. A failed export remains open with the source system protected from deletion.
Run Rhea's independent review
Rhea assigns a reviewer who did not create the linked claim evidence index. That reviewer reconstructs the cross-system claim evidence custody source, state, decision, correction, and metric from preserved evidence, then checks released and held cases across ordinary and exception paths. Earlier artifacts must remain available. An unexplained value, missing failed case, overwritten history, or owner without authority fails.
Anchor the rule hierarchy
Current 45 CFR 162.1102 and the CMS adopted-standards page anchor federal transaction status. Rhea records licensed implementation material, governing law, contract, plan, payer, and trading-partner sources separately for the cross-system claim evidence custody. A portal, edit message, or later publication receives only the authority its source and route support.
Keep paper and route-specific guidance scoped
CMS's professional-claim page supplies Medicare electronic and paper context. The NUCC Version 13.0 manual provides national paper-form instructions and defers to payer, clearinghouse, and vendor requirements. CMS says its Medicare FFS companion guides clarify and supplement the X12 TR3 rather than replace it and are authoritative only for Medicare FFS EDI protocols. Rhea preserves those boundaries in the linked claim evidence index.
Version edits instead of treating them as coverage
CMS limits Medicaid NCCI methodologies to specified Medicaid fee-for-service claims reimbursed using HCPCS or CPT codes. Its edit-files page publishes quarterly changes and states that an edit or MUE value does not establish state coverage. Rhea records program, quarter, state or payer additions, effective date, source, and actual review result.
Interpret acknowledgments by layer
The March 2026 CMS Medicare claim-status fact sheet illustrates 999 and 277CA edit stages for that Medicare route. X12 RFI 2099 says a 999 acceptance does not necessarily establish payer receipt date. Rhea preserves sender, receiver, unit, control number, timestamp, and business meaning before assigning the cross-system claim evidence custody state.
Separate correction, remittance, and money movement
X12 RFI 2060 explains the standard replacement or withdrawal path for a previously adjudicated claim and its payer claim control number, while payer routes can differ for pending claims. The CMS ERA and EFT page separates remittance information from the electronic transfer of funds. The linked claim evidence index keeps correction, reversal, adjustment, refund, patient balance, remittance, and deposit evidence distinct.
Use ABA coding commentary carefully
The ABA Coding Coalition FAQ is stakeholder guidance rather than the AMA, licensed CPT content, a payer policy, or law. Rhea uses it to frame questions, then verifies the current licensed code set and governing payer source. Public commentary never supplies missing service evidence or authority for a cross-system claim evidence custody decision.
Assign clinical and compliance ownership
The CASP public summary provides scoped autism-treatment context, and the BACB Ethics Code applies to covered behavior analysts while BACB has no separate organizational jurisdiction. The OIG General Compliance Program Guidance is voluntary and nonbinding. Rhea uses clear reporting, investigation, correction, auditing, and follow-up roles without claiming certification or legal safe harbor.
Related resources
- Build a Mature-Cohort ABA Claim Quality Audit.
- Audit Clearinghouse Mapping and ABA Claim Transformation.
- Trace Repeated ABA Claim Errors to Their Source.
- Separate ABA Claim Rejections, Denials, and Payment Adjustments.
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, Adopted Standards and Operating Rules.
- Centers for Medicare and Medicaid Services, Professional Paper Claim Form CMS-1500.
- National Uniform Claim Committee, 1500 Claim Form Reference Instruction Manual Version 13.0.
- Centers for Medicare and Medicaid Services, Medicare Fee-for-Service Companion Guides.
- 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.
- X12, RFI 2060, Withdrawal or Void Claim and Response.
- Centers for Medicare and Medicaid Services, Health Care Payment and Remittance Advice and Electronic Funds Transfer.
- ABA Coding Coalition, Frequently Asked Questions.
- U.S. Department of Health and Human Services Office of Inspector General, General Compliance Program Guidance.
- U.S. Department of Health and Human Services, Does HIPAA Require Covered Entities to Keep Medical Records for Any Period?.
- U.S. Department of Health and Human Services, Business Associate Contracts.
