To prepare ABA records for a payer post-payment audit, match the request to the payer, product, contract, claims, services, dates, providers, locations, authorizations, and payment history. Collect preserved clinical sources and coding evidence, then document scope decisions, secure production, delivery proof, questions, findings, response or appeal rights, corrections, voids, refunds, and closure. Never change a clinical record to make it match a submitted claim.

Define Hugo's payer post-payment audit production record

Hugo builds one claim-to-source trace for each sampled claim. He distinguishes the record as it existed for care, later permitted corrections, the claim sent, the remittance received, and the audit response. The record links the exact request, authority, scope, deadline, sources, approved disclosure or access route, production or response, downstream effect, and evidence required before closure.

Build Hugo's page-specific fields

Hugo records payer and product, contract and audit clause, request and deadline, claim and line identifiers, service and submission dates, billing and rendering identities, site, authorization, plan version, signed or otherwise completed clinical record, data and schedule evidence, code source, original claim, correction history, remittance, adjustment, other audit, collection owner, privacy route, package index, delivery, finding, dispute, appeal, refund or recoupment, and final reconciliation.

Verify scope before collecting or releasing records

Hugo confirms the sender through a trusted route, identifies the legal entity and product, preserves the request as received, and resolves unclear identifiers or periods. Collection remains scoped to responsive sources. Release requires the named privacy, contract, regulator, payer, security, and legal checks. Immediate client safety, emergency, or mandatory actions follow their own authorized routes.

Preserve source records and correction history

Hugo protects original records, authorship, dates, audit trails, claim versions, delivery artifacts, and later permitted corrections. A production copy can be organized, indexed, rendered, and redacted without silently changing the source. Any late entry, amendment, correction, claim replacement, void, refund, or explanatory response identifies its author, time, reason, authority, and relationship to the earlier evidence.

Keep decision owners separate

Hugo routes case-specific clinical questions to qualified clinicians, coding and claim questions to authorized reviewers, privacy and security decisions to those owners, refund and financial work to responsible roles, and legal authority, privilege, withholding, appeal, or hearing questions to counsel when required. An operations coordinator can track work without making every decision.

Create a complete item and exception log

Hugo assigns a stable identifier to each request, cohort, responsive item, production version, exception, supplemental submission, finding, and downstream action. The log explains duplicates, exclusions, missing sources, destroyed records under an authorized schedule, unavailable people, system failures, disputed items, and open questions. It never invents a document to make the package appear complete.

Work through Hugo's fictional example

Hugo reviews 16 paid-claim episodes. Eleven trace cleanly from service evidence through remittance and audit package. One uses the wrong plan version, one lacks a location source, one mixes corrected and original claims, one omits an offset, and one contains an unsupported narrative added after the request. Four repair. The added narrative remains excluded and escalated. The scenario is synthetic. It tests request, source, privacy, production, finding, and denominator logic without establishing legal authority, valid privilege, payer approval, clinical quality, employee conduct, accreditation, licensure, audit success, or payment.

Calculate Hugo's measures honestly

Initial trace completeness is 11 of 16, or 68.8%. Fifteen episodes validate, or 93.8%. Claims, lines, services, notes, payments, adjustments, findings, and refunds are reported independently.

Address Hugo's main program risk

A post-payment review can become a reconstruction exercise. Hugo permits accurate, attributed corrections under the governing record policy and preserves what the payer actually received at each stage.

Test Hugo's record against hard cases

Hugo tests paid clean claim, replacement, void, partial payment, bundled request, wrong provider, missing authorization, amended note, duplicate audit, offset, refund, and appeal. Each case states the source, decision owner, responsive cohort, client safeguard, privacy route, hold, correction or response, delivery evidence, downstream reconciliation, and closure rule.

Close Hugo's review with unresolved work visible

Hugo confirms request verification, authority, scope, clock, preservation, source trace, privacy and legal review, redaction or withholding, production integrity, recipient, delivery, findings, disputes, corrections, claims, refunds, client effects, validation, recurrence, and open work. The payer post-payment audit production record remains draft until every named reviewer completes the required review.

Place Hugo's review record within organizational scope

Hugo uses the CASP Organizational Guidelines public overview for high-level business, clinical-operations, and risk-management context. The CASP ABA Practice Guidelines public summary concerns ABA behavioral health treatment for people diagnosed with autism. CASP sells the detailed guidance. Neither public page grants an auditor access, defines this payer post-payment audit production record, or replaces governing law, contract, payer, regulator, or accreditation sources.

Preserve professional accountability for Hugo

The BACB Ethics Code applies to covered people and addresses competence, responsibility, confidentiality, documentation, billing and reporting, supervision, risk, evaluation, correction, and cooperation with investigations. BACB has no separate organization or corporation jurisdiction. Hugo keeps organizational, clinical, payer, privacy, employment, and legal decisions with their authorized owners.

Use compliance guidance within Hugo's limits

The OIG General Compliance Program Guidance is voluntary and nonbinding. It discusses auditing, reporting, investigation, corrective action, overpayments, nonretaliation, and program oversight. Hugo uses it as a compliance design reference. It does not establish the authority, scope, deadline, refund obligation, or appeal route for responding to a payer review after payment.

Classify payment, operations, and oversight routes for Hugo

HHS treatment, payment, and health care operations guidance includes medical-necessity, coverage, utilization-review, auditing, fraud-and-abuse, accreditation, certification, licensing, and credentialing activities within defined payment or operations categories. 45 CFR 164.512 separately permits certain disclosures to health oversight agencies for activities authorized by law. Hugo verifies the actual entity, purpose, conditions, and other applicable law instead of treating every external review as the same HIPAA route.

Apply minimum necessary to Hugo's actual route

HHS minimum-necessary guidance explains role-based access, routine protocols, individual review for nonroutine disclosures, reasonable reliance in specified circumstances, and justification when an entire record is necessary. The treatment-provider disclosure exception is specific and does not cover every audit. Hugo records why each item is responsive and limits workforce access and production to the approved purpose when the standard applies.

Protect Hugo's electronic production

45 CFR 164.312 includes access control, audit controls, integrity, authentication, and transmission-security specifications for electronic protected health information. It does not prescribe a universal portal, encryption product, hash, package format, or chain-of-custody form. Hugo selects reasonable safeguards through the regulated entity's risk analysis, policies, agreements, recipient route, and facts.

Keep CMS examples route-specific for Hugo

For Hugo's Medicare example, the CMS ADR page says medical review collects records and related information to test Medicare coverage, coding, billing, payment, and medical-necessity requirements. The CMS maintenance and access fact sheet gives current Medicare record-access examples. A commercial payer's post-payment rights, deadline, production route, and response options still come from that payer's current contract and sources.

Related resources

Sources