To reassess after a relapse like recurrence, address Imani's immediate safety and health needs, restore effective support, and preserve the original event record. Then verify response definitions, current treatment, integrity, context, reinforcement, access, health, direct experience, exposure, and candidate processes. Repair conditions and collect only evidence needed for the next decision. Recurrence calls for system review rather than blame.

Respond before explaining

Follow immediate safety, medical, crisis, protective, or emergency routes. Restore communication and previously effective supports as soon as authority and conditions allow.

Freeze the original event record

Preserve time, setting, people, cues, response, partner actions, consequences, health, access, treatment version, and corrections. Avoid rewriting the record after a hypothesis emerges.

Build one event-level differential

Join integrity, context, reinforcement, access, health, exposure, and client-report fields to each opportunity so overlapping conditions remain visible without double counting.

Repair and reassess prospectively

Create a dated repaired phase and collect only enough ordinary-use evidence for the next decision. Stop when the question is resolved or further burden lacks value.

Use this sequence to reassess after recurrence

Protect Imani, preserve the event, audit treatment and context, ask Imani, route repairs, test candidate explanations cautiously, and update the plan without blame.

Build Imani's relapse-like recurrence review

Create one versioned relapse-like recurrence review for the community recreation check-in routine. Include Imani'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 Imani's recurrence evidence

Reproduce Imani's 2/20 and 5/10 recurrence counts across 30 check-ins, plus 24/30 cue availability, 21/30 on-time response, two medication-change days, three crowded events, and four overlapping AAC backup failures. Verify event-level joins, treatment version, context, reinforcement, integrity, health, access, direct report, repairs, and follow-up.

Connect Imani's evidence to a decision

Imani's review assigns immediate actions before explanatory labels: restore AAC backup, replace missing cues, correct partner timing, route medication questions, and adjust crowding when feasible. The qualified clinician then decides whether the repaired record warrants a resurgence, renewal, or broader recurrence analysis. Each repair receives an owner and date.

Work through Imani's example

Imani has 30 recreation check-ins under the current plan. The prior target response occurs in two of the first 20 and five of the next ten. Review finds the current visual cue in 24/30, on-time partner response in 21/30, two medication-change days, three crowded events, and four AAC backup failures that overlap other categories. The pattern needs event-level analysis rather than one cause. 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 Imani.

Address Imani's main interpretation risk

Adding 24 + 21 + 2 + 3 + 4 as separate opportunity groups double-counts overlapping conditions. Calling the last 5/10 relapse also skips the response history and current treatment audit. Waiting for mechanism certainty can delay obvious access or integrity repairs. 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 Imani

For Imani's relapse-like recurrence 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 Imani.

Distinguish early increase from recurrence for Imani

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 Imani'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 recreation check-in routine.

Use alternative-reinforcement and communication literature within scope for Imani

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 Imani; they supply no universal schedule, delay, consequence, or relapse outcome.

Use renewal evidence cautiously for Imani

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 Imani, define people, places, cues, treatment continuity, access, and integrity before applying renewal language.

Preserve broad relapse limits and communication access for Imani

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

Choose Imani's next bounded action

Imani chooses a quieter check-in point and confirms the preferred backup message. The review retains each overlapping event condition in one opportunity-level record. 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 Imani's prior performance.

Close Imani's relapse review

Review the relapse-like recurrence review with Imani, 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