To review ABA outcomes and treatment integrity together, treat them as related but separate measures. Outcome data describe the person's response. Integrity data describe how closely the plan was implemented under a defined measure. Align both by session or opportunity, preserve their different units and denominators, and inspect component errors. High integrity cannot prove efficacy, while low or missing integrity can make an unchanged outcome harder to interpret.

Define both measures

State the outcome unit and the integrity protocol, steps, opportunities, scoring, observer, and denominator independently.

Align by time and context

Match service date, session, partner, setting, activity, and relevant opportunity rather than comparing unrelated phase averages.

Show paired coverage

Report outcome sessions with matched integrity evidence divided by outcome sessions due for the defined review.

Inspect components

Keep critical steps and error types visible because one global integrity percentage may hide the component that matters.

Limit the conclusion

Use the paired pattern to guide investigation and design, not as automatic proof that fidelity caused the outcome.

Build Priya's outcome-integrity paired review

For the review ABA outcomes and treatment integrity together question, create a versioned outcome-integrity paired review. Preserve the target, client priority, operational definition, observation state, service and entry times, author, numerator, denominator, missingness, graph, integrity protocol, component data, context, access, decision rule, qualified owner, snapshot, correction, implementation, and follow-up. Another reviewer should be able to reconstruct Priya's evidence and decision without guessing which values were available.

Work through Priya's data example

Priya has eight outcome sessions. Fidelity was directly observed in six. Four paired sessions show high fidelity and higher participation; two show lower fidelity and lower participation. The remaining two outcomes have no fidelity observation. The pattern is useful for investigation, yet six paired sessions cannot establish that fidelity caused the outcome difference. Show every count, denominator, state, and date before summaries. This fictional community participation study example illustrates one workflow and does not establish a universal maturity threshold, fidelity target, review frequency, plan change, or treatment recommendation.

Audit Priya's evidence trail

Priya's review lists all eight outcome sessions, six fidelity observations, matched dates, opportunity counts, protocol components, context, observer, and missing reasons. It reports paired coverage as 6 of 8, or 75%, and preserves the two outcome-only sessions. The audit also checks definition and protocol versions, source-record access, correction history, graph axes, session spacing, invalid states, observer evidence, calculation precision, review permissions, and downstream dependencies. Unresolved discrepancies remain visible and hold the exact decision they affect.

Address Priya's main data risk

A phase-average fidelity bar can hide session-level correspondence and critical component errors. Priya's table keeps time and components visible before any summary graph. A metric or alert can surface a concern. Qualified reviewers interpret measurement, outcome, integrity, client experience, context, and risk together. One score cannot establish treatment fit, clinical importance, causation, authorization, or completion.

Choose Priya's next action

The clinician may strengthen implementation support, collect strategically sampled integrity data, reassess the plan, or maintain the current approach with a review date. Client experience and burden remain central. Record the action, rationale, owner, due date, support, and review trigger. Keep preliminary evidence, finalized evidence, treatment integrity, outcome, client input, and clinical decisions as separate states so one cannot silently substitute for another.

Protect Priya's access and participation

Keep Priya's AAC, interpreters, mobility, food, water, bathroom use, prescribed care, health support, rest, relationships, and emergency help available. Use accessible consent and assent processes when applicable and respond to withdrawal, dissent, or distress. Data collection, fidelity observation, or review timing never authorizes staff to delay urgent care or remove ordinary supports.

Apply current sources to Priya's review

Priya's source set includes research on graphing the intersection of fidelity and rate and on treatment-integrity implications for outcome interpretation. The BACB ethics hub and CASP public summary provide professional context, while the BCBA Test Content Outline identifies examination content on measurement, integrity, and data-based decisions. The WWC handbook supplies research-design context. Research on graphing fidelity with rate, integrity reporting, and integrity effects shows why implementation evidence matters. A single-case design review and evidence-based ABA framework describe analysis and decision context. ASHA supports continuous AAC access.

Rehearse Priya's workflow

Test the outcome-integrity paired review with fictional preliminary records, a late correction, a missing denominator, no integrity opportunity, measured zero fidelity, high fidelity with low use, a critical component miss, an overdue review, and a no-change decision. Confirm that states, due cohorts, calculations, snapshots, permissions, alerts, and qualified routes behave as intended. Store expected results, software version, reviewer notes, and corrections before live use.

Close Priya's data review

Review the outcome-integrity paired review with Priya, the responsible clinician, and specialists required by the question. Preserve source data, versions, graphs, maturity status, integrity coverage, components, client input, access and safety evidence, decision, implementation, corrections, and later outcomes. Keep the page draft and noindex until every manifest-named review is complete.

Related resources

Sources