Skip to main navigation Skip to search Skip to main content

Retrospective consecutive controlled case series of outcomes for functional analyses of severe destructive behavior

  • Jessie K. Weber
  • , Katherine R. Brown
  • , Billie J. Retzlaff
  • , Alyssa M. Hurd
  • , Heather J. Anderson
  • , Kendra Smallwood

Research output: Contribution to journalArticlepeer-review

Abstract

Functional analysis methods allow clinicians to determine the variable(s) that maintain destructive behavior. Previous reviews of functional analysis outcomes have included large samples of published and unpublished data sets (i.e., clinical samples). The purpose of this review was to conduct a large retrospective consecutive controlled case series of clinical functional analyses. We sought to identify the prevalence of differentiation, procedural modifications for undifferentiated and differentiated cases, and identified function(s) of destructive behavior. In addition, we extended the existing literature by determining whether functional analysis differentiation and function varied when single or multiple behavior topographies were consequated in the functional analysis. We discuss our findings considering previously published functional analysis reviews, provide avenues for future research, and offer suggestions for clinical practice.

Original languageEnglish (US)
Pages (from-to)695-708
Number of pages14
JournalJournal of applied behavior analysis
Volume57
Issue number3
DOIs
StatePublished - Jul 1 2024
Externally publishedYes

Bibliographical note

Publisher Copyright:
© 2024 The Authors. Journal of Applied Behavior Analysis published by Wiley Periodicals LLC on behalf of Society for the Experimental Analysis of Behavior (SEAB).

Keywords

  • destructive behavior
  • functional analysis
  • retrospective consecutive controlled case series

Fingerprint

Dive into the research topics of 'Retrospective consecutive controlled case series of outcomes for functional analyses of severe destructive behavior'. Together they form a unique fingerprint.

Cite this