To audit evidence provenance in ABA treatment plans, lock a mature cohort and trace each material statement to its source, person, method, context, date, version, limitations, and clinical decision. Check direct client and proxy reports separately, preserve missing and conflicting evidence, and follow corrections through every consumer. Report fixed-denominator measures by statement and plan, age open gaps, and repair only affected records and controls.

Lock the audit cohort

Define mature plans, material-statement rule, period, settings, versions, evidence classes, required provenance fields, exclusions, corrections, and denominator before review.

Write a protocol that identifies the plan versions and data-complete cutoff. Define a material statement as one that can affect a goal, procedure, risk control, access support, referral, service decision, or representation to another party. Enumerate all qualifying statements before scoring them and keep the parent-plan relationship.

Create coding rules for evidence class, source identity, context, freshness, uncertainty, interpretation, decision link, client involvement, privacy route, and correction history. Pilot the rules and resolve reviewer differences. Preserve excluded statements with the reason.

Trace source identity

Check client, proxy, observer, clinician, record, instrument, assessment, implementation, health, payer, or other source with author and approved location.

Verify that every statement resolves to a stable source ID and controlled record. Distinguish the person who communicated or authored the evidence from the employee who entered it. Flag vague labels such as “team reports,” broken links, wrong-client records, and sources whose ownership cannot be verified.

Sample access permissions and purpose limitation for sensitive evidence. The audit need not expose the content to every reviewer; it should confirm through the approved process that the source exists, is attributable, and is available to authorized decision-makers.

Trace context and method

Verify dates, collection window, setting, opportunities, definitions, access, prompts, integrity, instrument version, missingness, uncertainty, and corrections.

Match context requirements to the evidence class. Direct observations need units, denominators, settings, support, and implementation conditions. Client and proxy reports need the question, response route, period, and authorship. Records and instruments need edition, author, effective date, and bounded use.

Check the actual source, not only the plan citation. Identify stale evidence presented as current, revised definitions merged across periods, unavailable opportunities omitted from denominators, and corrected values that never propagated.

Trace clinical use

Identify the interpretation and qualified author, decision supported, competing evidence, limitation, interim safeguard, client participation, plan version, and review trigger.

Follow the chain from evidence through interpretation to action. A source can be traceable yet used outside its scope. Verify that the qualified author states what the evidence supports, what remains uncertain, and why the decision follows. Check whether competing evidence and the client's direct response were preserved.

Record whether the decision reached implementation and whether a recheck trigger exists. A referral, hold, support change, or correction task that was never completed remains an open provenance-to-practice gap.

Test correction propagation

Sample source corrections and follow them through plan text, staff instructions, reports, payer packets, disclosures, dashboards, and later decisions.

Select corrections across severity, evidence class, and age. Start with the preserved original, then inspect the corrected source, affected statement, recipient map, notices, recalculations, clinical reassessment, and prevention control. Include failed deliveries and external artifacts where the organization has a route to verify them.

Measure propagation completeness using the fixed set of downstream uses. Do not call a correction complete because the current plan is accurate while staff or payer materials still carry the wrong claim.

Report and repair

Use fixed statement and plan denominators, preserve overlapping defects, age open gaps, assign owners, protect affected people, and verify targeted repair.

Report both defect-bearing statements and affected plans. One statement can lack source identity, date, and uncertainty, while one plan can contain several defective statements. Keep these overlapping counts separate and avoid summing them into a unique total.

Prioritize wrong-person attribution, safety or medical use, unauthorized disclosure, and decisions resting on unsupported claims through the responsible governance process. Every repair needs an owner, due date, interim protection, verification evidence, and retest. Share relevant findings with affected clients in an accessible and privacy-preserving way.

Build Zane's evidence-provenance audit

Use each material plan statement as Zane's audit unit and assign it to its parent plan. Score source and author, evidence class, context and collection period, as-of date and version, access conditions, uncertainty and limitations, interpretation, qualified decision link, client response, privacy route, and correction history. Preserve overlapping defects at the statement level and separately count affected plans. Stratifying by evidence class, plan section, author, and defect age can expose a consequential provenance gap hidden by a plan-level pass.

Work through Zane's example

Zane audits 30 material statements across ten mature plans. Twenty-seven have a source, 24 include context and period, 22 state limitations, and 20 link clearly to the decision they informed. The rates are 90%, 80%, 73.3%, and 66.7%, with corresponding gaps of 3, 6, 8, and 10 statements. A single statement can appear in several gap counts, and the number of affected plans cannot be derived from these totals. The results describe this audit cohort rather than a universal provenance score.

Address Zane's main provenance risk

A plan-level pass can hide one consequential unsupported statement. Zane keeps both statement-level results and the count of affected plans. A source can be accurate for one period or decision and unfit for another. Keep original evidence, interpretation, recommendation, consent, operational release, payer state, claim, and outcome as separate records.

Choose Zane's next evidence step

Owners protect clients affected by unsupported decisions, correct the specific sources and plan versions, and retest provenance on a new mature sample. Record the qualified owner, authority, person and scope affected, interim protection, evidence needed, access and privacy route, due date, correction method, recipients, closure state, and next review. Software may coordinate workflow while qualified people interpret evidence and decide within scope.

Apply professional evidence standards to Zane's record

For Zane's evidence record, the BACB ethics hub identifies the current Ethics Code, which addresses competence, client and stakeholder involvement, assessment, medical needs, documentation, confidentiality, risk, and data-based evaluation for covered people. BACB has no separate organizational jurisdiction. The BCBA outline is examination content, not practice authority. The CASP public summary supplies high-level planning context for ABA treatment of autistic people. An evidence-based ABA framework supports integrating research, clinical expertise, client values, and context.

Use integrity and access sources carefully for Zane

In Zane's case, the treatment-integrity practitioner guide, Essig review, impact study, and reporting review support explicit procedures, implementation evidence, observer quality, and cautious interpretation. They create no universal provenance threshold. ASHA supports continuous AAC access. For a HIPAA covered entity, HHS minimum-necessary guidance generally applies to uses, disclosures, and requests for protected health information, with rule-specific exceptions. It supports role-based information access rather than copying whole records into every plan field.

Close Zane's evidence review

Review the evidence-provenance audit with Zane, the responsible clinician, affected participants, and the specialists named in the manifest. Preserve direct client communication, source attribution, disagreements, versions, limitations, decisions, corrections, and open gaps. Keep this page draft and noindex until the required clinical, client or family, measurement, AAC, access, medical, records, privacy, ethics, research, and legal reviews are complete.

Related resources

Sources