To separate relapse from access, health, and system changes, review Farah's AAC, sensory, motor, visual, language, technology, materials, partners, schedule, pain, illness, sleep, medication, mobility, and other relevant changes before interpreting recurrence. Route repairs and clinical questions to qualified owners, preserve direct client report, classify invalid opportunities, and rebuild evidence after meaningful repair. A system failure should remain a system failure.

Ask Farah before interpreting recurrence

Use Farah's preferred communication to identify pain, fatigue, access loss, new effort, unwanted partner responses, and helpful repairs. Treat direct report as its own evidence source.

Audit access and system versions

Record device, software, page, vocabulary, backup, connectivity, materials, visual and motor access, language, partner availability, and update dates.

Route health questions promptly

Pain, illness, sleep, medication, vision, hearing, mobility, and other health changes require qualified health review. Immediate or urgent concerns follow the applicable safety route.

Rebuild evidence after repair

Create a repaired phase with restored access and documented health guidance. Avoid merging pre-failure, failure, and repair opportunities into one rate.

Use this sequence to separate relapse from access, health, and system changes

Ask Farah, version access, route health, classify invalid events, restore support, establish repaired evidence, and keep process claims bounded.

Build Farah's access-health-system differential review

Create one versioned access-health-system differential review for the community-classroom scheduling routine. Include Farah's priority, response classes, phases, contexts, treatment versions, reinforcement, exposure, integrity, access, health, recurrence timing, safety action, direct experience, invalidity, missingness, withdrawal, candidate process, alternative explanations, design limits, decision, qualified owner, correction, and reassessment trigger. Store only decision-relevant information with role-limited access.

Validate Farah's recurrence evidence

Reproduce Farah's 14/16 pre-update help, post-update 4/16 help, 7/16 leaving, five invalid page failures, and repaired 11/14 help with two invalid absences. Verify software, device, AAC, response effort, partners, schedule, health, medication, direct report, access repair, and phase dates. Keep invalid opportunities outside response-rate denominators and visible in coverage.

Connect Farah's evidence to a decision

Farah's record routes the loading failure to technology, eye strain and medication questions to the medical team, and response interpretation to the qualified clinician. These routes proceed in parallel. The team does not wait for a mechanism label before restoring communication access and ordinary support.

Work through Farah's example

Farah uses an AAC help message in 14/16 routine opportunities before a software update. After the update, help occurs in 4/16 and leaving the station in 7/16; five opportunities are invalid because the message page does not load. Farah reports eye strain and a new medication. After restoring the page and medical follow-up, help occurs in 11/14 opportunities, with two invalid absences. Preserve every planned and valid unit, response code, phase and context version, treatment component, reinforcement event, exposure, integrity result, access and health state, safety response, withdrawal, direct report, system failure, repair, correction, and unresolved item. This fictional example demonstrates one assessment control. It offers no diagnosis, person trait, universal relapse estimate, treatment effect, legal conclusion, coverage decision, payment promise, or outcome guarantee for Farah.

Address Farah's main interpretation risk

Calling 7/16 relapse assigns five software failures and potential health effects to Farah. The update also changes response effort and partner timing. A repaired phase can improve conditions without establishing which earlier variable caused the change. Review response and phase definitions, treatment history, reinforcement, exposure, context, integrity, access, health, partner behavior, direct experience, alternative explanations, authority, and design strength separately. A convincing graph cannot repair an unsafe, inaccessible, unwanted, or historically unsupported recurrence assessment.

Keep treatment scope and authority clear for Farah

For Farah's access-health-system differential review, the CASP public summary supplies high-level ABA behavioral-health-treatment scope for autistic people, with licensed detail outside this page. The current BACB Ethics Code addresses competence, client involvement, consent and assent when applicable, medical needs, risk, data, documentation, evaluation, discontinuation, and transition for covered people. The BACB outline supplies examination content. These sources create no individualized relapse protocol or practice authority for Farah.

Distinguish early increase from recurrence for Farah

The historical Lerman and Iwata analysis reviewed extinction data and found early increases under a defined burst criterion in a minority of reviewed data sets. An extinction burst describes a time-linked early increase after extinction begins, whereas Farah's later recurrence question requires its own phase history. The study offers no universal prevalence estimate for current care, no safety authorization, and no prediction for the community-classroom scheduling routine.

Use alternative-reinforcement and communication literature within scope for Farah

Athens and Vollmer evaluated differential reinforcement without extinction with seven children and varied dimensions such as immediacy, duration, and quality. The Tiger, Hanley, and Bruzek review discusses FCT assessment, response selection, partner response, schedule thinning, and related risks. These sources support careful history and delivery measurement for Farah; they supply no universal schedule, delay, consequence, or relapse outcome.

Use renewal evidence cautiously for Farah

The Podlesnik renewal review synthesizes basic and translational work on recurrence with context change while extinction or treatment contingencies remain. Much of that evidence comes from controlled laboratory arrangements. Understanding and Reacting to Relapse discusses practice-facing context and recurrence considerations. For Farah, define people, places, cues, treatment continuity, access, and integrity before applying renewal language.

Preserve broad relapse limits and communication access for Farah

Relapse and Its Mitigation distinguishes several recurrence histories and discusses mitigation concepts. It organizes hypotheses rather than proving which process occurred for Farah. ASHA's AAC portal says AAC users should always have access to communication tools or devices. Follow governing sources and preserve Farah's communication, health care, food, water, bathroom use, mobility, rest, relationships, safety, and emergency help throughout review.

Choose Farah's next bounded action

Farah chooses the restored message page plus a paper backup and asks the team to avoid screens during periods of eye strain. Record the qualified owner, source evidence, effective date, current phase and treatment version, ordinary supports, access and health state, implementation check, accessible explanation, disagreement route, and reassessment trigger. Preserve the earlier record when responses, people, settings, systems, schedules, health, or priorities change. A repaired arrangement creates a dated phase rather than an error in Farah's prior performance.

Close Farah's relapse review

Review the access-health-system differential review with Farah, the qualified behavior analyst, relevant partners, access owners, and specialists named in the manifest. Confirm that observed recurrence remains separate from resurgence, renewal, an extinction burst, treatment drift, access failure, health change, and treatment effect; every denominator is reproducible; AAC and basic access remain protected; urgent needs received action; and conclusions stay bounded to the supported history. Keep this page draft and noindex until every required review is complete.

Related resources

Sources