Compare Treatment Integrity Across Procedure Versions

To compare treatment integrity across procedure versions, map shared, removed, added, and redefined components. Preserve effective dates, implementer exposure, eligible opportunities, training, adaptations, outcomes, and client experience for each version. Calculate version-specific integrity before comparing shared components. A higher score for a shorter or clearer version may reflect design improvement, changed conditions, or both.

Build a version crosswalk

List unchanged, revised, added, removed, conditional, and critical components. Record the rationale and effective date for every change.

Map accepted client responses, partner actions, prompt rules, access supports, stop conditions, and measurement changes as well as procedural steps. Link each version to its qualified approval, intended settings, and distribution record. A renamed or combined component may carry the same mechanism, while a small wording change can alter what is due. Preserve those distinctions before calculating fidelity.

Add a content fingerprint or stable identifier and retain the source documents used for the crosswalk. Have a qualified reviewer confirm clinical equivalence rather than relying only on text similarity. Note why components changed, what problem the revision intended to solve, and what new risk or burden it might introduce. This frames the later comparison as a decision test.

Keep version denominators separate

Calculate correct components over components due under each version. Avoid treating fewer required steps as automatic improvement.

Report raw components due and correct, eligible opportunities, sessions, settings, and agreement coverage for each version. Compare unchanged components directly only when their definitions and opportunities remain compatible. Treat added, removed, and conditional steps separately. A higher percentage after simplification may reflect a smaller denominator, not stronger implementation of the shared clinical mechanism.

Show a shared-component rate beside each full-version rate when that comparison is valid. Keep optional and conditional steps out of the denominator when they were not due, and document the rule. If observers used different definitions across periods, qualify the comparison or rescore only when raw evidence and a transparent secondary-analysis method support it.

Account for rollout

Track who received the new version, training date, first use, observation coverage, and mixed-version sessions. A transition period needs its own state.

Inventory portal, mobile, printed, cached, and offline copies and identify which one was available in each observed session. Do not score a person against content they had not received or been prepared to use. Preserve inadvertent old-version exposure and route client-impact review separately. Hold uncertain sessions from version comparison without deleting them from the audit cohort.

Compare integrity beside outcomes

Review Priya's experience, access, effort, outcome, adverse effects, and maintenance. Select a version for fit and benefit, not score alone.

Align the evidence by version exposure and mature observation dates. Ask the client about usefulness, burden, communication, and desired change through accessible methods. Stronger integrity with poorer outcomes may indicate plan mismatch, while lower integrity with acceptable outcomes can raise questions about unnecessary components or measurement. Qualified clinical review should interpret the full pattern and alternatives.

Put the procedure-version comparison into practice

Priya's six-step routine becomes a four-step routine after client and staff review. The analysis scores each version with its own denominator, compares two shared critical components, and records training and exposure dates. Priya's direct feedback and vocational outcome determine whether the clearer version is also a better fit.

Keep supervision, quality, and employment roles separate for Priya

Priya's procedure-version integrity comparison identifies the clinical decision owner, observer, supervisor, quality reviewer, operations owner, privacy contact, and employment owner. State which process is active, what notice and evidence it uses, who may decide, and where the record belongs. One integrity observation should not silently change purpose after collection.

Protect client access during Priya's review

Priya's process keeps AAC, interpreters, mobility, food, water, bathroom use, prescribed care, health support, rest, relationships, and emergency help available. Obtain required consent and assent when applicable and follow the governing response to withdrawal or distress. Client protection can require immediate action while broader measurement and personnel conclusions remain pending.

Use raw evidence and matched denominators for Priya

Report Priya's correctly implemented components divided by eligible components due, observations completed divided by observations due, agreement pairs divided by pairs due, and repairs verified divided by repairs due. Keep procedure versions, critical steps, exposure, client outcomes, direct experience, access, missingness, adaptations, drift, burden, and adverse effects in separate series.

Ask six supervision and review questions for Priya

Use these questions in the procedure-version integrity comparison:

Which client decision, procedure version, component, and eligible opportunity apply?
Which people, settings, risks, supports, observation modes, and sample limits matter?
Which integrity, agreement, exposure, outcome, experience, access, and adverse-effect series stay separate?
Which skill, clarity, resource, workflow, safety, burden, supervision, or plan-fit barrier is supported?
Which clinical, quality, operations, privacy, employment, certification, or payer owner may act?
Which repair, stop rule, follow-up evidence, and review date close the loop?

Keep unresolved evidence visible with a state, owner, age, and next action.

A fictional supervision example for Priya

Priya is fictional and involved in a vocational request routine revised from six steps to four. Reviewers freeze 35 version, shared-component, changed-component, date, exposure, opportunity, integrity, outcome, experience, and comparison fields and complete 25 of 35 by the checkpoint. Missing, unobservable, inapplicable, adapted, drifted, disputed, failed, and pending fields keep their defined states.

The procedure-version integrity comparison measures evidence completeness. It does not establish effectiveness, safety, acceptability, competence, employment performance, certification compliance, medical necessity, authorization, payment, generalization, maintenance, or causation.

Use current sources within their scope for Priya

For Priya's procedure-version integrity comparison, the CASP public summary supplies high-level individualized assessment, implementation, and evaluation scope for ABA treatment of autistic people. The BACB Ethics Code addresses competence, client involvement, consent and assent when applicable, supervision, risk, documentation, and evaluation for covered behavior analysts. The BACB supervision page routes readers to role-specific supervision and training resources; those requirements do not replace licensure, payer, employment, or case authority.

For Priya, the BCBA Test Content Outline addresses procedural fidelity as examination content; case protocols require qualified case-specific authority. The Ferguson practitioner guide supports observable components and eligible opportunities. The Essig, Rotta, and Poling review supports caution in fidelity-report interpretation. ASHA says AAC users should always have access to their tools or devices. Set coaching triggers, comparison rules, and performance thresholds from the current case and setting.

Close Priya's review

Ask Priya, the implementer, and the responsible clinician to review the procedure-version integrity comparison through accessible communication. Record the evidence, perspectives, limitations, selected repair, responsible system, clinical decision, follow-up observation, client outcome and experience, and review date. Reopen the analysis when the procedure, client priority, access, health, setting, implementer, supervisor, risk, or outcome changes.

How to Compare Treatment Integrity Across Procedure Versions